Every superintendent knows the 4:30 p.m. routine. The trailer is quiet for the first time all day, the daily log is still open, and the manpower section is blank. You walk the floors in your head: how many electricians did the sub actually have on three? Was the drywall crew six or eight? Did the concrete pump operator show up before or after lunch? Then you type in your best guess, because the owner's rep wants the log tonight and nobody is going to count again tomorrow.
That guess becomes the official record. It gets pulled into pay application backup, delay claims, back-charge disputes and, if something goes wrong on site, an incident investigation. A construction manpower report is one of the most-used documents on a project, and on most jobs it is also one of the least accurate.
What is a construction manpower report?
A construction manpower report is a daily record of how many workers were on a jobsite, which company and trade they belonged to, where they worked and how many hours they put in. General contractors use it to track subcontractor staffing against the schedule, support pay applications and change orders, document delays, and know exactly who was on site in an emergency. The most reliable manpower reports are built from actual check-in and check-out records rather than from end-of-day estimates.
Why does the daily manpower count matter so much?
The daily manpower count matters because one number feeds schedule control, pay applications and T&M billing, delay claims, emergency response and productivity analysis. If the count is a guess, every one of those uses inherits the guess. It is tempting to treat manpower as a box to tick on the daily log, but in practice it feeds:
- Schedule control. If the mechanical sub committed to a crew of ten to hit a rough-in milestone and has been running five for two weeks, the manpower report is your early warning, and your evidence when you ask them to staff up.
- Pay applications and T&M work. Time-and-material tickets and labor-based billing need headcount and hours that hold up when an owner or lender reviews them.
- Delay and disruption claims. Months after the fact, a claims consultant will reconstruct what happened on site day by day. Contemporaneous manpower records are some of the strongest evidence available. Handwritten guesses are some of the weakest.
- Safety and emergency response. When you need to account for everyone on site, you need a list of names, not a number someone typed in at the end of the day. Where OSHA requires an emergency action plan, it must include procedures to account for all employees after an evacuation.
- Productivity analysis. Comparing installed quantities to worker-hours is only useful when the worker-hours are real.
What should GCs track every day?
A good construction manpower report answers five questions: who, for whom, what trade, where and how long. Procore's daily log, for example, has manpower fields for company, workers, hours, location, trade, cost code and comments. Here is the field list we recommend capturing for every project, every day.
| Field | Why it matters | Common mistake |
|---|---|---|
| Date | Ties the record to the daily log and schedule | Entering it the next morning and back-dating from memory |
| Company / contractor | Shows which sub is staffing the work | Duplicate contractor names ("ABC Electric" vs. "ABC Elec. Inc.") splitting the count |
| Trade / classification | Separates journeymen, apprentices, foremen, laborers | Lumping every worker under the company's main trade |
| Location / area | Shows where effort is going (building, floor, zone) | Leaving it blank on multi-building sites |
| Worker count | The headline number | Counting at one moment instead of over the whole shift |
| Total hours | Supports labor billing and productivity analysis | Assuming every worker did a full 8 hours |
| Worker names | Emergency accountability, orientation and certification checks | Not recorded at all |
| Notes | Weather, delays, inspections, visitors | Kept in a separate notebook that never makes it into the log |
A simple daily manpower report template
If you are still building the report by hand, this layout keeps the essentials in one place. One row per contractor, per trade, per location:
| Date | Contractor | Trade | Location | Workers | Hours | Notes |
|---|---|---|---|---|---|---|
| Mon | Example Electric | Electrician | Building A, Level 3 | 6 | 48.0 | Rough-in, east wing |
| Mon | Example Electric | Apprentice | Building A, Level 3 | 2 | 16.0 | |
| Mon | Example Drywall | Framer | Building A, Level 2 | 5 | 37.5 | One worker left at 2 p.m. |
| Mon | GC self-perform | Laborer | Site-wide | 3 | 24.0 | Cleanup, deliveries |
Keep a separate list of worker names behind each row. The count is what goes on the daily log; the names are what you need when somebody asks "was he on site that day?"
Where do manual manpower reports go wrong?
Manual manpower reports go wrong at five points: walk-through counts, foreman estimates, assumed hours, double entry and contractor name drift. Most inaccurate reports are not dishonest. They come from a process that asks a busy person to remember something they never actually measured. The usual failure points:
1. Counting by walking the site
A walk-through count is a snapshot. Workers on break, at the material yard, in the lift or in the porta-john are missed. Workers who arrived after your walk, or left before it, are counted wrong. On a large site, two walk-throughs at different times will rarely agree.
2. Relying on the sub's foreman
Asking each foreman for a number at the end of the day is faster, but it shifts accuracy to people who have their own reasons for rounding. Most foremen are honest. The process still gives you no way to check.
3. Hours assumed, not recorded
For your own non-exempt employees, the federal Fair Labor Standards Act already requires employers to keep a record of hours worked each day and each workweek. Many manpower logs still record headcount and then multiply by eight. Early departures, late arrivals and half-day crews disappear. Over a long project, for example, a crew of ten that routinely leaves an hour early shows up as 10 extra hours a day that never happened, which works out to roughly 50 hours a week on paper.
4. Double entry
The superintendent writes the numbers in a notebook, the project engineer types them into the daily log, and the accounting team re-keys them into the ERP. Every handoff is another chance for a transposed digit, and nobody knows which copy is right.
5. Contractor name drift
When the same subcontractor appears under two slightly different names, its manpower is split across two rows. Reports show half the crew you actually had, and trend analysis becomes meaningless. Fix it at the source: Procore, for example, lets admins merge duplicate company records into one primary company.
How do you build a manpower report you can defend?
You build a defensible manpower report by recording instead of estimating: roll it up from individual check-ins and check-outs, tie it to a clean contractor and trade list, and send it to the daily log without retyping. In short, a defensible construction manpower report has three properties:
- It is built from individual check-ins and check-outs. Each worker records arrival and departure, and the report is a roll-up of those events. Headcount and hours are calculated, not guessed.
- It is tied to a clean contractor and trade list. Ideally that list comes from your project management system, so the names in the manpower report match the names in your contracts and commitments.
- It flows into the daily log without re-typing. One source of truth, sent once to the systems that need it, with a clear record of what was sent and when.
Step-by-step: moving from estimated to recorded manpower
- Pick a check-in method your crews will actually use. QR codes at the gate, an access card, a helmet sticker or a face scan at a kiosk. The best method is the one that adds the fewest seconds at the gate. Our construction time clock buyer's guide walks through the trade-offs.
- Load your contractor and trade lists first. Clean up duplicates before go-live. If you use Procore or CMiC, import the lists instead of re-creating them.
- Enroll workers against the right contractor. Each worker should belong to a company and project so their check-ins roll up correctly.
- Define your locations. Building, level, zone, or whatever level of detail you report on. Put a check-in point at each controlled entrance.
- Run both processes in parallel for a week. Compare the recorded numbers to the manual log. The gaps are usually eye-opening, and they help you get buy-in from the field.
- Switch the daily log to the recorded numbers. Keep a short notes field for context the system cannot capture: weather, inspections, delays.
- Review exceptions, not everything. Look for workers who checked in but never checked out, contractors whose numbers suddenly drop, and logs that failed to sync.
How can GCs use manpower data to manage subcontractors?
GCs use accurate manpower data to compare each sub's staffing with its commitments, spot declining trends before milestones, check labor billing against recorded hours, and see who is on site right now. Once the numbers are real, the manpower report stops being an administrative chore and becomes a management tool:
- Staffing versus commitment. Compare each sub's daily headcount to what they committed in the look-ahead schedule. Raise it in the weekly coordination meeting with data, not impressions.
- Trend lines by trade. A steady decline in a trade's manpower two weeks before a milestone is a schedule risk you can act on early.
- Verification of labor billing. When a sub's T&M ticket claims more worker-hours than their crew checked in for, you have a factual basis for the conversation. See our guide on verifying subcontractor headcount and hours for a full process.
- Who is on site right now. Live presence data turns the manpower report into an emergency roster.
Manual vs. recorded manpower reporting at a glance
| Manual (walk-through or foreman count) | Recorded (check-in / check-out) | |
|---|---|---|
| Headcount accuracy | Snapshot, easy to miss workers | Every worker who checked in |
| Hours | Usually assumed | Calculated from actual times |
| Worker names | Rarely captured | Captured for every entry |
| Superintendent time | Daily data entry | Review and approve |
| Daily log entry | Typed by hand | Sent automatically |
| Audit trail | Whoever typed it last | Every change recorded |
How ADRO handles this
ADRO was built around the idea that the manpower report should write itself from what actually happened at the gate. Here is how it works in practice:
- Workers check in the way that fits your site. The gate QR code on their own phone (confirmed by a 4-digit code sent by text), or an access card or face scan at the kiosk. Each check-in and check-out becomes an entry log with a time, a project and a location.
- Manpower logs are created automatically. ADRO creates one manpower log per project, contractor, location and date, and recalculates its worker count and total hours from the entry logs attached to it. Nobody types the number in.
- Contractor corrections are built in. If workers were logged under the wrong or duplicate contractor, an admin can reassign the log. ADRO merges it with the existing log for the same project, location and date, and recalculates the totals.
- Daily log export with status tracking. With the Procore integration, manpower logs are exported to the Procore daily log. Each log shows its export status (pending, synced, updated, failed) and failed exports are retried automatically every hour. Corrections made after export are flagged as updated and sent again. CMiC customers can export manpower logs to CMiC as well.
- Clean lists from your system of record. Projects and contractors are imported from Procore or CMiC (plus locations and trades from Procore), so the names in your manpower report match the names in your contracts.
- Weekly summaries and a full audit trail. Admins get dashboard analytics and a weekly email report, and every change to the data is recorded.
If you are on Procore, our article on automating Procore daily log manpower entries goes deeper on the export side. For an overview of everything ADRO does on the jobsite, see the ADRO construction workforce platform overview.
Key takeaways
- The manpower report feeds schedule control, billing, claims and safety, so accuracy matters.
- Track contractor, trade, location, worker count, total hours and names every day.
- Walk-through counts and foreman estimates are snapshots; check-in records are evidence.
- Import your contractor and trade lists so names stay consistent across systems.
- Send the numbers to your daily log once, automatically, and track whether they arrived.
Sources
- OSHA: 29 CFR 1926.35, Employee emergency action plans
- U.S. Department of Labor: Fact Sheet #21, Recordkeeping Requirements under the FLSA
- Procore Support: Create Manpower Entries
- Procore Support: Merge Companies
Want to see it on your own jobsite? Book a 20-minute ADRO demo and we'll walk through it with your projects.