Read 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.
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.
Who can
- Documents at view or better: anyone who can read documents.
How to
The step-by-step walkthrough for this page comes from the in-app guide, which is not on this release yet. Everything above describes what the screen does and who can open it.
Related pages
Known limits
There is no form on this page, and no other page creates an obligation directly. Rows reach the register as a side effect of a draw's checklist, or with the project, or because an administrator wrote them. So a register that looks thin usually means nothing has written to it yet rather than that the deal carries no gates.