Compliance

Construction compliance calendar: what is due when

A compliance calendar organized by rhythm, not by document type. What is due weekly, monthly, annually, and on a multi-year cycle, plus the obligations that start a clock only when something happens.

On this page
  1. What compliance obligations does a construction contractor have and when are they due?
  2. What compliance tasks are due every week?
  3. What compliance tasks are due every month?
  4. Which compliance obligations are triggered by an event rather than a date?
  5. What compliance obligations come due once a year?
  6. Which compliance obligations run on a multi-year cycle?
  7. What does the full construction compliance calendar look like?
  8. Which deadlines are set by regulation and which are set by your contract?
  9. What happens if you miss one of these deadlines?
  10. What this calendar does not cover
  11. How does Contracts Connected keep these dates from slipping?
  12. Frequently asked questions

What compliance obligations does a construction contractor have and when are they due?

A construction compliance calendar is the schedule of recurring obligations a contractor must meet to stay in good standing on its contracts: certified payroll weekly, pay applications and insurance checks monthly, OSHA and certification filings annually, and a set of clocks that start only when something happens, like a hire, a subcontract award, or an injury. Those five rhythms cover nearly everything a contract administrator is accountable for.

Organizing the year by rhythm rather than by document type is the whole point. Most compliance reference material is filed by form number, which is useful when you already know what you are looking for and useless on a Monday morning when the real question is what is due this week. A calendar answers the Monday question. The scale is not small: federal agencies obligated more than $30.6 billion to commercial and institutional building construction alone in fiscal year 2025, according to prime award data published on USAspending.gov, and every one of those contracts carries a recurring obligation set on top of the work itself.

One warning before the detail. The deadlines below split into two kinds, and confusing them is the most common way a calendar fails. Some are fixed by regulation and are the same for every contractor in the country. Others are set by your specific contract, your subcontract, or your state, and no federal number exists for them. This page marks which is which every time, and it never guesses at the second kind.

What compliance tasks are due every week?

Three things run weekly on most jobs: certified payroll submission on prevailing wage work, an apprentice-to-journeyworker ratio check on the crews actually on site, and entry of any recordable injury onto the OSHA 300 log. Daily reports also roll up on a weekly cycle on most projects, though that timing is set by the contract rather than by a rule.

Certified payroll is the one with a hard federal clock, and it is the one most often misread. The obligation to submit is weekly under 29 CFR 5.5(a)(3)(ii)(A), which requires the contractor to submit certified payrolls “weekly, for each week in which any DBA- or Related Acts-covered work is performed.” The delivery deadline lives somewhere else entirely, in the Copeland Act regulation at 29 CFR 3.4(a), which requires each certified payroll to be delivered “within 7 days after the regular payment date of the payroll period.” Read that carefully: the seven days run from the regular payment date, not from the end of the work week. Firms that calendar it from the Friday the crew worked are giving themselves a deadline that does not match the rule.

The stakes on this one are not theoretical. In its 2023 Davis-Bacon rulemaking, the Department of Labor estimated there are “1.2 million workers on DBRA-covered contracts” and noted that “approximately 61,200 firms currently hold DBA contracts or subcontracts and approximately 91,700 firms perform on Related Act contracts.” Missing submissions carry a real remedy: under 29 CFR 5.5(a)(3)(iv), failure to submit the required records can cause suspension of further payment and “may be grounds for debarment action pursuant to § 5.12.”

The apprentice ratio check is weekly because crew composition changes weekly. Under 29 CFR 5.5(a)(4)(i)(C), the allowable ratio of apprentices to journeyworkers on the job site in any craft classification cannot exceed the ratio permitted under the registered program or the ratio applicable to the locality. The consequence is immediate and financial: any apprentice working on site in excess of the permitted ratio “must be paid not less than the applicable wage rate on the wage determination for the work actually performed.” That is a retroactive full-rate liability created by a staffing decision, which is why it belongs on a weekly check rather than an annual audit.

