Reference · built on requestOperator by FibricProperty & tenants

Unit Turn

Sequences make-ready work between a move-out and the next lease from punch lists, vendor load, and parts on hand, and proposes a ready date.

Request accessPricing ↗

About

Unit Turn is an operator job for the days a unit sits empty. It reads move-out and move-in dates from Entrata or Buildium, the punch list from an Entrata inspection or a Facilio work order's tasks, the make-ready work orders and their status in Facilio, Limble, MaintainX, or UpKeep, each vendor's open load, and the parts on hand in the storeroom or parts module of that system. It reads the trade order and durations you set.

For each turn it proposes a plan: one work order per trade in sequence, dated from the move-out, and the ready date the plan implies. When a task slips it proposes a new date. When a part for the turn is short it proposes a purchase request. The leasing manager approves each, and the record shows why the date moved.

This is a reference listing. It documents what Fibric would read from Unit Turn 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

  • Move-out and move-in dates: Entrata getLeases and getExpiringLeases by move-out date, and getUnitsAvailabilityAndPricing; Buildium move outs and leases
  • Punch lists: an Entrata inspection through getInspections, or a Facilio work order with its tasks and comments under /workorder/{id}
  • Make-ready work orders and status: Facilio /workorder by status and assignedTo; Limble tasks by scheduled window; MaintainX and UpKeep work orders
  • Vendor load: MaintainX vendors and their open work orders; UpKeep worker and team assignments; Limble tasks per assignee
  • Parts on hand: Facilio storeroom and bin quantities; Limble parts with quantities; MaintainX parts and purchase orders with fulfilment state
  • The trade sequence, durations, and which trades may overlap, set in the operator's configuration

Proposed actions

  • Target capability: propose the turn plan per unit: one dated work order per trade, through Facilio POST /workorder, Limble POST /v2/tasks, MaintainX, or UpKeep
  • Target capability: propose a ready date per unit from the plan and vendor load, and a new date when a task slips
  • Target capability: propose a purchase request where a part for the turn is short: Facilio POST /purchaserequest, or a Limble or MaintainX purchase order
  • Target capability: propose recording the ready date once the last task closes: an Entrata work order update or a Buildium note on the property

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

What you can build

  • Sequence a turn from an Entrata move-out

    A lease with a move-out date inside the horizon is read from Entrata. The operator proposes Facilio work orders per trade in your order, dated from move-out, and the ready date they imply.

    With Entrata, Facilio

  • Order paint before the painter arrives

    Limble parts on hand are checked against what the paint task needs. Short stock becomes a proposed Limble purchase order, dated to land before the task, and the Buildium move-out date sets the deadline.

    With Limble CMMS, Buildium

  • Move the ready date when a vendor slips

    A MaintainX WORK_ORDER_OVERDUE event on the flooring task pushes the tasks behind it. The operator proposes a new ready date and a Buildium note on the property explaining the change.

    With MaintainX, Buildium

  • Run turns in UpKeep

    Each trade becomes an UpKeep work order with a worker or team. The operator watches STATUS_UPDATED events, proposes the next trade's start as each closes, and reports the ready date against the Entrata move-in.

    With UpKeep, Entrata

Requirements

  • A property connector with move-out dates: Entrata or Buildium
  • A maintenance connector with work orders, assignees, and parts: Facilio, Limble, MaintainX, or UpKeep
  • A trade sequence with durations per unit type, entered in the configuration
  • Optional: a second maintenance connector where vendors work in their own system
Authentication
Nothing of its own. Leases, work orders, and stock are read, and plans and requests proposed, with the credentials each bound connector already holds.

Limits

  • Durations are estimates you enter. The operator sequences from them and from task completions, not from a vendor's own calendar
  • Parts come from the maintenance system's storeroom or parts module. No standalone inventory connector is bound in this listing
  • A ready date is a proposal. The available date in your property system changes only when a person approves it
  • It reads checklist items and comments where the system holds them. It does not judge finish quality

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 Unit Turn ↗

Questions and answers

What does the leasing manager approve?
The plan: the trades in order with dates and assignees, and the ready date. Later, any change to that date, and any purchase request. Approve, reorder, or decline. Work orders are created only after approval.
What record is kept for each turn?
The move-out and punch list read, the sequence and durations applied, each work order as created with its status history, every ready date proposed and why it moved, the purchase requests, and each approval with name and time.
Does it change the lease or the listing?
No. It proposes a ready date and, once the last task closes, a note or work order update in your property system. Lease dates, pricing, and marketing stay with the people who own them.
Ask about Unit Turn

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