Maintenance Issue
What happened, where, why it matters and what needs to be resolved.
MAINTENANCE & PURCHASE ORDERS
From issue reported to work completed.
A reported problem and an authorised commercial instruction are different records. Estivio’s connected model keeps both visible as work moves through contractor instruction, progress and completion.
REACTIVE WORK
A clear history from first report to final review.
One Maintenance Issue may require a contractor instruction and one or more Reactive Purchase Orders. Keeping those records distinct makes the original requirement and each authorisation easier to understand.
- 01
Maintenance Issue
Describe the problem, location, priority and supporting information.
- 02
Contractor instruction
Set out the scope, access and who will carry out the work.
- 03
Reactive Purchase Order
Record the authorised commercial instruction, issuing entity, values and approvals.
- 04
Works in progress
Follow updates and revisions against the instruction.
- 05
Completion
Record the outcome and any further action required.
- 06
Invoice / expenditure
Link later cost review to the work and Property that generated it.
This describes Estivio’s operational model. Invoice ingestion and accounting automation are not presented as live capabilities.
TWO DIFFERENT RECORDS
The problem and the authorisation each have a purpose.
Purchase Order
What has been approved, who is instructed, under which terms and for what value.
PLANNED WORK
Scheduled work has its own route.
Planned Purchase Orders support scheduled or programmed activity separately from reactive issues. Both routes can retain Site, contractor, approval, progress and expenditure context without treating every planned job as a response to a reported problem.
See the platform areasEARLY ACCESS
Help shape a more controlled works process.
Tell us where reported issues, approvals, contractor instructions and costs become disconnected today.