How does a Worker with no smartphone get their hours logged?

The foreman logs the time on their behalf. Every Time Entry carries its provenance — self-logged or foreman-entered — and the two are visibly distinguished everywhere they appear. They are not equally defensible in a pay dispute, so the record does not pretend they are the same thing.

A category of activity within a Job — prep, spray, cut-in, cleanup — that time is logged against, so labour cost breaks down by what was being done rather than only by which job it was done on. That is the difference between knowing a job lost money and knowing which part of it did.

Can hours be corrected in the field?

No, and that is deliberate. Offline the app can only add — new time entries, new photos, new notes. Corrections and deletions need connectivity. It means the offline path has no merge logic and therefore no silent data loss, which is the failure mode that ruins payroll trust permanently.

Does it handle overtime?

Overtime rules vary by state and getting them wrong is a liability rather than a bug, so we will say exactly which states are covered rather than claiming all of them. That list is being validated with real crews during the pilot.

Can I export to payroll?

Yes. Approved hours export for payroll, with the Job and Cost Code breakdown intact. Which payroll systems get a direct integration is being decided from what pilot crews actually run.

Time tracking and job costing for crews

The Sunday night job

Payroll is the thing that actually justifies a subscription, and for most crews it is currently a reconstruction: a stack of paper, a memory of who was where, and an hour of arithmetic that produces a number nobody fully trusts.

The point of logging hours against a Job and a Cost Code at the moment they happen is that Sunday night becomes reading rather than reconstructing. Approve the week, spot the worker who forgot to clock out, and see what the labour on each job actually cost.

Hours and money are stored as exact decimal values, not floating point. Rounding complaints in payroll never stop once they start.

Provenance

Who logged it is part of the record.

Half the workers in this market do not have a company phone, and a foreman entering their hours is normal practice, not an edge case. What is not acceptable is that entry looking exactly like one the worker made themselves.

So every Time Entry carries its origin — self or foreman — and Crewsome shows the difference everywhere the entry appears. In a pay dispute, the two are not equally defensible, and a system that blurs them is doing the owner no favours.

Self-logged and foreman-entered time are visually distinct
Provenance is set at creation and cannot be quietly rewritten
Admin edits are recorded, not applied silently
A Worker without a phone still counts toward your plan, and still gets paid right

What it does

Clock in under three seconds

From a cold app open, one-handed, gloves on. Nothing mandatory to fill in first — no required Job selection, no cost code gate, no setup wizard standing between a worker and starting.

Cost codes

Time logged against an activity inside a Job, so labour cost breaks down by what was being done and not just by where.

Provenance on every entry

Self-logged and foreman-entered time are marked differently and stay that way. You always know which is which, months later.

Breaks, GPS and geofence

Where the clock-in happened, recorded alongside it, so the question does not have to be asked.

Approvals with an audit trail

Approve the week, edit what is obviously wrong, and keep a record of what was changed and by whom.

Payroll export

Approved hours out the door with the Job and Cost Code breakdown attached, not flattened into a total.

Offline

You can start the clock without a bar of signal.

Clocking in, clocking out and adding a note all work with no connectivity, and the entry is saved to the device the moment it is made. Correcting or deleting one needs signal.

That asymmetry is a design decision, not a limitation we are apologising for. Full offline editing needs conflict resolution, and the characteristic bug of conflict resolution is silent data loss. Losing an hour of someone's pay quietly is worse than making them wait for signal to fix a typo.

Questions

How does a Worker with no smartphone get their hours logged?: The foreman logs the time on their behalf. Every Time Entry carries its provenance — self-logged or foreman-entered — and the two are visibly distinguished everywhere they appear. They are not equally defensible in a pay dispute, so the record does not pretend they are the same thing.
What is a Cost Code?: A category of activity within a Job — prep, spray, cut-in, cleanup — that time is logged against, so labour cost breaks down by what was being done rather than only by which job it was done on. That is the difference between knowing a job lost money and knowing which part of it did.
Can hours be corrected in the field?: No, and that is deliberate. Offline the app can only add — new time entries, new photos, new notes. Corrections and deletions need connectivity. It means the offline path has no merge logic and therefore no silent data loss, which is the failure mode that ruins payroll trust permanently.
Does it handle overtime?: Overtime rules vary by state and getting them wrong is a liability rather than a bug, so we will say exactly which states are covered rather than claiming all of them. That list is being validated with real crews during the pilot.
Can I export to payroll?: Yes. Approved hours export for payroll, with the Job and Cost Code breakdown intact. Which payroll systems get a direct integration is being decided from what pilot crews actually run.

The other two lanes

Job photos

Every photo lands on a Site and stays there. Annotate without touching the original.

Crew scheduling

Who is where tomorrow, decided once and visible to everyone who needs it.

Get the first invite

We are running a free pilot with a handful of real crews before anyone is charged. Leave an email and we will tell you when it opens.