A fitout risk register is one of the more useful project documents a client-side project manager can keep, and one of the most frequently abandoned. Useful, because the risks on a Sydney commercial office fitout cluster in predictable areas and a structured view of them lets the PM intervene early rather than react late. Abandoned, because risk registers that try to capture every conceivable issue become unwieldy and stop being read by the second month. The register that actually works is short, focused on the four categories where the project usually slips, and reviewed in a disciplined rhythm rather than maintained as a static document.
Those four categories, in roughly the order they bite, are building-side risks (the existing tenancy, the base building, the building’s own constraints), approval risks (landlord submission, council, certifying authorities, building-specific consents), trade-interface risks (sequencing, long-lead procurement, trade availability), and tenant-interface risks (brief still moving, decisions deferred, occupational pattern not settled). The work below is what each category usually contains, how to record the items in a way that leads to action, and how to keep the register alive rather than letting it ossify.
What A Fitout Risk Register Is, And What It Is Not
A risk register is a working document that captures the things most likely to delay, increase the cost of, or compromise the quality of the fitout, and tracks what is being done about each. It is a project-management tool. It is not an insurance document, a legal document, or a record of blame for things that have gone wrong. The point is to make uncertainty visible and to drive mitigation decisions earlier than they would otherwise be made.
The format that works best in practice is short text rather than colour-coded matrices. Each item gets a one-line description of the risk, a one-line description of the likely consequence, the action being taken, the person responsible for that action, and a target review date. Items that have closed out get marked closed and stay on the register for reference. Items that have moved get re-described to reflect the new shape. The register should fit on two or three pages by week three of the project; if it is longer, it usually contains items that should be in someone else’s running list.
Building-Side Risks In Tenancy, Base Building And Rules
The first category usually contains the most expensive surprises. The existing tenancy may have services in unexpected condition, base building elements that need attention, or fitout legacy that complicates the new work. The base building may have constraints that were not flagged at lease signing: limited goods lift access, restrictive after-hours rules, a tenancy fitout guide with provisions the design needs to accommodate. The building’s own current works (lift upgrades, services maintenance, base building refurbishment) may overlap the fitout window in ways that affect access.
The mitigations for this category mostly happen pre-construction. A pre-construction inspection of the tenancy with the fitout contractor, the mechanical contractor and ideally the electrician usually surfaces most of the legacy issues before they hit the programme. A read of the building’s tenancy fitout guide and a meeting with the building manager surfaces the rules and any current works. Risks that survive this work tend to be either lower-probability items (services that may have hidden issues but appear normal) or items where the response is contingency rather than elimination. Both are worth keeping on the register through construction so they are not forgotten if they materialise.
Approval Risks: Landlord, Council And Certifying Parties
Approvals are usually where the most predictable slip happens. The landlord’s review of the fitout drawings is the most common source. Most Sydney CBD landlords take two to four weeks for an approval, sometimes longer where the design touches the base building envelope, services beyond the standard, or anything visible from outside the tenancy. Approval is rarely a refusal; it is more often a sequence of conditions, queries, or required modifications that have to be cleared before site works can mobilise. Each round of comments resets some portion of the clock.
Where the fitout requires council approval (a development application or complying development certificate), the timing is usually longer and less flexible. Council DAs run on their own timetable, and the project programme has to be built around it rather than the other way around. Building Code of Australia certification, fire engineering reports, and accessibility certifications are usually contractor-managed but can introduce conditions late in the project that affect the fitout scope.
The cleanest mitigation is early submission and early conversations. Landlord submission as soon as drawings are at the right level of completeness, not at design freeze. Pre-submission conversations with the building manager about likely conditions. If a council pathway is involved, that conversation moves to the front of the programme rather than the middle. Risks that remain on the register through construction are usually about late conditions from certifiers rather than principal approvals, which by that point should have closed out.
Trade-Interface Risks Across Sequencing And Trades
Inside the construction window, the trade interfaces drive most of the slip. The most common cluster of trade-interface risks comes from long-lead procurement: custom joinery, frameless glass partitions, operable walls, specialist ceilings, sometimes lighting and AV. Each item ordered late lands too close to the date it has to be installed, with no contingency for damage in transit or last-minute manufacturing issues. The mitigation is identifying these items in the first programme draft and committing the orders early, with the design specifying them to a level that lets that early commitment happen.
Sequencing risks are the next layer. Services rough-in finishing late delays partition closure. Partition closure delaying late delays finishes. Joinery delivery landing into wet trades causes damage and rework. Each of these risks is contractor-managed in the daily coordination, but the PM’s register should capture the milestone-level interfaces where slip in one trade has consequences for the others. Trade availability is the third layer: trades whose specialised crews are committed to other projects in the same fortnight may not be able to recover lost time even where the contractor wants to. Where the project depends on a particular trade for a specialist scope, the register should note the contingency plan, not just the risk.
Tenant-Interface Risks: Brief Moving, Decisions Deferred
The tenant’s own readiness is often the largest source of risk on a fitout, and the one PMs are most reluctant to put on the register. Briefs that are still moving in the design phase. Layout decisions that the business has deferred. AV and IT scope that has not been signed off. Loose furniture decisions that lag the construction programme. Move-in plans that do not reflect what the build is actually delivering on the day.
These items belong on the register because they are real risks to the project, even though the risk holder is the tenant rather than the contractor. Surfacing them in writing usually drives the conversations that resolve them. “AV scope not signed off, design freeze in three days, programme slips a week per week of slip after that” is a sharper statement than a series of polite reminders. The PM’s job is to convert the ambiguity into a clearly stated risk, not to chase the decision personally. Where the business sees the consequence in writing, the decision usually moves.
Hybrid attendance and headcount uncertainty are a related risk where the project is delivering a layout sized to a working pattern that is still settling. If the floor is being built for sixty people with assumed peak attendance of forty, and the actual pattern turns out to be peaks of fifty-five, the meeting room mix and the booth ratio may not stand up. The mitigation usually involves designing for flexibility (modular partitions, scalable booth installations) rather than committing to a single attendance assumption. Where the assumption is firm, the register should still note the uncertainty so that the post-occupation review captures any drift.
Quantifying And Ranking Risks Without Overformalising
Most fitout risk registers run for a while as colour-coded matrices and gradually lose their usefulness because the matrix becomes the focus rather than the underlying issue. A simpler form usually works better: high, medium, low across two axes (likelihood, consequence), with the ranking written in plain English and the rationale captured in a sentence. Items that are high-high get attention every week. Items that are medium-anything get attention every fortnight. Items that are low-low get reviewed monthly or whenever something changes.
The point of the ranking is to drive where the PM’s attention goes, not to produce a dashboard for executives. A register where every item is yellow has stopped being useful. The discipline is to hold the line on the low-rank items so the high-rank ones get the attention they actually need. When a risk’s circumstances change, the ranking should change and the rationale should update. A register where the rankings have not moved in six weeks is usually a register that has not been read in six weeks.
Mitigation, Contingency And The Difference Between Them
Mitigation reduces the likelihood or consequence of the risk before it materialises. Early procurement of long-lead items is mitigation. Pre-construction services inspection is mitigation. Early landlord submission is mitigation. Where mitigation is possible and proportionate, the action belongs in the register against the risk it addresses, with a target completion date and a person responsible.
Contingency is what the project does if the risk materialises despite mitigation. Time contingency on the programme. Cost contingency in the budget. An alternative supplier identified for a specialised trade. A backup product specified for a long-lead item. Contingency is usually less specific than mitigation but should still be captured in the register: what the response is, what it costs, and how long it takes to mobilise. Risks where the only entry under contingency is “deal with it when it happens” are usually risks where the contingency has not actually been thought through.
The Review Cadence: Keeping The Register Alive
The register only does its job if it is read and updated on a rhythm. Weekly during construction is the usual baseline, with the PM reviewing the high-ranked items and any changes since the previous week. Fortnightly suits projects in the design and procurement phase where the pace is slower. Monthly is enough for low-tempo phases and post-handover defects management. Less than monthly and the register starts to drift from reality.
The format that survives is one where the register is a working document inside the project’s normal weekly meeting cadence rather than a separate review session. Five minutes at the end of the weekly site meeting is usually enough to confirm that nothing has changed on the high-ranked items, surface anything new, and update target dates for closed-out items. Where the weekly site meeting is purely operational and the register lives elsewhere, it usually fades. Where the register is the back-end of the weekly meeting, it stays current and the project has the visibility it needs.
If you are running a Sydney commercial office fitout from the client side and want a contractor whose project administration integrates cleanly with your risk register and the discipline behind it, we can walk you through how we structure procurement, approvals and trade interfaces against the same risk categories, and price the work in a way that makes the contingency lines explicit rather than buried.
📞 Call us on 1300 60 93 93