Two dates show up on a FEMA Public Assistance desk, and contractors mash them together. The disaster declaration date is when an event lands on the PA map. The Project Worksheet obligation date is when FEMA reserved federal share against a specific applicant, facility, and category. They can be days apart. They are often months apart. Neither is a bid date.
This note is about which clock to use for outreach. Educational desk note from RebuildAlert, operated by Record of Sale, LLC. Not FEMA guidance, not legal advice, not a bid board. Questions: publisher@noticenearby.com (email only).
For what an obligation is, see what a PA obligation actually means. For what to do in the weeks after a worksheet appears, see procurement timing after a PA obligation. Here the subject is the two timestamps.
Two public clocks, two OpenFEMA datasets
RebuildAlert reads two OpenFEMA surfaces that contractors already know by other names.
Disaster Declarations Summaries v2 is where the declaration date lives: event, state, designated area, incident type, and whether the PA program is declared. That row is the watchlist signal — “this county is in a declared event.” It is not a project. It is not dollars. It is not a buyer.
Public Assistance Funded Projects Details v2 is where the obligation date lives, next to project title, category, federal share, county, and disaster number. Applicants v1 joins on applicantId and disasterNumber and adds the mailing address. That is the buyer signal.
Watch only declarations and you write too early. Watch only obligations and you miss that a county is in a declared event — and which disaster a later C–G worksheet belongs to.
Use both. Do not treat them as the same day.
What the declaration date is good for
The declaration date is a relationship and staffing clock, not a procurement clock.
Fair uses:
- Decide whether to put the county on a watch. If PA is declared, obligated worksheets will eventually show up in Funded Projects Details v2. That is when RebuildAlert’s digest has something to email.
- Open a thin file. Note the disaster number, incident type, and designated area. Do not send a “we do debris / roads / roofs” blast the morning the declaration hits the news.
- Staff the emergency window. Categories A and B often move while the declaration is still warm. Introduce who you are once, then wait for a worksheet.
- Explain a later obligation. When a Category C worksheet obligates months later, the declaration date says this is the same event.
Unfair uses:
- Treating declaration day as “they are advertising.”
- Treating declaration day as a SAM.gov listing. PA construction is usually bought by the applicant, not a federal contracting officer.
- Treating declaration day as an award or NTP. Nothing has been reserved against a facility yet.
A declaration without an obligated worksheet is a weather report with a FEMA stamp. Useful. Not a job.
What the obligation date is good for
The obligation date is when federal share attached to that Project Worksheet. It is the first public moment many out-of-town contractors have a named facility, a category, a federal-share number, and an applicant they can write.
Fair uses:
- Start the 30 / 60 / 90 reminder described in the timing note. The first letter names the disaster, the facility language, and the category. The follow-ups are where patience pays.
- Size the conversation. Pair the date with federal share. The federal share calculator on the tools page splits obligated dollars into federal versus implied non-federal remainder. Educational only — see federal share vs non-federal share.
- Write the applicant, not FEMA. The mailing address is a contact signal, not a procurement date. Obligation day is when that address becomes worth a specific letter.
Unfair uses — the same ones that show up every season:
- Obligation ≠ bid advertisement. The applicant may still be designing, waiting on match, or planning to use an on-call.
- Obligation ≠ award. FEMA reserved dollars for the applicant. Nobody selected a contractor.
- Obligation ≠ SAM.gov listing. A large federal share does not create a federal solicitation.
- Obligation ≠ NTP. Notice to proceed sits after local award, often months later on permanent work — and sometimes before the OpenFEMA timestamp on emergency work.
The obligation date is when the money attached. It is not when you mobilize.
Why the gap exists — and why category changes it
The lag is not a data bug. Inventories, eligibility, and FEMA review sit in between. Each facility gets its own worksheet, so one disaster produces a sequence of obligation dates.
Categories A–G are the reason that sequence is uneven. You do not need another A–G encyclopedia (that note is here). Timing is the point:
A and B often compress the gap — or invert it. Debris and emergency protective measures can be underway, or finished, before Funded Projects Details v2 shows obligated. The declaration date is closer to “trucks are moving.” The obligation date may be a conversation after the fact: second-pass debris, monitoring, or whether C/E/F will follow. Use the category picker when you want the contractor read for that letter.
C through G usually stretch the gap. Roads, water control, buildings, utilities, and parks need a designed scope. It is normal to see a declaration in March and a Category C or E obligation in the fall — or the next calendar year. If your BD process only wakes up on declaration week, you will be gone when the permanent-work worksheets land.
Same disaster number. Different clocks. Different first sentences.
A desk method that uses both dates
Keep two lines on the card, not one.
- Declaration date + disaster number + designated area. This is the file label. It tells you the county is in the event and which later worksheets belong together.
- Each obligation date + category + federal share + applicant. This is a work item. One disaster file can have many.
Then apply a simple rule:
- Declaration only: watch, do not pitch a phantom package. One courtesy intro is optional if you already work that county. No “we can do your $50 million recovery” email.
- First A/B obligation: call sooner, ask what is still to let, ask whether permanent work is coming. Do not assume you missed everything. Do not assume trucks have not rolled.
- First C–G obligation: start the long cadence. Ask how they will procure and cover any local remainder. Expect silence. Follow up.
- Later worksheets on the same disaster: treat each obligation date as a new facility, not a duplicate of the first letter.
The county watch ROI tool is how you decide whether holding that file for months is worth Starter at $49/month (one state) or Pro at $99/month (nationwide). Soft math, not a forecast of how many worksheets a declaration will produce. Pricing is the paid path if the digest is what keeps the two clocks honest. The tools index stays free.
What RebuildAlert does with each date
The public homepage watchlist is declaration-shaped: PA program declared, recent events, designated areas. The paid digest is obligation-shaped: newly obligated A–G worksheets with project, category, federal share, county, disaster, and the applicant mailing address when OpenFEMA publishes it.
That split is intentional. Declaration dates fill a map. Obligation dates fill an inbox you can act on without pretending FEMA hired you.
RebuildAlert is not affiliated with FEMA or DHS. The federal government does not vouch for analyses after data leave OpenFEMA. Dates and dollars are as published after retrieval. We do not invent bid openings from either timestamp.
A short example
A flood is declared April 4. A Category B pumping worksheet obligates April 20. A Category C culvert obligates in November. A Category E fire-station roof obligates in February.
Fair reading: April 4 opened the file. April 20 is when you ask about emergency work still open. November and February each get their own letter — same disaster, same applicant.
Unfair reading: “Declared in April, so bids were in May.” “November obligation means NTP this month.” “This will be on SAM.gov because it is federal money.”
Three obligation dates. One declaration date. Four different letters if you write at all.
What not to put on the calendar
Do not put “bid opening” on the declaration date. Do not put “award” on the obligation date. Contact for this product is email only.
Record of Sale, LLC operates RebuildAlert at www.rebuildalert.com. Questions: publisher@noticenearby.com. We will not sell OpenFEMA names and addresses as a list, and we will not turn either date into a bid tab.
Use the declaration date to open the file. Use the obligation date to write a specific sentence. Wait for the applicant’s procurement — not for FEMA to put you to work.