This video explains how to document findings from the readiness check, organise compliance efforts, assign responsibilities, and prepare materials for audit readiness. The written guide below covers how to mark completed requirements, highlight gaps with status tracking, assign each gap to the right team member, add comments for context and accountability, and begin organising your documents so that audit preparation is smoother and more efficient.
How documenting findings turns your readiness check into a structured compliance plan
The readiness check gives you a clear picture of where your processes stand against ISO 19650. But a picture alone does not drive improvement. The next step is turning those findings into a structured plan with defined actions, clear ownership, and organised evidence. This is where the compliance journey shifts from assessment to execution, and it is the bridge between your readiness check and the formal gap analysis report that will guide your team through to audit readiness.
The process starts with the compliance checklist you have already worked through. For every requirement that your current processes already meet, check the box and mark the task as complete. This is important because it documents your existing compliance, not just your gaps. When the auditor reviews your status, they need to see evidence that compliant processes are in place, not just a list of things that were fixed. For requirements that are not met, leave the checkbox unchecked and change the status to highlight the gap. Using a status like “identified gap” makes these items immediately visible for follow-up and ensures they do not get lost among completed tasks.
Each identified gap needs an owner. Assigning a gap to a specific team member creates accountability and ensures that every issue has someone responsible for resolving it. Without clear assignment, gaps remain as observations rather than actions, and they tend to stall. The Kanban view makes it easy to assign tasks quickly and see at a glance who is responsible for what, while status tracking across grid, timeline, and Kanban views gives the whole team visibility into where things stand.
Comments are equally important. Adding a note to each gap explaining why the requirement is not met, what steps are needed to address it, or what constraints exist creates the context that team members need to take action. A bare checklist item that says “not met” does not tell anyone what to do next. A comment that says “need to collaborate with the project team to define milestones and link them to decision points” gives the assigned person a clear starting point. These comments also become part of the audit trail, showing the auditor that gaps were identified, understood, and addressed through a deliberate process rather than discovered at the last minute.
While documenting findings, it is also the right time to start organising your documents for the audit. This means importing your compliance materials into the Docs module and structuring them as smart documents using templates from previous projects or the Plannerly library. Centralising everything in one place, rather than scattering evidence across email threads, shared drives, and local files, saves significant time when the audit arrives. It also means that as you address gaps and create new processes, the documentation sits alongside the checklist items they relate to. The full BIM workflow approach can reduce administrative effort by up to 80% compared to managing compliance materials across disconnected tools, and starting this document organisation early means you benefit from that efficiency throughout the entire compliance journey rather than only at the end.
By the end of this step, you will have a structured, actionable view of your compliance status: requirements that are met are documented with evidence, gaps are visible with assigned owners and contextual comments, and your documents are starting to take shape in a centralised, audit-ready format. This is exactly what you need to generate the gap analysis report in the next stage, summarising everything into a clear document that guides your team through to certification.
How to document findings and assign compliance actions
- Mark met requirements as complete – For every checklist item where your current processes already align with ISO 19650, check the box and mark the task as complete. This documents your existing compliance and provides evidence for the auditor that these processes are in place.
- Highlight unmet requirements with status changes – For items that are not met, leave the checkbox unchecked and change the task status to something visible like “identified gap”. This makes gaps immediately distinguishable from completed items and ensures they appear in filtered views for follow-up.
- Assign each gap to a team member – Use the Kanban view or the task assignment feature to delegate each gap to the person best placed to resolve it. Clear ownership is essential for turning observations into actions.
- Add comments for context – For every gap, add a comment explaining why the requirement is not met, what steps are needed, or what constraints exist. Comments like “need to define metadata assignment process and train the team” give the assigned person a clear starting point and create an audit trail showing deliberate gap resolution.
- Attach supporting evidence – Where compliance is already in place, attach the evidence: documents, screenshots, process descriptions, or training records. Having evidence alongside the checklist item means the audit proof is centralised from the start rather than gathered at the last minute.
- Start organising audit documents – Import your compliance materials into the Docs module using templates. Structure them as smart documents so they follow the standards and are easily accessible by the whole team and any future auditor.
- Use status tracking to monitor progress – Use grid, timeline, and Kanban views to track the status of every gap across your team. This gives everyone visibility into what has been addressed, what is in progress, and what still needs attention.
- Prepare for the gap analysis report – With all findings documented, gaps assigned, comments added, and documents organised, you are ready to generate the gap analysis report that will summarise your compliance status, highlight action items, and guide your team through to audit readiness.
What you’ll learn
- Documenting compliance and gaps – How marking met requirements as complete and highlighting unmet requirements with visible statuses creates a structured, actionable view of your compliance position that works for both your team and the auditor.
- Assigning ownership for accountability – Why every identified gap needs a named owner, and how task assignment and Kanban views make it easy to delegate responsibility and track who is working on what.
- Adding context through comments – How comments on each gap create the context that team members need to take action and the audit trail that demonstrates deliberate, structured gap resolution rather than last-minute fixes.
- Early document organisation – Why starting to centralise and structure your compliance documents early in the process saves significant time at audit, and how smart document templates reduce administrative effort across the entire compliance journey.
- Status tracking for team visibility – How using grid, timeline, and Kanban views to monitor the status of every gap keeps the whole team aligned and ensures that nothing falls through the cracks between the readiness check and the audit.
- Building toward the gap analysis report – How the documented findings, assigned actions, and organised evidence from this step become the foundation for the formal gap analysis report that guides the rest of the compliance programme.
Common questions
Why is it important to document met requirements, not just gaps?
Documenting met requirements is essential because the auditor needs to see evidence that compliant processes are in place, not just a record of what was fixed. Checking boxes and attaching evidence for requirements you already meet creates a complete picture of your compliance status. It also gives your team confidence by showing how much of the standard they are already aligned with, rather than focusing only on what is missing.
What status should I use for identified gaps?
Use a status that makes gaps immediately visible and distinguishable from completed items. Something like “identified gap” or “needs action” works well. The key is consistency across the team so that when you filter the checklist by status, all outstanding gaps appear in one view. As gaps are addressed, update the status to reflect progress, such as “in progress” or “resolved”, so the team can track movement toward completion.
How do I decide who should own each gap?
Assign each gap to the person who has the most relevant knowledge or authority to resolve it. For process gaps, this might be the information manager or BIM manager. For IT infrastructure gaps, it might be the technology lead. For training gaps, it might be the team lead or HR. The Kanban view makes it easy to assign and reassign tasks as the picture becomes clearer.
When should I start organising documents for the audit?
Now. Starting document organisation at the same time as documenting findings means that evidence is centralised from the beginning. As you address gaps and create new processes, the documentation goes straight into the Docs module rather than sitting in emails or local files that need to be gathered later. This approach is significantly more efficient than leaving document organisation until the final audit preparation stage.
Explore further
- From ISO 19650 gaps to compliance goals – The full course lesson on turning identified gaps into structured compliance actions.
- ISO 19650 gap analysis report – How to compile your documented findings into a formal report that guides your team through to audit readiness.
- How to get ISO 19650 compliant – A practical guide to achieving compliance with actionable steps and tools.
- ISO 19650 concepts and workflows – The full help centre collection covering how each component of ISO 19650 works together in practice.