Weekly project status report
Put changes, milestones, risks, budget, and decisions in one report.
How to use the reportALA RESOURCES
Start with a useful working document.
Complete a template here and send it to ALA. You can also open a fillable PDF to keep with your project records.
REPORTING GUIDE
Project Status & RAID Reporting Guide
Turn updates into a report your team can use. Includes a weekly status outline, a guide to risks, assumptions, issues and dependencies, and a worked example.
Project starting brief
Define the deadline, current position, decision makers, and responsibility you need covered.
When to bring in a project managerGo-live readiness record
Record evidence, owners, accepted exceptions, and the launch decision.
Read the readiness guidePDFs open in a separate tab. Save a copy to keep your entries. If your browser does not support fillable fields, open the saved PDF in Adobe Acrobat or Preview.
SHARE WITH YOUR TEAM
ALA at a glance.
A one-page capability statement covering services, education and operational experience, and how to start an engagement.
A schedule change, in practice
The vendor is three days late.
Testing needs the vendor’s delivery. Training needs a tested system. Moving one date changes the others.
Illustrative example with fictional data.
Switch plans to see the three-day delay move through the schedule.
Download the planning templatesOperations platform rollout
October 2026
Working days
567891213141516
Vendor deliveryVendor
User testingTest lead
Staff trainingTraining lead
LaunchProject sponsor
Launch date12October
Training follows testing. Launch follows the readiness decision.
ALA’s next step
Confirm the vendor’s revised delivery, check staff availability, and take the new launch date to the project sponsor for approval.
Read the dates and assumptions
| Task | Original | Proposed |
|---|---|---|
| Vendor delivery | 5 Oct | 8 Oct |
| User testing | 6 to 8 Oct | 9 to 13 Oct |
| Staff training | 9 Oct | 14 Oct |
| Launch | 12 Oct | 15 Oct |
This example shifts dependent work by three working days. Weekends are excluded and task durations stay the same. The revised dates require vendor, staff, and sponsor confirmation; launch still depends on readiness.