Straight into the service manual page
WrenchQuarry
More

Public job deadlines: 5 day counts for your calendar

WrenchQuarry Editorial Team · Published · 12 min read · How these guides are written

Five public-job deadlines are counted in days from events such as a payment request, full contract execution or a wage determination. If you bid or work public jobs, some of the most important dates are not on the bid sheet. One belongs to an agency that owes you information about a payment. Another sits on a contract before it is signed. Another depends on when a wage determination was issued. Each one is counted in days, and a missed day can mean a late answer, a contract you never got to review, or a crew paid against an out-of-date rate.

Key takeaways

  • Count each deadline from its own starting event, not from the day you sent a request.
  • Put the issuance date and the effective date of each California determination on the calendar as separate entries.
  • Read the full section to confirm whether "days" means calendar days before you count.
  • Keep the official source link beside every entry, and give each entry one owner.

This post covers five of those day counts. The sources come from Minnesota, California and the federal government, and those rule sets are not the same. Your state, city or agency may use other numbers or other rules entirely. Read each item as an example of the kind of date to look for, then check the rule that governs your job before you rely on it.

Why these dates belong on one calendar

Public work usually spreads its dates across several people. The estimator tracks the bid, the office tracks invoices, the foreman tracks the start date, and the owner may be the only person who remembers that a payment request starts a response clock. When a date lives in one inbox, the people who need it most often never see it.

A shared calendar fixes most of that. Give it one owner, make it visible to everyone who touches a job, and add each date as soon as you learn it rather than when it becomes urgent. An entry that says "Agency response due" is easy to ignore. An entry that says "Agency must answer our written payment request. If nothing arrives, call the contact in the file" tells the reader what to do on that day. For the handoff side of this, see Field Service Work Order Checklist for Dispatch Handoffs.

Save the source with every entry. Rules get amended, and a date copied from memory can drift from the text. Keep the link to the official page next to the entry so anyone checking can read the wording themselves. For the five items in this post, those pages are the Minnesota statutes, the California determinations page and the federal acquisition subpart linked below. To check that a rule is still in force, see Confirm a rule is still in force: 3 government sources.

Count days the way the rule counts them

Before you put a date on the calendar, find out what kind of day the rule uses. Two of the five rules below say calendar days outright: the seven-day payment clock and the 180-day wage determination period. Calendar days include weekends and holidays. The other three rules say "days" without saying which kind, so read the full section before you count them. Do not guess.

The starting point matters just as much. Each rule counts from a different event, and counting from the wrong one is an easy mistake:

  • The seven-day clock starts when the agency receives your written request, not when you sent it.
  • The fifteen-day window runs back from full execution of the procurement contract.
  • The thirty-day window runs from the effective date of a guaranteed energy-savings contract.
  • The California ten-day period runs from the date the general determinations are issued.
  • The 180-day period runs from the date of the determination.

When a clock is tied to an event you do not control, such as the agency getting your request, log that event on the day it happens. A calendar cannot count back from a date nobody wrote down.

Illustrative example: counting two deadlines

A subcontractor's written payment request reaches the agency on day 0. The seven-day calendar entry for the agency's answer goes on day 7. Separately, a procurement contract is expected to be fully executed on day 30, so the back-count entry for the 15-day data deadline goes on day 15. Each entry carries its source link, and one owner reviews both at the weekly check.

The five deadlines side by side

The table puts the five deadlines in one place. Each row follows the wording of its source. The sections after it explain how to act on each one.

#DeadlineCounted fromWhat the quoted rule saysSource
1Seven calendar daysAgency receives a written requestAgency must provide payment information to a contractor or subcontractor of any tier who can document participationMinn. Stat. 15.72
2At least 15 daysFull execution of the procurement contractData described in section 13.591, subdivision 3 or 4, must be in hand at least 15 days before full executionMinn. Stat. 471.345
3Within 30 daysEffective date of a guaranteed energy-savings contractMunicipality sends the contract and the qualified provider's report to the commissioner of commerceMinn. Stat. 471.345
4Ten days after issuanceIssuance on February 22 or August 22General determinations take effect: March 4 (non-leap year) or March 3 (leap year) for February 22 issuances; September 1 for August 22 issuancesCalifornia DIR
5180 calendar daysDate of the determinationA wage determination used only when no general wage determination applies is effective for this periodFAR Subpart 22.4

The rows are not all the same kind of deadline. Some bind an agency or municipality, some set when rates take effect, and one sets how long a wage determination stays effective. Track them as separate entries so nobody confuses a deadline you must meet with one someone else must meet.

Deadline 1: seven calendar days to answer a payment request

Minnesota's rule on payment information for public improvement projects gives a contractor or subcontractor a way to ask about money. The statute says that, on written request from a contractor or subcontractor of any tier that can provide documentation of participating in the project, the public contracting agency must provide information about any progress payment, retainage payment, final payment or other payment it made. Minn. Stat. 15.72

The clock is in subsection (c). The agency must provide the requested information within seven calendar days of receiving the request. Minn. Stat. 15.72

Subcontractors have a separate line. The agency must make available to subcontractors the contact information for the agency's payment information. That matters for a sub who has no direct line to the agency's finance staff. Ask the agency for that contact, or ask your prime, and file it in the job folder.

In practice, the steps are simple:

  • Before you send a request, confirm you can show participation in the project. The statute depends on documentation, so keep the contract, work orders and daily logs in one place.
  • Send the request in writing and record the day the agency receives it. Put day seven on the calendar from that date.
  • If the day passes with no information, log it, follow up in writing and tell whoever handles disputes in your firm.

