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.

Spanish. The crew pages in the browser and the native app can be switched between English and Spanish with the Español / English link (it shows the language you would switch to). The choice is remembered on that device, and dates and month names follow the language. Job and visit notes written in English show a Translate link underneath that shows the note in the crew member's language; each note is translated once and kept on the device.

The native app has the same crew tools as the browser version: Start Day and End Day, Edit Crew (per-person attendance), Suggest Work, and Request Materials. A shared stop shows who the other crew is ("With …"), and tapping a push notification for a new job or a visit note opens that stop.

Office staff in the field. An owner or office employee doesn't need a separate crew login. When their own login is attached to a crew (Team → Crews → Linked Login, or automatically by ticking Schedule Jobs Directly on their employee record), the regular home screen shows a My Schedule tile on any day that crew has a visit — or a stop still clocked in from an earlier day — and hides it on days with nothing assigned.

It runs in the phone's browser, so there's nothing to download from an app store. It's also an installable web app: have crews use the browser's Add to Home Screen (iPhone Safari) or Install app (Android Chrome) option once, and it opens full-screen from a home-screen icon like a normal app; the icon opens the login screen, and a phone that is still signed in goes straight to its home. (If an icon was added before this changed and opens the marketing page instead, remove it and add it again.) It still needs a signal to load and save — installing doesn't add offline use. Inputs are sized so iPhones don't zoom in when a field is tapped, and controls are larger for gloved or one-handed use.

If an action is queued without signal (clock in/out, pause, resume, drive start/end), a banner says it's saved on the phone and will send when signal returns, and it is recorded at the moment it was tapped, not when the phone reconnects — so a lunch pause that syncs hours later still subtracts the right minutes. Taps older than 48 hours, or from a clearly wrong phone clock, fall back to the sync time.

A regular user can be a crew's Linked Login too. If someone who works a crew has their own login (a crew lead or owner, say), pick their name in Linked Login instead of creating a separate shared crew login for them. They sign in as themselves, keep their normal access, and find the crew's stops under Scheduling → My Crew Schedule in Landscapt (the link only appears for someone linked to a crew). It's the same Crew App screen, with the same clock-in and stop rules. Being listed under Team Assignments is separate: that puts someone on the crew's roster for scheduling and costing, but doesn't give them the Crew App.

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.

Request Materials (in the native crew app and on the browser stop page, under a Materials requests card) is the crew asking for something instead. Pick a stocked or project material from the catalog, enter a quantity and an optional note, and Submit Request creates a draft requisition tied to that job for the office to review. The quantity can be fractional, up to two decimals (half a yard of mulch is 0.5); maintenance parts aren't available in field requests. The crew never sees prices on the request. Each request is listed under the card with its status: Submitted, Pending approval, Approved, Rejected, Ordered or Closed.

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.

The paid day runs shop to shop, not stop to stop. At the top of My Schedule the crew has a green Start Day button. One tap by whoever has the phone starts the day for everyone working on the crew that day; once it's running the card reads "Day started 7:02 AM — 3 on the clock" with an End Day button that clocks everyone out at once. If a job is still in progress the app asks you to confirm before ending the day.

