RDI

RDI workflow

Subcontractor Labour & Attendance Verification

cloud recordings, the Recordings tab, and Gate Report ANPR data are used to verify subcontractor worker attendance — confirming arrival and departure times, headcounts, and overtime or weekend working claimed in labour returns.

Category
Subcontractor & Labour Management
Frequency
Very Common
Confidence
High
Evidence records
40
Cost model
Qualitative

Trigger, activity, conclusion

01 · Trigger

A subcontractor submits a labour return, daywork sheet, overtime claim, or payment application that the main contractor's PM or QS believes may be inflated, inaccurate, or unverifiable.

02 · Activity

Accessing the evidence system recordings for specific date(s) and time window(s) claimed by the subcontractor — reviewing footage to verify presence, number, arrival time, and departure time of workers.

03 · Conclusion

The labour claim is verified or refuted by footage evidence. Dispute resolved without escalating to formal adjudication.

Workflow steps

  1. Step 01

    A subcontractor submits a labour return, overtime claim, daywork sheet, or payment application containing specific attendance or hour claims.

    Inferred
  2. Step 02

    Main contractor's QS, PM, or commercial manager identifies figures inconsistent with their site observations — specific dates, claimed hours, or worker counts that seem unlikely.

    Inferred
  3. Step 03

    PM or QS identifies the relevant cameras and time windows (dates, start times, end times) that would cover the claimed worker attendance.

    Evidenced
  4. Step 04

    the evidence system recordings accessed via the Recordings tab and scrubbed to the relevant arrival and departure windows.

    Evidenced
  5. Step 05

    Footage reviewed to observe: whether workers were on site at the claimed time; how many; when they arrived; when they left; whether they were actively working or idle.

    Evidenced
  6. Step 06

    Where Gate Report ANPR is deployed, vehicle entry/exit timestamps cross-referenced with labour claims to provide a second independent data point.

    Inferred
  7. Step 07

    Observations documented — timestamps noted, screenshots captured, headcounts recorded.

    Evidenced
  8. Step 08

    Discrepancies between footage record and submitted claim compiled into a written note or schedule.

    Inferred
  9. Step 09

    Subcontractor presented with footage evidence and identified discrepancies. In most cases, subcontractor adjusts or withdraws the disputed element without further escalation.

    Evidenced
  10. Step 10

    Adjusted claim agreed and processed for payment. Footage record retained as part of commercial audit trail.

    Inferred

Evidence records

Paul was able to use the Recordings tab to verify when his concrete sub got to site and when they left. He needed to verify that they worked 12 hours.
Anonymized evidence record 6.1
Trevor brought the subby into his office and showed him a video of what happened (on the evidence system), after which he returned the €70k. Trevor explained that if the video was not produced, the subby was willing to go to court.
Anonymized evidence record 6.2
Used recordings to check whether the subcontractor's weekend crew had actually been on site as claimed in their daywork submission — the footage showed only two men on site for three hours, against a claim for six men for eight hours.
Anonymized evidence record 6.3

ROI model

Template E

dispute claims

Evercam provides visual evidence that resolves or prevents disputes with subcontractors, suppliers, and clients. Saving from faster resolution, avoided escalation, and prevented overcharges.

Formula

saving = (disputes_avoided_pct × disputes_per_year × avg_resolution_cost) + (overcharges_prevented_per_year × avg_overcharge_value)