🧠Overview / What This Guide Covers
A one-page recommendation is the fastest way to turn investment screening work into a decision—and to prevent re-litigating the same debate in every meeting. This guide gives you a practical structure to write a crisp, decision-ready page that summarises your investment analysis, key assumptions, returns, and risks. It’s for finance teams, corp dev, investors, and operators who need consistent investment evaluation across multiple opportunities. You’ll learn how to frame the decision, show the numbers without drowning in detail, and make next steps unambiguous—embedded in your end-to-end investment screening process—so stakeholders can approve, decline, or request diligence quickly.
âś… Before You Begin
Before you write, confirm what decision you’re asking for and who has authority to make it. Gather the minimum evidence: deal snapshot, strategic rationale, key risks, and the core outputs from your investment screening model (NPV/IRR/payback plus a downside case). If this is project investment screening for capex, also capture implementation plan, benefit owner, and timing of cash outflows. Clarify the evaluation lens: is this strategic investment screening (fit and capability) or is it primarily return-driven? Pull the 3–5 assumptions that truly drive value (price, volume, margin, ramp, working capital), plus the top two sensitivities you ran. Decide how you will express risk: “what could go wrong” and “what we will verify.” Finally, align on the scoring and thresholds your committee uses so the page reads like a decision aid, not a narrative. If you need a baseline for criteria and weightings, anchor your memo to consistent screening criteria so the recommendation is comparable across opportunities.
🛠️ Step-by-Step Instructions
Step 1: Lead with the decision and the context
Start the page with one sentence: “Approve / Decline / Proceed to diligence for X.” Then add two lines of context: what the opportunity is and why it’s on the table now (timing, trigger, constraint). This stops stakeholders guessing your intent. Next, summarise the opportunity in three bullets: what is being bought/built, timeline, and required resources. Keep it concrete and avoid adjectives. This opener should mirror your investment screening steps: define the decision gate, then provide just enough context to interpret the numbers. If the recommendation sits within a portfolio, state the constraint (budget, headroom, management bandwidth) so readers understand trade-offs. For the broader workflow this page supports—from intake to recommendation—keep alignment with the core investment screening guide so the one-pager fits your standard process.
Step 2: State the thesis and strategic fit in plain language
Write a two- to three-sentence thesis: why this opportunity wins specifically for you, and what must be true for it to work. Avoid generic claims like “large market” unless you pair it with a practical implication (“we can reach X% share using our channel”). In a short paragraph, cover strategic fit: adjacency to capabilities, customer overlap, and defensibility. This is the heart of strategic investment screening—it explains why the case deserves capital versus other uses. If this is external investment opportunity screening, include how the deal fits your portfolio (risk profile, duration, liquidity). Keep the narrative readable: one clear idea per sentence, claim supported by evidence, and a direct implication for the business. If you want a punchy narrative style that holds up in committee, follow a decision-memo structure that links claim → evidence → implication.
Step 3: Present the financial case and the drivers—no spreadsheet screenshots
Use a small “numbers box” to show base case returns: NPV, IRR, payback, and the single driver behind each. Then add two lines explaining what moves value (e.g., “Value is driven by churn and gross margin; capex timing is secondary”). This turns investment analysis into something executives can use. Next, show a downside case in one sentence (what you flexed, what happened to NPV/IRR) and state the threshold you care about (“Downside IRR stays above 12%”). That’s disciplined investment evaluation—interpreting, not just presenting, a model. If you operate under formal project investment appraisal, include the hurdle (WACC, payback limit, minimum headroom). For clarity, present base vs downside in a one-page comparison with a short interpretation and a single decision recommendation, rather than pasting raw sensitivity tables into the memo.
Step 4: Summarise risks, mitigations, and diligence asks
List 3–5 risks in ranked order, each paired with a mitigation and a validation step. Keep them specific: “customer concentration” is vague; “top customer is 28% of revenue and can terminate in 90 days” is actionable. Separate risks you can validate quickly (contract terms, vendor quotes) from risks you can only reduce over time (competitive response, execution capability). This is practical investment risk screening: converting uncertainty into a plan. For each risk, write the data you need and who will get it, so the decision doesn’t stall. If the recommendation is “Proceed to diligence”, define the diligence scope and timebox. If it’s “Decline”, state the one or two deal changes that would make you reconsider. For a ready list of common red flags and a clean way to word them, use a structured investment risk screening framework.
Step 5: Finalise, circulate, and lock the decision trail
Before sending, do a two-minute read test: can someone explain the decision, the drivers, and the top risks after a fast skim? If not, cut detail and sharpen the thesis. Standardise formatting so committees can compare recommendations across cases—this is what makes repeat investment project evaluation fast and fair. Circulate the page with the underlying model attached, but keep the one-pager as the single source of truth for the decision. Collect feedback in one place and lock the final version once the decision is made. In Model Reef, teams can share the recommendation alongside assumptions and scenario outputs, with collaboration and permissions that make approvals and handoffs clean. Once approved, schedule the next checkpoint so the recommendation turns into action, not a document.
⚠️ Tips, Edge Cases & Gotchas
The biggest mistake is writing a summary that doesn’t make a decision. Always include the ask, timing, and what happens next. Second, avoid mixing “facts” with “assumptions”; label assumptions clearly so stakeholders can challenge them without disputing reality. Third, don’t hide behind ratios—tie claims back to cash flow and constraints so financial investment screening doesn’t become a slide exercise. For internal capex, explicitly state benefit ownership and implementation dependencies; that’s often where project investment screening fails in practice. If you’re dealing with strategic bets that don’t meet near-term hurdles, use a separate label and approval route rather than stretching the core investment screening method. Finally, control versions: one page becomes five versions quickly. Use a workflow with comments, notes, and version history so the final recommendation is traceable and auditable.
🧪 Example / Quick Illustration
Decision: “Proceed to diligence for AcquireCo (AU$12M EV), subject to retention validation.” Thesis: the target adds enterprise customers we can cross-sell into and improves unit economics through shared operations. Financial box: base case IRR 18%, NPV AU$3.2M, payback 4.1 years; value is most sensitive to churn and integration cost. Downside: if churn rises by 1.5% and integration costs are 20% higher, IRR drops to 11% (still above hurdle). Risks: customer concentration, integration timeline, and pricing power; diligence asks include cohort retention by segment and vendor quotes for integration work. Output: a one-page recommendation that a board can approve in a single meeting, supported by a clean appendix model and an action checklist. For a repeatable narrative flow that suits board review, adapt the structure of a board reporting pack.
âť“ FAQs
One page means one page of decision content—tight, scannable, and prioritised. The goal is to let a stakeholder understand the decision, the value drivers, and the risks in minutes, not to reproduce your full analysis. If you need more detail, push it into an appendix (model outputs, sensitivity tables, diligence materials) while keeping the front page clean. A practical rule is: one decision sentence, one thesis paragraph, one numbers box, and one risk/next-steps block. If you can’t fit it, you likely haven’t prioritised what matters. Cut until only decision-critical information remains.
No—include the interpretation, not the full grid. Sensitivities are useful because they clarify what the case is underwriting and what breaks it, but tables slow comprehension and invite unproductive debate. Instead, state the two variables you flexed, the range, and what happened to NPV/IRR, then link that directly to diligence actions. If you need to show more, use a single base vs downside comparison with a short note on drivers. Tools that support scenario toggles make this cleaner because you can keep the detail in the model while presenting only the decision-ready view.
You can still write a one-page recommendation—just be explicit about uncertainty and the decision logic. For strategic moves, your investment evaluation often hinges on “what must be true” and “how we will validate it” more than precise valuation. Present a conservative base case, a clear downside, and the specific milestones that justify continued investment or a stop decision. This keeps the recommendation disciplined rather than narrative-driven. If optionality matters (delay, stage-gate, expand later), structure the decision around staged commitments and triggers rather than a single all-in bet. That approach keeps governance strong while preserving flexibility.
Use a controlled distribution process with clear versioning and access rules. One-pagers are decision artefacts; if multiple versions circulate, you lose trust and invite confusion. Lock the final version, store it with the underlying model, and require comments/changes to happen in one channel. Export in a format that preserves the narrative and visuals in a single file so stakeholders see the same content. If security and stakeholder access are a concern, align distribution to your organisation’s security and permissions standards. With those basics, sharing becomes faster and less risky.
🚀 Next Steps
Next, standardise the one-page structure across your pipeline so every recommendation reads the same way and decisions get faster over time. Then build a simple feedback loop: after each approval/decline, note what changed the decision and refine the template accordingly. If you want to scale this without document chaos, Model Reef can help you keep the one-pager, the underlying drivers, and scenario outputs connected—so the recommendation always traces back to the assumptions and evidence. If you’d like to see how the workflow looks end-to-end before rolling it out,start with a quick product walkthrough.
Back