Reference · built on requestOperator by FibricProperty & tenants

Work Order Aging

Open work orders ranked by age, severity, and what the lease obliges, with a priority change, a tenant update, or an escalation proposed.

Request accessPricing ↗

About

An open work order list sorts by whatever the CMMS sorts by. Work Order Aging sorts it by what matters: how long it has waited, how severe it is, and whether the lease or local code makes it urgent. It reads open orders with created dates, priority, status, and assignee from MaintainX, Corrigo Enterprise, Limble CMMS, or Facilio, and the same from Buildium or AppFolio Property Manager where orders are kept there. It reads the lease and unit behind each order, and the parts and purchase orders the order waits on.

It proposes a new priority where the ranking disagrees with the CMMS, a tenant update where an order has gone quiet, a purchase request where a part is missing, and an escalation where age crosses your line. You approve each.

This is a reference listing. It documents what Fibric would read from Work Order Aging and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Open work orders with created date, priority, status, and assignee from MaintainX /workorders, Corrigo WorkOrder queries, Limble /v2/tasks, or Facilio /workorder
  • Work orders in Buildium /v1/workorders and in AppFolio Property Manager with Status, Priority, ScheduledStart, and CompletedOn
  • WORK_ORDER_OVERDUE events from MaintainX and On Hold actions from Corrigo, with the hold reason
  • The lease and unit behind each order in Buildium, Entrata, or AppFolio Property Manager, and the categories your rules mark as lease or habitability obligations
  • Parts on order: MaintainX parts and purchase orders with fulfilment state, Limble parts quantities and purchase orders, or Facilio storeroom balances
  • The last comment or resident update on the order, so silence is measured from the last word, not the first

Proposed actions

  • Target capability: propose a priority change through Corrigo WoPriority, a Limble task due-time update, or a Facilio PATCH on the work order
  • Target capability: propose a tenant update as a Buildium note on the resident request, an Entrata lease activity, or a message through your messaging connector
  • Target capability: propose an escalation: a comment on the MaintainX or Limble order naming the age and the obligation, assigned to the manager you choose
  • Target capability: propose a purchase request through Facilio POST /purchaserequest, a MaintainX purchase order, or a Limble purchase order for the missing part
  • Target capability: propose a ranked backlog for the week, written as a note or a task where your team already looks

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Put heat and water at the top

    MaintainX holds open orders across a portfolio. The operator matches each to its Buildium lease, ranks habitability categories first by age, and proposes priority changes where the CMMS order disagrees.

    With MaintainX, Buildium

  • Tell the resident why it is waiting

    A Corrigo order sits On Hold for a part. The operator reads the purchase order state in Fishbowl Advanced and proposes an AppFolio note to the resident with the expected date.

    With Corrigo Enterprise, Fishbowl Advanced, AppFolio Property Manager

  • Order the part the backlog is waiting on

    Several Limble tasks wait on one part with no stock. The operator proposes a Limble purchase order and an escalation comment naming the tasks it will release.

    With Limble CMMS

  • Escalate what crossed the age line

    A Facilio work order on an Entrata unit passes your age line. The operator proposes a priority PATCH, a lease activity for the resident, and a comment to the manager.

    With Facilio, Entrata

Requirements

  • A CMMS or work order platform: MaintainX, Corrigo Enterprise, Limble CMMS, Facilio, or the work orders in Buildium or AppFolio Property Manager
  • A property connector to match orders to leases and units: Buildium, Entrata, or AppFolio Property Manager
  • A source of parts and purchase order state: the CMMS's own parts module, Facilio storerooms, or Fishbowl Advanced
  • Your ranking rules: which categories the lease or local code makes urgent, the age lines for escalation, and who receives it
Authentication
It reads orders, leases, and stock through the maintenance, property, and inventory connectors you attach, with the scopes you grant each; it has no login of its own.

Limits

  • Age is measured from the created timestamp in the CMMS. Work done but not closed looks old; the proposal shows the last action.
  • Which categories a lease or code makes urgent is your rule. It reads the category, not the statute.
  • It dispatches nobody and closes nothing. A priority change moves a field; the technician and the CMMS keep the work.
  • Parts state comes from the systems you connect. A part in a truck is not seen.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Work Order Aging ↗

Questions and answers

What do I approve in a ranked backlog?
Each change on its own: the new priority, the tenant update text, the escalation, or the purchase request. The proposal shows the order's age, its category, the lease it maps to, the parts it waits on, and the last comment. Approve, edit, or leave the order where it is.
What is recorded when a priority moves?
A receipt: the order id, its previous and new priority, the rule that ranked it, the lease and unit, the note or message sent to the resident, the purchase request id if one was raised, who approved, and how to restore the old priority.
Can it reassign or close a work order?
It does neither. It changes priority fields, writes updates, and raises purchase requests, each after a person approves. Assignment and completion stay with your maintenance team and the CMMS.
Ask about Work Order Aging

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy