FICTIONAL DOCUMENT PREVIEW / NOT CLIENT DATA
MARGINSPAN / MARGINSCAN / INTERACTIVE FILEMS-DEMO-001 · REV 01
A REPORT YOU CAN OPEN / NOT A SALES DECK
MS-DEMO-001 / $2.84M / NO CLIENT DATA

One project. Four findings. Every claim has a trail.Open the evidence.

Explore a fully fictional MarginScan on a $2.84 million medical office buildout. Open the findings, follow the example records, and see what a reviewer would check before making a financial claim.

ALL AMOUNTS, NAMES, RECORD IDS, DATES, AND EXCERPTS BELOW ARE FABRICATED FOR DEMONSTRATION. NO CLIENT DATA.
MS / PROJECT CONTROLSREV · A
ILLUSTRATIVE PROJECT FILE
MEDICAL OFFICE
BUILDOUT
General construction · fictional case
SITE CONTEXT / ILLUSTRATIVEFIELD CONDITION
≠ COMMERCIAL APPROVAL
TRACE THE PAPERDR-118 → RFI-042 → PCO LOG → PAY APP
REPRESENTATIVE CONSTRUCTION PHOTO · FICTIONAL PROJECT & RECORDS · NO CLIENT DATA
FILE MS-DEMO-0014 FINDINGSILLUSTRATIVE · NO CLIENT DATA
SHEET 01 / EXECUTIVE READOUT

The number is the beginning of the investigation.

On this fictional project, leadership sees a forecast moving downward. The review separates what can be priced from what still needs documentation and human judgment.

CONTRACT VALUE$2.84MIllustrative executed baseline
BUDGETED GROSS PROFIT31.8%Original budget assumption
FORECAST GROSS PROFIT26.4%Latest fictional forecast
FORECAST MOVEMENT−5.4 PTSNot the same as confirmed loss
MS-DEMO-001 / COMMERCIAL POSITIONPAY-APP-STYLE RECONCILIATION SHEET
ILLUSTRATIVE · NOT AN INVOICE
ON A PHONE, SWIPE THE BILLING LEDGER LEFT / RIGHT TO SEE EACH REVIEW COLUMN ↔
SOURCE REF.REVIEW CONDITIONFACE VALUECLASSIFICATION
PCO-LOGSix pending change orders$87,400Potential revenue; not approved
CMT-012Remaining buyout vs. allowance$41,200Calculated cost exposure
LAB-008Forecast labor above baseline+640 HRSUnpriced; excluded from total
SOV-009Billing support not reconciledNOT PRICEDMay overlap PCOs; not added
TWO SEPARATELY PRICED REVIEW ITEMS$128,600

Combined face value for review prioritization only. It is not confirmed lost profit, approved revenue, or a recovery promise.

CONTROL CHECK / KEEP THE MATH HONEST
5.4% × $2,840,000$153,360Illustrative change in forecast gross-profit dollars
$153,360 − $128,600$24,760Difference not allocated to a verified finding

These are two different views of the same project: a forecast movement and a register of identifiable conditions. Their difference is not additional recoverable money. A reviewer would reconcile forecast assumptions, labor cost rates, and potential overlap before taking action.

SHEET 02 / INTERACTIVE FINDINGS REGISTER

Don't take our word for it. Open the evidence.

Each finding starts with an observation. Expand it to follow fabricated example documents, examine what they establish, and see what would still need a real reviewer to decide.

+ CLICK ANY FINDING BELOW, THEN OPEN EACH EXAMPLE DOCUMENT
F-01 / HIGHSix change orders in the approval gapField direction exists. Commercial entitlement still needs review.$87,400POTENTIAL REVENUEOPEN ↘OPEN / CLOSE ↕
WHAT THE RECORDS SUGGEST

In the fictional PCO register, six changes total $87,400. The field trail exists, but the owner-approval status is still open. The amount is not treated as approved revenue or guaranteed recovery.

REVIEW QUESTION

What direction, notice, pricing, acknowledgment, and contract language support each individual change?

OPEN A FICTIONAL SOURCE RECORD TO FOLLOW THE TRAIL
DR-118 / FIELD→RFI-042 / SCOPE→PCO-LOG / PRICING→COR-031 / RESPONSE→PAYAPP-08 / BILLING
FIELDDaily Report DR-118VIEW EXCERPT +
SIMULATED FIELD NOTE · DEMO ONLY

“Additional partition backing installed at Level 02 per site direction. Foreman recorded crews and quantities pending formal CO approval.”

