Track funding and approval gates in a construction schedule

On September 21, 2026, the U.S. Department of Energy announced more than $99 million for 21 selected geothermal projects, and the same announcement says that selection for award negotiations does not commit the department to issuing an award or providing funding. For a team building one of those projects, or any job waiting on a grant or loan, a schedule that carries news like that as one milestone called "Funding secured" will show work released by an event that has not happened yet. Selection and an executed award release different work, and the schedule has to keep them apart. Read the DOE announcement.

Name the event, then date it

"Funding secured" could mean the project was selected for negotiations, that an agreement was executed, or that money is available for one package. When the schedule uses one label for all of those, the reviewer cannot tell which has happened.

Take the names from the project's own decision process and its controlling documents. A hypothetical sequence might run from selection notice received, through negotiations completed and award agreement executed, to package release approved and authorization to proceed issued. Your project may need fewer steps or different ones. For each gate, ask the responsible project representative which record proves it happened, and if nobody knows yet, log the question with a name against it instead of picking a label that reads well.

Keep actuals and forecasts apart

"Expected next month" and "received September 21" carry different weight, and the schedule should show which one each gate has, with the source and the date the information came in.

Leave unknown fields blank and put a named person on chasing each one, because a plausible date with no source gets copied forward from update to update as if someone had confirmed it.

Tie each gate only to the work it controls

An approval milestone should not become a predecessor to every activity in the schedule just because it matters. Work out which packages actually wait on it and which can proceed, check what other prerequisites apply, and record why each relationship was added.

Some agreements allow limited work before full authorization and others prohibit it. The schedule should follow what the project has actually agreed, and it should never imply authority to place orders or mobilize that nobody has granted. On a multi-package job, one overall "approved" milestone can hide an open prerequisite on the package that starts next, and tying every package to one late gate can produce a forecast slip that the real release process would never cause.

A moved approval date, worked through

Consider a hypothetical equipment package. The team forecasts release approval on October 6 and plans the purchase order after it. At the next update the responsible reviewer moves the forecast to October 13. The approval has not happened on either date.

Keep the previous update, record the new forecast and where it came from, then look at the procurement chain behind it. Check its other predecessors, calendars, remaining durations and float, and confirm the vendor's quoted lead time still stands before using it.

The seven-day move in the approval forecast does not by itself move completion seven days, and it says nothing about fault, compensation or entitlement. The owner update should name the revised approval forecast, the package affected, the assumption still unconfirmed and the next decision. If the milestone effect has been modeled and reviewed, report it with its comparison basis. If it has not, say it is still being assessed.

Review gates at every update

Keep the same gate IDs from one update to the next. When a gate moves from forecast to complete, attach the record that proves it. If a gate's definition changes, note the revision so a renamed milestone does not pass for an ordinary date change.

In the update meeting, go through newly completed gates, revised forecasts, missing evidence and overdue follow-ups, and ask whether the downstream ties still match how work will actually be released. Schedules copied forward keep old assumptions long after the approval process has changed, so check the ties against the latest agreement each time.

Check what moved after the gate

When an update moves a gate forecast, compare the update before the move with the one after. Pathizer's free Update Compare reads two .XER schedule updates in your browser, with no sign-in. Give it that pair at pathizer.com/xer-update-compare and it lists what changed between them, including activities added and deleted and start, finish, duration and total float changes. What the approval means, and what the agreement allows, remain questions for the project team.