Skip to content
The first pages of the IT Project Status Report template

IT Project Status Report

Document template for Google Docs and Word

Make a copy in Google Docs
Price
Free
Style
Modern
Difficulty
Beginner
Updated
November 12, 2026

Every page (8)

Overview

Steering groups want one answer first: will the project land on time, on budget and in scope? This template gives that answer on the opening page with an overall rating and separate ratings for schedule, budget and scope, then holds the detail a delivery lead or PMO needs. It runs across eight pages: status, delivery, defects, environments, cutover readiness, risks and a guide to replacing the sample.

The sample is a fictional report from Saltmarsh Works for a testing-heavy release, with £840k spent against a £1,400k budget, one critical defect and a payments milestone that has slipped two weeks. Replace the names, dates and figures with your own baseline and current forecast, and agree the RAG thresholds with your PMO before you publish the first report.

Useful for

  • A weekly steering update where the sponsor needs only the headline and the decision
  • A release whose cutover depends on defect closure, test sign-off and client availability
  • A PMO that wants budget burn and forecast at completion on one page each week

What's included

  • Status page with overall and separate RAG ratings and headline KPIs
  • Delivery page with a milestone timeline and the gate due next
  • Defects page with a risk register, owners and the response for each defect
  • Environments page with the four test copies, data controls and the build path
  • Cutover page with five gates, a checklist of conditions and named owners
  • Risks page with a heat map, scorecard and a guide to replacing the sample

How to use it

  1. 1

    Click Make a copy in Google Docs, then confirm on the Google page. The copy is saved to your own Google Drive.

  2. 2

    Set the reporting period and replace the project name and sponsor in the title block.

  3. 3

    Rewrite the RAG rules in the key to match your PMO's thresholds, then set this period's status.

  4. 4

    Replace the milestone dates and budget figures with your baseline and current forecast.

  5. 5

    Delete the guide page, then send the report to the steering group or present it at the meeting.

What you need

Requirements

  • A Google account with access to Google Drive

Works with

  • Google Docs
  • Microsoft Word (download the .docx)

Questions

Should I report green when a milestone is late?

No. Write the RAG rules into the key first, for example amber for any milestone slipped more than a week, and report that status even when the news is unwelcome. Steering groups forgive bad news far more readily than hidden slippage.

Are the organisation, people and figures real?

No. Saltmarsh Works, the people named, the dates and every figure in this sample are fictional. Replace them with your own project data before you send a report to anyone outside the team.

How often should the report go out?

Weekly during build and testing, and daily in the final cutover week. A one-day period suits a live cutover, while a monthly report suits a steady, low-risk phase. Keep the same layout so readers learn where to look.

  • #project-status-report
  • #status-report-template
  • #weekly-status-report
  • #rag-status-report
  • #steering-committee-report
  • #project-status-update
  • #google-docs-template
  • #it-project-management

More project status report templates

See all 14

Also in Project management

All project management templates
Get this template

Preparing your template…