Purpose
When the CLA Draw Agent flags a failure during draw review, processors and approvers now have a clear, documented way to proceed. Overriding a finding never deletes or hides the agent's original assessment — it records a human decision to move forward, along with who made that decision, when, and why, so the reasoning stays visible on the draw going forward.
Key Features
Agent-Blocked Approval Messaging: Draw findings are grouped into review categories so it's immediately clear what still needs attention before a draw can move forward.
Explainable Findings: Each flagged item includes a plain-language summary, the specific files or data behind the finding, and what's needed to resolve it.
Not Applicable Policy Transparency: Policies the agent determined don't apply to a draw are listed separately with the reasoning, so it's clear they were evaluated, not skipped.
Human Override: Processors and approvers can override a blocking finding, selecting a decision and reason and optionally adding a comment.
Preserved Agent Signal: Overriding a finding never turns it green or removes it — the original finding stays visible alongside the override.
Inline Audit Trail: Every override is recorded directly on the finding, showing who overrode it, when, and why.
Target Users
Draw Processor
Draw Approver
How It Works
1. Reviewing What Needs Attention
From a draw, the Agent review tab shows a See What Needs Review summary across six categories:
Category | What It Reviews |
|---|---|
Documentation Check | Confirms required documents were submitted. |
Draw Reconciliation | Matches submitted draw amounts against supporting documents. |
Policies Review | Evaluates the draw against your organization's configured SOPs. |
Draw Checklist | Tracks any remaining manual checklist items. |
Compliance Confirmation | Confirms compliance-related requirements are met. |
Final Approvers | Shows the approval status for the draw. |
Each category shows a status icon — a green check for passed, a red exclamation for a blocking failure, an amber triangle for a warning, or a clock for pending review.
2. Understanding a Flagged Finding
Expanding a category shows its individual findings. A blocking finding includes:
A Summary explaining what the agent found and why it's blocking.
The specific files or data associated with the issue, each with a View File link.
Guidance on what's needed to resolve it (for example, what a valid document should include).
A note when related items have been added to the notification list so the borrower or builder can be notified.
Each finding also has a Show Agent Instructions option and a quick Was this assessment helpful? feedback control.
3. Seeing What Didn't Apply
A Not Applicable Policies section lists any SOPs the agent evaluated and determined don't apply to this draw, along with the reason — for example, a policy that only applies to a different draw type. This keeps it clear the agent considered every policy rather than silently skipping some.
4. Overriding a Finding
Selecting Override on a blocking finding opens the Override agent decision dialog. The dialog is explicit that the agent's original decision remains on record, and that overriding documents proceeding despite the identified condition. It asks for a New Decision:
New Decision | Meaning |
|---|---|
Resolved | The underlying issue no longer exists. |
Not applicable | This check shouldn't have applied to this draw. |
If Resolved is selected, a required Reason follows:
Reason (shown when Resolved is selected) | Meaning |
|---|---|
Corrected elsewhere in the draw | Already fixed on another tab (e.g., budget, reallocation) but not yet re-evaluated. |
Documentation accepted outside Built | Info exists elsewhere in the package. |
Approved exception | An approved business exception. |
Other | Doesn't fit another category. |
An optional Decision comment field allows adding free-text context for the record. Selecting Apply override completes the action.
5. After Overriding
An overridden finding's status icon changes, and its Override button becomes an Overridden label. The finding itself still displays its original summary and files, with an added line recording the override — who made it, the date and time, and the decision and reason selected. Reopening an overridden finding also offers a Remove override option.
Benefits
Clear signal on why the agent stopped a draw, instead of a generic block with no explanation.
A documented, attributable reason any time a processor or approver proceeds despite a flagged issue.
No loss of the agent's original finding — overriding is a recorded decision, not a fix.
Less time spent re-investigating an issue that's already been reviewed once.
Best Practices
An override documents a decision to proceed — it's not a way to mark an issue resolved in the underlying data. If the issue is genuinely fixed, resolve it at the source so the agent can re-evaluate.
Choose the Reason that most specifically describes the situation; use Other only when nothing else fits, since it's less useful in an audit review.
Use the Decision comment field to add context a future reviewer — including compliance or audit — would need to understand the override without asking the person who made it.