Closing the books on a season (and why you never delete one)
The water’s done — what do you actually do in the software? Close the season: sign the year without sealing it away. A closed fall is next March’s answer key, which is why one can’t be deleted and shouldn’t want to be.
· 5 min read
The water’s done, the gear’s stacked, the last stragglers have paid or been politely reminded. One question left: what do you actually do with the season in the software? The answer is short — you close it — but what closing means, and what it emphatically doesn’t, is worth five minutes, because the operators who understand it stop treating past seasons as clutter and start treating them as the most valuable thing in the account.
A season in LakeOps is a bucket with a term and a year — Fall 2026 — and it moves through three states: upcoming when it’s created, open while the work lives in it, closed when the year is finished. Closing is the fall’s last piece of desk work, and the shortest.
What closing does
One thing: it stops the season being a live target. Nothing new can be generated into a year you’ve finished accounting for — no March mishap can drop fresh work into Fall 2026, and the season’s numbers stop moving. Closed is the software agreeing with reality: that year is over.
Everything else about a closed season works the way it did the day before you closed it. Reports still take its date range, the completed-work picture still exports, and every customer’s page still shows what that fall held. The only door that shuts is the one that would let new work leak into an accounted year.
What closing doesn’t do
Closing hides nothing. Every job, every price, every photo, every payment and every minute on the clock stays exactly where it is and stays reportable. A closed season isn’t an archive you hope never to open — it’s the finished, exportable picture of a year.
That distinction is why the close isn’t scary. You’re not sealing anything away. You’re signing the year.
When to close
Not the day the last boat comes out. Close when the work is genuinely done and you’ve collected what you’re going to collect — usually a few weeks after the last pull, once the season’s completed-work report has stopped changing. A good sequence for late November: sweep the balances oldest-first, run the end-of-season debrief while memory’s fresh, then close.
Why you can’t delete a season — and shouldn’t want to
A season with jobs in it can’t be deleted, and this is a feature wearing a restriction’s clothes. The season is what makes “what was this customer worth to us last fall” a question with an answer. Come March, that answer is everywhere: quoting a new customer from what similar shorelines actually took, deciding whether the customer asking for a discount is a six-year account or a chronic headache, showing a new crew member the photos of how that canopy stacks. Every one of those is a closed season doing work.
Shops that ran on whiteboards know the alternative: the year got erased in December, because the board was needed for next year. Every answer it held went with it.
Closing and rollover are different things
The two get mixed up constantly. Closing ends a season. Rollover is the yearly pass where you confirm each standing arrangement before generating the next season’s work — the “yes, again” walk through the customer list. They’re independent, and usefully so: you can build Spring 2027 in February while Fall 2026 is still open with two slow payers on it. Nobody has to finish last year to start next year.
What about work that turns up after the close?
Somebody will call in December — a snowplow found their shore station, a canopy came loose in a storm. A closed fall doesn’t get reopened for that, and doesn’t need to: a repair is a job of its own, created directly, with no seasonal arrangement behind it. It gets done, it gets billed the day it’s finished, and Fall 2026’s numbers stay exactly what you signed them as. The season is the record of the season; the odd job in the off-months stands on its own.
The rhythm, year over year
Late winter: create spring, walk the rollover, generate. Spring: work it, close jobs as they finish. Early summer: collect the last of it, close spring. Late summer: create fall, roll over again — fall arrangements are their own list, often covering different equipment. Late fall: collect, debrief, close. Two closes a year, each one a finished chapter, and after a few of them the account holds something no whiteboard ever did: the whole history of the business, by year, by customer, by shoreline — every season of history you put in it, yours.