Milestone map
3 milestones
Source and Structure Public Financial Data
2 weeks
Select a publicly listed company and download three full years of income statement, balance sheet, and cash flow statement data from public filings. Build a clean historical data model in a spreadsheet with consistent formatting, correct line-item labelling, and a colour-coded input/formula structure (blue cells for hard-coded inputs, black for formulas). Verify that your historical cash flow statement reconciles with the balance sheet — cash ending balance must match in both.
Proof required
Submit your spreadsheet (or a shareable link) with three years of historical three-statement data for a named publicly listed company. The spreadsheet must show: (a) income statement, balance sheet, and cash flow statement on separate tabs, (b) a reconciliation check (cash balance cross-checks between BS and CFS), and (c) correct accounting equation balance (Assets = Liabilities + Equity) for each year. Cite the specific filings used (SEC EDGAR or company IR page, with filing date).
What gets checked
Common mistakes
Resources
What a verifier looks for
You'll sign in first, then come straight back here.
Build Forward-Looking Projections with Documented Assumptions
2–3 weeks
Extend the historical model with three-year forward projections. Every projected line item must be driven by an explicit assumption (revenue growth rate, margin expansion/contraction, working capital ratios, capex as % of revenue). Create a dedicated Assumptions tab that documents each driver with its current value, source or rationale, and sensitivity range. The model must remain fully linked — changing an assumption cell must ripple through all three statements.
Proof required
Submit the updated spreadsheet with projections for three future years. The Assumptions tab must contain at least eight named drivers (e.g., revenue growth %, gross margin %, SG&A %, capex %, D&A %, receivables days, payables days, tax rate). For each driver, provide one sentence explaining your rationale (e.g., 'Revenue growth 8% — consistent with 3-year average and management guidance'). A finance professional must sign off that the model is fully linked and the assumptions are reasonable and documented.
What gets checked
Common mistakes
Resources
What a verifier looks for
You'll sign in first, then come straight back here.
Sensitivity Analysis and Expert Model Review
1–2 weeks
Build a two-variable sensitivity analysis table (data table) showing how a key output (e.g., net income, free cash flow, or EV/EBITDA multiple) changes across a matrix of assumption scenarios. Present the completed model to a finance professional for a technical review, walk them through the model structure and key assumptions, and document their feedback and any revisions made.
Proof required
Submit: (a) the final model with at least one two-variable sensitivity table (minimum 5×5 grid), (b) a written model review memo from a finance professional (minimum 150 words) identifying the model's strengths, at least one structural or assumption concern, and any revisions recommended, and (c) a change log (minimum 3 entries) documenting revisions made in response to the review. The reviewer must be identifiable — name, title or professional background, and date of review.
What gets checked
Common mistakes
Powstik Guide
A 5×5 sensitivity table and a reviewer's memo on your model.
Steps
Template
Review session log Date: Duration: Reviewer name: Reviewer role and credentials: Challenge 1 (the sensitivity drivers): What they asked: My answer: Did it hold? Challenge 2: What they asked: My answer: Did it hold? Challenge 3: What they asked: My answer: Did it hold? What I will change because of this session:
What gets sent back
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
You'll sign in first, then come straight back here.
Part of