In most construction projects, documentation is seen as a technical exercise.
Plans are drawn, requirements are addressed, and information is compiled with the expectation that it will support a smooth approval process.
But in practice, that is not always what happens.
Even when documentation is prepared to a high standard, projects can still experience delays, requests for further information and unexpected revisions.
One of the reasons for this sits in what could be described as a perception gap.
What the Perception Gap Actually Means
The perception gap is not about whether documentation is good or bad.
It is about how that documentation is experienced by different stakeholders in the process.
In recent industry feedback, two simple questions were asked:
• Designers were asked how confident they are in the quality of the documentation they produce
• Building surveyors were asked how they experience the documentation they receive
The responses did not align.
Designers generally rated their documentation highly.
Building surveyors were more measured in their response.
That difference highlights something important.
The same set of drawings can be interpreted in very different ways depending on where you sit in the process.
Why This Gap Exists
There is no single cause of the perception gap.
It tends to emerge from a combination of factors that build over time.
These include:
• Different interpretations of regulatory requirements
• Assumptions about what is considered “clear” or “complete”
• Varying levels of detail across documentation sets
• Time pressures that influence how information is prepared
Technology has improved how documentation is created.
But it has not removed the human element of interpretation.
And that is where the gap often sits.
How the Perception Gap Shows Up in Projects
The impact of this gap is rarely obvious at the point of submission.
Instead, it tends to appear during assessment.
Common outcomes include:
• Requests for further information
• Clarification around compliance pathways
• Revisions to drawings or supporting documentation
• Delays that extend approval timeframes
At that stage, changes are more difficult to manage.
Multiple stakeholders are already involved, and project timelines are in motion.
What starts as a small difference in interpretation can quickly escalate.
The Role of Technology in the Gap
It would be easy to assume that better technology solves this issue.
In reality, the relationship is more complex.
The industry now has access to advanced tools that improve accuracy and coordination.
However, those tools do not guarantee consistency.
The perception gap often exists not because technology is lacking, but because it is used differently across teams.
Even small inconsistencies in how systems are applied can lead to different outcomes.
Technology supports the process.
It does not replace the need for alignment.
When the right technology is implemented consistently across project teams, it can significantly improve standardisation, reduce ambiguity and support clearer communication between stakeholders. Used well, it becomes a tool that helps bridge the gap rather than contribute to it.
Bridging the Gap Starts Earlier Than Most Think
Addressing the perception gap is not about adding more information at the end of the process.
It is about improving alignment at the beginning.
This means:
• Being clear on how documentation will be interpreted, not just how it is prepared
• Identifying potential compliance questions earlier
• Structuring information in a way that supports efficient assessment
• Reducing reliance on assumptions between stakeholders
When this happens early, it reduces the need for rework later.
A Shift in Perspective
One of the more valuable shifts the industry can make is recognising that documentation is not just a deliverable.
It is a form of communication.
And like any form of communication, it is only effective if it is understood as intended.
This requires a move beyond technical completeness.
It requires clarity, consistency and an awareness of how information will be interpreted by others.
Final Thoughts
The perception gap is not about fault.
It is about alignment.
Most project teams are working with the right tools and strong technical capability.
But even high-quality documentation can lead to delays if it is not interpreted consistently.
Bridging that gap is where meaningful improvements can be made.
And where smoother, more predictable project outcomes begin.
At Deemed to Perform, we work with builders, designers and developers to improve documentation clarity and alignment early in the process. If you are experiencing delays or ongoing requests for further information, our team can help identify the gaps and provide practical guidance to keep your project moving.
📞 hello@deemedtoperform.com.au| 0404 300 268
