Read and keep the obligations register

Every gate on the deal, banded by the surface it belongs to, with what blocks and what has been waived.

An obligation is a gate: something that must be satisfied before an event may happen. Origination diligence, a per-draw checklist, an agency condition and a lender's standing requirement are all obligations, and they are all read here.

Each row shows its status, whether an outstanding item blocks the event it is attached to, and where a waiver was granted, who granted it and why.

When it is due

A row's Due date is resolved, not typed. An obligation due a fixed number of days after a milestone, such as a dedication seven years after paved access, is dated off that milestone and moves when the milestone moves. Until the milestone is recorded the cell reads "awaiting" the event it waits on rather than sitting blank, and a standing constraint with no due date says so. An option's window resolves the same way, so a window anchored to a milestone can close on a date the project already knows.

Banded by surface, not one flat list

The bands are the different points in a deal an obligation applies at. A single list sorted by title would bury a standing agency condition under forty rows of one draw's checklist, and the two are not the same kind of question.

Where the verdicts come from

This page adds no rules of its own. A per-draw item's blocking rule is the same rule the draws page reads, and this register shows the rows every other surface already writes.

Entering a gate

Add obligation records a gate the draw did not: what has to happen, its kind and the surface it applies at, who answers for it from the party register, which contract it sits under, and when it is due. The due rule is the same grammar every other date uses: a fixed date, a number of days or months after an event or a schedule task, or no date at all for a standing obligation. Somebody with documents access at edit records it, and the row it writes is the same row a draw's checklist writes for its own gate.

Editing a row opens the same form, with where it stands beneath it: open, satisfied, or waived. Waiving needs documents access at approve, the floor a waiver on a draw checklist is held to. Overdue is never recorded; it is read off the due date.

The draw's own gates are the exception. A per-draw or per-advance row is answered item by item from the Draws tab, and the register reads those rows without offering to edit them.