09 Apr 2026 The Minimum Viable Monthly Job Review Packet (and Why It Works)
Why the “minimum viable packet” matters
Most contractors do not have a problem with job review meetings. They have a packet problem.
When every PM brings different reports, different assumptions, and different levels of detail, the meeting turns into a discovery. When the meeting turns into discovery, decisions come late—often after margin has faded, billing has lagged, and cash pressure has already built.
The goal of a minimum viable packet (MVP) is not to simplify for the sake of simplicity. It is to create a standard, repeatable packet that produces decision-grade clarity without drowning the meeting in detail.
Why job reviews break down
Common symptoms:
- The packet varies by PM or job, so leaders cannot compare jobs consistently
- The meeting is spent explaining reports instead of making decisions
- Forecasting happens live because the pre-work was not completed
- The same issues repeat because follow-ups are not captured and carried forward
These are process problems, not people problems.
What “decision-grade” reporting looks like
Decision-grade reporting answers the questions leadership actually needs to manage the work:
- What changed since last month?
- Why did it change (what is the driver)?
- What action is required now—and who owns it?
To get there, you don’t need a complex packet. You need a consistent one. A simple test: if someone asks, “Why did the margin move?”, your packet should allow the team to answer that in about 60 seconds.
The 4-page minimum viable Monthly Job Review Packet
A practical minimum viable packet typically includes four core pages. Run these for two cycles before adding anything else.
1) Cover Sheet (portfolio scan + action register)
The purpose is to prioritize meeting time (risk first), record decisions, and capture follow-ups.
The minimum fields you should include are the job list, risk flags, key issues, decision/next action, owner, and due date.
2) Summary Sheet (one page per job)
The purpose is to tell the job story on one page.
The minimum fields you should include are:
- Contract value (original + approved COs)
- Forecast GP & margin
- % complete + billing position (over/under)
- top 3 drivers / risks / actions
3) Job Cost Review (variances + forecast support)
The purpose is to connect budget, cost-to-date, and remaining cost assumptions to EAC.
The minimum fields you should include are budget, cost-to-date, cost-to-complete, EAC, variance, and the 1-3 drivers behind any material change.
Keep it at the major cost code level in leadership review. Drill down only when there’s a variance.
4) Change Order Log (pipeline format)
The purpose is to turn “change work” into collected revenue by making ownership and next actions visible.
The minimum fields you should include are CO description, amount, status, aging, next action, and owner. This prevents COs from living in email threads until they become disputes.
Where the Contract Extract fits
Contract Extract is valuable, but it is typically not a recurring monthly page for every job. Instead, treat it as an MVP component created once per job and updated only when the terms change. Use it when contract terms materially affect profit or cash: retainage terms, notice requirements, liquidated damages, billing terms, allowances/contingencies, or milestone billing rules.
Packet order (the meeting flow)
Run the packet in the same order every time. Consistency is the point.
- Summary Sheet à Job Cost Review à Change Order Log à Contract Extract (as needed)
This structure keeps the team focused on the job story first, the forecast drivers second, and the recovery actions third.
What not to include (avoid packet bloat)
The minimum viable packet works because it forces clarity. The fastest way to break it is to overload it.
- Do not bring full cost-code detail unless there is a clear exception worth discussing
- Do not attach every ERP report “just in case”
- Do not allow each PM to customize their own packet format
- Do not add optional pages until the MVP has run cleanly for two cycles
How to implement the packet in two cycles
Cycle 1 (this month): adopt the packet structure and use “good enough” data.
Cycle 2 (next month): improve accuracy and enforce standards:
- Summary sheets must be one page
- Forecast assumptions must be stated
- CO log must have next actions and owners
Why the minimum viable approach works
- It standardizes job reviews across PMs and jobs
- It shortens meetings by removing unnecessary detail
- It forces forecast discipline (pre-work happens before the meeting)
- It makes issues visible earlier and creates real accountability
Take the next step
If you want stronger job control, start by standardizing the packet, then run it twice before expanding it.
Download the Monthly Job Review Toolkit. It includes:
- The MJR Playbook
- Templates that match the packet pages
- Facilitator checklist and meeting form
If you would like a second set of eyes on your current packet, request a 15-minute Job Review Packet Review. We’ll review your current packet and identify what to simplify, what to add, and the fastest upgrades to improve decision-making.