1. Internet Access Control Project Status
Peter Wiegard
12th December 2017

2. <Project Name> - Project Status Report as of <Date>
Project Objective: <Max 2 line summary of the project objectives. This normally would be your first one or two sentences of the respective section in the PID.>
Project Sponsor
Project Manager
Start Date
(Business Case approved)
Final delivery
(Practical completion)
<Sponsor name>
<Project Manager name>
<Actual date>
<Planned or actual date>
Overall Project Status
Key Milestones
Nov 18
Dec 18
Jan 19
Feb 19
Mar 19
Apr 19
Decisions and guidance requested
<List the decisions or instructions from the board you request. Be concise and confirm any decisions and guidance given is also minuted. This also includes project change requests submitted for approval.
Use “None requested”, when needed.>
Baselined 2 1 3 4 5
8 Nov
1 Dec
15 Dec
22 Dec
31 Jan
Actual or planned 1 2 3 4 5
15 Dec
17 Dec
22 Dec
19 Jan
31 Jan
KEY MILESTONES PRESENTED ABOVE
<Milestone name>
Budget
Actuals (total project)
<Total approved budget $>
<Actual spend to date $>
Remaining (forecast)
Estimate at completion
<Future spend $>
<Total project cost $>
Significant risks and issues
<List any significant risks and issues (rating ‘high’) and remediation activity. Use headline level in the text.>
Deliverables or activities completed in this period
<List the deliverables completed in this reporting period.>
<Alternatively, you may refer to some key activities, e.g. a design workshop with users, kick-off meeting with a vendor, etc.>
Deliverables or activities in the next period
<List the deliverables planned to be completed in the next reporting period.>
<Alternatively, you may refer to some key activities, e.g. a design workshop with users, kick-off meeting with a vendor, etc.>
Gray
Originally planned or completed activity
Green
On track; will complete as planned A
Yellow
Planned delivery at risk
Red
Will miss planned date

3. <Project Name> - Project Status Report as of <Date>
This slide instructs on how selected fields are used.
Text in [square brackets and small blue font] are guidance notes for what data is to be provided. This slide must be removed from the report issued.
<Project Name> - Project Status Report as of <Date>
[Project name as in the PID, the formal and full name of the project.]
Project Objective: <Max 2 line summary of the project objectives. This normally would be your first one or two sentences of the respective section in the PID.>
Move the arrow left/right, as needed.
Project Sponsor
Project Manager
Start Date
(Business Case approved)
Final delivery
(Practical completion)
<Sponsor name>
<Project Manager name>
[The date when the Business Case was approved. This is the date when the project formally commences.]
[The date when the last delivery is made and handed over to the users. The project will continue to the DLP or Close stage.]
Overall Project Status
Key Milestones [Timeline is monthly for the next 6 months (rolling 6 months).]
Decisions and guidance requested
<List the decisions or instructions from the board you request. Be concise and confirm any decisions and guidance given is also minuted. This also includes project change requests submitted for approval.
Use “None requested”, when needed.>
Nov 18
Dec 18
Jan 19
Feb 19
Mar 19
Apr 19
Baselined
Six months rolling timeline only. 2 1 3 4 5
8 Nov
1 Dec
15 Dec
22 Dec
31 Jan
Actual or planned [Use traffic light colours to indicate the status of each milestone] 1 2 3 4 5
Current figures and numbers only.
15 Dec
17 Dec
22 Dec
19 Jan
31 Jan
KEY MILESTONES PRESENTED ABOVE [Only for the next 6 months. Milestones after that will be eventually come into the future reports.]
<Milestone name>
Budget
Actuals (total project)
[Latest approved / revised budget for the total project.
If operational with no budget, state ‘Opex’.]
[Latest known spend for the total project.
If operational and spend is untracked,
state ‘Opex’.]
Remaining (forecast)
Estimate at completion
[Latest forecast of remaining work + purchases for the total project. If operational with no forecast, state ‘Opex’.]
[This field = Actuals + remaining]
Significant risks and issues
<List any significant risks and issues (rating ‘high’) and remediation activity. Use headline level in the text.>
[Refer to your Risk / Issue Register ID’s and risk / issue names.]
Deliverables or activities completed in this period
<List the deliverables completed in this reporting period.>
<Alternatively, you may refer to some key activities, e.g. a design workshop with users, kick-off meeting with a vendor, etc.>
Deliverables or activities in the next period
<List the deliverables planned to be completed in the next reporting period.>
<Alternatively, you may refer to some key activities, e.g. a design workshop with users, kick-off meeting with a vendor, etc.>
Gray
Originally planned or completed activity
Green
On track; will complete as planned A
Yellow
Planned delivery at risk
Red
Will miss planned date