The injury log entry is also weekly in practice, because 29 CFR 1904.29(b)(3) gives you seven calendar days: “You must enter each recordable injury or illness on the OSHA 300 Log and 301 Incident Report within seven (7) calendar days of receiving information that a recordable injury or illness has occurred.” See certified payroll review checklist for primes→ for the review mechanics that sit under the weekly submission.

What compliance tasks are due every month?

The monthly cycle is built around the pay application and everything that has to travel with it: the payment request itself, the supporting lien waivers, a conditional waiver exchange with subcontractors, a subcontractor compliance status review, and an insurance expiration look-ahead for the next 30 to 60 days. Almost all of the monthly timing is contract-driven rather than regulation-driven, with two important federal exceptions.

The first exception is the payment clock on federal construction work. FAR 52.232-27(a)(1)(i)(A) sets the due date for a progress payment at 14 days after the designated billing office receives a proper payment request, and FAR 52.232-27(a)(2) requires the billing office to return an improper invoice within 7 days after receipt. The second exception runs downhill and is the one primes get caught by: FAR 52.232-27(c)(1) requires the prime to include a clause in each subcontract obligating it to pay the subcontractor “not later than 7 days from receipt of payment out of such amounts as are paid to the Contractor under this contract.” Seven days, from receipt, not from whenever the accounting run happens to fall.

Insurance is the other item that genuinely belongs on a monthly look-ahead, because certificates expire on their own schedule and nobody tells you. FAR 52.228-5(c) requires the contractor to “maintain a copy of all subcontractors’ proofs of required insurance” and make copies available to the contracting officer on request, and FAR 52.228-5(b) means a cancellation or adverse material change is not effective until at least 30 days after written notice to the contracting officer. That 30-day window is the only warning you are structurally guaranteed, and it is only useful if somebody is looking. See additional insured endorsement verification checklist→ and COI endorsement requirements by project type→ for what to check when a certificate comes in.

Everything else in the monthly cycle is yours to define. Pay application cutoff dates, the specific lien waiver form, whether waivers are conditional or unconditional, retainage percentage and release triggers, and the cadence of subcontractor compliance review are all set by the contract, the subcontract, or state law. There is no federal monthly number for any of them, and any page that gives you one is making it up. See retention release tracker→ and federal prompt payment compliance checklist→.

Which compliance obligations are triggered by an event rather than a date?

Five events start their own clocks: a new hire, a new subcontract award, a change order, an incident on site, and contract completion. These are the obligations that break most calendars, because they cannot be scheduled in advance and they are frequently the shortest deadlines a contractor faces.

A new hire starts the fastest clock on the list. Under 8 CFR 274a.2(b)(1)(i)(A), the employee completes Form I-9 Section 1 at the time of hire, and under 8 CFR 274a.2(b)(1)(ii) the employer must complete Section 2 within three business days of the hire. Construction has a wrinkle most industries do not: 8 CFR 274a.2(b)(1)(iii) provides that an employer who hires someone for a duration of less than three business days must complete both at the time of hire, which matters on short-call and day-labor work. On contracts carrying FAR 52.222-54, E-Verify adds its own set: enroll as a federal contractor “within 30 calendar days of contract award,” initiate verification of new hires “within 3 business days after the date of hire,” and verify employees assigned to the contract within 90 calendar days after enrollment or 30 calendar days of assignment, whichever is later. Wage classification has to be settled before the first payroll runs, not after it is questioned.

A new subcontract award triggers the collection set: insurance certificates and endorsements, bonds where required, a W-9, license verification for the trade and the state, and execution of the required flow-down clauses. The specific limits, forms, and bond amounts are contract-specific and come from the prime contract and the subcontract. The one federal anchor is FAR 52.228-5(c), which requires the prime to insert the substance of the insurance clause into subcontracts for work on a government installation and to keep every subcontractor’s proof of insurance retrievable.

A change order re-opens two questions people forget to re-ask: whether the existing insurance limits are still adequate for the changed scope, and whether the bond needs a rider to cover the increased contract value. Both are contract-specific determinations. Neither happens automatically.

