Construction Control

Construction Control — Articles

T&M Ticket Tracking: A Template Only Helps If Every Ticket Ties to a Change Order

Time-and-material work is billed from paper created in the field, under field conditions. A foreman writes up the day's extra work on a ticket. The ticket gets signed or it doesn't, photographed or it doesn't, and then it travels — truck visor, job trailer, a photo in someone's messages, an email to the office. At the end of the month, billing has to turn that flow of paper into numbers on a pay application.

That is where T&M tracking quietly fails. Not in the field, and not in the arithmetic — in the log. Tickets that were never written into one place, in one format, with a change-order request attached to each one, cannot be reconciled against anything. And unreconciled tickets turn into the three outcomes nobody wants: extra work that gets questioned because its backup is incomplete, extra work that gets billed twice because the same ticket arrived by two routes, and extra work that never gets billed at all because nobody can prove which change order it belongs to.

A tracking template is the start of the fix. The discipline of keeping it current is the rest.

1. Capture the complete field set — at the ticket, not at billing time

Every ticket in the log needs the same fields, filled in while the work is in front of someone: the ticket number, the date, a description of the scope performed, the labor hours, the loaded hourly rate, and the change-order request the ticket belongs to. Material and equipment entries belong on the ticket too, where your subcontract's T&M terms call for them.

The reason for insisting on the full set at capture time is simple: the missing field is never discovered when it can still be fixed. It is discovered at billing, weeks later, when the crew has moved to another job and the hours on an incomplete ticket are a memory instead of a record. A ticket missing its date, its scope, its hours, or its rate is backup with a hole in it, and a hole is what a reviewer pulls on.

One related field habit sits outside the log entirely. Many subcontracts' T&M terms call for daily tickets acknowledged by the contractor's representative, and field guidance on T&M billing makes the same point: get the ticket acknowledged while the work is still visible. The log records what the ticket says; the acknowledgement is a jobsite practice, and no spreadsheet performs it for you.

2. One ticket, one entry, one number

Duplicates are a tracking failure, not a dishonesty failure. The same day's work legitimately exists as a carbon copy in the trailer and a photograph sent to the office. If both get entered — under slightly different descriptions, on different days — the change order's backup total inflates, and a duplicate found by a reviewer casts doubt on the tickets around it.

The defenses are boring and complete: every ticket carries a unique number; the log is a single document, not a per-project-month rebuild; each ticket is entered exactly once, under its number; and before any total is relied on, the log gets sorted by ticket number and date so a double entry shows up as what it is — the same work, twice in a row.

3. Link every ticket to its change-order request when it is written

This is the step that separates a ticket log from a ticket pile. A ticket with no change-order request named on it is floating work: performed, documented, and connected to no mechanism that can get it into the contract. A change-order request with no tickets behind it is the mirror image: an amount with nothing underneath it — written from an estimate, carried in the log, and unsupported the first time anyone asks what it consists of.

Both directions get checked, every time the log is updated. Every ticket names its change-order request. Every change-order request names its tickets. The link is made when the ticket comes in from the field, not reconstructed at billing from handwriting and memory — reconstruction is where tickets get attached to the wrong change order, or to none.

4. Keep each change order's ticket total current while the work runs

A change-order request is usually priced before or as the work starts. The tickets then accumulate on their own schedule. If nobody compares the two until billing, the request's amount and its own backup can disagree by whatever the work actually took — and a pending change order whose tickets do not support its figure is exactly the kind of internal mismatch that weakens the request while it is still being decided.

The tracking habit is a running total per change-order request, updated as tickets are logged. When the tickets pass the requested amount, that fact is visible the week it happens — while the conversation your subcontract requires can still be had — instead of at the pay application, where it arrives as a surprise.

SYNTHETIC EXAMPLE: A change-order request, COR-004, is priced at $4,800 for added conduit work. By the end of the second week, the log carries seven entries against it. Ticket T-118 was photographed and also turned in on paper, and sits in the log twice at $620. Ticket T-121 has a date and a rate but no labor hours, so it carries no billable value yet. Ticket T-123, $540 of Saturday work, names no change-order request at all. The log's raw total for COR-004 reads $5,940 — a number inflated by a duplicate entry and by work that has not been tied to this request. Cleaned up — the duplicate removed, T-123 held out until its request is confirmed, T-121 completed or held — the same log supports the request with four complete tickets totaling $4,780. Same fieldwork, same week: one version is a dispute waiting for a reviewer, the other is backup. (All names, numbers, and figures in this example are invented for illustration.)

5. The template is the workbook's own log format

The free T&M Ticket Log Template is the T&M Tickets sheet from the Construction Control workbook, offered on its own — one row per ticket, with the fields from section 1 as its columns and the change-order link built into every row. If you track tickets in it as they come in, the reconciliation below needs no reformatting, because the log already speaks the workbook's language. It is also on the Construction Control site with the rest of the free tools.

Where the workbook fits — and where it doesn't

Tracking gets the tickets into one reliable record. The workbook's job starts there. Construction Control is an Excel workbook for use alongside your AIA G702/G703 that reconciles T&M tickets to change-order requests to the pay-app schedule of values and flags seven exceptions by name: Duplicate ticket, Missing fields, Unlinked ticket, COR without backup, Pending COR vs ticket mismatch, Approved COR missing from pay app, and Approved COR vs billed value. Sections 2, 3, and 4 of this article are the first, second, third, and fifth of those checks, done by hand — the workbook runs them across the whole log at once, including the two downstream checks (an approved change order missing from the pay application, or billed at a value other than its approved value) that a ticket log alone cannot see. You can watch the workbook work in the demo — the same seven checks firing on synthetic example data.

The boundaries, plainly. The Missing fields check covers four fields — date, scope of work, labor hours, and loaded hourly rate. The ticket log has no signature or acknowledgement field, so the workbook cannot confirm a ticket was signed; that stays a field habit, as section 1 says. The workbook does not check your G702/G703 totals and does not check retainage. It does not flag a change order that was billed before it was approved. And the "Prior completed $" column (column D) on its Pay App SOV sheet is typed in by hand.

Two companions to this template. The Pay App Pre-Submission Checklist is a free one-page PDF covering the full pass you run after tracking, before the application goes out. And the workbook itself is the Construction Control Subcontractor Pay App Bridge, a one-time $39 purchase.

Nobody loses T&M money on the day the work is performed. It leaks out later, one unlogged, unlinked, or double-counted ticket at a time. Track every ticket once, completely, and attached to its change order — and the billing at the end of the month becomes an assembly job instead of an investigation.

Before your next application