Every property team has a process for inspections. Most don’t have a playbook. The difference matters: a process is what you do; a playbook is what survives staff turnover, portfolio growth and a disputed report two years after the fact.
This guide lays out the twelve decisions that separate a well-run inspection programme from an ad-hoc one. None of them are about software. All of them become harder to fix the longer you wait.
Who this playbook is for
This playbook is written for teams running inspections at scale — where consistency, audit trail and regulatory defence matter as much as the inspection itself.
What happens without a structured inspection process
The gap between a team with a playbook and one without shows up in the outputs long before it shows up in a regulatory conversation.
- Inconsistent reports across inspectors
- Missing or incomplete evidence
- Difficult to defend decisions
- Slow report turnaround
- Inconsistent processes across teams
- Consistent outputs across teams
- Complete audit trail
- Defensible inspection records
- Faster reporting
- Scalable workflows
This article focuses on what and why. For step-by-step setup inside the product, see the help centre — we’ve linked the relevant guides throughout.
Why a playbook beats a checklist
Checklists tell you what to tick. Playbooks tell you what a “good” answer looks like, what to do with a bad one, and how the output will be used six months from now.
A playbook defines decisions. A checklist ensures those decisions are applied consistently — across every inspection.
The symptoms of a missing playbook are familiar:
- Two inspectors produce wildly different reports for equivalent properties
- Photo evidence exists but nobody can find the right image when it matters
- Remediation is requested but closure isn’t proven
- Audit requests turn into a three-day scavenger hunt across inboxes and shared drives
Every one of these is a playbook problem dressed up as a software problem. Fix the playbook first; pick tooling that supports it second.
The twelve decisions
We group them into four clusters: scope, capture, closure and governance. You won’t answer all twelve on day one, but having a forcing function for each prevents drift.
Scope
Scope decisions define what you’re inspecting, how often, and who signs it off. They look boring on a slide and cost you six months when they’re wrong.
01Inspection Type
- Why it matters
- Defines what data is captured and how inspections are structured. Mis-typed inspections produce misaligned reports.
- Common mistake
- Using one generic template for every inspection type — “works for everything” really means “optimised for nothing”.
- Best practice
- Create distinct templates per inspection type:
- Move-in / pre-tenancy
- Mid-term and periodic
- Compliance (HHSRS, NSPIRE, fire risk)
- Condition reports
- Specialist inspections (PPM, dilapidations)
02Frequency
- Why it matters
- Over-inspecting drains capacity; under-inspecting creates regulatory and insurance exposure.
- Common mistake
- Picking one frequency based on “what the regulator requires” without checking insurer expectations or internal risk appetite.
- Best practice
- Write down three numbers per inspection type — regulatory floor, insurer expectation, internal target — and commit to the highest that’s operationally sustainable.
03Responsible Role
- Why it matters
- People move on. Accountability should sit with the role, not the individual, or your playbook breaks every time someone is promoted.
- Common mistake
- Naming a specific person as the sign-off authority, with no defined deputy or role definition.
- Best practice
- Define a responsible role (e.g. Regional Compliance Lead), a deputy role, and document the handover between them.
Capture
Capture decisions are about the unit of evidence: what counts, how it’s structured, and how much judgement the inspector is allowed to exercise in the field.
04Template Design
- Why it matters
- The template is the contract between field and office. A good one constrains variation; a bad one invents it.
- Common mistake
- Letting regional teams spawn their own templates from scratch, producing a dozen near-duplicates that don’t aggregate.
- Best practice
- One national template with regional variants, or regional templates that share a skeleton. Both work. Mixing approaches doesn’t.
05Scoring Methodology
- Why it matters
- Scoring changes how outputs are consumed downstream — by portfolio owners, auditors and remediation teams.
- Common mistake
- Choosing the most “precise” method (e.g. 1–10) regardless of whether stakeholders can act on that granularity.
- Best practice
- Pick based on how the output is used: binary (pass/fail), graded (1–5), or hazard-banded (HHSRS-style). Precision without action is noise.
06Evidence Density
- Why it matters
- Sets the floor for what counts as a “complete” inspection. Determines whether you can defend a finding eighteen months later.
- Common mistake
- Leaving evidence density to inspector judgement — which produces wildly different reports from the same template.
- Best practice
- Define minimums per inspection type: photos per area, required captions, readings per compliance item. Enforce in the template.
The minimum amount of captured evidence (photos, readings, comments) required to consider an inspection “complete”. Low density = faster reports, weaker audit trail. High density = slower reports, stronger audit trail. Pick deliberately per inspection type.
What this looks like in practice
Decisions are abstract until you see them running end-to-end. Here’s what a move-in inspection looks like when scope and capture decisions are set:
- Move-in template selected from the library
- Property inspected on-site against the template
- Photos captured per room, with required captions
- Notes and defects recorded against structured fields
- AI-assisted descriptions generated from captured evidence
- Report completed, reviewed and delivered same-day
Reduce report writing time without cutting corners on evidence
- Generate structured descriptions from captured photos
- Pre-fill inspection data from recurring property and tenant records
- Create summaries and action lists instantly from findings
What a structured report looks like
See how inspections translate into clear, consistent outputs — across residential, commercial and compliance use cases.
Closure
Most teams are good at the inspection itself and weak at closure. This is where disputes are won and lost.
Why closure matters. Incomplete or unclear reports create disputes, delays and rework. Clear outputs reduce queries and improve trust between field teams, tenants and stakeholders.
07Action Generation
- Why it matters
- An unlinked action is an action that never happens. The report has to generate the follow-up, not assume someone will read it.
- Common mistake
- Flagging issues in the report body with no mechanism to turn them into tracked, owned actions.
- Best practice
- Every flagged issue auto-generates an action with owner, due date and SLA. No orphaned findings.
08Remediation Evidence
- Why it matters
- If you can’t prove a fix, you haven’t fixed it — from an audit or dispute perspective.
- Common mistake
- Marking actions complete without proof: no photo, no date, no signoff.
- Best practice
- Require photo + date + role + signoff on every remediation before closure. No exceptions for “minor” items.
09Re-inspection Triggers
- Why it matters
- Not every fix needs a physical re-check, but some do. Getting this wrong wastes field time or leaves risk unresolved.
- Common mistake
- Defaulting every remediation to a physical re-inspection, or allowing remote signoff for everything.
- Best practice
- Define which issue types require a physical re-check (e.g. safety-critical) vs remote signoff (e.g. cosmetic), and document the rule.
Governance
Governance is the unfun cluster, which is why most teams skip it. Don’t.
Why governance matters. In regulated environments (HHSRS, NSPIRE, fire risk assessments), incomplete or inconsistent records create compliance risk — and legal exposure when things go wrong.
- Full audit trail of every change to every report
- Timestamped evidence that can’t be reordered or re-dated
- Defensible inspection records months or years after the fact
- Consistent standards across teams, regions and portfolios
10Chain of custody
- Why it matters
- If the system can’t tell you who touched a report and what they changed, you can’t defend it in a dispute.
- Common mistake
- Editable reports with no versioning or change log — “last saved wins”.
- Best practice
- Immutable submitted records with full edit history. Amendments tracked as new versions, not overwrites.
11Retention
- Why it matters
- Retention is a legal question, not an IT one. Get it wrong and you’re either non-compliant or paying to store evidence you shouldn’t still have.
- Common mistake
- Treating retention as a storage setting rather than a policy tied to jurisdiction and inspection type.
- Best practice
- Define retention periods per inspection type, aligned with regulatory and insurance requirements. Review annually.
12Audit Access
- Why it matters
- If external auditors can’t get a portfolio-level view on demand, your audit day becomes an audit week.
- Common mistake
- Building audit access as an afterthought — a spreadsheet export stitched together the night before.
- Best practice
- Provide read-only portfolio access with filters by date, type, region and status. Auditors self-serve.
“We used to think the report was the deliverable. It isn’t. The deliverable is the ability to answer any question about any inspection, eighteen months later, in under a minute.”
How Property Inspect supports this
Capture, structure and report inspections in one workflow — with the audit trail, governance and scoring built in.
How to roll this out without a rewrite
Teams that succeed with a playbook don’t do it in one sweep. They sequence it:
- Ship scope and capture decisions first. They affect field staff directly and produce visible quality gains within a month.
- Address closure next. This is where executive stakeholders notice reduced follow-up time.
Tackle governance last, once the first two are stable. Retrofit governance onto chaos and you’ll just have governed chaos. - The order matters. Reversing it — starting with governance — is how good intentions become a three-quarter project that ships nothing operational.
Scaling inspections across teams and portfolios
As portfolios grow, consistency becomes the critical constraint. A playbook that works for one region with one team starts to fracture without deliberate structure.
- Standardised templates across teams — with regional variants, not regional rewrites
- Consistent reporting outputs regardless of inspector or region
- Centralised data and oversight for portfolio-level questions
- Easier onboarding of new inspectors — the playbook is the training material
What a good output looks like
You’ll know your playbook is working when three things happen:
- Two inspectors produce reports that look like they came from the same team
- Any stakeholder can answer “what’s the status of property X” in one click
- Audit preparation time drops from days to hours
A good output, regardless of inspection type, shows:
- Consistent structure across reports — same layout, same section order, same level of detail
- Clear evidence linked to findings — every claim traceable to a photo, reading or note
- Actionable outcomes — every issue tied to an owner, due date and SLA
- Professional presentation — something you’d be comfortable sharing with a regulator, client or tribunal
None of that happens because of software. It happens because you made twelve decisions, wrote them down, and held the team to them. Software just stops you from having to do it by hand.
Key takeaways
- A structured inspection process improves consistency and reduces regulatory risk across your portfolio.
- Standardised templates enable faster reporting without sacrificing evidence quality.
- Complete, structured evidence is what makes inspection decisions defensible months or years later.
- Clear outputs — actions, evidence, signoff — reduce disputes and follow-up queries.
- Scalable workflows are what let growing portfolios keep the playbook intact across teams and regions.