An underwriting handoff is the point where responsibility for a deal moves from one person to the next, and a shared deal book is the structure that carries the deal's context across that gap. Teams hand deals off constantly: from intake to analyst, from analyst to credit decision, from decision to funding. Each handoff is a chance to lose the note that explains why the latest statement month was skipped, or why a deposit was excluded from revenue.
On a small-business funding desk the chain is short but dense: intake collects the file, an analyst reads the bank sheet, a credit lead makes the call, and operations moves the approved deal toward offer and funding. In MCA shops the same person often wears two of those hats, which makes the written record matter more, not less.
Handoffs are one stage of a longer process. For the full path from intake to funding, see MCA Underwriting: The Complete Guide.
One shared structure for every deal
Agree on a simple place for source files, extracted results, open questions, and review notes, and keep it the same from deal to deal. A bank statement should land in the same spot whether the deal is a small working capital advance or a larger facility with years of history behind it. A familiar structure lets a new reviewer orient themselves without a walkthrough from the last person, and it makes exceptions obvious: when a book is missing its credit report or its most recent statement month, the gap has a place to show up.
The structure does not need to be complicated to be effective. It only needs to be consistent enough that everyone on the team knows where to look first, and where to leave what they find. We covered the intake side of that structure in our note on organizing underwriting documents; this one is about what happens after the file is built, when it starts moving between people.
Handoffs fail in predictable places
Most lost context follows three patterns. The first is the stray note: an observation about a deposit or a balance that lives in a chat thread, or in someone's head, instead of on the deal. The second is the vague status: a book marked in review with no owner and no next step, so every person who opens it starts from zero. The third is the unexplained exception: a deal approved outside policy on revenue, average daily balance, or negative days, with the outcome recorded but not the reasoning.
None of these requires a new rule. They require a shared place to put things, and the habit of using it every time, especially on the deals that feel routine. Routine deals are exactly where skipped steps hide, because nothing about them feels worth writing down until something is missing.
Notes the next reviewer can act on
A useful note names the issue, points to the source, and says what happens next. "One negative balance day in February, see the February statement, reason recorded after speaking with the merchant" is a note the next underwriter can act on. "Looks odd" is not. The same shape works for anything worth flagging. "Two recurring daily debits to the same funding company, likely two existing positions, raised for the credit review" tells the next person what was seen, where to find it, and what to do with it.
Keep observations separate from decisions, and avoid shorthand that only makes sense to the person who wrote it. A good test: could someone pick up this deal tomorrow and act on the note without a follow-up call? If not, add the missing detail while the context is still fresh. Write notes for the reviewer you have never met: the person reopening this file in three months may be new to the team, or may be you with forty other deals in between, and either way the note has to stand alone.
Notes attached to a specific document or transaction age far better than notes about the deal in general, and the few seconds they take now save a reconstruction later, when the deal resurfaces with less time and less memory behind it.
What a good handoff includes
When a deal moves between people, the handoff does not need to be a meeting. It needs to cover a short list:
- Document status: what has arrived, what has been parsed, and what still needs review.
- The screening result and any flagged exceptions, with the rules that triggered them.
- Open questions, each attached to the document or transaction it concerns.
- Decisions already made, with the reasoning, including exceptions the team chose to approve.
- Outstanding stips and follow-ups, each with an owner.
- The next action, written plainly enough for someone who has never seen the deal.
On a busy desk, this is the difference between a deal that waits on one person's memory and a deal that keeps moving through the queue. It also gives the credit lead a complete picture without a status meeting, and gives intake a clear list of what to chase next.
A readable history of resolved questions
When a question is resolved, record the outcome next to the original note, with the reasoning. If the team accepted two existing debt positions because total debt service stayed inside policy, that decision should live where the positions were first flagged, not in a retired email chain. Keep the history readable so the team can see what changed and why. What the team decided last month should be as easy to find as what arrived yesterday.
A readable history also makes disagreement cheaper. When two reviewers see a position count or a revenue figure differently, the record shows what was checked before, and the conversation starts from evidence instead of impressions.
Continuity is the point: each handoff should build on the work already done. Resolved questions are part of the record too. Keeping them visible shows why a decision was made, not just what was decided, and that history becomes the fastest onboarding a new reviewer can get. It also helps months later, at renewal or on a second facility, when last season's reasoning is suddenly relevant again, and when a funding partner asks not just what was decided but how the file was kept.
How this looks in Lendquo
In Lendquo, the book is the shared structure. Documents, parsed results, screening outcomes, and review notes live together in the underwriting workspace, so a deal can move from intake to credit decision to funding without losing context between people. Less has to be re-explained, because the reasoning is already filed where the next person will look. For teams that share books across roles, team access on the Growth plan keeps everyone working from the same record.