The statute sets the deadline. What follows a missed day is a question for someone who advises your firm on public contracts, so check with them before you decide on next steps.

Deadline 2: fifteen days before full execution

Minnesota Statutes section 471.345 includes a rule about access to information. It says that reasonable access to necessary information, along with a reasonable opportunity to seek relief, includes having the data described in section 13.591, subdivision 3 or 4, in hand at least 15 days prior to full execution of the procurement contract. Minn. Stat. 471.345

Two things stand out. First, this deadline is measured backward from a future date, full execution. Second, it is tied to when the data arrives, so the data has to be in hand 15 days before full execution. Asking for it is not enough. Do not assume this applies only to energy-savings contracts.

For the calendar, that means:

  • You may not know the execution date when you first see a job. When you learn a likely date, add a back-count entry that subtracts 15 days, and keep it marked as provisional until then.
  • Look up section 13.591, subdivisions 3 and 4, before you ask for the data, so your request names the right category of data.
  • Make the request in writing so the date it arrives is on record.
  • If the execution date moves, move the back-count entry with it. A stale entry is worse than none, because people will trust it.

Deadline 3: thirty days after a guaranteed energy-savings contract takes effect

Minnesota's statute says that a municipality entering into a guaranteed energy-savings contract must provide a copy of the contract and the report from the qualified provider to the commissioner of commerce within 30 days of the effective date of the contract. Minn. Stat. 471.345

This is the municipality's duty, not yours. It still belongs on your calendar if your firm is part of an energy-savings project, because the filing sets a checkpoint you can confirm. Ask the municipality whether the copy and report went in, and note the answer with the date. Read the full section to see whether the days are calendar or business days before you count.

Practical points:

  • Start the count from the effective date written in the contract, not the signing date and not the day your crew first heard about the job.
  • Set one entry for the 30-day deadline and a follow-up entry before it, so the check happens while there is still time to act.
  • Keep copies of anything the municipality gives you, so the record is complete if a question comes up later.

Deadline 4: ten days after California's general wage determinations

The California Department of Industrial Relations says general determinations are issued twice a year, on February 22 and August 22, and take effect ten days after issuance. For determinations issued February 22, the effective date is March 4 in a non-leap year and March 3 in a leap year. For determinations issued August 22, the effective date is September 1. California DIR

Put both the issuance date and the effective date on the calendar. They are different days, and the gap between them is where estimates and payroll can fall out of step. Label each entry clearly, for example "issued" and "takes effect," so nobody reads one as the other. A job that runs across an effective date is the case to watch most closely. Note the date in the job file so the estimator and the payroll lead see it at the same time.

Check the leap-year rule when you set the February entry. The effective date for a February issuance depends on whether that year is a leap year, so the calendar entry should name the year it belongs to and carry the correct March date. Also note which determinations govern each job. That depends on the contract and the rule that applies, so confirm it with the contracting agency in writing.

Deadline 5: 180 calendar days for a wage determination

The labor standards subpart of the federal procurement rules says general wage determinations are published on the Wage Determinations at SAM.gov website. FAR Subpart 22.4 The same subpart says that a wage determination it describes as used only when no general wage determination applies is effective for 180 calendar days from the date of the determination. FAR Subpart 22.4

The rule is short, so the practical work is in the setup:

  • Count from the determination date itself, not from the day you downloaded it or the day someone forwarded it to you.
  • Put the 180-day end point on the calendar and set your own reminder lead time that gives your estimator enough room to act.
  • If a job runs past the end point, do not assume the old figures still apply, and do not assume they stop applying. Ask the contracting officer for the current determination in writing and file the answer.

Keep the calendar working

A calendar only helps if people trust it. Dispatchers and owners also read it for different reasons. A dispatcher needs to know which crew goes where and which paperwork must be ready before the crew arrives. An owner needs to know which payment and contract dates could affect cash flow. Build the calendar so each person can filter by job and by type of date, and make sure both views come from the same entries rather than two copies that drift apart.

A few habits keep it useful:

  • Review it at a set time each week, with the office and the field leads both looking at the same list.
  • Give each entry an owner. If an entry has no name beside it, it will not get done.
  • Add the contact for each deadline question, including the agency payment contact from the Minnesota subcontractor rule, so the person on the calendar knows who to call.
  • When a date changes, do not delete the old entry. Strike it through or note the change and the reason. That record protects you when someone asks what the schedule was and why it moved.
  • Re-check the source links regularly, and again after any change to the bid or the contract. A link that still works can still point to an older version of a rule.

For a checklist on tracking open deadlines through closeout, see Job file closeout: 6 steps to track deadlines.

These five dates are not a complete list for every job. They are a working set you can copy into your own calendar, then extend with the rules for your state, your agency and your contract.

Next step today: pick one open job, add its earliest deadline from this post to your shared calendar, and paste the official source link beside it.

Frequently asked questions

Who must meet the 30-day filing deadline?

The municipality is the party required to file, not your firm, but the filing still gives you a checkpoint you can confirm.

How should I log California determinations?

Add the issuance date and the effective date as two separate, clearly labelled entries.

Where should I check the wording of a rule?

Use the official page linked beside each deadline, and check it again after any change to the bid or the contract.

Who should own the shared calendar?

One named person should own it, and every entry should have its own owner so nobody is left guessing.

Sources

More field guides