Monthly Job Review for General Contracting

Obtain any company-wide guidelines or templates for monthly job reviews. Note required agenda items such as safety, cost, schedule, risk, and client issues, as well as any standard reports that must be included.

Decide what you want every review to accomplish, such as confirming forecast and contingency position, validating schedule outlook, surfacing major risks, and agreeing on specific corrective actions.

Draft a simple agenda with fixed sections (safety/quality, cost and forecast, schedule and milestones, change orders, risks and opportunities, client/contract issues, action items). Allocate approximate time to each section.

Based on project size and complexity, determine an appropriate length (for example, 60–90 minutes) and whether the review will be in-person, virtual, or hybrid. Ensure there is enough time for discussion, not just report reading.

Write a one-page description of the monthly review purpose, agenda, and expected outcomes. This becomes the reference when preparing each month’s meeting.

Provide the guide to project management, field leadership, and operations leadership so everyone has the same understanding of what the monthly job review is intended to do.

List the roles that should always attend, such as project manager, superintendent, project engineer, cost/controls lead, and operations manager. Decide which roles are optional but recommended, such as safety lead or estimating support.

Choose a recurring day and time each month that works for the core group (for example, first Tuesday of the month at 9:00 AM). Aim for a consistent slot to make planning easier.

Send a recurring calendar event to all required and optional attendees with a clear title (for example, “Monthly Job Review – Project Name”). Include location or virtual meeting link.

In the invite description, state when pre-read materials will be sent (for example, 24 hours in advance) and any expectations for attendees to review reports beforehand.

A few days before each review, quickly confirm that key decision-makers (project manager, operations manager) can attend. If critical people have conflicts, decide whether to adjust the time or proceed with delegates.

When project staff or leadership changes, promptly update the invite list so the correct people are always included in reviews.

Coordinate with accounting to confirm the cut-off date for posted costs (for example, through the end of the prior month). Use this same date for all cost reporting in the review.

Generate reports showing budget, committed, incurred-to-date, and remaining for each major cost group and cost code. Export these to a format you can work with (spreadsheet or PDF).

Using your established cost tracking process, update cost-to-complete and projected final cost by major cost group. Ensure this forecast reflects the latest information on productivity, buyout, and risks.

Run or update a summary showing approved, pending, and potential change orders, including values and brief descriptions. Highlight high-value or contentious items.

Review the reports and flag major variances, trends, or surprises that should be discussed in the meeting. Note a few plain-language talking points for each significant issue.

Combine cost, forecast, and change order reports into a single “Financials” section of the review packet. Label files clearly with report name and date so attendees can find what they need quickly.

Open the most recent schedule after it has been updated and approved through your schedule update process. Confirm the data date and that it reflects current actuals and logic.

Create a concise list or view of major milestones and their current forecast dates. Include any activities currently on the critical path and those with very low float.

Note any changes in milestone dates compared to the prior review. Mark whether dates have moved earlier, later, or stayed the same, and by how much.

Gather simple production data or percent-complete information for major phases (for example, “framing 65% complete, drywall 30% complete”). Use site reports and the schedule to support this.

List significant schedule risks, such as long-lead deliveries, design hold-ups, or trade performance issues. Also note any opportunities where productivity could pull dates forward.

Capture a screenshot of the schedule Gantt, a milestone chart, or a simple table, and add a one-page narrative summary. Place these in a “Schedule” section of the review packet.

Collect safety stats for the month: recordable incidents, near misses, OSHA inspections, and any significant safety observations or corrections. Note trends like repeated issues or improved compliance.

Look at internal quality checklists, third-party inspections, and punch lists to identify major quality issues, recurring defects, or areas where rework has been required.

Open the project risk register and update status for existing risks (likelihood and impact) and add any new risks that have emerged. Remove or downgrade risks that are no longer significant.

Select the top 3–5 risks that leadership should focus on this month. For each, note current status and key mitigation steps being taken or proposed.

Write a few paragraphs summarizing safety and quality performance in plain language, focusing on what’s going well and what needs attention.

