Project Status Report
Week Ending XXX
Report No. XX
Base engineering assessments program (Stage X)
XXX BASE

(Purpose:This document is to be used to update project progress and status during project execution including details of any potential / current risks or issues that may impact on the project. Note: each section is to be reviewed and updated as appropriate each week to ensure all information is up to date.)

Project | Weekly report template rev7 .docx | Page 1 of 9

A. PROJECT INFORMATION
Project Number: / Phase: / Date: / Report No.: / Report for Week Ending:
Project Name: / Base Engineering Assessment Program / Project Leader:
Client: / Project Sponsor:
Attention: / Originator / Author of this document:
B. SAFETY
Are there any new WHS (P1, near
miss or LTI) issues? / No / Yes. If yes, add details to Attachment C.
C. ISSUES
Are there any newissuesor areas of concern that may affect the project budget, schedule or quality: / No / Yes. If yes,add details to Attachment D.
D. Activities UNDERTAKEN THIS reporting period
Include comments on any activities, inspections, meetings and/or report writing undertaken this week
E. Activities planned for next reporting period
Include comments on any activities, inspections, meetings and/or report writing planned for next week
F. CONTINUED IMPROVEMENT
Include comments on key risks or opportunities
distribution
BEAP team / PM/CA
AC Team Leader / AC Site / Technical Leads

Attachments:

Attachment A: Budget status

Attachment B: Schedule

Attachment C:WHS issues register

Attachment D:Budget, schedule and quality Issues register

Attachment E:Stakeholder engagement register

Attachment F:Data source register

SCHEDULE & Quality CON

Attachment A: Budget Status

(CONTENT GuideLINE)

Attachment B: Schedule

(CONTENT GuideLINE: Include a baselined/tracked gantt chart)

Attachment C: WHS Issues Register

(CONTENT GuideLINE: Enter details of any lost time injuries (LTIs, AC Organisation only) or near misses that have occurred in the reporting period including details on future mitigation measures to prevent a reoccurrence:)

The following WHS issues (P1, near misses or LTIs) have where required been reported to base stakeholders and closed out through raising a Works Request (WR) with the local CMS to address the matter. Issues identified are noted in the table below or in the attachment C:
Date of Incident / Date Reported / Details of Incident / Hazard / Base Response (inc Works request No.) / Status / Comments
e.g. 1/1/12 / e.g. 1/1/12 / Enter description / Enter assigned work # / e.g. Details of action required etc..

Attachment D: BUDGET, SCHEDULE AND QUALITY ISSUE REGISTER

(CONTENT GuideLINE)

Category / Description / Likelihood / Impact / Planned Mitigation / Control / Next Review
General
Enter either ‘Budget’, ‘Schedule ‘Quality’. / Enter description of the issue / Enter likelihood / Enter impact including estimates of cost / time implications / Enter planned mitigation / control / Enter planned review date
e.g.Base access issue / Unescorted access to Irwin Barracks requires Red Pass which takes a number of weeks to obtain. / High / Potential impact on schedule and cost /
  1. AC is currently completing documentation to obtain Red Passes, but they will not be available for the Technical visits.
  2. Escort will be provided by AC Project Manager with Defence Contractor pass.
/ Ongoing

Attachment E: Stakeholder ENGAGEMENT Register

(CONTENT GuideLINE: Example of Stakeholder Register)

No. / Time/ Date / Type of Contact / Stakeholder (Company) / Contact made by / Purpose / Infrastructure Category / Next Contact / Status / Notes
01 / 1/1/14 / e.g. Meeting, email, phone / e.g. J Smith (CMS) / e.g. AC person / e.g. Tech workshop / e.g. ICT, Electrical, Fuel etc. / 1/2/14 / e.g. Open – Awaiting feedback / e.g. link to minutes..

Attachment F: DATA SOURCE REGISTER

(CONTENT GUIDELINE: EXAMPLE OF DSR EXTRACT)

No. / Document Description / Info Type / Infrastructure Category / DEMS No / Document Issue Date / Review Date / Location / Validity / Outcome / File Path
01 / e.g. Site Plan / e.g. Electronic, Photo / e.g. ICT, Fuel / If applicable / e.g. 1/1/12 / e.g. 1/2/14 / e.g. Physical location / e.g. Valid or not / e.g. further investigations required? / Link to document

Project | Weekly report template rev7 .docx | Page 1 of 9