An incident on site carries the shortest deadlines in all of construction compliance, and they are measured in hours. Under 29 CFR 1904.39(a)(1), a work-related fatality must be reported to OSHA within eight hours. Under 29 CFR 1904.39(a)(2), an in-patient hospitalization, an amputation, or the loss of an eye must be reported within 24 hours. There is a reportability boundary at 29 CFR 1904.39(b)(6): a fatality is reportable only if it occurs within 30 days of the incident, and a hospitalization, amputation, or eye loss only if it occurs within 24 hours of the incident.

Contract completion starts the closeout sequence, and one federal item has a hard number attached. Under FAR 52.219-9(l)(1)(i), where an individual subcontracting plan applies, a report is required “for each contract within 30 days of contract completion.” Separately, when a past performance evaluation lands, FAR 42.1503(d) gives the contractor “up to 14 calendar days from the date of notification of availability of the past performance evaluation to submit comments, rebutting statements, or additional information.” Fourteen days is short, the notification arrives without warning, and an uncontested evaluation follows the company into every future source selection. See federal closeout binder checklist→.

What compliance obligations come due once a year?

The annual set is the densest part of the calendar and the one most often discovered late: OSHA summary posting and electronic submission, tax filings for paid subcontractors, SAM.gov registration and representations renewal, veterans and equal opportunity reporting, affirmative action program updates where they still apply, subcontracting plan reports, past performance evaluations, program recertifications, and insurance, license, and prequalification renewals.

Start with OSHA, because it has the cleanest fixed dates in the whole calendar. The regulation states the posting window directly:

“You must post the summary no later than February 1 of the year following the year covered by the records and keep the posting in place until April 30.”

29 CFR 1904.32(b)(6)

That is a window, not a date. Taking the 300A down in March is a violation in its own right. Electronic submission is separate and later: 29 CFR 1904.41(c) requires covered establishments to submit “by March 2 of the year after the calendar year covered by the form(s).” Which establishments are covered is worth checking against your own headcount, because construction sits in both tiers. NAICS 23, construction, is listed in Appendix A to subpart E, so establishments with 20 to 249 employees submit Form 300A data. Establishments with 250 or more employees also submit 300A. Only one construction code appears in Appendix B, NAICS 2381, foundation, structure, and building exterior contractors, and those establishments with 100 or more employees must also submit Forms 300 and 301.

The safety obligations behind those filings are not a formality in this industry. In OSHA’s list of the top 10 most frequently cited standards for fiscal year 2025, covering October 1, 2024 to September 30, 2025, five of the ten are construction standards, and fall protection general requirements at 29 CFR 1926.501 ranked first.

Tax. Form 1099-NEC for paid subcontractors is due on or before January 31. The IRS instructions state it plainly: “Section 6071(c) requires you to file Form 1099-NEC on or before January 31, using either paper or electronic filing procedures.” Form 1099-MISC runs later, by February 28 on paper or March 31 electronically.

SAM.gov. This one is annual but anniversary-based, which is why it slips. FAR 52.204-13(b) requires the contractor “to review and update on an annual basis, from the date of initial registration or subsequent updates, its information in SAM.” FAR 4.1201(b)(1) adds that representations and certifications must be reviewed and updated at least annually and “are effective until one year from date of submission or update to SAM.” There is no national due date. Your due date is twelve months from the last time somebody touched the record, and a lapse can cost you an award.

Veterans reporting. VETS-4212 is due annually and the regulation gives a fixed date: 41 CFR 61-300.10(c) provides that “VETS-4212 Reports must be filed no later than September 30 of each year following a calendar year in which a contractor or subcontractor held a covered contract or subcontract.” Coverage starts at a contract or subcontract of $100,000 or more, and 41 CFR 61-300.1(a) names construction expressly. The data ending date is chosen from a pay period during July 1 through August 31 under 41 CFR 61-300.10(d)(1), so the data pull is a separate task from the filing.

