- Five paperwork clocks from three official sources govern public and permitted jobs: 5 business days under Caltrans, 10 days under Minnesota statute, and 14 days for the EPA CGP waiting period.
- The four Caltrans and Minnesota clocks start at a specific named event — completing placement of the material, topographic survey, the date an invoice arrives, or the date the municipality pays the prime contractor — so always record the start event alongside the count; the quote for the EPA 14-day clock does not name its start event.
- Caltrans counts are in business days, not calendar days, and the two Caltrans provisions send forms to different email addresses (NOA@dot.ca.gov and ADL@dot.ca.gov).
- The 10-day Minnesota invoice notice and the 10-day subcontractor payment rule bind different parties (municipality and prime contractor, respectively), and neither should be confused with the payment period for audited contracts.
- The EPA's 14-day period applies only to the EPA CGP, and coverage also requires meeting the eligibility requirements in Part 1.1 of the permit.
A paperwork clock is the number of days a rule gives you to send, answer or pay a document on a public or permitted job. The clock starts from a specific event that the rule names. Public and permitted jobs come with a lot of this paperwork. A form has to reach an engineer, an invoice has to be answered, a subcontractor has to be paid, and a permit notice has to be complete before coverage starts. Each of these can carry a deadline, and the deadline comes from the rule that governs that step, not from the job itself.
This post covers clocks from three official sources. The lengths are 5 business days, 10 days and 14 days. Each clock belongs to one rule from one agency or one state, and it applies only there. The sections below say where each rule applies and quote what it says, so you can check the wording against your own contract or permit.
Net takeaways
Check the source covers your job first
Each clock in this post is tied to the source that states it. The Caltrans quotes cover contractor submissions under the California Department of Transportation's construction manual. The Minnesota quotes cover a municipality's contracts, vendor invoices and subcontractor payments under Minnesota's statute. The EPA quotes cover the Construction General Permit and its NOI.
Before you count days, find the page that names your agency, state or permit, and read whether its wording covers your job. A Caltrans count does not carry over to a Minnesota municipal invoice, and the EPA's 14 days is stated for the EPA CGP only. Reading the scope first keeps you from applying a number to a job it was never written for.
Scope is the step people skip most often, usually because a number looks familiar from an earlier project. A deadline you have seen on a past job is not evidence that it applies to the job in front of you. Read the sentence that opens the rule, check which party it binds, and only then decide whether the clock is yours.
Caltrans: 5 business days for contractor forms
Under the California Department of Transportation's construction manual, a contractor submits a form to the resident engineer within 5 business days of completing placement of the material. The section gives the submission address as NOA@dot.ca.gov.
The same section sets a second 5-business-day deadline for a different submission. Under that provision, the contractor submits the form to the resident engineer and by email to ADL@dot.ca.gov within 5 business days after the topographic survey.
The two clocks start at different events. The first counts from completing placement of the material. The second counts from the topographic survey. If you track both on one job, write the start event next to each count, so nobody has to work out from memory which event applies to a given form.
The two submissions also go to different addresses. Put each one on the entry for its own submission, so the form does not end up in the wrong inbox. The first goes to NOA@dot.ca.gov. The second goes to ADL@dot.ca.gov in addition to the resident engineer.
Both provisions count business days, and that word changes the arithmetic. Mark each count as business days on your calendar so nobody counts calendar days by habit. Whether a particular day qualifies as a business day is a question for the agency's own pages, not for this post. These are Caltrans rules only. Other agencies and states can set different clocks, so a Caltrans count should not be carried into another job without checking that agency's own pages.
Five clocks side by side
The five clocks in this post come from three official pages. The table lists each one with the event that starts it and what the quote requires. The audit provision in the Minnesota statute has no number of days in its quote, so it is not a row. It is covered in its own section below.
| Source | Clock | Starts when | What the quote requires |
|---|---|---|---|
| Caltrans construction manual, Section 5-1 | 5 business days | Completing placement of the material | Form goes to the resident engineer at NOA@dot.ca.gov |
| Same page, second submission | 5 business days | Topographic survey | Form goes to the resident engineer and to ADL@dot.ca.gov by email |
| Minnesota Statutes section 471.425, incorrect invoice | 10 days | Date the invoice is received | Municipality notifies the vendor |
| Same statute, prime contractor to subcontractor | 10 days | Date the prime contractor is paid by the municipality | Prime contractor pays the subcontractor for undisputed services |
| EPA Construction General Permit FAQ, incomplete NOI | 14 days | Not stated in the quote | Coverage is delayed until the NOI is completed and the waiting period has passed |
Use the table as a comparison. Each row is a single provision, and the linked page holds the full wording. Where a row says the quote does not state something, that gap is part of the answer. The quote is silent on that point, so do not fill it in from another source.
Minnesota: 10 days to notify a vendor about a bad invoice
Under Minnesota Statutes section 471.425, if an invoice is incorrect, defective or otherwise improper, the municipality must notify the vendor within 10 days of the date the invoice is received. The count starts at the date the invoice is received, so that is the date to write down.
Keep a simple log of invoices as they arrive. For each one, record the date the invoice is received, the invoice number and the job it belongs to. A log like this makes it easy to see which invoices are inside the 10-day window and which are past it. The quote does not say what happens after the window closes, so do not assume a result the statute does not state.
This 10-day clock covers the notice about an improper invoice. The payment period is in a separate sentence of the same statute, and the quote for it does not give a number of days. Do not read the 10-day notice as the payment deadline.
Minnesota: an audit can hold the payment period
Under the same Minnesota statute, the standard payment period for a negotiated contract or agreement that requires an audit before acceptance and payment of the vendor's invoice does not begin until the municipality completes the audit.
The statute's words are that the period "shall not be begun until the completion of the audit by the municipality." Under this sentence, the period cannot begin until the audit is complete, whatever the invoice date.
Both conditions have to hold for this sentence to apply. The contract has to be a negotiated contract or agreement, and it has to require an audit by the municipality before acceptance and payment. If your job does not fit both, this sentence does not describe its payment period, and the quote does not give a different one.
For office staff, that means the audit completion date belongs in the job file next to the invoice. An invoice still waiting on an audit has no payment period running under this sentence, and the file should show the audit date that will start it.
Minnesota: 10 days from a prime contractor to subcontractors
Under the same Minnesota statute, each contract of a municipality must require the prime contractor to pay any subcontractor within 10 days of the date the prime contractor is paid by the municipality for undisputed services provided by the subcontractor.
Both halves of that sentence set its reach. The clock starts when the prime contractor receives payment from the municipality. It is not tied to the day a subcontractor sends a bill. The sentence also covers undisputed services only, so the 10 days does not apply to services that are in dispute.
The requirement sits in the municipal contract, and it binds the prime contractor. A subcontractor or office that wants to track its own payment should ask the prime for the date it received the municipality's payment, since that date starts the count under the quote. Keep that date and the subcontractor's invoice date in the same file, so the two can be compared.
Because the quote ties the count to the date the prime contractor is paid and to undisputed services, the records that matter most are the date the municipality's payment reached the prime contractor and a note of which services are in dispute.
The EPA's 14-day waiting period for an NOI
Under the EPA's Construction General Permit, an incomplete NOI delays permit coverage until the NOI has been completed and the applicable waiting period has passed. The EPA gives that waiting period as 14 days for the EPA CGP.
Coverage has to wait on each of two separate conditions. It waits for the NOI to be completed, and it waits for the waiting period to pass. The same FAQ treats eligibility as its own matter. To be authorized under the CGP, the operator must meet the eligibility requirements specified in Part 1.1 of the permit. Read Part 1.1 itself before assuming that a completed NOI means a job is covered.
The FAQ also says a paper copy of the NOI is included as Appendix J of the 2017 CGP. Office staff who keep paper files can look for that appendix in the 2017 permit. The 14 days belongs to the EPA CGP. Do not apply it to another permit, because the quote gives it only for the EPA CGP.
When you cite this FAQ, note that the appendix reference is to the 2017 CGP. A reader working from a different version of the permit should check that version's own pages rather than assume the same wording or appendix applies.
Name the party each rule binds
Each rule in this post names who has to act, and that party is part of the rule. Write the party down next to the number, so a clock is never tracked without its owner in view.
| Rule | Party bound | Action required |
|---|---|---|
| Caltrans provisions | Contractor | Submit the form |
| Minnesota invoice sentence | Municipality | Notify the vendor |
| Minnesota subcontractor sentence | Prime contractor | Pay the subcontractor |
| EPA FAQ | Operator | Meet the eligibility requirements in Part 1.1 of the permit |
Under the Caltrans provisions, the party is the contractor, which submits the form. Under the Minnesota invoice sentence, the party is the municipality, which must notify the vendor. Under the subcontractor sentence, the party is the prime contractor, which must pay the subcontractor. Under the EPA FAQ, the operator is the party that must meet the eligibility requirements in Part 1.1 of the permit.
A vendor's office and a municipality's office may both read the same 10-day figure in these pages, but the figure binds different parties. Check which side of the rule your office sits on before deciding who watches the clock.
Put the clocks on one shared calendar
Put every clock in this post on one shared calendar, with the start event, the unit and the source link on each entry. When the calendar holds those details, nobody has to rely on memory for the rule behind a date.
Use separate fields for each part of an entry, as the table below shows. Keep business days and calendar days in different columns, so a 5-business-day entry cannot be read as five calendar days.
| Field | What to write in it |
|---|---|
| Clock length | The number exactly as the quote states it |
| Unit | Business days or calendar days, in its own column |
| Start event | The event the quote names, such as completing placement of the material |
| Source link | The page the quote came from |
| Owner | The office role responsible, plus a backup |
| Due date | Filled in only after the start event has happened |
Record the events that start the clocks as they happen. Those include the date the placement of the material is completed, the date of the topographic survey, the date an invoice is received, the date a prime contractor receives payment from a municipality and the date an audit is completed; the quote does not name a start event for the 14-day waiting period. Write each entry when the event happens, not later from recollection.
If a start event has not happened yet, leave the due date blank rather than estimating it. A date entered from a guess can look like a confirmed deadline, and it is easy to forget that it was never checked against an event.
Check the linked source again when a manual, statute or permit is updated. A number written into the calendar earlier may need comparing with the current page, and the link is what makes that comparison possible.
Assign an owner to each clock
Assign one person in the office to each clock, so every deadline has someone watching it. The office member who handles invoices and the one who handles subcontractor payments may be different people, so split responsibility by clock rather than by job. Write each owner's role next to the entry, along with a backup for the days when the owner is out.
| Clock | Owner role | Backup |
|---|---|---|
| Caltrans 5 business days, placement | Contractor-facing reviewer | Second reviewer |
| Minnesota 10 days, invoice notice | Office member who handles invoices | Second reviewer |
| Minnesota 10 days, subcontractor payment | Office member who handles subcontractor payments | Second reviewer |
| EPA 14 days, incomplete NOI | Operator-side coordinator | Second reviewer |
Review the list at a set time each week. A clock that is approaching should not depend on someone remembering to look, and a short weekly review gives every owner a fixed point to check the dates they are responsible for.
Not legal or tax advice.
More guides
Questions readers ask
What is a paperwork clock?
A paperwork clock is the number of days a rule gives you to send, answer, or pay a document on a public or permitted job. The clock starts from a specific event that the rule itself names, and the deadline comes from the rule that governs that step, not from the job.
How many days does a contractor have to submit a form after completing placement of the material under Caltrans?
Under the California Department of Transportation's construction manual, the contractor submits the form to the resident engineer at NOA@dot.ca.gov within 5 business days of completing placement of the material. Note this counts business days, not calendar days.
What is the second 5-business-day Caltrans deadline, and where does that form go?
The same section sets a second 5-business-day deadline after the topographic survey. The contractor submits the form to the resident engineer and by email to ADL@dot.ca.gov — a different address than the first submission.
How long does a municipality have to notify a vendor about an incorrect invoice in Minnesota?
Under Minnesota Statutes section 471.425, if an invoice is incorrect, defective, or otherwise improper, the municipality must notify the vendor within 10 days of the date the invoice is received.
Does the 10-day invoice notice deadline also apply to payment?
No. The 10-day clock covers only the notice about an improper invoice. The payment period sits in a separate sentence of the same statute, and the quote for it does not give a number of days, so the 10-day notice should not be read as the payment deadline.
How does an audit affect the payment period under the Minnesota statute?
For a negotiated contract or agreement that requires an audit by the municipality before acceptance and payment of the vendor's invoice, the standard payment period does not begin until the municipality completes the audit. Both conditions must hold: the contract must be negotiated, and it must require the audit.