Field operations
Field data that shows up costed — not re-keyed on Friday.
Foremen enter time and requests from a phone, against the job, phase and workcode they are standing in. It is captured once, checked against the budget at entry, and posts to payroll and job cost the same week — not typed off paper on Friday.
Timecards from the field, by job, phase and workcode.
A foreman enters the crew's hours from a phone, on the job. Each row carries the job, the phase and the workcode, split into RT, OT and DT. The card here is one crew for one week — 192 regular, 12 overtime and 4 double-time hours, each coded to the phase it was worked on.
No paper timesheet, no Friday session re-keying a week of hours from a clipboard.
| Employee | Job | Phase | Workcode | RT | OT | DT |
|---|---|---|---|---|---|---|
| L. Marquez | 26-1077 | 03-200 Framing | FR-METAL | 40 | 6 | 0 |
| T. Nguyen | 26-1077 | 09-250 Drywall | DW-HANG | 40 | 2 | 0 |
| C. Boyd | 26-1077 | 09-260 Finish | DW-TAPE | 32 | 0 | 0 |
| A. Silva | 26-1042 | 09-510 Ceilings | AC-GRID | 40 | 4 | 4 |
| R. Kaur | 26-1042 | 07-210 Insulation | IN-BATT | 40 | 0 | 0 |
| Crew total — 5 | 192 | 12 | 4 | |||
The daily report, where the work happened.
Crews, hours, weather, deliveries and notes go into a daily report tied to the job, filed from the field the day it happened. It is a record for the job file and a first read on production — not a form somebody reconstructs from memory a week later.
Material requests that become a purchase-order trail.
A field material request starts a document trail, not a text message. The request becomes a purchase order, the PO becomes a receipt, and the receipt becomes a cost on the job — each step traceable back to the person on site who asked for the material.
- Request raised against the job and phase
- Turns into a purchase order to the vendor
- Receipt closes the PO and posts the cost
Truck and equipment requests the yard can schedule.
The field asks for a truck, a lift or a delivery; the yard sees the request against the calendar and schedules it. What went where is recorded, so equipment time lands on the job that used it instead of disappearing into overhead.
Field work orders with rates, priced on the spot.
Extra work gets a field work order — the scope, the crew, the hours and the rates that apply — so a T&M ticket or a small estimate is written where the work is, on a ratecard, not guessed at from memory back in the office. The same FWO becomes the basis for billing the extra and for costing it.
Checked against the budget before it posts.
Entry is not blind. As hours and requests go in they are checked against the job's remaining budget by phase, so an overrun is flagged at the source — while a foreman or PM can still ask why — not discovered at closeout. Because the same entry feeds payroll and job cost, “what did this week cost, and where” is answerable the same week — see job costing and union payroll.
What the PM and payroll ask about the field.
What does a foreman see — the whole company’s jobs?
Does a foreman need to know cost codes, or just the work?
Does it run on a phone, and off signal?
How is non-contract work (NCW) captured?
When does field data actually hit payroll and job cost?
Can the office correct a field entry?
Get Friday's data on Tuesday.
We'll put a real crew's week through timecards, daily reports and the budget gate on your jobs. No per-seat charge for the field — see pricing.