EEO-1. This one is genuinely in motion right now, and any calendar that states it flatly is out of date. The standing rule at 29 CFR 1602.7 requires employers subject to Title VII with 100 or more employees to file the EEO-1, and the regulation’s stated date is on or before September 30 of each year. In practice the EEOC announces the actual collection window each year and it has recently differed from that date, so confirm the current window rather than working from the regulation alone. More significantly, on July 23, 2026 the EEOC published a proposed rule to rescind and remove the EEO-1 filing requirement from 29 CFR part 1602, with comments closing August 24, 2026. It is a proposed rule, so the obligation stands until a final rule says otherwise, but this is a line item to re-check before you rely on it.

Affirmative action programs. Executive Order 11246 was revoked by Executive Order 14173 on January 21, 2025, which stated that “Executive Order 11246 of September 24, 1965 (Equal Employment Opportunity), is hereby revoked” and allowed contractors 90 days to continue complying with the prior regulatory scheme. The Department of Labor proposed rescinding the implementing regulations on July 1, 2025 and extended the comment period in September 2025; no final rule has issued. What did not go away is the statutory pair. Section 503 of the Rehabilitation Act and VEVRAA remain, and their regulations still require annual maintenance: 41 CFR 60-741.40(b)(3) requires the disability affirmative action program to be “reviewed and updated annually,” and 41 CFR 60-300.40(c) requires the same for protected veterans. Both attach at 50 or more employees, at $50,000 for Section 503 and $100,000 for VEVRAA, and both require the program to be prepared within 120 days of the commencement of a contract.

Subcontracting plan reports. Under FAR 52.219-9(l)(1)(i), the Individual Subcontract Report is submitted semiannually for the periods ending March 31 and September 30, due 30 days after the close of each reporting period. The Summary Subcontract Report is annual: “The report shall be submitted annually by October 30 for the twelve month period ending September 30.” Both are filed through eSRS.

Past performance. FAR 42.1502(a) provides that “past performance evaluations shall be prepared at least annually and at the time the work under a contract or order is completed,” which means a CPARS evaluation is an annual event on every contract over the simplified acquisition threshold, not just a closeout event.

Program recertifications. An 8(a) participant owes an annual review submission to its servicing SBA district office under 13 CFR 124.112(b), including a certification that it still meets program eligibility and that no changed circumstances have arisen. A CMMC Level 1 organization must “conduct a Level 1 self-assessment on an annual basis and submit the results in SPRS” under 32 CFR 170.15(a)(1).

Renewals. Insurance, contractor licenses, and prequalification packages all renew annually in most cases, and every one of those dates is set by a carrier, a state licensing board, or a customer rather than by federal rule. They are the single most common cause of a lapse, because nothing in the federal system reminds you. See contractor license verification checklist, state by state→.

Records retention review also belongs on the annual list, as the moment you determine which files have aged past their required holding period and become eligible for destruction. The retention periods themselves vary by document type and by the rule that governs each one, and they run from events like final payment or contract completion rather than from the calendar year.

Which compliance obligations run on a multi-year cycle?

Three categories run longer than a year: set-aside program terms, security assessment cycles, and records retention expiry. They are easy to ignore precisely because they never come due in the current year, right up until the year they do.

The 8(a) Business Development program term is the clearest example. Under 13 CFR 124.2(a), “a Participant receives a program term of nine years from the date of SBA’s approval letter certifying the concern’s admission to the program.” Nine years from an approval letter is a date that lives in a filing cabinet, not in anyone’s calendar, and the business planning that has to happen before graduation needs to start years ahead of it.

CMMC runs on a three-year cycle with an annual overlay, which is an easy pattern to get half right. Under 32 CFR 170.16(a)(1), an organization holding Level 2 (Self) status “must conduct a Level 2 self-assessment every three years and submit the results in SPRS.” Under 32 CFR 170.17(a)(1), a Level 2 certification assessment “must be completed within three years of the CMMC Status Date.” Both levels then require an affirmation “at the time of each assessment, and annually thereafter,” under 32 CFR 170.16(a)(2) and 170.17(a)(2). The assessment is triennial; the affirmation is annual; missing the annual affirmation is enough to break the status even when the assessment is current.

