Why Every Covered Instruction Requires a Current Review Record

Every escrow file closes on instructions. The payoff goes to a lender. The seller proceeds go to a bank. The broker commission goes to an office. Each of those is a payment direction the office acted on.

When one of those directions changes, or arrives new, or conflicts with something already in the file, the office faces a decision: release, hold, or reject. That decision, and the evidence behind it, is the review. And the review, captured in a timestamped record on the day of closing, is what the file can later prove.

The thesis of this article is narrow: every covered instruction requires a current review record. Not a stale one. Not a generic one. A current record, built from the evidence in front of the office at the moment of release, retained on the file, and available when someone asks what happened months later.

This is not a software pitch. It is a control doctrine. The office decides. Veto records the review.

What a covered instruction is

A covered instruction is any payment direction the office treats as controlling for disbursement. It is not every email or phone call. It is the set of values the office relied on when it moved money.

The simplest test: if the office would not release funds without this value being settled, it is a covered instruction. If changing the value would change the release decision, it is covered.

Most offices already know which instructions are covered. They may not have written the list down. The list usually includes wire instructions for seller proceeds, payoff demands from lenders, commission disbursement directions, and any amended or revised payment instruction that supersedes a prior version. For a deeper definition of the record itself, see The review receipt standard.

A covered instruction is not defined by its channel. An instruction that arrives by email, by lender portal, by phone, or by courier can all be covered. What makes it covered is that the office treated it as the basis for releasing funds.

What a current review record contains

A review record is the file-ready artifact that captures what the office reviewed before it acted. "Current" means the record reflects the evidence in front of the office at the moment of release, not evidence that has since changed or that belonged to an earlier version of the file.

A complete record contains six elements, drawn from the standard described in The review receipt standard and the self-audit in Can your file prove the review?. They fall into four groups.

### What changed and what was checked

The specific instruction that differs from what was already on file. Not "proceeds changed" but "destination account changed from one institution to another." For each check, the result and its limitation stated. A routing number confirmed active does not prove account ownership. A callback completed does not prove the voice on the line was the authorized party. The record says so.

### What stayed open

Missing authorization, unanswered callback, domain mismatch not run, document referenced but never received. Stated on the record, not hidden. An open item is not a failure. An open item the file cannot show is a failure.

### Who reviewed it and what the office decided

Named reviewer and when the review was saved. The office's decision: hold, release, escalate, return, or proceed with a documented exception. The decision is the office's. The record captures it.

### What evidence was retained

Prior notes, documents, and communications that bear on the change, including prior callbacks and authorizations. If the evidence informed the decision, it belongs on the record. If it did not, it does not.

The rule a covered instruction triggers

The rule is that a covered instruction cannot proceed unless a current review record supports it. This is a control principle, not a software feature. It describes what the file should be able to show after the fact.

The principle has three parts. First, coverage: the office identifies which instructions are covered. Second, currency: the review record must reflect the evidence at the moment of release, not an earlier version. Third, retention: the record stays on the file, available for audit, reconstruction, or defense.

When all three hold, the file can answer the five questions behind every disbursement dispute: Did the payment instructions change, and through what channel? Who reviewed the change, and against what approved instruction record already in the file? What did the office have in hand when it decided to proceed? What stayed open and unresolved? Who approved proceeding?

Those questions are reconstructed slowly, from fragments, after the money is gone. The review record exists to answer them on the day of closing. For the case law behind why those questions matter, see Before buyer funds move, build the record.

Why currency matters more than completion

A review record can be complete and still be wrong. The danger is not a missing record. The danger is a record that was current at nine in the morning and stale by two in the afternoon.

Currency is the property that the record reflects the evidence the office relied on at the moment of release. A record loses currency when a material value changes after sign-off: a revised payoff figure, an amended closing disclosure with different totals, a new routing number, a changed payee. The record itself did not disappear. It simply no longer describes what the office acted on.

This is why a covered instruction requires not just a review record, but a current one. A stale record is evidence of a prior review. It is not evidence of the review that supported the release. The distinction is what separates a file that defends itself from one that reconstructs itself.

