1. Home
  2. Help
  3. Engines
  4. Owner Report
Field & Compliance · Engine

Owner Report

Generate an executive project-health summary for owners and stakeholders. Rolls up engine-run history, tracker state, risks, and schedule variance into a 1–2 page brief.

Engine Phase: Field & Compliance Runtime: 40-80 seconds Pro+

What it does

Owner Report pulls from everything the project has accumulated — engine sessions, tracker rows, risk flags, schedule data, budget burn — and synthesizes an executive brief: project status, schedule variance, budget position, top risks, RFI/CO/submittal counts, and PM asks-of-the-owner for the next period.

Use it for monthly owner meetings, stakeholder updates, and board-level reporting. One click replaces an hour of PowerPoint.

When to use it

What to upload

No upload required by default — the engine pulls from the active project's state. You can optionally upload a narrative brief or recent progress report to add context the tracker state doesn't capture.

Step by step

  1. Open the engine

    Sidebar → EnginesOwner Report.

  2. Set reporting period

    Week / Month / Custom date range. Defaults to "since last report" if you've run this engine before.

  3. Optionally add narrative

    Paste or upload any PM notes / progress narrative you want integrated.

  4. Run

    30–60 seconds — the engine scans your project's engine sessions + tracker state + schedule for the period.

  5. Review sections

    Executive summary, schedule position, financial position, RFI/CO/submittal counts, top risks, PM asks.

  6. Export

    PDF (formatted for owner meetings) or PPTX (editable deck with one slide per section).

Understanding the results

Executive summary

2–3 sentences — project status + the one or two things the owner needs to know.

Schedule position

Variance vs baseline, projected substantial-completion date, critical-path items at risk.

Financial position

Budget burn, CO totals, anticipated remaining cost, contingency remaining.

Activity counts

RFIs + COs + submittals + pay apps this period, with response-time stats.

Top risks

Pulled from engine runs + tracker flags over the reporting period.

PM asks

Specific decisions or inputs the PM needs from the owner before the next reporting period.

Every control, explained

Reporting period selector

Week / Month / Custom.

Include narrative input

Free-form text for PM-side context.

Run analysis

One run.

Export PDF

Owner-meeting report.

Export PPTX

One slide per section — editable deck.

Copy as email

Pastable text version for inline-email update.

Chains

Chains into

Brief the PM — Owner report insights inform PM handoff with current project status and risks.

Chained from

Contract Context for Report — Contract terms and risks carry forward to provide context in the owner progress report.
Include in Owner Report — Pay app data carries forward \u2014 budget performance and billing status feed into the owner report.
Feed Daily into Report — Daily field data carries forward \u2014 aggregated into owner progress reports.
Closeout Status Update — Punch list completion percentage feeds into owner report closeout section.

Exports

Troubleshooting

Report is too thin

Project state is limited — fewer engine runs and tracker items means less for the engine to synthesize. Add a narrative brief in the input to give it context, or run more engines first.

Schedule variance missing

Requires a baselined schedule in the Schedule tool. Without a baseline, the engine can't compute variance.