Control question: does the signed scope include this work?
RFIRFI-042 / Scope ClarificationVIEW EXCERPT +
SIMULATED DESIGN QUERY · DEMO ONLY

The drawing note references an alternate partition assembly. The response directs the revised detail but does not itself establish a negotiated change-order amount.

Control question: does the direction satisfy contractual change requirements?
PCOChange Log / PCO-014–026VIEW EXCERPT +
SIMULATED COMMERCIAL REGISTER · DEMO ONLY

Six pending proposals: $14,500 + $16,200 + $9,300 + $20,100 + $11,100 + $16,200 = $87,400. All six show “Pending”; none are classified as Approved.

Control question: verify exact items and prevent overlap with billed work.
COROwner Correspondence COR-031VIEW EXCERPT +
SIMULATED EMAIL TRAIL · DEMO ONLY

“Received the revised pricing packet. Please attach the field directives and affected drawing references before commercial review.” Receipt is not approval.

Control question: who owns the response, and when is it due?
SOVPay Application 08 / SOVVIEW EXCERPT +
SIMULATED PAY-APP CROSS-CHECK · DEMO ONLY

The approved contract schedule does not yet include these pending proposals. This is a reconciliation condition, not proof that the work is presently billable.

Control question: what is approved, completed, submitted, and billed?
RECOMMENDED HUMAN REVIEW

Validate notice and entitlement, reconcile scope and quantities, assemble substantiation, assign the PM/contract administrator an owner and due date, and update the commercial log. No recovery amount is promised.

F-02 / HIGHRemaining buyout exceeds the allowanceThe estimate-to-commitment handoff needs a cost-to-complete check.$41,200COST EXPOSUREOPEN ↘OPEN / CLOSE ↕
WHAT THE RECORDS SUGGEST

The illustrative estimate carries $312,000 for remaining packages. The updated commitment-and-quote outlook is $353,200. The $41,200 difference needs to be tested for approved scope changes, duplicate allowances, and committed versus merely quoted costs.

REVIEW QUESTION

Is this genuine cost growth, a forecast classification problem, or a scope item that can be legitimately passed through?

TRACE THE FICTIONAL ESTIMATE → COMMITMENT → FORECAST
EST-REV3 / BASELINE→PO-021 / COMMITMENTS→ETC-009 / FORECAST
ESTEstimate Rev 03 / AllowanceVIEW EXCERPT +
SIMULATED ESTIMATE CONTROL · DEMO ONLY

Remaining buyout allowance for open finishes and MEP support packages: $312,000. Baseline source identifies quantities and exclusions requiring validation.

Check: compare scope inclusions and procurement status.
POCommitment Register PO-021VIEW EXCERPT +
SIMULATED PROCUREMENT REPORT · DEMO ONLY

Committed amounts and the remaining procurement outlook total $353,200 for the same hypothetical scope grouping. Open quotes remain separately identified from executed POs.

Check: remove duplicates, allowances, and any approved owner additions.
ETCCost-to-Complete ETC-009VIEW EXCERPT +
SIMULATED FORECAST WORKPAPER · DEMO ONLY

The variance is flagged for PM review and forecast classification. Labor cost is not included in this buyout comparison, avoiding accidental double counting.

Check: update the forecast only after actual scope and procurement reconciliation.
RECOMMENDED HUMAN REVIEW

Reconcile each remaining package against executed commitments, exclusions, allowances, and approved changes. Assign forecast ownership and document the expected cost consequence. Treat the amount as a cost exposure to validate, not a recovery claim.

F-03 / HIGHLabor hours moved, but cost is unverifiedQuantities, timecards, and projected man-hours require reconciliation.+640 HRSNOT DOLLAR-PRICEDOPEN ↘OPEN / CLOSE ↕
WHAT THE RECORDS SUGGEST

The fictional productivity comparison shows 7,820 budget-equivalent hours against an 8,460-hour projected total. The 640-hour difference is a useful exception, but rate mix, earned quantities, and forecast treatment must be verified before translating it into margin dollars.

REVIEW QUESTION

Does the variance represent real productivity loss, changed scope, incomplete quantity tracking, or a stale crew forecast?

TRACE THE FICTIONAL FIELD HOURS → JOB COST → PRODUCTIVITY FORECAST
DR-124 / FIELD→TME-015 / TIME→LAB-008 / FORECAST
FIELDDaily Report DR-124VIEW EXCERPT +
SIMULATED FOREMAN NOTE · DEMO ONLY

Crew reports disrupted access and multiple remobilizations. The notes reference affected areas but contain no reviewed labor-cost claim.