Place safety, quality, and risk summaries into their own section of the monthly review materials so they are visible and not overshadowed by cost and schedule pages.

Gather financial, schedule, safety/quality, and risk documents into a single PDF or a clearly structured digital folder with labeled files. Include a short cover page with the review date and project name.

Write an email that explains what is included, highlights any especially important issues, and reminds attendees of the meeting date and time. Encourage them to review key sections beforehand.

Distribute the packet at least 24 hours before the meeting (longer if possible) to all attendees. Use the established distribution lists to avoid missing anyone.

Check that attached files are not too large for email limits, or provide a link to a shared drive or project platform. If using a portal, confirm permissions so recipients can open the documents.

Store the exact packet sent in a dated “Job Review” folder so you can reference it later if questions come up about what was reviewed.

On the morning of the review, send a short reminder with the meeting link/location and reference to the already-sent materials.

Join the virtual meeting or arrive in the room 5–10 minutes early. Test screen sharing, audio, and any display of the review packet. Have the agenda visible and ready.

Open by briefly restating the purpose of the monthly job review and walking through the agenda. Confirm that everyone has the packet and ask if any additional urgent topics need to be added.

Begin with a short discussion of safety and significant events since the last review. This sets context and emphasizes that performance is more than just cost and schedule.

Move through the major sections in order, highlighting key points rather than reading every line. Ask targeted questions of the project manager, superintendent, and others to prompt discussion.

Invite leadership to question assumptions, request clarification, and suggest alternate approaches where they see issues. Keep the tone constructive and focused on solutions.

Before ending, recap the most important problems and opportunities discussed, then transition into confirming decisions and action items so the meeting leads to concrete follow-up.

Bring an action log template with columns for description, owner, due date, and status. Keep it open and visible during the meeting so everyone can see items being captured.

When a decision is made (for example, “approve additional crew for drywall,” “pursue VE option B”), write it down with enough detail that someone reading later will understand exactly what was agreed.

For each action item, ask who will take the lead and by when it should be completed or updated. Avoid vague assignments like “team” or “ASAP”; always capture a name and realistic deadline.

If an action requires higher-level approval, such as adjusting budget or negotiating a claim, record who will handle the escalation and what level of approval is required.

Before closing the review, read through the action list out loud and ask attendees to confirm that it is accurate. Make corrections on the spot so there is no confusion.

After the meeting, save the log in the project’s “Job Review” folder and use it as the starting point for next month’s review and interim follow-ups.

Within a day of the review, write a brief summary of what was discussed in each major agenda section, focusing on key issues rather than every detail. Include any major concerns or positive developments that were highlighted.

Include the updated action log with the meeting notes, either as an attachment or via a link to the shared file location. Make sure the log version matches what was agreed at the end of the meeting.

Have the project manager quickly review the notes and action log to confirm accuracy and completeness. Correct any misstatements before sending to a wider audience.

Email the notes and action log to all meeting attendees and any other stakeholders who need to know the outcomes, such as accounting or estimating support.

Save the notes and log in the dated “Monthly Job Review” folder alongside the pre-read packet so all materials for that month are stored together.

If your organization uses a separate system for tracking strategic actions, enter key action items there as well, linking them to the monthly review.

Do not wait until the next month to look at the action log. At least once a week, review open items and note which ones are coming due or are overdue.

Contact each action owner as needed to confirm progress, offer help, or clear obstacles. Encourage brief status updates rather than waiting for full completion before hearing anything.

Mark actions as “In Progress,” “Complete,” or “Blocked,” and add short comments explaining current status. Keep the log up to date so it accurately reflects reality.

When actions result in changes to budget, forecast, schedule, or risk status, update the relevant systems (cost tracking, schedule, risk register) so those improvements or changes are reflected.

Before the next monthly review, summarize which actions were completed, which are still in progress, and which need further discussion. Include this summary early in the next review agenda.

If the same type of action item appears month after month, note this and consider whether a deeper process change is needed. Raise these patterns in the review so they can be addressed more permanently.