Platform • inspections • outputs • remedials • portal

Explore the platform by the part you need.

Not every team needs every part of the platform on day one. Start with the capability area closest to your problem, then go deeper into the pages, screenshots and guides behind it.

7-day trial. No card. Cancel anytime.

Need the audience view first? See use cases →

Platform areas

Choose the area you
actually need.

Start with the capability closest to your problem. Not every team needs every part on day one.

Need the audience view instead?
How it hangs together

Even one area works better
when the record stays joined up.

Teams often start with one module. The platform still works best when the trail does not break between steps.

1
Block A · Q1 2026
42
Doors
6
Flags
36
Pass
FD-001 · Flat 1A entrance Pass
FD-002 · Stairwell S1 Remedial
FD-003 · Flat 2B entrance Pass
Step 1
Capture the door
record cleanly.
Stable door IDs, photos, findings and history are the anchor point for everything that follows. Without a clean record here, every downstream output gets rebuilt from scratch.
  • Door IDs and histories persist across repeat visits
  • Photos and findings attached to the right opening
  • QR tags keep site and office records in sync
2
Remedial Quote — Block A
Replace intumescent strip ×4 £320
Realign FD30 door leaf ×2 £480
Replace self-closing device ×3 £540
Site attendance + RAMS ×1 £280
Total (excl. VAT) £1,620
Step 2
Turn it into
useful outputs.
Quotes, RAMS, PDFs, portal-ready documents and invoices are stronger when they come from the live record, not rebuilt from notes, emails or a separate spreadsheet.
  • Quotes pull directly from inspection findings
  • RAMS packs generated without re-entering door data
  • PDFs and exports share one consistent source of truth
3
Highfield Housing — Q1 2026
42
Inspected
6
Remedials
3
Docs
Block A Inspection Report.pdf Ready
Remedial Quote — March 2026 Ready
Step 3
Keep delivery and
follow-up joined up.
Remedials, scheduling, portal sharing and billing work better when they remain part of the same evidence trail, not handed off into emails, spreadsheets or separate systems.
  • Remedials linked back to the door that flagged them
  • Client portal shares live status without email threads
  • Stripe billing connected to the same delivery record
Start with any step — the record follows
No rebuild between site, office and handover
Start with the question

Find the right part of
the platform for your problem.

The clearest route in is usually the question your team is already asking.

If the question is...
How do we run
cleaner inspections?
1
Start with inspections & door register.
Door IDs, findings, photos and histories captured and held in one place.
2
Then review QR tags, floorplans and repeat-visit history.
These extend the inspection record so each visit builds on the last.
3
Use the inspection checklist and door ID guides for rollout.
Resources library maps directly to this platform area.
If the question is...
How do we generate
cleaner outputs?
1
Start with quotes, RAMS & builderif the issue is commercial packs or delivery documents.
Outputs built from the live inspection record, not retyped from notes.
2
Start with documents & exportsif the issue is PDFs, invoices or client handover.
One consistent source generates reports, quotes, RAMS and exports.
3
Then link back to the use case closest to your team.
Contractors, FM and housing each have an audience-specific path.
If the question is...
How do we standardise
and scale?
1
Start with integrations, reporting & onboarding.
Connect finance and CRM tools, report across buildings, and roll out systematically.
2
Then check remedials, portal & billingif the workflow keeps extending after inspections.
Keeps delivery and follow-up joined up without extra systems.
3
Use resources to review migration, exports and access controls.
Practical guides for teams switching from existing processes.
Not sure which question fits? Browse by audience instead.
What cuts across every part

Four things that show up
regardless of where you start.

These are not features of one module. They run through the whole platform.

Door-level history
Evidence stays attached to stable door IDs so the record still makes sense over repeat visits and follow-up work, months or years later.
  • Findings and photos persist per door, per visit
  • Remedials linked to the opening that flagged them
  • Timeline visible across the full inspection history
Client-ready outputs
Generate PDFs, CSVs, RAMS, invoices and portal-visible documents from the same underlying source of truth, not rebuilt each time.
  • Reports, quotes and RAMS from one live record
  • Portal documents available without re-exporting
  • CSV exports for your own retention policies
Security & control
Roles, workspace separation and 2FA support wider rollout without pulling the workflow apart, built in rather than bolted on after the fact.
  • Separate customer workspaces
  • Role-based access controls at workspace level
  • Optional 2FA policy for workspace users
Supporting content
The resources library maps cleanly to each platform area so teams can go deeper into the detail that matters most, including guides, checklists and rollout notes.
  • Guides aligned to each module, not generic docs
  • Migration and onboarding notes for switching teams
  • Compliance context alongside the platform detail
Applies to
Inspections Quotes + RAMS Remedials Documents Client portal Reporting
See how security and compliance work in practice.
Start today

Run one real building.
See how it holds together.

Capture a set of doors, produce a real output, and check how the audit trail looks afterwards. No setup cost, no card required.

No card. Cancel anytime.

Inspections Quotes + RAMS Remedials Client portal PDF exports Stripe billing