Check: validate hours, earned progress, causation, and change documentation.
TIMETimesheet Extract TME-015VIEW EXCERPT +
SIMULATED LABOR RECORD · DEMO ONLY

Crew allocation codes and time-book entries support an hour-count comparison. Loaded labor rates are not provided in this example.

Check: job coding, burdened rates, and rework versus added scope.
ETCLabor Forecast LAB-008VIEW EXCERPT +
SIMULATED CONTROL WORKPAPER · DEMO ONLY

Budget-equivalent 7,820 hours. Current projected total 8,460 hours. Difference +640 hours. No cost impact is assigned and none is added to the $128,600 priced-items register.

Check: quantify only after labor-cost and production records reconcile.
RECOMMENDED HUMAN REVIEW

Validate forecast methods and earned quantities with the PM and superintendent, separate changed work from productivity variance, and price the impact only if the evidence supports it. Unquantified stays unquantified.

F-04 / MEDThe pay application lacks a clean paper trailBilling support is unresolved; the same change dollars must not be counted twice.OPENUNPRICED PROCESS RISKOPEN ↘OPEN / CLOSE ↕
WHAT THE RECORDS SUGGEST

A fictional pay-application review finds two schedule-of-values line items without an obvious approval-backup reference. The gap may relate to the pending changes already recorded in Finding F-01. No separate amount is counted.

REVIEW QUESTION

Does every submitted line tie to completed work, approved contract value, supporting records, and actual billing history?

TRACE THE FICTIONAL PAY APP → APPROVAL BACKUP → RECONCILIATION
PAYAPP-08 / SUBMISSION→SOV-009 / LINES→PCO-LOG / OVERLAP
PAYPay Application 08VIEW EXCERPT +
SIMULATED BILLING PACKAGE · DEMO ONLY

Line items for revised partitions and supplemental supports are included for backup review. Supporting approval references are blank in the review workpaper.

Check: distinguish requested billing, approved value, and amounts actually paid.
SOVSchedule of Values SOV-009VIEW EXCERPT +
SIMULATED SOV TRACE · DEMO ONLY

Two cost-code references do not map cleanly to approved contract modifications in the hypothetical document set. The workpaper requests backup, not a new claim.

Check: approval history, billing status, and contract requirements.
CTRLOverlap Check / PCO RegisterVIEW EXCERPT +
SIMULATED RECONCILIATION NOTE · DEMO ONLY

Potential connection to PCO-014–026. The billing exception is unpriced and excluded from financial totals until duplicate scope and approval are resolved.

Check: do not count one commercial condition as two separate losses.
RECOMMENDED HUMAN REVIEW

Tie the billing package, approved contract modifications, and change log together line by line. Build a clean approval packet and identify the responsible billing owner. No separate dollar exposure is claimed.

REPRESENTATIVE PHOTO ONLY · FICTIONAL DOCUMENTS & VALUES
ABOUT THIS FILE TAP TO OPEN +

A fully fictional, evidence-linked construction profitability review. No actual client, contracts, or financial records are represented.

FILE NUMBERMS-DEMO-001
FILE STATUSILLUSTRATIVE
SCOPEONE PROJECT
CLIENT DATANONE
SAMPLE DOCUMENT EXCERPTS ARE INVENTED FOR THIS DEMONSTRATION. SOURCE IDS DO NOT REFER TO ACTUAL CONTRACTS, CLIENTS, OR PROJECT FILES. NO REAL RECOVERY OR OUTCOME IS IMPLIED.
SHEET 03 / WHAT HAPPENS AFTER THE REVIEW

A finding is only useful when somebody can act on it.

The point isn't to decorate a report with red boxes. It's to give the owner and project team a defensible position, a priority, the source records, and an accountable next move.

01 / Source-backed findings

What the project record shows, what is still missing, and why the issue matters.

02 / Reconciled impact classes

Confirmed, calculated, estimated, or unquantified—never one misleading recovery total.

03 / Professional review and QA

Human judgment before a finding becomes client-facing. Exceptions and uncertainty remain visible.

04 / Owner-ready action register

Clear next steps, responsible roles, and follow-up conditions that leadership can use.

YOUR PROJECT. YOUR RECORDS. AN ACTUAL REVIEW.

Start with one project worth understanding.

MarginScan is a defined, human-reviewed construction profitability engagement—not a software subscription and not an accounting, legal, or engineering opinion. Scope and terms are confirmed before work begins.

DOCUMENT MS-DEMO-001 / END OF ILLUSTRATIVE EXCERPTNO CLIENT DATA · NO GUARANTEED OUTCOMES