Field · Crew

One code. No app store.

Your framer does not want a fourteenth app, does not remember a password, and may not read English first. They get a text with a code, tap it, and they are clocked in at 6:48 with GPS on the row.

Start for free All field tools

No download · no password · works on the phone they already carry

Day one

Thirty seconds from hire to clocked in.

The reason crew software fails is never the software. It is the twenty minutes on a Monday morning that nobody has, spent at an app store with five people who came to frame a house.

Step 01

Add the number

You enter their mobile number and pick their crew. That is the whole of the setup on your side.

Step 02

They get a text

A link and a six-digit code. No account to create, no email address required, nothing to install.

Step 03

Tap the code

The portal opens in the browser already on the phone. It remembers them — they will not enter the code again.

Step 04

Clock in

One button, thumb-sized, with the project already selected from where they are standing.

Step 05

Hours land

Time posts to the right project and phase, into payroll and into the actual column, with no second entry.

New sub crew showing up Tuesday? Same five steps, same morning, no IT ticket and no shared login floating around a group chat.

What’s in the portal

Five things, and nothing else.

The portal is deliberately small. A crew member should be able to find every one of these without being shown twice, and should never land somewhere that asks them a question the office should be answering.

Clock in and out

One button. GPS confirms they are at the site boundary and stamps the row. Breaks and lunch are two more taps, not a form.

Today’s work

The phase they are on, the task list for it, and what has to be finished before the inspector comes. Written in short lines, not paragraphs.

The schedule

Where they are expected tomorrow and next week, updated the moment the planner moves. No Sunday night text chain asking which job.

Photo upload

Same one-tap camera as the app. Shot, tagged to the phase they are clocked into, and into the site feed. Works with no signal.

Chat

A line to the PM and the project channel. Questions land next to the job they are about instead of in a group text from four months ago.

Built to be readable

Big type, high contrast, icons that carry the meaning on their own, and language settings per person. Nobody has to decode a screen to get paid correctly.

Time & attendance

Hours land on the phase they were worked on.

A timesheet that only says “8 hours, Tuesday” is a number you cannot cost. Every entry here carries a project, a phase, a location, and a rate — so labor rolls into the actual column without anyone allocating it later.

GPS stamped at clock-in and clock-out, with the distance from the site boundary on the row
Phase picked from what they are working on, or defaulted from the schedule
A PM can enter or correct hours for the whole crew on one tap grid at the end of the day
Overtime and burdened rates applied per person, so the ledger sees true labor cost
Missed clock-outs surface the next morning instead of at payroll on Thursday
Every correction is logged with who made it and why — the same rule the budget lives by

See how labor hits the ledger

Cedar Street · Tuesday · 5 on site

6:48aInM. Ortiz — framing. GPS 12 m from boundary.—

6:51aInD. Reyes — framing. GPS verified.—

7:02aInJ. Whitfield — rough-in, plumbing.—

11:30aBreakCrew lunch, 30 minutes, unpaid per your settings.−2.5 hrs

2:15pPhaseD. Reyes switched from framing to rough-in for the duct chase.split

4:31pOutAll five clocked out. 42.5 hours across two phases.42.5 hrs

4:34pBLT AIFraming labor at 71% of current with the roof deck still open. Worth a look before Thursday.4,270

Payroll

The same hours, once, into your payroll run.

The hours that costed the job are the hours that pay the person. Nobody rekeys a timesheet on Thursday afternoon and hopes the two systems agree.

ADPDirect export PaychexDirect export CSVAny provider QuickBooksJob costing XeroJob costing

Export a pay period in the format your provider expects, with regular and overtime already separated
Per-person rates, burden, and job classifications carried through to the file
Hours split across projects and phases stay split — a person on two jobs on Tuesday exports as two lines
The period exported is stamped, so the same week cannot be sent twice by accident
Sub crews tracked for attendance without touching your payroll at all

See every integration

The practical questions

What crews and foremen actually ask.

Does the crew need to download anything?

No. The portal runs in the browser that is already on the phone. They tap the link in the text, enter the code once, and the phone remembers them from then on. Your PMs and managers can use the iPhone app if they want the full product, but the crew never has to.

What if someone doesn’t speak English well?

Language is set per person. Screens are built around big type, high contrast, and icons that carry the meaning on their own, and the clock-in flow is one button on an otherwise empty screen. Getting paid correctly should not depend on reading a paragraph.

What happens if their phone has no signal at the site?

Clock-in, clock-out, and photos are captured on the device and sync when signal returns. The GPS coordinates and the real timestamp are recorded at the moment it happened, not at the moment it uploaded, so a dead zone never costs anyone a quarter hour.

Can a foreman clock in the whole crew?

Yes. A foreman can clock a crew in and out from one grid and correct the day at the end of the shift. Every entry records whether the person clocked themselves in or someone did it for them, so the record stays honest without a debate.

Do sub crews go in the portal too?

If you want attendance and photos from them, yes — same code, same thirty seconds, and their hours track against the job without entering your payroll. What they invoice is handled separately against their scope. See sub payments.