RAIN EVENT EMERGENCY RESPONSE SHOULD BE YOUR BEST MARGIN WORK.
QUICK ANSWER
Rain event emergency response — emergency BMP deployment, inlet protection, sediment cleanup — is almost always T&M work done under time pressure with documentation collected after the fact. Most SWPPP contractors do the work, spend 3 days assembling the documentation, and bill at cost with minimal markup. The margin opportunity is real. The billing process to capture it usually isn't in place.
T&M DOCUMENTED BEFORE YOU LEAVE THE SITE. BILLED WITHIN 48 HOURS.
BY JOSH LUEBKERPublished: June 2026Updated: June 2026
Why Rain Event Billing Gets Left on the Table
T&M DOCUMENTATION ASSEMBLED AFTER THE FACTThe event happens on a Tuesday at 11pm. Crew mobilizes, installs emergency BMPs, documents the site. By the time someone assembles the T&M documentation — crew hours, equipment deployed, materials used — it is Friday. Three days of memory and maybe photos. The GC gets a bill that is hard to defend because the documentation doesn't match the event timeline.
LUMP SUM BILLING ON T&M WORKSome SWPPP contractors bill rain events as a lump sum — a flat mobilization fee plus estimated materials — rather than actual T&M. This avoids the documentation problem but consistently leaves margin on the table. Emergency response T&M at documented actual cost plus markup almost always exceeds a lump sum estimate for the same event.
EMERGENCY MARKUP NOT APPLIED CONSISTENTLYMost SWPPP contracts include a provision for emergency response markup — typically 15 to 25% above cost — for mobilizations outside regular business hours, weekend deployments, and weather emergency work. Most contractors apply markup inconsistently or not at all because the contract language isn't reviewed and tracked systematically.
MULTI-SITE EVENTS BILLED SEPARATELY INSTEAD OF CONSOLIDATEDA single rain event can trigger simultaneous emergency response at 3 to 5 sites. Each site gets a separate mobilization, separate documentation, separate billing. Consolidated billing — one invoice covering all sites from a single event — is cleaner, faster, and easier for the GC to approve than 5 separate invoices with partial documentation on each.
The CFOS Rain Event Billing Protocol
ON-SITE DOCUMENTATION AT THE EVENTCrew documents the event on-site using a standardized form — start time, mobilization trigger, crew count, hours by crew member, materials installed by type and quantity, photos with timestamps and GPS coordinates. Documentation complete before crew demobilizes. Not assembled from memory three days later.
48-HOUR BILLING CYCLET&M invoice submitted within 48 hours of event completion. Emergency response billing that waits 2 weeks is harder to approve — the GC has moved on, the urgency is gone, and every line item becomes a negotiation. 48-hour billing captures the event while it is still fresh and defensible.
CONTRACT MARKUP APPLIED EVERY TIMEEmergency response markup clause reviewed at contract signing. Markup rate documented. Applied automatically to every qualifying event. No crew chief decides whether to apply markup. It is built into the billing process at the contract level.
MULTI-SITE CONSOLIDATIONWhen a single rain event triggers response at multiple sites, SPM consolidates into a single invoice with a site-by-site breakdown. One approval. One payment. Documentation organized by site rather than scattered across 5 separate invoices. GCs approve consolidated emergency invoices faster.
LUMP SUM VS T&M DECISION AT CONTRACT SIGNINGFor each contract, SPM reviews whether lump sum event billing or T&M billing maximizes expected revenue based on typical event complexity, crew size, and contract markup provisions. Hybrid structures — lump sum mobilization plus T&M materials — are common and work well for events where mobilization is predictable but scope varies.
WHICH SCENARIOS LEAK MOST
WHERE EMERGENCY BILLING LEAKS: FOUR RAIN-EVENT SCENARIOS.
The Named-Storm Mobilization
A forecast hurricane or named storm triggers pre-positioning across every active site — crews, materials, pumps staged before a drop falls. Pre-event mobilization is billable emergency response under most MSAs, and it's the single most commonly donated scope in SWPPP because nobody papers work done before the emergency officially exists.
The 2AM Callout
The GC's super calls at 2am: the basin's breaching. After-hours emergency response carries premium T&M rates in most agreements — overtime labor, emergency equipment rates, minimum-hour callout charges. Crews that respond first and document later bill straight time for premium work, every storm.
Multi-Site Simultaneous Response
One rain event, eleven sites responding at once. The billing leak is allocation: shared crews, shared pumps, and shared materials smeared across sites without per-site time and material records. What can't be allocated can't be invoiced — and disputes eat whatever gets estimated after the fact.
Post-Event Repair & Reinstallation
Silt fence down, wattles displaced, inlet protection gone — post-event restoration is new billable scope, not warranty work on the original install. The subs that photograph damage same-day and price restoration within 48 hours collect. The ones that just fix it donate it.
WHAT DISCIPLINE RECOVERS
WHAT DISCIPLINED EVENT BILLING RECOVERS.
Same-Week
Documentation, or the revenue doesn't exist. The rain-event rule: every response documented the week it happens — crew hours by site, equipment hours, materials consumed, photos timestamped. Multi-site trades that batch documentation to month-end lose the allocation fight before it starts. Same-week paper converts emergency response from disputed estimate to payable invoice.
$24K → $1.1M
What per-site discipline built. The $5.2M erosion contractor netting $24K wasn't underpricing rain response — nobody could see which sites' emergency work was billed and which absorbed it. Per-site job costing and event-billing discipline were core to the system that took net profit to $1,105,000 at a 30% margin.
48 Hours
From response to priced invoice. Emergency work follows the same protocol as change orders: documented, priced, and submitted within 48 hours of the response — while the GC's super remembers the 2am call. Event invoices submitted weeks later get scrutinized; invoices submitted while the mud is fresh get paid.
Frequently Asked Questions
If your MSA or contract provides for them — and most SWPPP agreements either do or will if you ask at signing. Standard structures include overtime multipliers for after-hours response, minimum callout charges (4 hours is common), emergency equipment rates, and pre-positioning charges for forecast events. The negotiating moment is contract signing, not the storm. If your current agreements are silent on emergency rates, price the next renewal with an emergency response schedule attached — GCs sign it readily because they need the 2am response more than you need to give it away.
Contemporaneous everything: crew names and hours by site, equipment with on/off times, materials consumed with quantities, timestamped photos of conditions before and after, and the name of whoever directed the response. The gold standard adds a same-day email to the GC confirming the response and scope — one paragraph, sent while it's fresh. Invoices built on that package survive scrutiny; invoices built on a foreman's recollection three weeks later get cut in half.
It depends on the contract and the typical event complexity. T&M billing at documented actual cost plus markup almost always generates more revenue than lump sum estimates for the same event — but requires on-site documentation to be defensible. Lump sum avoids the documentation problem but consistently undervalues the work. SPM evaluates each contract at signing and recommends the structure that maximizes expected revenue given the GC relationship and documentation capability.
Start time, mobilization trigger (rainfall threshold, GC direction, permit requirement), crew roster with hours by individual, materials installed by type and quantity, site photos with timestamps and GPS coordinates, and demobilization time. All of this is captured on-site during the event using a standardized field form — not assembled from memory afterward.
Multi-site events get consolidated into a single invoice with a site-by-site breakdown attached. One approval, one payment, one AR line to track. Documentation organized by site within the consolidated package. GCs approve consolidated emergency invoices faster than 5 separate invoices with partial documentation.
15 to 25 percent above documented cost for after-hours mobilizations, weekend deployments, and emergency weather work. The exact rate is contract-specific. Many contractors have the provision in their contracts but never apply it consistently because the clause isn't tracked at the billing level. CFOS applies it automatically on every qualifying event.
YOUR EMERGENCY RESPONSE MARGIN IS BEING LEFT ON THE SITE
If your rain event billing is assembled from memory days after the event, you are losing money on your best markup opportunity. First call shows you what the protocol looks like.
Former commercial construction project manager and master electrician. Managed 150+ projects totaling $300M+ including Google data centers, military bases, hospitals, and high-rises. Now fractional CFO for commercial subcontractors doing $1M–$12M through Sulphur Prairie Management.
CONTROL Book →