• Who "everyone" is. The crew's roster for that date: the employees under Team → Crews → Team Assignments, adjusted by any same-day reassignment on the Crew Board, minus anyone marked not working and minus anyone whose Days on the Team Assignment don't include that weekday (an employee on one crew Mon–Wed and another Thu–Fri counts only on the crew they're scheduled with that day; a same-day reassignment always wins). Deactivated or terminated employees are never on a roster. A crew with nobody on its roster can't start a day — the button stays disabled, with a note underneath, until someone is added (tap Edit Crew to add the people working, or ask the office). A crew account created under Settings → Users starts with an empty roster, so add team members under Team → Crews first.
• Forgot to tap Start Day? Starting the first job opens the day anyway, so payroll still has a shift. It's flagged Started at first job in the Payroll report, because the real start (at the shop) was earlier — the office can correct it there.
• Start Job and Stop Job clock the whole crew too. Start Job punches every working member in on that stop at the same moment and Stop Job punches them out. Those per-person job punches feed Job Costing; the Start Day / End Day shift feeds payroll. They are separate on purpose: drive time and shop time are paid but aren't on a job.
• The day is the company's day. Which calendar day a shift belongs to follows your organization's time zone, not the phone's.
• Started a job after End Day? Storm call-back, or End Day tapped by mistake: starting a job reopens that person's shift for the day, and the time between End Day and the new job start is taken off as an unpaid break, so the hours worked after End Day are paid and nothing is counted twice. Tapping Start Day on a day that has already ended does nothing; only starting a job reopens it.
• Working past midnight. A shift that started the evening before and is still running (storm work) stays one shift: after midnight the card reads Day started yesterday with an End Day button, a second Start Day isn't offered, and the first job after midnight doesn't open an overlapping shift. End Day closes it once. Until 6am, yesterday's unfinished stops also stay on the list, marked From yesterday, so a route that runs past midnight can be finished. A shift from the day before that started more than 12 hours ago (a 3pm start nobody ended) is treated as forgotten, as is any shift open more than 16 hours: End Day doesn't close it at an absurd length, it stays open and the Payroll report flags it for the office to correct. Someone who left before midnight and comes back after it rejoins the shift they left, so the time away is only taken off once. If you export Payroll while some days are still open or have no shift, Landscapt warns that hours are understated or missing and asks you to confirm — fix those days first for accurate pay.

Late, out, or leaving early: Edit Crew. Tap Edit Crew on My Schedule for the roster with each person's in/out time. For each person:

• Not working — out today (sick, vacation, hasn't shown). They are skipped by Start Day and Start Job, so they aren't clocked in by mistake.
• Clock In — arrived late. Their shift starts now, and if a job is in progress they join its punches from now.
• Left for the day — ends their shift and any open job punch, and marks them not working so the next Start Job doesn't clock them in again.
• Back — someone who left returns the same day. Their shift reopens and the time they were away is taken off as an unpaid break. If a job is still in progress, their earlier job punch reopens too with the time away taken off, so the hours they work on that job after returning are counted in job hours and Job Costing.

Someone from another crew is helping today: Add someone to my crew today. At the bottom of Edit Crew, pick the person from the list and tap Add. The list shows people on the company's other crews who aren't already on yours today. They join your crew for today only (the same one-day move the dispatch board's Team Assignment makes), are clocked in like a late arrival, and join the running job's punches if a job is in progress. Tomorrow they are back on their usual crew. If they were already clocked in on a job with another crew, that job punch is closed at the moment you add them (their day shift keeps running), so their time is counted once — the same happens when the office moves them with Team Assignment on the dispatch board.

Sub-items under a service. If the estimate's service had sub-items (the products to bring and the tasks to do), the stop lists them under that service with their quantities. Crews never see prices. They're for planning only and don't bill or change inventory. The office sees the same list under the service on the job.

While a job is running, the timer shows how much of the stop's budgeted time is left (for example “1h 05m left”), turning red as “over budget” once it runs past. Break time doesn't count against it. A stop with no budgeted hours shows the plain elapsed time. When a crew stops a job, a Time summary shows each person's start and finish and the total crew time, so they can fix someone who arrived late or left early before tapping Done.

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. A leftover visit on a job that is On Hold or Cancelled isn't on the crew's list, so Start Job and Stop Job skip it rather than starting, completing and invoicing work nobody asked for. A double tap, or a tap queued offline that replays later, is treated as already done instead of showing an error. If a crew taps Start Job on a stop that was already completed, skipped or cancelled, the app tells them its status instead of clocking in, and visits with no client clock in the same as any other. If the office marked a stop complete while the crew was still punched in, the crew's Clock Out closes those leftover punches so they don't stay open on the Timesheet. If a crew already started the stop (Start Job clocked them in) and then skips it, their clocks stop at the skip — as long as no other service at the same stop is still running — so the hours still reach the Timesheet and Job Costing instead of staying open.

If the stop has chemicals, a Confirm chemicals applied card lists each one at its planned amount. Enter how much was actually used, or tick Not used, then tap Confirm chemicals. Confirming only works once the stop is running (the card says "Start the job first" until then), and it records the crew foreman as the applicator, with their applicator license, plus a matching mix volume when the amount changed. When the company requires crew confirmation, Stop Job stays disabled until every chemical is confirmed. Chemicals on a service the crew skipped (or the office cancelled) aren't listed to mix or confirm and never hold up Stop Job. If the crew starts a stop the office never dispatched, its chemicals are loaded at Start Job so the card, the confirmation and the stock deduction still work.

Label, how applied, conditions and extra products. These work the same in the browser crew page and in the iOS and Android crew app. Each chemical has a View label link showing its EPA number, re-entry interval, whether it is restricted-use, and the label directions the office entered on the product. If a chemical has no planned amount (no area or application rate was on file), the card says so and the crew enters what they measured. How applied opens the method, target and area treated, starting from what the office planned; changing them saves the new values on the record when the chemical is confirmed. Under the list, Conditions takes the temperature and wind (and/or pH, depending on the company's Chemical Tracking setting). The temperature and wind are filled in from the National Weather Service reading nearest the property (tap Update to refresh it) and can be corrected; if no reading is available they are typed as before. They're optional and are saved on every chemical confirmed in that tap. Add a chemical records a product the office didn't preload, such as a spot treatment or a substitute: choose the product, the amount and the unit, and optionally how it was applied and the conditions (inside the confirm card it uses the conditions already entered there). A stop with no chemicals planned shows a small Chemicals card with the same button, as long as the company tracks at least one chemical product, so a crew can still record a treatment the office didn't plan. It is saved already confirmed, with the foreman as applicator, and counts toward the compliance report and stock like any other. When the office has filed a label or Safety Data Sheet for the product, View label also shows an Open button for it.

Confirmed records are final for the crew. Once a chemical is confirmed, or once its visit is completed, skipped or cancelled, the crew can no longer change it: the confirmation is the record of what was applied and may already be on a Notice of Treatment. If something was entered wrong, the office corrects it from the visit's Chemical Applications panel, and the change is kept in the record's audit trail.

Reference. The Reference button on the crew home screen (browser) or the top of the schedule (iOS/Android) opens the company's library of labels, Safety Data Sheets, SOPs and training. Search by title, filter by type, and tap a document to open it. Documents the office marked office-only don't appear, and opening one needs a connection.

If the office put a second crew on the same stop, your stop card says With <other crew> and the stop screen shows who else is on site. You each have your own stop: tap Start Job and Stop Jobfor your crew, and your hours are worked out from your clock times and your headcount only. Nothing you do clocks the other crew in or out. The visit is billed once by the office from the lead crew's stop, so your stop doesn't create its own invoice, and chemicals are confirmed on the lead crew's stop. Materials and sub-items for the stop show on your stop too, so either crew can record what was used.

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.

Time left on the running job. While a stop is running, its timer counts down from the stop's budget in clock time, not including breaks. Each visit on the stop adds its budget: the visit's own Budgeted Hours (set on the dispatch board, in man-hours) divided by the number of men on it, or otherwise the per-person budgeted hours of every service the visit covers. The web and phone apps work it out the same way.

• 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. If the crew had already ended the day (End Day, or everyone clocked off) before that late Stop Job — say paused at 4pm, End Day at 5pm, Stop Job the next morning — the stop is closed at the end of the day instead, so the overnight isn't counted as a break against anyone's hours.
• 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.

That formula is the starting estimate. When people have actually been clocked in on the stop (Start Job punches the crew in), the visit's hours follow the real punches instead: each person's own clock-in to clock-out, minus their breaks, added together — so someone who arrived late or left early is counted for exactly the time they were there. The stop's pause time comes off each person only up to the time they were on the job, so someone who joined after a lunch pause isn't docked for it. (The app records how long the stop was paused, not exactly when, so someone on the job for part of the visit can still be docked up to their own time there.) The crew-size multiplication is used only when there are no punches for the stop.

Crew times only change through the app. Start Day, End Day, clocking people in and out and editing punches all go through the crew app's own checks; a crew login can't change shift or punch times any other way. Every change to a day shift, and every Payroll correction, is kept in the audit history.

Once a visit's invoice is sent, its punches are locked for crew. Stop Job usually puts the visit straight onto a draft invoice, and while that invoice is still a draft the crew can keep correcting member punches (Edit Crew, Time Summary). Once the invoice has been issued (printed, sent or paid, and not voided or deleted), the crew app refuses changes or deletions to member punches on that visit and tells you to ask the office to correct the time. The office can still edit times. Editing punches doesn't change the invoice amount: an auto-created invoice bills each service's quantity and rate, not the hours worked.

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. If your connection drops and the app resends the note, it is saved once, not twice. Each note shows who wrote it and when: "You" for the crew's own notes, "Office" and the person's name for remarks from the office.

Notes from the office. The job's crew note appears under Job Notes with its formatting (bold, bulleted and numbered lists), and you read and acknowledge it before clocking in. A note typed on a single visit is plain text. When the office adds or changes a visit note, your phone gets a "Note from Dispatch" notification only if that visit is dispatched, in progress, or scheduled within the next two days. A note on a visit further out is waiting on the stop when you get there, and you still have to acknowledge it before you can start.

Add Photo takes a picture with the camera (or, in the phone app, picks one from the library) 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. If your company turned on Require a Before photo to start a job or Require an After photo to stop a job (Landscapt Settings, in the crew app section), the Photos area shows Before and After buttons, and Start Job or Stop Job stays disabled until a photo with that label is on the stop. A photo that is still uploading with no signal counts.

Photos bigger than about 3 MB (typical for a recent phone camera) are shrunk on the phone before they upload (longest side 2,400 px, re-saved as a JPEG), so uploads don't fail on a weak connection; smaller photos go up untouched. If an upload fails you can pick the same photo again and retry.

Required Before and After photos. When your company turns on "Require Before photo" and/or "Require After photo", the Photos card shows a Before photo and an After photo button. Each one lets you take the picture or choose one already in your photo library, and tags it Before or After (a photo added with the plain Add Photo button doesn't count). Nothing stops you starting the job — both required photos are checked when you tap Stop Job, which stays disabled until they're on the stop. A photo still waiting to upload with no signal counts; the app uploads it before it sends the Stop Job. A photo whose upload failed doesn't count until you retry it.

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.

The day clock lands in Report Center → Payroll (admins and managers only): each person's clock-in, clock-out, breaks and total hours per day, ready to correct and export for payroll.

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.

• Gate codes and property notes. The stop shows the property's gate or lock code in large type, and the property's crew notes count as notes to read before Start Job, the same as job notes. The stop lists each note once: the job note, then each service's own note, then the property's standing note (which now shows even when the job or a service has its own note). A package step still waiting on the Waiting List isn't on the crew's list until the office dispatches it, the same as on the dispatch board.
• Full addresses. The stop page shows the full address, including state and zip, and wraps it rather than cutting it off. Map links use the full address too.
• Times in company time. Times on the crew screens are shown in the company's timezone, so a phone set to another zone still shows the right clock times.
• Signed out or no connection. If the crew's sign-in has expired, My Schedule and the stop page say so with a sign-in button. With no connection they say they couldn't load and offer Retry, instead of looking like there's no work.
• Finished stops. A stop the office cancelled shows as cancelled, with no Start Job. Skipped and cancelled stops count as done in the day's progress, and an All stops done card reminds the crew to tap End Day.
• One-handed use. Start Job and Stop Job sit in a bar at the bottom of the screen, above the iPhone home bar, and small buttons are at least finger-sized. When a button is disabled, the reason shows under it.
• Empty roster. If no one is on the crew today, Edit Crew explains how to add people (Team → Crews in the office), and a login that isn't linked to a crew doesn't show Edit Crew.
• Photos. Photos for every service on the stop load together, so they show straight away after the page reloads.