The scale of that program is worth knowing before assuming it does not apply. In the CMMC program final rule published October 15, 2024, the Department of Defense reported that “DoD awards an average of 1,366,262 contracts and orders per year that contain DFARS clause 252.204-7012, to 31,338 unique awardees, of which 683,718 awards (50%) are made to 23,475 small entities.” See CMMC compliance software for contractors→ for the tooling side, and note that whether CMMC applies to you at all is a scoping question that turns on whether you handle federal contract information or controlled unclassified information.

Records retention is the third multi-year clock. The relevant point for a calendar is structural rather than numerical: retention periods on federal work generally run from an event such as final payment or completion of all work on the prime contract, not from the date the document was created. That means a record generated in year one of a five-year job stays live well past the end of the job, and the destruction-eligibility date cannot be computed until the triggering event actually happens.

What does the full construction compliance calendar look like?

The table below is the calendar itself. Every row lists what is due, how often, what starts the clock, the rule that sets it, and what happens if it slips. Rows marked “contract-specific” have no federal deadline; the number comes from your contract, your subcontract, or your state.

ObligationCadenceTriggerGoverning citationConsequence of missing
WEEKLY
Certified payroll submissionWeeklyAny week in which covered work is performed29 CFR 5.5(a)(3)(ii)(A); delivery within 7 days after the regular payment date, 29 CFR 3.4(a)Suspension of further payment; may be grounds for debarment under 29 CFR 5.5(a)(3)(iv) and § 5.12
Apprentice to journeyworker ratio checkWeeklyCrew composition on site29 CFR 5.5(a)(4)(i)(C)Apprentices over the permitted ratio must be paid the full wage determination rate for work actually performed
Recordable injury entered on OSHA 300 logWithin 7 calendar daysReceiving information that a recordable case occurred29 CFR 1904.29(b)(3)Recordkeeping violation; incomplete log at the annual certification
Daily report roll-upWeekly in practiceProject scheduleContract-specificLoss of contemporaneous record for delay, claim, and change order support
MONTHLY
Pay application submissionMonthlyBilling cycle in the contractContract-specificPayment cycle missed by a full period
Federal progress payment due date14 days after receiptDesignated billing office receives a proper payment requestFAR 52.232-27(a)(1)(i)(A)Interest penalty accrues to the contractor
Payment down to subcontractorsWithin 7 days of receiptPrime receives payment from the governmentFAR 52.232-27(c)(1)Interest penalty owed to the subcontractor under the required subcontract clause
Lien waiver exchange, conditional and unconditionalMonthly with the pay applicationPayment application and receiptContract-specific and state-specificPayment withheld; waiver rights and lien rights affected under state law
Subcontractor compliance status reviewMonthlyActive subcontractsContract-specificNon-compliant subcontractor continues working and billing
Insurance expiration look-aheadMonthly, 30 to 60 days forwardCertificate expiration datesFAR 52.228-5(b) and (c) on federal work; otherwise contract-specificUninsured subcontractor on site; prime cannot produce proof on request
PER EVENT
Form I-9 Section 1At the time of hireNew hire8 CFR 274a.2(b)(1)(i)(A)Civil penalties for paperwork violations
Form I-9 Section 2Within 3 business days of hireNew hire8 CFR 274a.2(b)(1)(ii); at time of hire if the job is under 3 business days, (b)(1)(iii)Civil penalties for paperwork violations
E-Verify enrollmentWithin 30 calendar days of awardContract carrying the E-Verify clauseFAR 52.222-54(b)(1)(i)Contract non-compliance on an express clause
E-Verify new hire queryWithin 3 business days after date of hireNew hireFAR 52.222-54(b)(1)(ii) and (b)(2)(i)(A)Contract non-compliance on an express clause
Wage classification set for a new workerBefore the first payrollNew hire on prevailing wage work29 CFR 5.5(a)(1)Misclassification creates back wage and interest liability
Subcontract compliance package: insurance, bonds, W-9, license, flow-downsAt award, before mobilizationNew subcontract awardContract-specific; insurance flow-down on government installations at FAR 52.228-5(c)Unverified subcontractor on site; flow-down gap discovered at audit
Insurance adequacy and bond rider re-checkAt executionChange order altering scope or valueContract-specificCoverage or bond penal sum no longer matches the contract value
Mobilization compliance verificationBefore work beginsProject startContract-specificWork performed by an unverified party
Fatality reported to OSHAWithin 8 hoursWork-related fatality within 30 days of the incident29 CFR 1904.39(a)(1); reportability limit at (b)(6)Citation and penalty for late reporting
Hospitalization, amputation, or loss of an eye reportedWithin 24 hoursEvent within 24 hours of the incident29 CFR 1904.39(a)(2); reportability limit at (b)(6)Citation and penalty for late reporting
Individual Subcontract Report at completionWithin 30 days of contract completionContract completion under an individual subcontracting planFAR 52.219-9(l)(1)(i)Non-compliance with the subcontracting plan clause
CPARS evaluation responseWithin 14 calendar days of notificationAgency issues a past performance evaluationFAR 42.1503(d)Uncontested evaluation follows the company into future source selections
Closeout sequenceAt completionProject completionContract-specific and agency-specificFinal payment and retainage release delayed
ANNUAL
OSHA 300A summary postedFebruary 1 through April 30Prior calendar year of records29 CFR 1904.32(b)(6)Recordkeeping citation, including for early removal
OSHA electronic submission of injury dataBy March 2Prior calendar year; establishment size and NAICS determine scope29 CFR 1904.41(c); Appendices A and B to subpart ERecordkeeping citation
Form 1099-NEC for paid subcontractorsOn or before January 31Prior tax year paymentsIRC § 6071(c), per IRS instructionsInformation return penalties
SAM.gov registration and reps and certs refreshAnnually, on the registration anniversaryDate of initial registration or last updateFAR 52.204-13(b); FAR 4.1201(b)(1)Registration lapses; ineligible for award
VETS-4212 reportNo later than September 30Held a covered contract or subcontract of $100,000 or more41 CFR 61-300.10(c); scope at 61-300.1(a)Non-compliance with the reporting clause
EEO-1 filingAnnually, window announced by the EEOC100 or more employees, subject to Title VII29 CFR 1602.7; note the EEOC proposed rescission published July 23, 2026Enforcement action; confirm current status before relying
Section 503 affirmative action program updateAnnually50 or more employees and a contract of $50,000 or more41 CFR 60-741.40(b)(3); program due within 120 days of contract commencementProgram must be produced to OFCCP within 30 days of request
VEVRAA affirmative action program updateAnnually50 or more employees and a contract of $100,000 or more41 CFR 60-300.40(c); program due within 120 days of contract commencementProgram must be produced to OFCCP within 30 days of request
Individual Subcontract ReportSemiannually, periods ending March 31 and September 30, due 30 days after closeContract with an individual subcontracting planFAR 52.219-9(l)(1)(i)Non-compliance with the subcontracting plan clause
Summary Subcontract ReportAnnually by October 30 for the 12 months ending September 30Subcontracting plan in placeFAR 52.219-9(l)(2)(D)Non-compliance with the subcontracting plan clause
CPARS past performance evaluationAt least annuallyContract over the simplified acquisition thresholdFAR 42.1502(a)Gap in the past performance record used in future source selections
8(a) annual review submissionAnnuallyParticipation in the 8(a) BD program13 CFR 124.112(b)Termination or early graduation from the program
CMMC Level 1 self-assessmentAnnuallyLevel 1 status required by contract32 CFR 170.15(a)(1)Loss of status; ineligible for awards requiring it
Insurance renewalAnnuallyPolicy periodContract-specific and carrier-specificCoverage lapse; contract default exposure
Contractor license renewalAnnually or per state cycleState licensing board cycleState-specificUnlicensed work; several states bar recovery entirely
Prequalification refreshAnnually or per customer cycleCustomer requirementContract-specificRemoved from bid lists
Records retention review and destruction eligibilityAnnuallyRecords that have passed their retention periodVaries by document type; clocks generally run from final payment or completionPremature destruction of records still required, or indefinite storage of records that could be released
MULTI-YEAR
8(a) program termNine years from SBA approval letterAdmission to the program13 CFR 124.2(a)Graduation without a transition plan in place
CMMC Level 2 self-assessmentEvery three yearsLevel 2 (Self) status32 CFR 170.16(a)(1)Loss of status
CMMC Level 2 certification assessmentWithin three years of the CMMC Status DateLevel 2 (C3PAO) status32 CFR 170.17(a)(1)Loss of status
CMMC annual affirmationAt each assessment and annually thereafterAny CMMC Level 2 status32 CFR 170.16(a)(2); 170.17(a)(2)Status broken even when the assessment is current
Records retention expiryVaries, commonly multi-yearFinal payment or completion of all workVaries by document typeRecords destroyed while still required, or produced late because they were archived rather than indexed

