Opening a season and generating the work
Last updated October 03, 2026
To create a season’s work, stop anyone who canceled on the service plans list, add the season (a term and a year), and press Generate the jobs — LakeOps creates exactly one job per service plan of that term that is rolling forward.
This is the one office ritual LakeOps asks you to perform, twice a year, and it replaces the spreadsheet most shops already keep for exactly this purpose.
Create the season
A season is a term and a year: Spring 2027, Fall 2027. Every job belongs to one, which is what makes “what did we do last fall” a question with an answer. Choose Seasons in the sidebar and press Start a season beside the tabs, pick the term and the year, and press Create season. You can add start and end dates as a label for yourself; they do not gate anything.
What the season offers you
Creating a season lands you on its Season details; to come back to it later, choose Seasons in the sidebar — it opens the running season lake by lake — and then Season details. It tells you two numbers: how many service plans of that term are rolling forward, and how many jobs are still waiting to be made. If anything is waiting, there is a button to make it. That is the whole screen.
It does not ask you to walk a list, because deciding who is on the books is not something you should only be able to do twice a year, in a hurry, on the screen that also charges you. That decision lives on the service plans list, where you can filter by lake, term or service, stop a whole group at once with a reason, and start them again if you were wrong. Do that first, then generate.
Generating never stops anybody. It only creates work. Stopping a customer is done on their service plan, deliberately, and it is reversible. There used to be a screen where an untidy click could cancel somebody for good; there is not any more, and that is the reason for the split. For the customer who is renovating this year and back the next, see skipping a season without canceling the plan.
Generating
Press Generate the jobs and LakeOps creates exactly one job per service plan that is rolling forward, each with a line for every item on that plan, all pending. Big books are generated in the background, so the page comes straight back and fills in as it goes.
Running it twice cannot create duplicates. The database itself refuses a second job for the same service plan in the same season. A double-click, a retry after a dropped connection, or reinstating a customer in March and generating again are all safe — the season tells you how many already exist, and the button disappears once nothing is waiting.
What you have afterwards
A backlog. Not a schedule — there is no route to build and nothing is assigned to anybody. Every job sits pending, visible on the map, and gets picked up when a boat with the right gear reaches that shoreline. That is how dispatch works here: a route built in March is fiction by May.
Adding work after you have generated
Two ways, and they are both normal:
- New customer signs up in April — create their service plan and the season will offer to generate again. Only the missing job is created. From the plan’s own page there is also a one-click catch-up for exactly this.
- Somebody wants a repair or a one-off relocate — create a job directly, with no service plan and no season behind it. See what a job is.
A closed season is the one thing you cannot generate into. Closing is the statement that the year is finished; reopening it silently would rewrite an accounting record.
Still stuck? Ask us — or go back to the help center.