Opening a season and generating the work
To create a season’s work, add the season (a term and a year), open its rollover screen, uncheck anyone who canceled, and generate — LakeOps creates exactly one job per active agreement for that term.
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. You can add start and end dates as a label for yourself; they do not gate anything.
The rollover screen
This is the useful part. It lists every active standing agreement matching the season’s term, each with:
- the customer and the property, with the lake and zone;
- how many items that agreement covers;
- when that work was last completed — or “first season” if it never has been.
Everything is ticked by default. Walk the list, untick the people who sold up or moved on, and write one reason in the box at the bottom. Unticking cancels the agreement, which stops the work generating this year and every year after — it is not a one-time skip.
Generating
Generate, and LakeOps creates exactly one job per remaining agreement, each with a line for every item on that agreement, all pending. The season flips to open.
Running it twice cannot create duplicates. The database itself refuses a second job for the same agreement 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 screen tells you how many already existed.
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, and it is deliberate: 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 agreement and generate the season again. Only the missing job is created.
- Somebody wants a repair or a one-off relocate — create a job directly, with no agreement 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.