Weekly site report template for Project Managers

No document repeats as often on a PM's calendar as the weekly site report, and few carry as much weight in how the developer or leadership perceive the project. With a template already built, filling it in takes 15–20 minutes with that week's data, instead of starting every Friday from a blank sheet.

It starts with the basics — project, responsible PM, week number or date, recipient — and moves into the RAG status indicator: red, amber or green for Schedule, Cost, Scope, Quality and Risks, each with a one-line justification. Next come the indicators: percent of work complete, cost executed, milestones completed out of the total, and open issues, each with its planned figure, actual figure, the deviation between the two, and the trend.

The rest of the document covers activities completed this week and planned for the next — each with its owner, status or date and a comment —, active risks with their probability, impact, action and owner, and closes with a section for pending decisions and next steps.

Built to be filled in the same day as the weekly cutoff, with that week's numbers already closed, the result needs no touch-up: it goes straight to the developer or leadership as is.

This report's numbers are only as good as the source data: percent complete or cost deviation is only useful if it comes from that week's takeoff and budget, not a figure recalled on Thursday afternoon. Bloqbase keeps that data current as each project progresses, so filling in the status indicator starts from a figure already available in the project, not rebuilding it from scratch before sending the report.

The template is free with your email. And if you'd rather see that status indicator generate itself, with nobody updating it by hand every week, tell us your case and we'll show you inside Bloqbase.

How to put it to work on a real project

The idea isn't to download another file and forget it in a folder. Use it with a specific case: a pending certificate, a coordination meeting, a cost overrun or a handover to the developer. Fill in the resource with real data from your project, validate the result with your own technical judgment, and keep it as an internal reference to repeat the process next time.