For Investment Banking & Private Equity

Move from inherited model review to client-ready handoff evidence.

Review the model, explain what moved, and hand off evidence without hiding inside the spreadsheet.

Same product, every capabilityHonest evidence boundaries

Workflow stack

  1. TrustLens / Flow Diagram / CalcScope for formula review
  2. Sensitivity for key-driver testing
  3. Compare + MCI for version deltas
  4. Sign Block + Certificate + Evidence Pack + Replay Proof for handoff evidence

Handoff

A reviewed block, comparison/MCI explanation, signed certificate envelope, Evidence Pack, and optionally a signed replay envelope for a specific output delta.

The workflow creates review evidence. It does not certify that the deal model, assumptions, or valuation conclusion is correct.

Workflow proof

Each promise maps to commands, context, result, artifact, and limit.

No demo placeholder. These panels describe the actual command stack and the output a reviewer or model owner can expect to see.

  1. Understand the inherited model before marking it up

    Situation

    A deal model arrives from a client, sponsor, or previous deal team and the next version needs edits fast.

    Commands used
    ModelXcel ProFormula ToolsTrustLensKeytipFIShortcutCtrl+Shift+I
    ModelXcel ProFormula ToolsFlow DiagramKeytipFDShortcutCtrl+Shift+W
    ModelXcel ProFormula ToolsCalcScopeKeytipPP
    What the user sees
    • Formula structure, result values, proof-state badges, PATH/OFF branch state, and dependency paths.
    • A step-by-step CalcScope tree for the selected formula and a Flow Diagram when the formula needs visual tracing.
    Output artifact

    Copied formula explanation, review notes, and a clear list of cells to inspect, edit, or sign.

    Caveat / limit

    These tools explain logic and proof state; they do not prove that the model design or assumptions are correct.

    Open related docs →

  2. Test the drivers that matter before the pack changes

    Situation

    The team needs to know which assumptions move IRR, MOIC, debt capacity, or another selected output.

    Commands used
    ModelXcel ProFormula ToolsSensitivityKeytipSAShortcutCtrl+Shift+S
    What the user sees
    • Ranked input bars, output metric switching, impact percentages, hide-zero and top-N controls, and click-to-cell navigation.
    • Copy Data output for model-review notes or a deal-team pack.
    Output artifact

    Sensitivity data export and a ranked driver list for the selected outputs.

    Caveat / limit

    Sensitivity perturbs detected drivers; it is not a replacement for scenario design or full commercial judgement.

    Open related docs →

  3. Explain what changed between versions

    Situation

    A new model version changes outputs and the team needs to know whether the movement is expected.

    Commands used
    ModelXcel ProCompareCompare WorkbooksKeytipCO
    Compare ResultsExplain Output ChangeMCI
    What the user sees
    • Formula/value/format/structure deltas grouped into reviewable changes.
    • Ranked drivers, dependency paths, residual, and one-click routes to TrustLens, Worksheet Map, review issues, or an exported report.
    Output artifact

    Saved comparison result plus MCI output-change explanation for the selected output.

    Caveat / limit

    Attribution depends on the selected baseline/revised files, reachable drivers, and residual. It explains the movement; it does not say the movement is right.

    Open related docs →

  4. Create evidence for the handoff

    Situation

    The model is going to an MD, IC reviewer, lender, or client and the team wants evidence of what was reviewed.

    Commands used
    ModelXcel ProProofSign BlockKeytipSB
    ModelXcel ProProofCertificateKeytipCT
    ModelXcel ProProofReplay ProofKeytipRP
    What the user sees
    • Signed formula blocks, coverage, ledger verdict, certificate export options, and replay status for a selected output movement.
    • A .mxreplay.signed envelope when Replay Proof is exported.
    Output artifact

    Certificate JSON plus .mxcert.signed for workbook proof state; Evidence Pack when the recipient needs the certificate, sealed ledger, and verifiers; .mxreplay.signed for an output-delta replay.

    Caveat / limit

    Both Certificate JSON and Replay Proof can be signed, but they answer different questions: ledger state versus a specific output movement. Signing identity is self-asserted and fingerprints should be confirmed out of band.

    Open related docs →

Outputs

Artifacts this workflow can hand off.

The artifact matters because the claim matters. A sidecar, certificate snapshot, map workbook, comparison packet, and signed replay envelope all prove different things.

Typical Investment Banking & PE handoff set
  • Reviewed model packetInternal handoffFormula explanations, sensitivity data, and comparison/MCI notes attached to the model review.
  • Proof CertificateSnapshotWorkbook proof state as JSON with a .mxcert.signed envelope, or as branded workbook/PDF formats that remain self-hash only.
  • Evidence PackAudit handoffCertificate JSON, signed envelope, sealed ledger snapshot, and offline verifiers in one folder; Replay Proof exports remain separate.
  • .mxreplay.signedSigned replayExternally verifiable evidence for a selected output movement, subject to the replay limitations notice.

How to read the evidence

Useful, specific, and bounded.

What you seeTrustLens / Flow Diagram / CalcScope for formula review
What it meansThe page starts with the job this persona runs most often, not a generic feature pitch.
What to do nextOpen the matching workflow panel and inspect the command list before promising an outcome.
What you seeA reviewed block, comparison/MCI explanation, signed certificate envelope, Evidence Pack, and optionally a signed replay envelope for a specific output delta.
What it meansThe handoff is a package of evidence, not a blanket certification of the workbook.
What to do nextThe workflow creates review evidence. It does not certify that the deal model, assumptions, or valuation conclusion is correct.
What you seeCertificate, coverage, heatmap, issue set, or signed replay.
What it meansEach artifact answers a different review question.
What to do nextUse Certificate for proof-state snapshots and .mxreplay.signed only for externally verifiable output-delta replay.

Compare other use cases

Project Finance & PPPKeep long-tenor infrastructure models navigable, source-bound, and change-aware.Corporate FP&AExplain forecast changes, mark review status, and pressure-test close-cycle assumptions.Audit & AssuranceDefine review scope, track issues, verify proof state, and export workpaper-ready evidence.