Post-closure obligation monitor

A post-closure obligation monitor is useful only when it produces a quality alert: the obligation clause, the calendar window that clause creates, and the evidence that is missing inside that window. If the window is still current and the required filings are on file, the queue stays empty. The system does not invent a clawback, a warranty year, or a breach. An officer still decides whether to request, document late, waive, or escalate.

Post-closure is the period after substantial completion, final payment, or deobligation, when delivery has ended but the instrument still binds the recipient. Remaining duties often include environmental sampling through a stated monitoring horizon, construction or equipment warranties, records-retention clocks, and repayment language that fires only if a defined trigger is met.

This check does not replace listing residual liabilities at award close. Use it with the residual liability identifier so the monitor only watches duties the closeout package actually created.

Do not start from a dashboard tile. Start from the signed closeout instrument and the evidence log that is supposed to prove each remaining duty.

Load four artifact classes before any model scores risk. First, the award, cooperative agreement, or contract, including special conditions and attachments that survive closeout. Second, the closeout letter, modification, or residual-conditions schedule that restated those duties and named the start event. Third, any warranty, monitoring, or recapture exhibit incorporated by reference. Fourth, the evidence log: inspection reports, sampling results, warranty certificates, as-built packages, and correspondence that started or paused a clock.

If your agency stores the file in a grants, permitting, or case system from vendors such as Microsoft, Accela, Tyler, or Salesforce Government Cloud, pull the same artifacts those systems already hold. Treat the platform as a filing cabinet. The legal source remains the signed instrument, not a status field or a workflow stage labeled closed.

Confirm three fields on every candidate obligation before you allow a flag:

1. The clause citation: article, special condition, or attachment, plus enough of the sentence that creates the duty.

2. The window: start event, duration or end date, and the unit (days, seasons, or months after the start event).

3. The evidence standard: the document, signature, lab result, or inspection that satisfies the clause, and where it should appear in the log.

If any of those three is missing, stop. An alert with no window is not an alert. It is a guess that sends an officer hunting for a date the file never recorded.

When the instrument and the log are loaded, the monitor compares what the clause requires inside the window with what the log actually contains. A quality flag names all three. A quality non-flag is silence.

One pattern. A coastal restoration cooperative agreement closed after substantial completion. Special Condition 14 requires wetland vegetation surveys in growing seasons 1, 2, and 3 after the as-built date recorded in the closeout letter. The evidence log holds the year-1 survey and a signed as-built. Growing season 2 has ended. There is no year-2 survey in the log and no approved deferral. The alert should read, in substance: Special Condition 14; window, growing season 2 after the as-built date on the closeout letter; missing evidence, year-2 vegetation survey or an approved deferral. It should not say the recipient owes recapture. The officer still acts: request the survey, document a late filing, or open a compliance path.

The packet an officer can use in one sitting is short:

• Clause cite and quoted duty, enough of the sentence to stand without opening the PDF.
• Window: start event, computed end, and the source date used for the computation.
• Missing evidence: the specific artifact, not a vague line that monitoring is incomplete.
• Do not add a clawback assertion or an invented end date.

If the same file is still inside growing season 2 and the survey is not yet due, the monitor produces nothing. Empty is the correct output.

Spend flags that look like they belong in closeout but are really payment anomalies belong with the drawdown anomaly monitor, not in this queue.

Most post-closure files will have live windows and complete logs. A current window, evidence on file or not yet due, is a non-event.

Leave the queue empty when:

• The clause and window are confirmed, the due date has not passed, and nothing in the log contradicts the clock.
• The required artifact is in the log, even if it lives in a linked inspection module rather than the closeout folder.
• The instrument never created the duty the model wants to watch.

Do not leave it empty when the window has closed, the artifact is absent, and there is no approved deferral or waiver on the record. That is the quality alert. The officer still acts. The monitor does not collect, negotiate, or recapture.

Asset packages that should have been in the handover file but never were are a documentation gap, not a post-closure monitoring gap. Route those to the asset handover documentation generator instead of forcing them into an obligation alert.

Three failure modes show up in this work.

An alert with no window. The model finds monitoring language and fires on the clause title. Without a start event and an end, you cannot tell overdue from not yet due. Reject the flag. Send it back for a date source: closeout letter, as-built, substantial completion certificate, or a modification that restated the clock. If none exists, the duty is incomplete in the file. That is a package defect, not a recipient breach.

Treating the flag as a clawback. Recapture, refund, and liquidated-damages clauses fire on defined triggers, often after notice and an opportunity to cure. A missing survey, a lapsed warranty certificate, or a late inspection is evidence of a possible condition, not a recapture event. Do not auto-generate a demand letter, a receivables entry, or a label that recommends clawback. If enforcement follow-up is already open on the same recipient, the post-enforcement compliance monitor is the related check. This monitor stops at clause, window, and missing evidence.

Inventing a warranty year. Models will pad a missing duration with a customary one-year or two-year warranty because construction specs often use those figures. If the closeout instrument does not state the period, or does not incorporate the spec, there is no warranty year to watch. Leave that row empty. The same rule applies to environmental horizons and records-retention clocks: duration comes from the signed text, not from practice in a neighboring program.

A quieter error is treating a workflow status of closed as the end of surviving special conditions.

Run this monitor after the closeout package is assembled and residual duties are listed, not during active performance. When an alert fires, open the cited clause and the log line before contacting the recipient. Confirm the date math and that the artifact is truly absent, then act.

The quality bar is an alert that cites the obligation clause, the window, and the missing evidence, or an empty queue while the window is current. Invented clawbacks, invented warranty years, and flags with no window are defects in the monitor, not findings about the recipient.