Red flag report vs full scope FDD report: when clients commission each, how the analyst's job changes, and why speed beats completeness in a red flag review.
Your first day on a live deal, your manager says "it's a red flag review, five working days, ten pages, findings only." If your instinct is to open a blank workbook and start building the full EBITDA adjustments schedule you were trained on, you have already misread the assignment — and you'll deliver a beautiful piece of work that answers a question nobody asked. The single most useful thing a junior analyst can learn early is that not every engagement wants the same deliverable, and getting that wrong wastes the two things a deal team never has: time and fee budget.
Financial due diligence is not one product. It is a family of products that share a toolkit — the same quality of earnings logic, the same net debt discipline, the same working-capital instincts — but differ sharply in depth, tone and turnaround. The two you'll meet most often sit at opposite ends of that spectrum.
A full scope report is the exhaustive document most training material describes: complete coverage of every material P&L and balance-sheet line, a fully built EBITDA bridge, a reconciled net debt bridge, a normalised working-capital analysis, databook appendices, the lot. It follows the classic FDD report structure and it is what the buyer relies on to sign a binding SPA.
A red flag report exists to answer one question, fast: is there anything here that should stop the buyer proceeding, or that materially moves the price? It is short — sometimes ten pages against fifty — and organised around findings rather than comprehensive coverage. Think of it as triage in a hospital corridor, not a full diagnostic workup.
A red flag report is not a worse version of a full scope report. It is a different product with a different job. Judging it by the standards of the full report — "but you didn't tie out working capital!" — misses the point entirely.
The trigger for a red flag review is almost always early-stage, competitive, and time-boxed. A buyer in a broad auction wants a quick sanity check before committing more fees; a private equity house wants ammunition for an indicative offer without paying for full scope work on a deal they may not win; a corporate wants to know whether a target is worth chasing at all. Speed and cost discipline are the whole point.
Full scope work typically follows once the buyer has narrowed the field — often after exclusivity is granted and there is a defined window to do the complete job properly. The red flag findings then become the roadmap: the full scope team knows exactly where to dig hardest rather than starting from a blank page.
| Dimension | Red flag report | Full scope report |
|---|---|---|
| Core question | Anything that kills or repriced the deal? | Complete financial picture for signing |
| Length | ~5–15 pages, findings-led | ~30–80 pages, comprehensive |
| Typical timing | Pre-exclusivity, competitive auction | Post-exclusivity, preferred bidder |
| Coverage | Highest-risk items only | Every material line |
| Evidence bar | Enough to raise the question | Fully reconciled and supported |
| Audience | Deal team deciding whether to proceed | Deal team, lenders, lawyers, IC |
The temptation is to think a red flag report is "the same work, but you write less down." It isn't. The work itself is different because your operating principle flips from completeness to prioritisation.
Prioritisation over completeness. In full scope you eventually cover everything. In a red flag review you deliberately choose not to look at areas unlikely to hide anything material, and you pour your limited hours into the handful of items most likely to move price or kill the deal: customer concentration, obvious one-off items inflating EBITDA, revenue that may not be as recurring or high-quality as the teaser claims, undisclosed litigation, covenant breaches, or a working-capital number that looks manufactured.
Judgement with less evidence. You may flag a concern off a single data-room document rather than the fully reconciled schedule you'd build for a full report. That is not sloppiness — the job is to surface the question, not answer it exhaustively. A well-written red flag point often ends with "recommend confirming in full scope phase," which is exactly the right posture.
Tone and access. A red flag report frequently goes straight to a deal team, sometimes before management even knows a rigorous review is underway. You may be working off a thin data room with no management call. That constrains what you can assert, and your language has to reflect it: "appears," "based on limited information provided," "subject to confirmation."
Suppose you have 40 analyst hours on a red flag review of a €12m-EBITDA distribution business. The full scope version of this engagement would run to roughly 300 hours. You cannot do 300 hours of work in 40, so allocation is the job. Here is a sensible split versus how the same lines get treated in full scope.
| Work area | Red flag hours | Full scope hours | Why the red flag weighting |
|---|---|---|---|
| EBITDA one-offs & add-backs | 12 | 60 | Directly moves the headline multiple |
| Customer concentration & revenue quality | 10 | 55 | Top deal-killer in this sector |
| Net debt & debt-like items | 8 | 45 | Straight cash-for-cash price impact |
| Working capital | 4 | 50 | Scan for a manufactured number only |
| Tax, IT, HR, legal-adjacent | 2 | 40 | Flag obvious issues; defer the rest |
| Report writing | 4 | 50 | Short, findings-led |
| Total | 40 | 300 |
The lesson is stark: working capital gets 4 hours in the red flag mode and 50 in full scope. Spend twelve building an exhaustive NWC schedule and you've burned nearly a third of your budget on the one area least likely to kill this particular deal — while the concentration risk that actually matters gets a rushed afternoon. Matching effort to the assignment is the skill; raw thoroughness is not.
A red flag point is not a paragraph of hedged prose. The house format is tight and repeatable:
A grader — and a partner — can tell in ten seconds whether you understand the product. Findings that read like a full-scope appendix, with three pages of build-up before the point, signal someone who couldn't distinguish the two. A crisp, ranked list of five things that matter signals someone who can.
When a red flag review converts, your findings become the scoping document for the next phase. This is where the two products connect: the red flags you raised tell the full scope team where the risk sits, so they don't waste their (larger) budget re-triaging from scratch. Good analysts write the red flag report already half-thinking about that handover — flagging not just "here is a problem" but "here is what full scope should test to size it."
This continuity is also why the distinction matters for the FDD process as a whole. The red flag report de-risks the buyer's decision to spend real money on full scope; the full scope report de-risks the decision to sign. They are two gates in one funnel, not competitors.
Interviewers love this topic precisely because it separates candidates who understand client service from those who only understand technique. Expect: "You're staffed on a red flag review with five days. Walk me through how you'd approach it."
"First I'd confirm the scope explicitly with my manager — what's the deal question, is this pre-exclusivity, and is there a management call or just a data room. In a red flag review the goal isn't completeness, it's answering 'should the buyer proceed and at what price' fast. So I'd triage: I'd spend most of my time on the items most likely to move price or kill the deal — EBITDA one-offs, customer concentration and revenue quality, and net debt or debt-like items — and deliberately only scan working capital and the softer areas for anything obviously manufactured. I'd write it as a ranked list of findings, each with an impact estimate and a clear recommendation to proceed, reprice, or test further in full scope. I'd rather deliver five sharp, well-evidenced red flags on day five than a half-finished full-scope report. And critically, if I found something that genuinely kills the deal early, I'd raise it with my manager immediately rather than waiting for the written report — the whole value of a red flag review is speed."
That answer works because it leads with scoping and communication, shows you know what to prioritise and why, and ends on the judgement that speed-to-signal is the product. Contrast it with "I'd build the EBITDA bridge, then the net debt bridge, then working capital" — technically fine, completely tone-deaf to the assignment.
The best analysts are not the ones who can do the most work — they're the ones who do the right work for the assignment in front of them. A red flag report and a full scope report draw on the same toolkit, but they are different products serving different decisions at different moments, and reading which one you're on is a professional skill in its own right. Learn to ask "what's the deal question and how long have I got?" before you open the workbook, and you'll already be ahead of the analyst who opens it first and asks later.
The Transaction Services Interview Programme (€119.99, one-time) includes a dedicated module on engagement scoping — red flag versus full scope, how to allocate limited hours, and how to write findings-led deliverables that partners actually use — plus worked interview answers on the exact "you've got five days" scenario. Enrol today.
Hundreds of candidates prepared their interviews with this programme. Those who landed the role have one thing in common: they worked the cases before walking into the room.
