A field-to-office time capture system

STEP 01 OF 10

Decide what the system has to prove before you decide what it should record

A time-capture system exists to answer three questions when someone asks, months later: how many hours, on what, and under what agreement. Design the form around those three answers first, then add convenience features — not the other way round.

The obligations that will actually be checked are specific: the Employment Standards Act's hours-of-work ceilings and overtime threshold, and, separately, the federal reporting rule on payments to subcontractors doing “construction activities.” A system built around a generic timesheet template tends to miss the second one entirely.

STEP 02 OF 10

Capture time at the point of work, not at the point of memory

Daily entry, from the person doing the work, beats a foreman reconstructing a week from a paper stub on Friday afternoon. Same-day entry is also what makes every later step in this guide possible — you cannot flag an ESA ceiling in real time from a number written down five days late.

STEP 03 OF 10

Build the daily and weekly ceilings into the form itself

Ontario's ESA sets the default: “the maximum number of hours most employees can be required to work in a day is eight hours or the number of hours in an established regular workday, if it is longer,” and the maximum in a week is 48 hours. Both limits can only be exceeded through a written or electronic agreement — and before that agreement is signed, the employer must give the employee “the most recent information sheet about hours of work and overtime pay prepared by the Director of Employment Standards.”

Flag any entry that would put a worker over either ceiling before it is approved, not after payroll finds it. If no signed agreement is on file for that worker, the flag should stop the entry, not just note it.

STEP 04 OF 10

Route every entry through a same-day sign-off, not a batch review

A foreman or supervisor confirming each day's entries the same day catches transcription errors while the work is still remembered, and creates the approval record an ESA complaint or a T5018 review will eventually ask to see. A weekly batch approval creates the same paper trail four days too late to matter operationally.

STEP 05 OF 10

Keep the rest-period rules visible to whoever is scheduling, not just to payroll

The ESA guarantees at least 11 consecutive hours off work each day, at least 8 hours off between shifts in most cases, and either 24 consecutive hours off a week or 48 hours over two weeks. A system that only checks totals after the fact cannot prevent a scheduling conflict with these — put the same rule in front of whoever is building next week's crew assignments, not just in front of payroll at close.

The same guide sets an eating-period rule that a field-to-office system should also flag: employees cannot work more than five consecutive hours without a 30-minute meal break, though that break can be split into two shorter segments by agreement. On a long shift with a single logged block of hours and no recorded break, that is worth a flag before the entry is approved, not a detail payroll notices only if a complaint is filed later.

STEP 06 OF 10

Separate employee hours from subcontractor payments at the point of entry, not at year-end

ITR 238(1) defines “construction activities” broadly — erection, excavation, installation, alteration, modification, repair, improvement, demolition and more — and s.238(2) requires an information return (the T5018) from every person or partnership that pays or credits an amount for goods or services in the course of construction activities, where the payer's own income is derived primarily from those activities. That is a payment-reporting obligation, entirely separate from payroll hours, and it needs its own field in the system from day one.

Tag every entry as “employee” or “subcontractor payment” at capture time. The two categories have different retention rules and different filing deadlines — see a payroll close that takes an hour for the close itself.

This tag also has to survive a choice your firm makes once and cannot easily undo: the T5018 reporting period is either calendar-year or fiscal-year, and once chosen it cannot be changed for subsequent years without the Minister's authorization. Build the capture system's subcontractor-payment field around whichever period your firm actually uses, not a generic calendar-year assumption.

STEP 07 OF 10

Flag the 44-hour line before payroll sees it

Overtime “begins after they have worked 44 hours in a work week” at “1½ times the employee's regular rate of pay.” If your crew works under a signed averaging agreement (2 to 4 weeks, with an expiry date — maximum two years for non-union employees), the system needs to track the average across the whole agreement period, not flag every single week that individually crosses 44 hours. The worked example below shows why that distinction changes the number payroll actually owes.

STEP 08 OF 10

Check WSIB — or the equivalent — before the first hour is logged for a new subcontractor

In Ontario, a clearance “is valid for up to 90 days,” so a check run once at the start of a long project is stale well before the project ends — build a recheck into the system rather than relying on the one done at onboarding.

BC runs a different mechanic: WorkSafeBC issues a clearance letter rather than the same 90-day Ontario certificate, so confirm the actual rule for wherever the work is happening before assuming Ontario's cycle applies. Gate the first time entry for a new subcontractor on a clean clearance check, the same way you would gate it on a signed contract. Hiring and keeping a field crew covers the separate 10-day clock that starts the moment a new employee, rather than a subcontractor, is hired, and preparing for a COR audit is where the same clearance discipline gets checked again from the outside.

STEP 09 OF 10

Watch for the misclassification risk the system itself can create

A time-capture system built only for “employees” quietly pressures anyone paid the same way, on the same schedule, to look like an employee regardless of the contract they signed. Ontario's classification tests weigh the substance of the working relationship over its label, and control over hours and method of work is one of the factors. If your system schedules a “subcontractor” identically to how it schedules an employee, that is a fact a misclassification claim will use, not just a bookkeeping quirk.

This is a design choice worth making explicit rather than letting it happen by default: if a worker sets their own hours, brings their own tools, and can send a substitute, a time-capture system built for that arrangement should look different from one built for a scheduled crew — a same-day sign-off gate, in particular, assumes a degree of supervisory control that fits an employee relationship far more naturally than a genuine subcontractor one.

STEP 10 OF 10

Keep the record for six years, not for the current project

Set retention at the point of design, not as a later cleanup task. See a payroll close that takes an hour for the underlying rule and a worked example on the close itself.