Work orders for communities

Every intervention, controlled from start to finish.

Onzane brings the origin, planning, supplier, deadlines, communications, evidence, validation and financial closure of the work together in one order.

An operational record

Create. Assign. Execute. Validate. Close.

Each stage preserves owners, dates, decisions and evidence so work can be followed without scattered conversations.

  1. 01 Create

    Define the scope from an incident, asset, plan or specific need.

  2. 02 Assign

    Choose staff or supplier, priority, dates and service commitments.

  3. 03 Execute

    Record progress, blockers, communications, time and evidence.

  4. 04 Validate

    Review the result and approve or return it with a traceable reason.

  5. 05 Close

    Reconcile the award, final cost and invoices before locking the record.

Six ways to start

Work begins where the need arises.

An order can be created directly or preserve the context of its source, linking it to the issue, space, asset, offer or plan.

01 Manual creation

For a one-off intervention defined by the community.

02 From an incident

Turn a validated report into operational work.

03 From a location

Place the work in an entrance, room or common area.

04 From an asset

Preserve equipment, history, warranty and documents.

05 From an awarded offer

Carry over the approved scope, supplier and amount.

06 From a plan

Automatically generate each recurring execution.

01A shared queue makes all open work visible and actionable.

Lifecycle

Statuses that explain what is happening.

From draft to closure, every transition reflects a real action and records who performed it.

  1. 01
    Before execution

    Draft, awaiting quote, awarded and scheduled.

  2. 02
    During the work

    In progress or blocked, with reason, owner and next action.

  3. 03
    After execution

    Completed, validated, cancelled or reopened with a reason.

02The order preserves context, relationships and status without reconstructing the story.

Shared execution

The supplier works in the same flow.

The supplier panel replaces disjointed exchanges: the company receives the scope, coordinates dates and documents what happens.

01Accept or reject

Confirm the assignment or explain why it cannot be accepted.

02Propose dates

Agree on the visit without losing sight of the target commitment.

03Block and resume

Record waits for parts, access or community decisions.

04Add evidence

Attach photos, documents, measurements and comments.

05Request completion

Submit the result so the community can validate it.

03Community and supplier share a verifiable timeline.

Service commitments

Deadlines stop being an invisible promise.

Onzane can monitor different times by priority, contract or work type and highlight exceptions before they become breaches.

  • Order acceptance time
  • Time to propose or confirm planning
  • Maximum resolution time
  • Warnings, escalations and queues by risk
04Indicators surface the exception without hiding work that is progressing properly.

Result control

Completing does not mean automatic approval.

The community can require evidence and a checklist before accepting the work. If something is missing, it returns the order with a specific reason.

01Required evidence

Photos, documents, readings or signatures depending on the work.

02Validation checklist

Explicit criteria to review scope and result.

03Reasoned rejection

The order returns to the supplier with the reason and audit trail.

05Validation turns evidence into a recorded decision.

Financial closure

The final cost is also part of the work.

The order connects the awarded amount, approved variations and received invoices so operational and financial closure tell the same story.

  1. 01
    Compare

    Contrast the awarded offer, final amount and invoiced documents.

  2. 02
    Explain differences

    Document extra materials or work before accepting the cost.

  3. 03
    Lock or reopen

    Close the record and require a reason for later changes.

06Offer, execution and invoicing are reconciled in the same record.

Frequently asked questions

Work orders in Onzane.

How each intervention is created, coordinated, validated and closed.

01What is the difference between an incident and a work order?

An incident records a problem or report. A work order defines the operational intervention needed to resolve it, with an owner, planning, statuses, evidence and closure. One incident can create one or more orders.

02Where can a work order come from?

It can be created manually or from an incident, location, asset, awarded offer or maintenance plan that generates recurring executions.

03Can an external supplier work on the order?

Yes. The supplier can accept, propose dates, start, block, resume and complete the work, and provide updates and evidence from its panel.

04Can service-level agreements or SLAs be monitored?

Yes. Onzane can measure acceptance, planning and resolution times by contract, priority or work type, with warnings and escalations.

05What happens if the result is not correct?

An authorised person can reject validation and state the reason. The order returns to the relevant operational status and keeps the decision in its history.

06Can photos or documents be required?

Yes. The order can define mandatory evidence and a checklist that must be completed before requesting validation.

07How are invoices linked to the work?

Financial closure compares the awarded amount, final cost and linked invoices. Differences must be explained before closing the record.

08Is the history preserved if the manager or supplier changes?

Yes. Statuses, communications, owners, evidence, validations and costs remain in the community context for authorised users.

Traceable operations

Turn every intervention into a controlled process.

We help you configure work types, statuses, owners, SLAs and validation criteria that fit your community.

Review my operations See community maintenance