Which deadlines are set by regulation and which are set by your contract?

Regulation sets the deadlines that are the same for every contractor in the country: certified payroll timing, OSHA posting and reporting, I-9 and E-Verify windows, SAM.gov renewal, VETS-4212, subcontracting plan reports, CPARS response, program terms, and assessment cycles. Your contract, your subcontract, and your state set almost everything in the monthly cycle, plus insurance limits, bond amounts, retainage, licensing, and prequalification.

The distinction matters more than it sounds. A regulatory deadline can be calendared once, company-wide, and it will be right for every project you run. A contract-specific deadline has to be read off the actual document, project by project, and it changes when the contract changes. Firms that build one company calendar and stop there end up compliant on the federal items and exposed on the contract items, which is the more common failure mode by a wide margin, because the contract items are the ones tied to getting paid.

There is also a third category worth naming: obligations that exist but whose timing is genuinely unsettled. The EEO-1 is sitting in that category as of this writing, with a live proposed rescission. The right treatment for anything in that state is to keep it on the calendar with a re-check date attached, not to remove it and not to assume last year’s window repeats.

What happens if you miss one of these deadlines?

The consequences fall into four buckets: money withheld, penalties assessed, status lost, and a record you cannot produce later. Which one you get depends on the obligation, and the table above lists the specific consequence for each row.