The control doctrine is straightforward. When a material value changes, the prior record is superseded. A new review is required, or a named exception is logged. The file carries both versions, so an auditor can see what the office relied on at each decision point. The mechanics of how records go stale, and why the review already happens but the record often does not survive, are laid out in The review already happens.

Who is responsible for the review

The office is responsible. Not the software vendor. Not the bank. Not the title underwriter. The escrow holder, acting under its own instructions and its own policies, is the release authority.

This is a point worth dwelling on because it is where vendor marketing and operational reality diverge. Tools that verify wire instructions, confirm bank accounts, or authenticate payees are useful. They produce evidence the office can review. But a passed verification is not permission. The permission to release is an office state, created by policy, evidence, source limitations, and the judgment of the person who signs off.

A DFPI-licensed independent escrow company must strictly and faithfully perform the parties' written instructions, and when instructions conflict, the office is expected to clarify before it closes. That duty sits with the office. The review record is how the office documents that it met the duty. Veto does not decide whether an instruction is legally sufficient. Veto records what the office reviewed, shows whether the instruction matched the approved record already in the file, and keeps anything that does not reconcile visible as an open exception the office chose to carry.

What happens when the record is missing

When the record is missing, the file cannot answer. The question "what did the office check before it released funds?" becomes a reconstruction exercise that runs on memory, email threads, and whatever the production system logged, which is usually the fact of disbursement, not the reasoning behind it.

The consequences fall into three categories.

Audit exposure. The office cannot produce evidence of its review process. ALTA Best Practices Pillar 2 and Pillar 3 expect documented controls over funds release. An underwriter or examiner who asks for the file and finds no review record has nothing to evaluate.

Liability exposure. When a loss occurs, courts and claimants reconstruct the file. As the reported cases show, offices that confirmed instructions but could not prove they resolved the open item against an independent source were held responsible for the loss. The record is what separates a defensible file from an indefensible one.

E&O exposure. Errors and omissions carriers ask, during application and renewal, whether the office has documented wire verification procedures and whether it can produce evidence of what was reviewed before a loss. A file with no review record is harder to defend and may affect coverage positioning. The record does not guarantee a favorable outcome. It gives the office something concrete to stand on.

How exceptions are handled

Not every release is clean. Sometimes the office proceeds with an open item: a payoff figure that is verbal but not yet documented, a callback that did not connect, an instruction that arrived late and the parties cannot wait. The control doctrine does not forbid these. It requires that they be named.

An exception is a documented departure from standard procedure. It records who approved it, why, and when. The exception appears on the file alongside the review record. It is not a silent bypass. A silent bypass is the absence of a record where one should exist, and it is the pattern that creates the most exposure.

The distinction matters because it defines what a good file looks like. A good file is not one where every instruction was clean and every callback connected. A good file is one where every covered instruction has a current review record or a named exception, retained on the file, available for review.

Exceptions are a normal part of escrow operations. The office may carry a covered instruction with an open item if the approver signs off and the reason is logged. What the file cannot do is carry a covered instruction with no record at all. That is the gap the control doctrine closes.

Mapping the control to ALTA Best Practices, DFPI expectations, and E&O carrier questions

Three external frameworks converge on the same expectation: the office should be able to prove what it reviewed before it released funds. Each framework phrases the expectation differently, but they all point at the review record.

The table below maps how a current review record on every covered instruction addresses each framework's requirements.

