1. Home
  2. Help
  3. Engines
  4. PM Handoff Report
Award · Engine

PM Handoff Report

PM Handoff Report is the engine that builds a printable project-kickoff package for the field PM taking over from pre-construction. From the contract and any project context you add, it produces an executive overview, financial structure, critical dates, a risk register, contacts, scope notes, week-one actions and a reviewer sign-off field.

Updated

Engine Phase: During construction Runtime: 50-90 seconds Pro+

What does the PM Handoff Report do?

PM Handoff Report takes the contract plus any project context you provide and builds a complete project-kickoff package: executive overview, financial structure, critical dates, risk register, contacts, scope notes, week-1 action list, and a reviewer sign-off field. It's structured so the field PM can print it, keep it on the truck, and know what they're walking into.

When should I use the PM Handoff Report?

Use PM Handoff Report for the handoff from pre-construction to the field PM after contract signing, when a new PM takes over a project already under way, or when an owner-side rep briefs an incoming PM agent.

What do I upload to the PM Handoff Report?

Any combination of project documents — contract, scope, permit, safety plan, schedule, procurement log. The engine reads them all together and produces one unified brief. Most users feed the signed contract plus 1–2 supplementary docs.

How do I run the PM Handoff Report?

To run PM Handoff Report, open it, upload the project bundle, run the analysis, review all the sections, add your PM notes, then export and sign off.

  1. Open the engine

    Sidebar → Engines → PM Handoff Report.

  2. Upload project bundle

    Contract + supplementary docs. The engine tolerates mixed content.

  3. Run analysis

    50–90 seconds for a typical bundle.

  4. Review all sections

    7 sections by default — expand/collapse each.

  5. Add PM notes

    Each section has an optional PM notes block you can type into before exporting.

  6. Export + sign-off

    PDF export includes the reviewer sign-off fields for the incoming PM and outgoing pre-con rep to initial.

How do I read the PM Handoff Report results?

The result is a seven-section package: project overview, financial structure, critical dates, risks and watch items, contacts, scope notes and week-one actions.

Section 1 — Project Overview

Project name, parties, site location, scope headline, contract value, duration.

Section 2 — Financial Structure

Pay schedule, retainage, LDs, bond, insurance — lifted from contract review.

Section 3 — Critical Dates

Notice periods, milestones, substantial-completion target.

Section 4 — Risks & Watch Items

Top risks + any accepted-risk markers from a chained Contract Review.

Section 5 — Contacts

Owner rep, architect, GC PM, sub leads, inspectors — extracted from contract preamble and correspondence.

Section 6 — Scope Notes

Plain-language scope summary + known exclusions.

Section 7 — Week 1 Actions

Specific actions the incoming PM should take in their first week — permits, submittals, mobilization, kickoff meetings.

Every control, explained

Run analysis

One run.

Add PM notes (per section)

Free-form notes — saved with the session, appear in exports.

Expand / collapse section

Click any section header.

Export PDF

Formatted handoff bundle with sign-off fields.

Export DOCX

Editable Word file — useful if your PM wants to fill in more detail before signing.

Copy as text

Plain-text dump for pasting into email or project docs.

Chains

Chains into

Run Full Contract Review — Run a detailed contract review to surface more risk flags and obligations for this handoff.
Generate Contract Summary — Create a concise contract summary highlighting key terms for the PM.

Chained from

Generate PM Handoff Report — Create a structured handoff brief with risks, deadlines, and action items.
Brief the PM — Owner report insights inform PM handoff with current project status and risks.

Exports

Troubleshooting

Contacts section mostly empty

Contacts aren't always in the contract itself — they come from cover emails, design-team rosters, and kickoff notes. Upload those too, or fill the contacts block manually.

Week-1 actions feel generic

Use the chat: "This is a datacenter project — regenerate week-1 actions with datacenter-specific steps." The engine adapts when given context.