Withholding is the most immediate. Davis-Bacon non-compliance can cause suspension of further payment under 29 CFR 5.5(a)(3)(iv), and a late payment down to a subcontractor triggers an interest penalty under the clause the prime was required to insert. Penalties attach to the OSHA reporting and recordkeeping items and to information returns. Status loss is the quietest and most expensive: a lapsed SAM.gov registration makes you ineligible for award, a missed CMMC affirmation breaks a status you already paid to earn, and a missed 8(a) annual review can end program participation.

The fourth bucket is the one nobody budgets for. An uncontested CPARS evaluation, a certified payroll that was never submitted, or a flow-down that cannot be evidenced does not hurt on the day it is missed. It hurts eighteen months later, in a source selection, an audit, or a dispute, when the record that would have settled the question does not exist. That is why a compliance calendar is worth building even for obligations that carry no immediate penalty.

What this calendar does not cover

This page is a calendar, not a manual, and there are four things it deliberately does not do.

It does not tell you how to complete any of these documents. It tells you when they are due and what rule sets that date. The mechanics of a certified payroll review, an endorsement check, or a closeout binder live in the linked resources.

It does not cover state and local obligations in any systematic way. Licensing cycles, lien and notice deadlines, retainage rules, prompt payment statutes, workers compensation reporting, and local business licensing all vary by jurisdiction, and several of them carry deadlines shorter than anything on this page. A contractor working in more than one state needs a state layer on top of this one.

