For Project Finance & PPP / Infrastructure

Keep long-tenor infrastructure models navigable, source-bound, and change-aware.

Bind the source inputs, map the model structure, and isolate the changes that move debt-case outputs.

Same product, every capabilityHonest evidence boundaries

Workflow stack

  1. Bind Source / Bind Vector for source integrity
  2. Trace Precedents / Dependents / Flow Diagram for navigation
  3. Worksheet Map + Risk Heatmap for structure and review triage
  4. Compare + MCI for version changes

Handoff

A source-bound input set, active-sheet map/export workbook, heatmap review lens, and comparison/MCI delta packet.

Source bindings detect drift from a captured source snapshot. They do not prove the source itself is authoritative or commercially 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. Pin the source assumptions that drive the case

    Situation

    Tariffs, inflation curves, EPC costs, debt terms, or operating assumptions need traceable source context.

    Commands used
    ModelXcel ProProofBind SourceKeytipBS
    ModelXcel ProProofBind VectorKeytipBV
    ModelXcel ProProofVerify WorkbookKeytipVW
    What the user sees
    • Source kind, target, notes, SHA-256 snapshot, vector range, and fresh/broken verdicts after verify.
    • Proof ledger records for source bindings and any later drift.
    Output artifact

    Workbook proof ledger plus bound source/vector records that can be included in a certificate snapshot.

    Caveat / limit

    Binding detects whether the captured value changed. It does not validate that the tariff, macro source, or contract term is correct.

    Open related docs →

  2. Navigate a large workbook without losing the thread

    Situation

    A 30-tab model has cross-sheet logic, external links, named ranges, and hand-edited formulas.

    Commands used
    ModelXcel ProFormula ToolsPrecedentsKeytipTP
    ModelXcel ProFormula ToolsDependentsKeytipTD
    ModelXcel ProFormula ToolsFlow DiagramKeytipFDShortcutCtrl+Shift+W
    What the user sees
    • Precedent/dependent trees, formula flow modes, cell references, named ranges, external-reference nodes, and navigation back to the grid.
    • A diagram that distinguishes formula structure from direct cell inputs.
    Output artifact

    Trace/diagram output for review notes and a list of links or formulas needing follow-up.

    Caveat / limit

    External workbook references are surfaced as references; the tools do not chase closed external workbooks as if they were open dependency graphs.

    Open related docs →

  3. Turn workbook structure into a review map

    Situation

    Before lender or authority review, the team needs to know where inconsistencies, hardcodes, and complex formulas concentrate.

    Commands used
    ModelXcel ProMapWorksheet MapKeytipWM
    ModelXcel ProMapRisk HeatmapKeytipRHShortcutCtrl+Shift+R
    What the user sees
    • A diagnostics tree, same-workbook <source>_Map sheet, map legend, and Risk/Structure/Audit heatmap modes.
    • Heatmap category counts and a heuristic health score in the legend panel.
    Output artifact

    Worksheet Maps - <timestamp>.xlsx export for selected map sheets, plus heatmap-guided review notes.

    Caveat / limit

    Worksheet Map analyzes an active worksheet and generated map sheets; Risk Heatmap is a heuristic visualization, not proof of correctness.

    Open related docs →

  4. Explain the version delta before it becomes a meeting

    Situation

    A bank case, sponsor case, or authority-return version changes DSCR, LLCR, PLCR, IRR, NPV, or another key metric.

    Commands used
    ModelXcel ProCompareCompare to Previous Version
    ModelXcel ProCompareCompare WorkbooksKeytipCO
    Compare ResultsExplain Output ChangeMCI
    What the user sees
    • Version picker, grouped workbook deltas, aligned-sheet detection, and output attribution into ranked drivers.
    • Dependency paths from changed inputs to the selected project metric.
    Output artifact

    Comparison result and MCI explanation packet for the selected output movement.

    Caveat / limit

    MCI explains selected output movement from the compared files; it is not a general assurance opinion on the model.

    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 Project Finance & PPP handoff set
  • Bound source ledgerIntegrity recordSource and vector snapshots stored in the workbook proof state and checked by Verify Workbook.
  • Worksheet Maps - <timestamp>.xlsxStructure exportSelected map sheets, summary, legend, and formula detail sheets for review packets.
  • .mxcmp / MCI exportVersion evidenceGrouped changes and output-delta attribution for the selected metric and compared files.

How to read the evidence

Useful, specific, and bounded.

What you seeBind Source / Bind Vector for source integrity
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 source-bound input set, active-sheet map/export workbook, heatmap review lens, and comparison/MCI delta packet.
What it meansThe handoff is a package of evidence, not a blanket certification of the workbook.
What to do nextSource bindings detect drift from a captured source snapshot. They do not prove the source itself is authoritative or commercially 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

Investment Banking & PEMove from inherited model review to client-ready handoff evidence.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.