Skip to main content
← Field Notes

July 14, 2026

Billing Coordination Time in Environmental Consulting

Yes—coordination time (scheduling inspections, transmitting SWPPP documents, tracking submittals) is billable when your contract defines it as a task and you capture a delivery record proving the work happened. The obstacle is rarely legitimacy; it's documentation. Consultants who can't show a timestamped record of what was sent and when tend to write off coordination hours rather than defend them.

Yes, you can bill for coordination time—scheduling site inspections, transmitting SWPPP revisions, chasing signatures on a Notice of Intent, following up with a Regional Water Board reviewer. These are project tasks, not overhead. The problem many small consulting firms run into isn't whether it's legitimate to bill; it's that they can't prove the coordination happened, so it gets written off at invoice review or challenged during a payment dispute.

Is coordination time actually billable, or is it just overhead?

It depends on how your contract treats it. If your scope of work lists deliverables only—"prepare SWPPP," "conduct quarterly monitoring"—then coordination gets buried and clients assume it's baked into the fixed fee. If your contract names coordination as a task category with an hourly rate, it's billable the same way field time is.

The distinction that matters to a client's AP department is whether the time maps to a defined project activity. "Emailed the contractor" reads like overhead. "Transmitted revised SWPPP Rev. 3 to GC and confirmed receipt ahead of the applicable BMP implementation window under the CGP—confirm the current version at the SMARTS portal" reads like project work. Same task. Different defensibility.

The California Construction General Permit (Order 2022-0057-DWQ) is built on deadlines—inspection frequencies tied to qualifying rain events, corrective action timelines, and annual report submittals. Confirm the current permit terms and submittal deadlines at the SMARTS portal. Every one of those deadlines generates coordination: reminders, document transfers, sign-off requests. That's chargeable effort with a paper trail already implied by the regulatory structure.

Why do firms write off coordination hours instead of billing them?

Three reasons, in rough order of frequency.

First, the time never gets captured. Someone spends time tracking down a QSP's inspection signature over several emails, and it doesn't make it onto a timesheet because it felt like "just admin."

Second, it gets logged but stripped at invoice review. The principal looks at "1.5 hrs coordination" against a fixed-fee task and cuts it to avoid an awkward client conversation.

Third—the expensive one—it gets billed, then challenged. A client disputes a line item, asks what the coordination actually consisted of, and the firm has an email thread across two inboxes and no clean record. Rather than reconstruct it, they credit the invoice. A firm that does this consistently across its billings can leak meaningful revenue over time.

How do you document coordination so it survives a dispute?

The standard is simple: for every coordination charge, you should be able to produce what was sent, to whom, and when—without reconstructing it from memory or scattered inboxes.

That means:

  • A tamper-proof send record. Not "I'm pretty sure I emailed it Tuesday." A timestamped log showing the document, recipient, and delivery time that you didn't edit after the fact.
  • The artifact tied to the task. The transmittal of SWPPP Rev. 3 should link to the coordination line item, so the invoice and the proof reference the same event.
  • Delivery confirmation, not just send confirmation. "Sent" and "received" are different facts. A dispute usually turns on whether the client got it before a deadline.

This is the specific gap Mainstay closes. When you transmit a compliance document through it, the delivery record is captured automatically and time-stamped, and billing can trigger off that delivery event. So the coordination charge and the proof it happened are generated by the same action—you're not assembling evidence weeks later when someone questions the invoice.

What should coordination billing look like on the invoice?

Break it out. Bundling coordination into a lump "project management" line invites the "what is this?" question. Itemize it against the activity:

  • "Transmitted SWPPP Rev. 3 to GC; confirmed delivery 6/18 — 0.5 hr"
  • "Coordinated QSP inspection scheduling following 6/12 rain event — 0.75 hr"
  • "Submitted annual report to Water Board SMARTS portal; confirmed upload — 0.5 hr"

Each line points to a specific, dated, deadline-relevant task. A client can see what they're paying for, and if they ask, you have the delivery record behind each one. This is also what lets you bill on delivery rather than waiting for a monthly cycle—cash moves when the work is provably done, rather than after a longer billing cycle.

Does billing for coordination change your liability exposure?

It can reduce it. The same documentation that defends a charge also proves you met a delivery obligation. If a client later claims they never received a required document before a permit deadline, your tamper-proof send record answers that directly. You're not just protecting revenue—you're building the evidence that shows you did what your scope required, on time.

Mainstay coordinates the delivery and documentation of environmental compliance work — it is not a compliance advisor and makes no regulatory determination. Always confirm requirements with the relevant agency.

Sources

This post is for general informational purposes only. Mainstay coordinates the delivery and documentation of environmental compliance work — it is not a compliance advisor and makes no regulatory determination. Regulatory requirements vary by permit type, jurisdiction, and project conditions. Always confirm applicable requirements with the relevant agency or a qualified professional.