Two boats, one shoreline: dispatching removals without a schedule
The second boat is where dispatch breaks: two crews collide at a property, or each assumes the other has a shoreline covered. The answer isn’t a better schedule — it’s pointing each boat at water and letting it take what’s waiting there.
· 6 min read
Run one boat and dispatch is easy — everything pending is theirs. The trouble starts with the second boat. Now two crews can show up at the same property, or worse, each can assume the other has a stretch of shoreline covered and nobody goes. Most shops solve it with a morning of assignments: this list for you, that list for them. By ten o’clock the wind has made both lists wrong.
The answer isn’t a better schedule. It’s no schedule: point each boat at a piece of water and let it take whatever’s pending there. The boats can’t collide, because the thing they’re working from is the same live pool — and they can’t idle, because the pool never runs dry while the lake has work on it.
Point a boat at water
Setting up a boat’s day in LakeOps is five choices, none of them a route: what gear is aboard, which lake, which stretches of shoreline, which services, and who’s on the crew. That’s the whole decision. The crew’s chart then shows the pool — open removals on that water, in those zones — ordered by where the boat actually is, worked out on the phone as they go.
Nothing is assigned. A deployment doesn’t hand a crew a list built at 6am — it defines which slice of the pending pile is theirs to draw from. A list made at the landing would be wrong by the third stop; the pool is right every time anyone looks at it.
Why two boats can’t step on each other
Send both boats to the same lake — even the same shoreline — and the worst that happens is they meet at a property, which on a fall lake is just Tuesday. What keeps the record straight is that every piece is marked on its own, by whoever did it: the fork barge’s crew marks the dock they pulled, the crane crew marks the lift, and neither wipes out the other. A piece gets finished once. There’s no version of this where two crews “both had it”, because nobody ever had it — they took it, one piece at a time.
The half-done property this produces isn’t a problem either. It reads as part-done on everyone’s map, and its remaining pieces sit in the pool for whichever boat gets back there — possibly a different one, with different gear, on a different day.
The gear sorts the work by itself
The classic two-boat mistake is the fork barge motoring over to a lift only the crane can move, discovering that on arrival, and burning half an hour. That trip doesn’t happen here: if a piece needs gear the boat didn’t bring, the app says so plainly — “needs the crane barge” — instead of hiding the stop or letting the crew find out at the dock. Same for headcount, when a piece takes more crew than the boat carries.
Which means the office can run the split by gear instead of by guesswork: the crane barge sweeps the lifts down a shoreline, the fork barge takes everything else, and neither wastes a stop on work it can’t do. The map makes the split visible before anyone launches: each property wears a ring for the gear it needs, so “what should the crane do today” is a ten-second look, not a meeting.
And why neither boat idles
Collisions are half the two-boat problem; the other half is the crew that finishes its list at two o’clock and motors home with daylight left. That crew doesn’t exist here, because there’s no list to finish — as long as the water they’re pointed at holds pending work, the chart offers the next nearest stop, ordered from where the boat actually sits. A fast crew simply gets through more of the pool. The day ends when the light does, or the wind says so, not when a list written at dawn runs out.
When the wind turns, move a boat
A west wind at ten o’clock closes the west shore. With assigned lists, that’s an afternoon of rescheduling. Here it’s one action: repoint the boat at the lee shore — from the office or from the boat — and its pool changes with it. Nothing needs un-assigning, because nothing was assigned. LakeOps tells you how many jobs are waiting where you’ve just sent them, which is the number the person on the radio actually wants to hear.
The specific request still works
Pools don’t mean you can’t direct. A customer rings at eight about a lift that has to come out today — add it to a boat’s day by hand, and it stays with that crew even through a weather move. The pool handles the season; the extras handle the phone calls. Both ride the same chart.