LETO: evaluating a property maintenance workflow

Illustrative evaluation. This fictional property-agency scenario sets out proposed demonstration checks. It does not describe a customer deployment or measured savings.

A letting agency wants to reduce repeated follow-up on routine repairs while keeping spending and contractor decisions under its control. Reports arrive with incomplete details, approvals sit in email and another colleague often has to reconstruct the history when a case changes hands.

LETO is available now for customer demonstrations. The agency proposes one bounded maintenance workflow as its starting point, using fictional records and its own blank process checklist.

Define the permitted actions

Before the demonstration, the agency sets out its approved contractor list, the information required in a repair report and the decisions needing staff or landlord approval. It identifies which reminders may be sent automatically and which exceptions must return to a named person.

The team also identifies the records held in its existing property system. Any connection must have an agreed read and update scope. LETO’s integration register is used to discuss the route and permissions needed for that account, without assuming that a listed provider is already connected.

Follow a repair through the case

A fictional tenant submits a routine repair report with a photograph. The demonstration should show how LETO attaches the report to the relevant property record, identifies missing details and records its assessment. Staff inspect the information before the case progresses through the configured approval steps.

The agency then examines the instruction or notification prepared for a contractor from its own list. It checks what may be sent automatically, what requires approval and where the response is recorded. The published LETO maintenance workflow provides the capability context for these steps.

Test an exception and a handover

The next example falls outside the agreed spending or action limit. The agency asks to see the work held for the appropriate person and inspects the explanation on the case. The demonstration should make the approval requirement visible to the colleague responsible for the next step.

A second staff member then opens the case without the first person’s explanation. Can they identify the report, requested information, approval status, contractor response and outstanding action? Does the history distinguish a request from a confirmed outcome? These are acceptance questions for the demonstration, not results claimed in advance.

Decide what a pilot would need to establish

The agency records the steps demonstrated, any remaining manual work and the configuration or connection work still required. A pilot would then measure handling effort and unresolved cases against the agency’s own starting position. It would also inspect exceptions and incorrect actions, rather than count only completed tasks.

The commercial review includes the relevant plan, onboarding, usage allowances and any separate integration costs. The decision is whether the defined workflow saves enough administrative work while retaining the approvals and records the agency requires.

Read the LETO property management article, inspect the product website or contact AIC to arrange the demonstration. Bring a blank repair checklist, the systems involved and the approval boundaries your team needs to preserve.