Demo — sample data. Close out a stop, log an issue, and watch the board, the log and the numbers update. Built by IN IT 2 FIX IT
Signed in as
Crew Board

Which crews are where, and what's actually done?

Every property on today's schedule, which crew has it, whether it's finished, and how the hours compare to what the contract allows. When a property manager calls Thursday asking whether anyone showed up Tuesday, the answer is on this screen instead of in a truck somewhere.

Property ▲ Status ▲ Crew ▲ Service ▲ Arrived ▲ Departed ▲ Hours ▲ Budget ▲ Over / under ▲

"Were you here Tuesday?"

The single most common call a landscape office gets. Right now it costs a radio call, a crew leader's memory, and a callback. Here it's a timestamp and photos.

Hours over budget is where margin dies

The contract is a fixed price. Every hour a crew spends over the budgeted time on a property comes straight out of profit — and on paper route sheets nobody ever adds it up.

Skipped stops stop disappearing

Rained out, gate locked, dog in the yard. If nobody logs it, it never gets made up — and the property manager is the one who notices.

Close out a stop

What the crew leader taps on a phone before pulling off the property.

Work completed

The stop turns green on the board with the crew, the times, the hours against budget, and the photos attached. Nobody retypes a route sheet at the end of the day.

Log an issue or extra work

The part that usually dies in a text message to the account manager.

Extra work gets a dollar value and a photo the moment the crew sees it — instead of being remembered three weeks later, if at all. That backlog is on the owner's board.

This is the answer to the phone call

Property, crew, arrival and departure time, what was done, and photos. Not to argue with the customer — to answer them in ten seconds and be right.

Chemical applications are a legal record

Applicator, product, rate and date, captured at the property instead of reconstructed from memory at the end of the week when an inspector asks.

Nothing gets written twice

Logged once by the crew leader on a phone. It feeds the board, the customer's proof of service, the payroll hours and the extra-work backlog.

Revenue — this week
$0
Stops completed
—
—
Hours vs budget
—
—
Extra work quoted
—
—
Revenue per crew day
—
across all crews

Revenue by day

Hover any column for the exact figure.

Where the money came from

Contract maintenance versus everything else.

Biggest accounts

By revenue for the period shown.

Paid time vs time on a property

Every hour on the clock, and how much of it reached a customer's property. The difference is drive, load, fuel and waiting — real work that no contract pays for directly.

What's leaking right now

$6,480
Crew hours over contract budget this month — 4 properties running long every visit
$11,900
Extra work the crews found and nobody quoted — 17 items sitting in the backlog
$2,240
Skipped stops never made up — 8 visits billed but not delivered

The extra work is the growth

Crews spot dead shrubs, broken heads and drainage problems every week. On most operations that walks off the property with them. Captured, it's the highest-margin revenue in the business.

Over-budget properties have names

Every fixed-price contract has one or two sites quietly eating the margin. This tells you which ones, so you can re-price them at renewal instead of guessing.

Built from what the crews already logged

Nobody assembles this report. It's the same taps the crew leader made on the phone, added up.

Is this close to how your operation actually runs?

This is a demo built to start a conversation. If it's close, the real version gets shaped around your properties, your crews, your services and your contract terms. If it's nowhere near, tell me that too — that's just as useful.

Tell me what's wrong with it