Enter and approve timecards

A timecard in STrOp is more than hours-for-payroll. The same entry becomes labor cost on the job (against the cost code), the source rows for certified payroll on public work, the attachment behind a T&M ticket, and the break-compliance record California asks about when it matters. One entry, entered once, by the person who was there.

What you need

  • A crew roster — timecards pick workers from it.
  • The job and, ideally, cost codes set up, so hours land where the estimate said they would.
  • If the day was scheduled on the board first, most of this is pre-filled.

The foreman's entry

  1. Timecards (/timecards), pick the project and the date.
  2. If the crew was on the schedule for that day, the rows come pre-populated from the assignments — confirm rather than retype. Otherwise add each worker; their classification and default cost code follow from the roster.
  3. Per row: hours and time type (regular, overtime…), the cost code or scope the work belongs to, and — when the hours back a T&M ticket or field work order — attach them to it. That link is what makes extra work billable instead of arguable.
  4. The California fields are not decoration. Meal break taken (and provided on time), rest breaks, heat-illness recovery where it applies — answer them from what actually happened. These attestations are the record if a break claim ever lands.
  5. Submit. Draft timecards are yours to edit; submitting hands the day to the approver.

The approval pass

  1. Field → Approvals shows submitted timecards waiting.
  2. Review against what you knew about the day — right job, believable hours, extra work attached to its ticket. Approve, or kick back for the foreman to fix and resubmit.
  3. Approved is the cutoff that counts. Job cost, payroll reporting, and progress metrics read approved hours. An un-approved week is invisible cost.

Common mistakes

  • Batching Friday. Five days entered from memory is how hours land on the wrong job and breaks get attested wrong. The entry is built for the tailgate, on a phone, day of.
  • Skipping the T&M attachment. Hours on extra work that aren't tied to the ticket become a negotiation later. Attach them the day they happen.
  • Letting submitted sit. Approvals are the gate to every downstream number — a PM who approves weekly is always a week blind on cost.

See also

This is how STrOp works

The data flows you read about here are how the platform threads bid, execution, billing, and closeout. Single pipeline. No re-keying.

Request beta access →

Last updated 2026-08-20.