Identify Risk Process | Project Documents Inputs
Sep 08, 2026
In the complex landscape of Australian architecture and construction, starting the risk identification process without reviewing your existing documentation is like designing a building without checking the site survey.
Under the Project Management Institute (PMI®) standards outlined in the PMBOK®, Project Documents represent the second major input category for the Identify Risk process.
This category consists of eight essential documents that house the assumptions, constraints, and historical data necessary to identify potential threats before they derail your budget or schedule.
For Australian architects, these PMI-aligned documents map perfectly to everyday project management and architectural practice tools.
The 8 Critical Project Documents and Their Australian Equivalents
1. Assumption Log (Local Equivalent: Design Briefs & Planning Reports)
Assumptions and constraints recorded here can directly influence individual and overall project risks.
In local practice, reviewing your Design Briefs and Planning Reports helps uncover hidden assumptions regarding client expectations or local council planning controls that might threaten compliance.
2. Cost Estimates (Local Equivalent: Quantity Surveyor Cost Plans)
These provide quantitative assessments of project costs, ideally expressed as a range. Conducting a structured review of your Quantity Surveyor Cost Plans (e.g., Concept, Schematic, or Detailed Cost Plans) reveals whether the current budget estimate is insufficient, posing a major risk to the project's viability.
3. Duration Estimates (Local Equivalent: Project Schedules)
These present quantitative timeline assessments. Reviewing your Project Schedules as a range of durations highlights tight buffers or unrealistic milestones that threaten your delivery timeline.
4. Issue Log (Local Equivalent: Site Reports)
Active issues logged during construction can escalate into severe, long-term project risks. Reviewing Site Reports regularly helps identify unresolved structural, material, or labour issues before they impact future phases.
5. Lessons Learned Register (Local Equivalent: Post-Project Reviews)
This register captures risk lessons from earlier project phases or historical projects to see if similar risks might recur. In local firms, checking Post-Project Reviews prevents you from repeating past design or compliance mistakes.
6. Requirement Documentation (Local Equivalent: Client Briefs)
This lists all project requirements, enabling the team to target high-risk deliverables.
Reviewing the Client Brief ensures complex design goals such as high sustainable performance targets or specific zoning approvals are flagged early.
7. Resource Requirements (Local Equivalent: Resourcing Plans)
These assess the quantitative resource needs of a project.
Examining Resourcing Plans helps determine if labour, consulting engineers, or specialised builder capacities are insufficient, which could compromise project quality and schedule.
8. Stakeholder Register (Local Equivalent: Stakeholder Matrices or Consultation Logs)
This register indicates which individuals, consultants, or community groups should participate in identifying risks and who is available to act as a dedicated risk owner.
Using a Stakeholder Matrix or Consultation Log ensures critical project actors are aligned.
Next Step: Moving Beyond Internal Documents
Reviewing these eight internal project documents is a vital step in robust risk planning.
In our next post, we will expand our boundaries to look at Agreements, exploring how contract types, milestone schedules, and penalty clauses serve as the third critical input for identifying risks in your projects.
Course Information & Syllabus Download
Click on the image below to explore and find out more about our 12-hour online training regarding risk management for architects that is aligned with 12 CPD. The link will take you to the landing page of the course, where you can download the full syllabus, find details, and see how it has been mapped to NSCA 2021.
