For Audit & Assurance / Risk

Define review scope, track issues, verify proof state, and export workpaper-ready evidence.

Turn model review into evidence: findings, status, proof coverage, and the right artifact for the claim.

Same product, every capabilityHonest evidence boundaries

Workflow stack

  1. Model Health + Cell Search + Circular Refs for review scope
  2. Model Sentinel for adopted workbook checks, declared gap checks, and new-failure alarms
  3. Review Issues / Flag Cell + highlights for findings
  4. Audit Trail / Mark Cell + Highlight Audit for status
  5. Coverage / Verify Ledger / Seal Ledger / Certificate / Evidence Pack / Replay Proof for proof evidence

Handoff

A model-health scope, circular-reference findings, Sentinel check state, issue set, audit-status sidecar, proof coverage/ledger verdict, signed certificate envelope or Evidence Pack, and the correct replay artifact when the claim is output movement.

ModelxcelPro supplies evidence and integrity checks. It does not issue an audit opinion or prove model correctness.

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. Define the review scope

    Situation

    An audit or model-risk reviewer needs to find errors, hardcodes, volatile formulas, complex formulas, and other high-review areas.

    Commands used
    ModelXcel ProAuditModel HealthKeytipMH
    ModelXcel ProAuditCell SearchKeytipCS
    ModelXcel ProAuditCircular RefsKeytipCR
    ModelXcel ProMapRisk HeatmapKeytipRHShortcutCtrl+Shift+R
    What the user sees
    • Workbook diagnostics, attribute-based search results, circular-reference loop paths, and heatmap concentrations by risk, structure, or audit mode.
    • Counts for errors, hardcodes, volatile functions, external references, and complexity bands.
    Output artifact

    Model Health report, search result list, Circular Refs result list, and heatmap-driven review scope.

    Caveat / limit

    Diagnostics identify review areas. Circular Refs scan is read-only; Probe Convergence recalculates only behind explicit consent, and Break Loop restores through .mxbreaks and Restore Broken, not Ctrl+Z.

    Open related docs →

  2. Watch model checks and gap checks

    Situation

    The workbook already has audit sheets, named check cells, inline check rows, or a key-results register, and reviewers need to know what newly failed.

    Commands used
    ModelXcel ProAuditModel SentinelKeytipMS
    What the user sees
    • Adopted workbook checks, declared gap checks, current pass/fail state, baseline comparison, and alarms only for failures new against that baseline.
    • After a version compare, register rows can use Explain value to route a movement into Material Change Intelligence.
    Output artifact

    .mxchecks sidecar, Sentinel snapshot evidence, certificate Sentinel summary with declared-check count when present, and Evidence Pack inclusion when .mxchecks is present.

    Caveat / limit

    Declared checks are sidecar-only and labelled as yours, not the model's own. Model Sentinel does not change the workbook, unhide sheets, recalculate, run macros, or insert formulas.

    Open related docs →

  3. Track findings where the cells live

    Situation

    Findings need severity, status, comments, ownership, and a way to return to the exact cell later.

    Commands used
    ModelXcel ProAuditReview IssuesKeytipRI
    ModelXcel ProAuditFlag CellKeytipFC
    ModelXcel ProAuditHighlight IssuesKeytipHI
    What the user sees
    • Issue tracker rows with severity, status, tags, comments, filters, and navigation.
    • Severity-colored highlights for currently open issues.
    Output artifact

    .mxreview sidecar and exported issue sets or CSV review packets.

    Caveat / limit

    Issue records persist; highlight colors are a review lens and can be toggled or stripped without deleting the issue set.

    Open related docs →

  4. Record review status and coverage

    Situation

    Reviewed cells need a clear status trail that survives the workbook session and supports coverage discussion.

    Commands used
    ModelXcel ProAuditAudit TrailKeytipAT
    ModelXcel ProAuditMark CellKeytipMC
    ModelXcel ProAuditHighlight AuditKeytipHA
    What the user sees
    • Verified, Questionable, Needs Attention, and Erroneous statuses with reviewer notes and coverage summaries.
    • Status-colored highlights for reviewed cells.
    Output artifact

    .mxaudit sidecar and optional audit-status report.

    Caveat / limit

    Audit status is reviewer evidence, not an automated assurance conclusion. The sidecar must accompany the workbook when shared.

    Open related docs →

  5. Verify proof state and choose the right artifact

    Situation

    The reviewer needs to know what is bound, signed, drifted, or tampered with, and whether the export is the right kind of evidence.

    Commands used
    ModelXcel ProProofCoverageKeytipCC
    ModelXcel ProProofVerifyKeytipVL
    ModelXcel ProProofSeal LedgerKeytipSL
    ModelXcel ProProofCertificateKeytipCT
    ModelXcel ProProofEvidence PackKeytipEP
    ModelXcel ProProofReplay ProofKeytipRP
    What the user sees
    • Coverage percentages for bound inputs and signed formulas, ledger integrity verdict, and drift from Verify Workbook when used.
    • Certificate export fields, Evidence Pack contents, and Replay Proof signed-envelope export when a selected output delta needs independent verification.
    Output artifact

    Coverage/ledger verdict, .mxcert.signed Certificate snapshot, Evidence Pack, or .mxreplay.signed output-delta proof.

    Caveat / limit

    Coverage percentages do not mean every important cell was reviewed. Certificate JSON and Replay Proof are both signed when their envelopes are exported, but they answer different questions: ledger state versus output movement.

    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 Audit & Assurance handoff set
  • Model Health reportScope evidenceWorkbook diagnostics used to target review procedures.
  • .mxchecks + .mxbreaks + .mxreview + .mxauditWorkpaper sidecarsSentinel adopted and declared checks, Circular Refs restore data, issue records, and audit statuses that preserve review context beside the workbook.
  • Coverage / Certificate / .mxreplay.signedProof evidenceCoverage and ledger state, signed Certificate JSON envelope or Evidence Pack for ledger state, or signed output-delta replay depending on the claim.

How to read the evidence

Useful, specific, and bounded.

What you seeModel Health + Cell Search + Circular Refs for review scope
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 model-health scope, circular-reference findings, Sentinel check state, issue set, audit-status sidecar, proof coverage/ledger verdict, signed certificate envelope or Evidence Pack, and the correct replay artifact when the claim is output movement.
What it meansThe handoff is a package of evidence, not a blanket certification of the workbook.
What to do nextModelxcelPro supplies evidence and integrity checks. It does not issue an audit opinion or prove model correctness.
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.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.