Property Inspection Workflow

How long does it take to get this workflow up and running?

Publishing the workflow takes minutes inside assess.one — there is no implementation project, no external software to install, and no developer required. Once published, your team can run live inspections immediately. The entire setup from first login to first completed inspection can happen the same day.

How do I customise the inspection sections for my properties?

You can edit steps, rename sections, add or remove inspection areas, and adjust the fields captured at each stage directly inside assess.one. If your properties include garages, communal areas, or kitchens, you add those steps in the workflow builder without writing any code. Changes take effect as soon as you republish.

What do I need to set up before running the first inspection?

You need the workflow published in assess.one and the relevant team members assigned to their roles — typically the property manager conducting the inspection. No external tools, integrations, or data migrations are required to start. Photo upload capability is built into the platform, so inspectors can attach evidence directly to each section.

How does the workflow decide which closing step to use?

After the property manager records the overall inspection outcome, the workflow evaluates that result and automatically routes to the correct close: urgent maintenance raised, standard maintenance raised, minor follow-up required, or satisfactory. This routing logic is configured inside assess.one and can be adjusted to match your own outcome categories and thresholds.

Who needs access to run this workflow?

At minimum, the property manager conducting the inspection needs access to assess.one to progress through the steps and submit findings. If your organisation has maintenance coordinators or supervisors who need to review outcomes or action maintenance tasks, they can be assigned roles with appropriate visibility. Access and role permissions are managed inside the platform.

How are urgent maintenance tasks created automatically?

When the inspection outcome is recorded as urgent, the workflow routes directly to the Create Urgent Maintenance Task step before closing the inspection. This ensures a maintenance record exists before the inspection is finalised — no manual handoff required. The task details are captured as part of the workflow run, creating a clear audit trail linking the inspection finding to the resulting action.

Can I set up notifications so the right people are alerted when an urgent issue is found?

Yes. Notifications for specific steps or outcomes — including urgent maintenance routing — are configured inside assess.one. You can alert maintenance coordinators, property owners, or supervisors via email or Slack when the workflow reaches a critical decision point. No third-party development work is needed to set this up.

How do I handle inspections across a large portfolio of properties?

Each inspection is a separate workflow run, so you can have multiple inspections running simultaneously across different properties without them interfering with each other. Each run produces its own complete inspection record with findings, photos, and outcome. You can filter and review runs by property, date, or outcome status inside assess.one.

Does the workflow produce a record I can use for compliance or dispute purposes?

Yes. Every workflow run creates a timestamped inspection record capturing the assessments, photo uploads, and recorded outcome for each section. This record is stored inside assess.one and provides a clear, auditable account of what was inspected, what was found, and what action was taken. This is particularly useful for tenancy disputes or landlord compliance requirements.

Can I adjust the approval or sign-off logic if a manager needs to review inspection outcomes?

Yes. If your process requires a senior property manager or compliance officer to approve the overall outcome before the inspection is closed, you can add an approval step directly in the workflow builder. Approval logic, including who approves and what triggers escalation, is configured inside assess.one without any external development.