It does not reproduce retention periods. Those vary by document type and run from events rather than dates, and getting them right requires working through each document class against the rule that governs it.

Most importantly, it does not replace reading your contract. The solicitation and the contract routinely add obligations beyond the statutory baseline: agency-specific reporting, submittal schedules, small business participation reporting, safety plan updates, quality control documentation, and certifications that exist only because someone wrote them into Section H. Those are as binding as anything in the CFR, they are frequently on tighter cycles, and no general reference page can know what is in your particular contract. Where an obligation is unclear or where the consequence of a miss would be material, the contracting officer and qualified counsel are the right sources, not a web page.

How does Contracts Connected keep these dates from slipping?

Contracts Connected exists because knowing the deadline was never the hard part. The hard part is that the deadlines attach to documents that arrive from different places, sit in different systems, and expire without telling anyone. The platform reads certificates of insurance, certified payroll, W-9s, and license records as they come in, tags each one to the contract, the subcontractor, and the requirement it satisfies, and surfaces the expirations and gaps before they turn into a missed date.

That turns the monthly insurance look-ahead from someone opening a folder into a list that is already built, and it turns a document request into a search rather than a reconstruction project. Our co-founder ran a large federal general contracting firm for 15 years, about 100,000 documents a year. See subcontractor compliance software→, subcontractor compliance automation→ and compliance software for federal GCs→.

Frequently asked questions

What compliance obligations does a construction contractor have and when are they due?

They fall into five rhythms. Weekly: certified payroll on prevailing wage work, apprentice ratio checks, and injury log entries. Monthly: pay applications, lien waiver exchange, insurance expiration review. Per event: a new hire, a subcontract award, a change order, an injury, or contract completion each start their own clock. Annually: OSHA posting, tax filings, SAM.gov renewal, certification renewals. Multi-year: program terms and assessment cycles.

How often does certified payroll have to be submitted on a prevailing wage job?

Weekly, for each week in which covered work is performed, under 29 CFR 5.5(a)(3)(ii)(A). The delivery deadline is set separately by the Copeland Act regulation at 29 CFR 3.4(a), which requires the certified payroll to be delivered within 7 days after the regular payment date of the payroll period. That clock runs from the payment date, not from the end of the work week, which is the detail most firms get wrong.

When does the OSHA 300A annual summary have to be posted?

29 CFR 1904.32(b)(6) requires the summary to be posted no later than February 1 of the year following the year covered, and kept in place until April 30. It is a posting window, not a single date, so taking it down early is itself a violation. Separately, covered establishments must submit the data electronically by March 2 under 29 CFR 1904.41(c).

What compliance obligations are triggered by hiring a new employee?

Form I-9 Section 1 must be completed at the time of hire and Section 2 within three business days of the hire, under 8 CFR 274a.2(b)(1). If the job lasts less than three business days, both must be done at the time of hire. On contracts carrying FAR 52.222-54, E-Verify must be initiated within 3 business days after the date of hire. Wage classification has to be set before the first payroll.

How often does SAM.gov registration have to be renewed?

Annually, but on your own anniversary rather than a fixed calendar date. FAR 52.204-13(b) requires the contractor to review and update its SAM information on an annual basis from the date of initial registration or subsequent updates. FAR 4.1201(b)(1) adds that representations and certifications are effective only until one year from the date of submission or update, so both clocks run from when you last touched the record.

Which compliance deadlines come from the contract rather than from a regulation?

Most of the monthly cycle. Pay application cutoff dates, lien waiver forms and exchange timing, retainage percentages and release triggers, subcontractor insurance limits, bond amounts, prequalification refresh intervals, and daily report timing are all set by the contract, the subcontract, or state law rather than by a federal rule. There is no national number for any of them, which is why they belong on a project calendar rather than a company one.

Contracts Connected is the Back-Office System (BOS) for construction.

See what it would take off your plate.

SOC 2 Type II · U.S. hosted · AI optional
Book a demo