Dock install scheduling: why the March plan is gone by the second week of May
Ice-out moves three weeks year to year, a north wind closes a shoreline with no notice, and half your customers call the week they arrive. Here’s the way of running install season that survives all three.
· 7 min read · updated August 19, 2026
Ask a dock company when install season starts and you’ll get a range, not a date. Ice-out on a big northern lake moves three weeks year to year. In a late spring the whole book compresses into five weeks. In an early one you’re on the water before your seasonal hands have quit their winter jobs.
Then the weather does it again every morning. A north wind closes the exposed shorelines and opens the protected ones. A boat pushed off the north arm by four-foot rollers can be productive all day in the bay — but only if somebody can tell it what’s waiting in there. That’s the whole problem, and it’s not a planning problem. It’s a knowing-what’s-left problem.
The more carefully you plan the route, the more the weather costs you
A plan is a liability in proportion to its detail. The tighter you build the route in March, the more of it you throw away the first morning the wind turns.
Most field service software descends from one model: a job has a date and a technician. That holds up when the constraint is a person’s time and the work sits at a fixed address. On a lake, the constraint is the water. Which shorelines are workable today comes down to wind direction and fetch, and nobody knew that last week.
Why a date and a crew name is the wrong thing to write down
Write a date and a crew onto every job and every weather day means bulk-editing dozens of records. Nobody has time for that in the middle of May, so nobody does it, and by the second week the schedule in the software has no relationship to what’s happening on the lake.
The unit is wrong too. A job at a property is really four or five pieces, and a crew commonly sets some of them. A dated job that’s three-quarters finished has no honest state to sit in.
What to do instead: send boats at water
Stop scheduling and start sending. Everything still waiting sits on one list, sorted by which bay it’s in. Each morning you send a boat, with a crew and the gear aboard, to a lake and the bays they’re going to work. They take whatever’s still waiting there.
| A calendar | Sending boats at water |
|---|---|
| A job carries a date and a crew | A job carries a place and a state |
| Weather means reassigning dozens of records | Weather means moving one boat |
| A crew sees its list | A crew sees everything still open where they are |
| Progress is jobs closed | Progress is pieces finished |
| Being ahead means nothing | Being ahead means pulling the next bay forward |
What you give up, and why it turns out not to matter
The obvious objection is that customers want to know when you’re coming. In practice a seasonal dock customer doesn’t want a date — they want the dock in before the weekend they arrive. A promised Tuesday you miss is worse than an honest “we’re working your bay this week.”
The second objection is that without a schedule you can’t tell whether you’re on track. You can tell better. Count what’s left and the rate you’re finishing it, and you know whether you’ll make the Fourth. A calendar full of dates you’ve already broken tells you nothing.
Four things you need before this works
- Bays. Work has to be findable at a coarser grain than an address — a bay, an arm, a stretch of shoreline one boat can work in a day.
- Every piece tracked on its own. Otherwise a part-done property is invisible, and the next crew re-does work or skips it.
- The gear a shoreline needs. A list of open work is only useful if a crew can tell which of it they can take on with what’s aboard today.
- A map. This is spatial. A list of addresses is no substitute for seeing which pins are still gray.
What “are we on track” looks like without a schedule
How much was there at the start, how much is left, and how fast it’s coming down — by week, by bay, and by the gear it needs. Flat for a week means you’re treading water, and you’d rather find that out in the first week of June than the last.
That’s the whole of it, and it’s why there’s no calendar in LakeOps. How sending crews out works.