The Crew App

A crew signs in and lands on a home screen with three tiles: My Schedule, Dashboards, and Job Photos. That's the whole app for them — no clients list, no invoices, no estimates, and no sidebar full of office screens.

It runs in the phone's browser, so there's nothing to install. Tell crews to add it to their home screen once and it behaves like an app from then on.

Because the login is shared, the app records hours for the crew — see below. Individual people's times are handled by the office, not on the phone.

Whether crews see prices is your choice: Hide pricing from crews under Landscapt Settings removes rates and amounts from everything they can reach. It's worth turning on if you'd rather the crew not be drawn into a pricing conversation on a driveway.

My Schedule is the day's work as a list of stops, in route order. Each card shows the client, the address, the services due there, and a status.

Tapping a card opens the stop: the address (tap it for directions), the client's phone (tap to call), any notes the office left, the list of services, the buttons below, and — when the office called for specific materials on the job — a Materials called for card (see below).

When the office has planned specific products for a job (the Products section on the Job record, or on the dispatch board's job popup), the stop shows a Materials called for card listing each one with the quantity the office planned. This is separate from Request Materials below — it's not the crew asking for something, it's the crew confirming what was already ordered for them.

For each material still pending, the crew can:

• Confirm or edit the quantity and tap Mark Used — the field starts pre-filled with the planned quantity, but the crew can correct it if less (or more) actually went down. The planned quantity itself is never overwritten, only what actually got used.
• Not Used — the material wasn't needed at this stop after all.

Once resolved, the row becomes read-only and shows what was recorded. The web crew stop page (for crews working from a browser tab instead of the app) has the identical card and does the same thing against the same underlying job — either side works from the same planned list.

Drive time is tracked for the day, not per stop — it covers the yard to the first job and everything between. Tap Start Drive when the truck moves and End Drive when it stops.

You don't have to remember to end it: starting a job automatically closes an open drive segment, so a crew that drives off and taps Start Job at the next property gets the drive recorded correctly without a second thought. You also can't start drive time while a job is running — stop the job first.

Start Job and Stop Job apply to the whole stop. Skip is the exception — it's per service, so a crew can skip the hedges and still complete the mow at the same property.

When a crew taps Stop Job, the hours for that stop are:

(clock out − clock in − break minutes) × number of crew members

Those hours are then split across the services at the stop in proportion to their budgeted hours, so a stop with a two-hour cleanup and a half-hour mow doesn't credit them equally. That's what the office compares against budget on the dispatch board.

• Breaks come off the total. Pausing for lunch and resuming subtracts those minutes. If a crew clocks out while still on a break, the break is closed at that moment and still subtracted — nobody gets billed for a break somebody forgot to end.
• Forgot to clock in? If there's no clock-in on the stop, the app falls back to the job's scheduled start time and the time you tapped Stop Job. It's an estimate, not a measurement — clocking in is what makes the number real.
• Overnight shifts work. A clock-out time earlier in the day than the start time is treated as the next day rather than as negative hours, which matters for storm work that runs past midnight.

Notes to Office sends a message back from the field. It shows on the dispatch board against that stop, so it's the right place for "couldn't reach the side bed, sprinkler running" rather than a text message to somebody's phone.

Add Photo takes a picture with the camera and attaches it to the visit. Before-and-afters, damage found on arrival, and anything a client might query later all belong here — they stay attached to the visit rather than living in someone's camera roll.

Crews are at the property every week and notice things the office never sees. The Suggest work button on a stop sends that back: pick the service from a short list, add a note, take a photo, send. It arrives as a ticket for the office to price and quote.

The photo is the part that matters most — with one, the office can usually quote the work without driving out to look at it.

The full round trip — what the office sees, converting one into an estimate, and the two reports that show whether suggestions turn into money — is in the Tickets guide under "Field upsells from crews".

Everything a crew does lands on the Dispatch Board in real time: status moving to In Progress and Completed, actual hours against budgeted, notes, skip reasons, and photos. Nothing needs to be re-entered at the end of the day.

Dashboards are scoped separately. A crew only sees dashboards that have been explicitly marked visible to crews, so you can give them a job-count or hours board without exposing revenue.

For the office's half of this — stop order, route optimisation, and exactly how actual hours are compared against budget — see the Dispatch Board guide.