| Framework | What it expects of the office | How a current review record on every covered instruction addresses it | |---|---|---| | ALTA Best Practices Pillar 2 (Escrow Trust Accounting) | Written procedures for disbursement, dual control on wires, documented reconciliation of escrow trust accounts (ALTA Best Practices) | The review record is the file-level artifact that a covered instruction was reviewed before release. It captures who reviewed, what was checked, and what the office decided, which is the documentation Pillar 2 expects on each file. | | ALTA Best Practices Pillar 3 (Privacy and Information Security) | Procedures to verify wire instructions and protect nonpublic personal information tied to wires (ALTA Best Practices) | The review record shows the verification steps taken, their results, and their limitations. It documents that the office applied its wire verification procedure, which is the evidence Pillar 3 expects. | | DFPI independent escrow duty | Strict and faithful performance of the parties' written instructions, with clarification when instructions conflict (DFPI consumer information) | The review record shows the office identified the instruction, checked it against what was already on file, and either resolved the conflict or carried a named exception. That is the documented performance of the duty. | | E&O carrier underwriting questions | Whether the office has documented wire verification procedures, dual control, and can produce evidence of what was reviewed before a loss (ALTA title insurance and settlement industry guide) | A review record on every covered instruction gives the office a concrete answer to the carrier's question. The carrier is not asking whether fraud was prevented. The carrier is asking whether the office can show its work. |

The convergence is the point. ALTA, DFPI, and E&O carriers are not asking the office to prevent fraud. They are asking the office to show what it reviewed and why it proceeded. A current review record on every covered instruction is the artifact that answers all three.

The boundary between recording and deciding

This is where the doctrine draws its line, and it is important to state it plainly.

Veto records the review. It does not approve, authorize, guarantee, insure, verify, release funds, validate identities, confirm bank accounts, authenticate payees, or make wires safe to send. The escrow office remains the release authority.

The office decides. Veto records the review.

That boundary is what makes the review record useful. The record is not a stamp of correctness. It is a timestamped account of what the office reviewed, what the evidence showed, what stayed open, and what the office decided to do about it. It is valuable precisely because it does not pretend to be more than it is.

A review record that claimed to verify or approve would overstate what any record can do. A review record that honestly states what was checked, what it proved, and what it did not prove is the artifact that holds up when the file is examined. The honesty is the utility.

Run a live-file control test

The way to see whether this doctrine belongs in your file is to run it on one real disbursement, before the next one closes.

Take a covered instruction from a recent or pending file. Build the review record: what changed, what was checked and against what source, what stayed open, who reviewed it, and what the office decided. Then ask whether that record would answer the five questions if the file were reconstructed six months from now.

If the record is already there, the doctrine is already operating. If it is not, the file test is where to start. The office's own evidence, on one real file, is the test that matters. Run a live-file control test and see what the file can prove today.

Frequently asked questions about covered instructions and review records

### What makes an instruction covered?

An instruction is covered if the office treated it as controlling for disbursement. The practical test: if changing the value would change the release decision, or if the office would not release funds without the value being settled, it is covered. Most offices know which instructions are covered in practice. Writing the list down is the first step toward a review record on each one.

### Does every revised payoff or wire instruction need a new review record?

If the revision changes a material value the office treated as fixed at sign-off, yes. A revised payoff figure, a new routing number, a changed payee, or amended closing disclosure totals all require a fresh review or a named exception. The prior record is superseded but retained. Cosmetic edits that do not change a covered value do not trigger a new record. The doctrine targets material changes, not every document revision.

### Who signs off on the review record?

The office's own policy determines who is authorized. Many offices require the escrow officer or a manager to sign off on covered instructions, with dual control on outbound wires above a threshold. The review record captures the named reviewer and the timestamp. Veto does not decide who signs off. The office sets its own authorization policy and records who applied it.

### How long should review records be retained?

Review records should be retained as long as the closing file itself, because they are part of the file's audit trail. They are the evidence the office relied on at each decision point. Discarding a superseded review record removes the ability to show what the office knew and when. Both the original and any superseding versions belong in the retained file.

### What if a covered instruction arrives after the wire is queued at the bank?

The same rule applies. A covered instruction requires a current review record before release. If a material change arrives after the wire is queued but before funds leave the office's control, the prior record is stale and the release should not proceed until a current record is built or a named exception is logged. Once funds leave the office's control, the record cannot reverse the transfer. The control doctrine operates before release, not after. The value of a current review record is that it makes the moment of release a deliberate, documented decision rather than a default.