For subcontractors, doing the work is only half of the job. The other half, and important part, is proving that it happened.
A foreman can lose an hour or more every evening to paperwork, and many say that the admin side eats more time than actually running the daily crew.
Daily reports, timecards, RFIs, and change orders are still being managed on paper or are scattered across spreadsheets, texts, emails, and cloud drives (SharePoint, Dropbox, etc.), which no one can easily search. This paperwork isn’t just a time sink. It’s the record that you fall back on when a change is disputed, a payment stalls, or an audit might land.
When the record is messy or late, the cost almost always shows up downstream: slower billing, a weaker position in disputes, and importantly, thinner margins.
Digitizing field documentation hits both problems at once. It gives crew leads their evenings back AND gives PM’s the real-time visibility the GC already has. The right subcontractor project management software can solve these issues and put time back in your day and money back where it belongs.
Below is where the hole gets dug on time, cost, and risk, and how to backfill it before the job caves in!
Most contractors chalk up the cost of paperwork as simply “The cost of doing business,” and it almost never adds up. However, when you do, it lands on the same three places the rest of this article works through: time, cost, and risk.
Time, from manual reentry between the field and the office. Keying the same data twice carries a 1% to 4% error rate, and each error takes 30 to 90 minutes to troubleshoot and fix. Putting it into perspective, across a single crew, that’s a “paperwork tax” of 2 to 10 hours every week, on top of the actual job.1
Cost, from errors that are only surfaced during a dispute or audit. A gap that nobody caught at the time (an expired supplier quote, undocumented scope changes, a number carried forward on a “broken” Excel spreadsheet) becomes a charge you can’t defend later. These gaps quietly inflate project budgets, and they cost you a second time at audit: inconsistent records cause delays and drive up auditing costs, on top of accounting and audit work that already runs small businesses 1% to 5% of revenue. Disorganized records just keep digging the hole deeper, making it harder and more expensive for you to backfill and they weaken your position the moment any of those items gets challenged.2,3
Risk, from PMs working off outdated information. When the office runs a week behind in the field, overruns and schedule slips get caught after the labor has already been spent. At that point, there’s not much more left to fix, only potential fallout to manage: cash flow problems, late supplier payments and friction with the GC. Each one traces back to the same root: information is captured too late, in the wrong place, by the wrong workflow/process.
The next three sections provide insights to fix these at the source, starting with Daily Reports.
Most foremen tend to write their daily reports from memory at the end of a day, which is the worst possible time to do so. Plenty of us can’t remember what we had for dinner last night, yet we ask a foreman to construct a full day of manpower moves, deliveries, delays, and field changes from whatever they can still recall at 5 pm or even later.
The details that tend to slip are exactly the ones you need later:
Which crew was on which cost code?
How long and what was the root cause of the delay?
What was the condition of the jobsite for the day’s task?
What quantities were incorporated into the work?
That’s not just a paperwork problem. A thin or late report is a weak T&M ticket, a delay you cannot substantiate, and a pay app you can’t back up. One missed detail becomes a rejected change, a budget variance nobody caught in time, or a dispute you walk into without evidence.
If you’re writing reports at the end of the day (or the end of the week), the data you provide is likely outdated.
The fix isn’t just writing the report sooner in the day, either; it’s changing what the report is.
Real-time reports replace the retrospective reporting process, providing PMs with same-day visibility, highlighting bottlenecks and budget issues before they become bigger problems.
Open the report at the start of the shift and treat it as the foreman’s running log for the day. A delivery arrives, log it. Another trade holds you up for two hours; log it (especially since the exact time will still be fresh in your memory). A new crew/manpower onsite, a photo of a changed or differing site condition, a verbal direction from the GC, it all goes in as it happens.
By the end of the day, the report is already written because it was built one entry at a time rather than reconstructed from memory.
Reacting and responding appropriately to a daily report can be more than 4 times slower without real-time reporting, and some might be impossible to address without significant effort.
The right subcontractor project management software is what makes this approach practical. The foreman captures labor counts (and even time spent by the crew on a timecard), quantities, photos, and notes from the jobsite in the moment, on the device already in their pocket instead of hauling notes back to the office or field trailer to process later.
The payoff runs in two directions. In the field, the foreman gets their evening back instead of spending an hour at their desk or parked in the cab of their truck. In the office, the PM sees today’s labor and production today, not next week, and can catch a potential budget or schedule slip while there is still time to do something about it.
Feed that running log and process into a central system, like a good subcontractor management software, and the visibility is automatic instead of something someone has to chase and track down.For a sub, most RFIs start in the field. Your crew stumbles upon a conflict between the plans and the actual conditions, a detail that doesn’t exist, or a spec that contradicts itself. You write it up and send it up through the chain to the GC, and that’s the moment you lose control of it.
The answer now sits in someone else’s inbox, the clock is ticking on your schedule and deadlines, and you’re left with two options, both bad:
Stop the work and wait
Proceed and risk re-work
Buried in an email thread, that RFI has no distinct owner and no deadline anyone is tracking. You find out it’s overdue when your foreman calls asking if an answer has been received yet.
Moving RFIs into a centralized, trackable, and transparent log fixed the visibility problem, but the bigger win for a sub is the paper trail.
A logged RFI is a time-stamped record (audit protection) of exactly what you asked for, what you recommended, and when you did so. Every day it goes unanswered is a day you can point to later, whether you’re defending a schedule skip or a delay claim. This isn’t just good practice and housekeeping, it’s leverage!
So, what does a structured RFI workflow look like? And how does it impact the schedule?
A structured, digitized RFI replaces complicated email threads with a transparent sequence of events.
A field issue is identified, documented, and written up as an RFI using a standardized process, then logged in your subcontractor project management software with photos, plan references, and the date submitted.
The RFI is reviewed by the internal team, routed to the appropriate person (such as the GC), and then to design teams, architects, or engineers (this custody chain varies widely depending on the relationship established at the award of the project). A due date is set.
The assigned “owner” of the RFI reviews, marks up plans as applicable, issues revisions and additional clarifications, and submits their response through the same custody chain in reverse, logged against the original request rather than scattered across multiple email chains and replies.
The answer is clearly logged and gets back to the project/field team and is distributed to those responsible for performing the work.
Once all concerned parties are on the same page, the RFI is closed out, and work can proceed.
Throughout the process, the status shows where each RFI stands at a quick, digestible glance:
The schedule impact is the whole point here. When every open RFI carries a hard due date and a visible owner, an overdue answer surfaces the moment it’s late, rather than after the delay is already baked in and risk is realized. You have the record to show whose court the ball was in the entire time.
Change orders are typically the most disputed paperwork on a job, and for a sub, they’re where margin quietly disappears. The scope grows, the schedule creeps, and the budget impact soon follows if you don’t document it correctly and on time.
But in the field, everything flows downhill, and so does the pressure to just keep going. The GC’s super says, “Keep Moving.” The crew doesn’t want to stand around, and the instinct is to “do the work now, document it later, and ask for forgiveness.” That instinct is exactly what gets subs burned.
There tends to be a significant grey area with change orders, as some contractors may argue that the extra cost was implied, even if it’s not in the contract or documented. Start changed work on a verbal go-ahead with nothing in writing, and if the GC’s office questions the costs afterward, you’re then arguing about labor you’ve already spent without a leg to stand on.
Most contract documents also put a clock on you. Miss the written-notice window for a change, dispute, or claim (even by just a few days), and you can waive the right to money entirely, no matter how legitimate and extensive the work was.
To avoid these troubles, specific documentation must be in place before, during, and after the change, as follows.
The documentation isn’t just busy work. It’s what turns extra work into a paid change order instead of a write-off, soured relationship, or friction on the jobsite.
Written direction to proceed must be received from the GC before the changed work starts. If all you can get is a verbal go-ahead, confirm it in writing the same day. A quick email restating that you were told to do so is enough to create a record. Be sure to save this documentation to your pending change order request in your subcontractor project management software for visibility among the project team.
Daily T&M tickets. If you’re working ahead of a priced and executed Change Order, ensure these are signed by the GC’s field rep, as these are your fallback if the pricing is disputed later.
Copies of email threads, meeting directives, and conversations related to the change must be logged with the COR rather than scattered across inboxes.
When the record is complete, time-stamped, and signed, there is no grey area left to argue because you:
On paper, it’s black and white. Off-paper, it’s all grey, and that is where subs lose.
Every section above points to the same shift: capture the record once, in the field, as the work happens, instead of rebuilding it at a desk after the fact. Do that consistently, and the wins compound.
Daily Reports go in accurately, substantiated, and on time.
RFIs carry a clock and a paper trail.
Change orders get paid because the documentation was in place at the first notion of a change, during, and after.
The payoff isn’t necessarily less paperwork. It’s a tighter operation: billing goes out faster because the backup is already organized, there are fewer disputes because every change has a signed record behind it, and foremen and PMs spend their time on the quality of the work instead of reworking it.
That’s the difference between documentation as a chore vs. documentation as leverage and protection.
eSUB is built for subcontractors specifically, not adapted from a GC tool, which is why the workflows above map how a sub actually operates: Field to Office, Sub to GC, Quote to Closeout.
If paperwork bottlenecks are costing you time and margin, request an eSUB demo to see eSUB in action on the kind of work you do.
References:
[1] Struto. “How do you Calculate the Hidden Cost of Manual Data Entry?” - https://www.struto.io/blog/how-do-you-calculate-the-hidden-cost-of-manual-data-entry
[2] Talo.”Cost of accountant for small business”. - https://talo.com/costs/cost-of-accountant-for-small-business
[3] Cherry Bekaert. “Construction Audits: How to Prepare, Benefits and Compliance Tips”. https://www.cbh.com/insights/articles/construction-audit-guide-tips-for-readiness-compliance/