Reference · built on requestOperator by FibricProperty & tenants

Move Coordination

Move-in and move-out days built from lease dates, elevator holds, and inspections, with tasks, access dates, and notices proposed.

Request accessPricing ↗

About

A move needs an elevator pad, an inspection, keys or credentials, and a resident who knows which hour is theirs. Move Coordination assembles that from records you already keep. It reads move-in and move-out dates from Entrata getLeases, Buildium leases and move outs, or AppFolio occupancies. It reads inspections from Entrata getInspections, elevator holds from the board where your staff record them in Asana, monday.com, or Jira Service Management, and credential start and end dates in Verkada or tenant records in ButterflyMX.

For each move it proposes the tasks with due dates, the credential activation or end date, the inspection work order, and the notice to the resident. You approve the set. It flags two moves that claim the same elevator window.

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

  • Leases filtered by move-in and move-out date ranges in Entrata getLeases, move outs and renewals in Buildium /v1/leases, and occupancies in AppFolio Property Manager
  • Inspections through Entrata getInspections in the maintenance service, with created and completed dates
  • Elevator holds and move slots as tasks with due_on in Asana, items on a monday.com board, or requests in a Jira Service Management queue
  • Access users with start and end dates in Verkada, and tenants, units, and access tools in ButterflyMX
  • Delivery events on move notices from SendGrid or Postmark, and inbound replies through the Postmark Inbound webhook
  • Open work orders on the unit, such as a turn or a repair, that must finish before the move-in

Proposed actions

  • Target capability: propose the move's tasks with due dates, as Asana tasks, monday.com items, or Jira Service Management requests: elevator pad, keys, walkthrough
  • Target capability: propose a credential end date on move-out for the departing resident in Verkada, or a tenant removal in ButterflyMX, timed to the lease
  • Target capability: propose a new tenant record and invitation in ButterflyMX, or an access user with a start date in Verkada, for the arriving resident
  • Target capability: propose a move-out inspection work order through Entrata sendWorkOrders, MaintainX POST /workorders, or Corrigo WoCreateCommand
  • Target capability: propose the notice to the resident through SendGrid or Postmark, naming the elevator window, the inspection time, and the key handover

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

What you can build

  • Schedule a move-out from the lease

    Entrata lists a move-out next month. The operator proposes Asana tasks for the elevator pad, walkthrough, and key return, an inspection work order, and a Verkada end date on the resident's credentials.

    With Entrata, Asana, Verkada

  • Set up an arriving resident's access

    A Buildium lease starts next week. The operator proposes a ButterflyMX tenant record with the invitation, a monday.com item for the move slot, and a Postmark notice with the elevator window.

    With Buildium, ButterflyMX, monday.com, Postmark

  • Catch two moves on one elevator

    Two Jira Service Management requests claim the same elevator hours. The operator proposes moving the later request to the next open window and a SendGrid notice to that resident.

    With Jira Service Management, Twilio SendGrid

  • Hold the move-in until the turn is done

    An open MaintainX work order on the unit ends after the lease start. The operator flags the conflict and proposes a task for the manager and a notice with the new time.

    With MaintainX, Asana

Requirements

  • A property connector with move-in and move-out dates: Entrata, Buildium, or AppFolio Property Manager
  • A work board where elevator holds and move tasks are kept: Asana, monday.com, or Jira Service Management
  • An access connector with per-user dates: Verkada, or ButterflyMX for tenants and access tools
  • A messaging connector for resident notices, Twilio SendGrid or Postmark, and your move rules: elevator hours, buffer between moves, and inspection lead time
Authentication
It reads leases, boards, and access records through the property, work, access, and messaging connectors you attach, each with its own scopes; it signs in to nothing itself.

Limits

  • Elevator holds are read from the board where you record them, not from the elevator. A hold nobody wrote down is not seen.
  • It activates and ends no credential on its own. Each access change is a proposal with a date, applied once after approval.
  • It treats the lease dates in your property system as final. A move that shifts is re-proposed when the lease changes.
  • It takes no deposit, computes no deduction, and signs no inspection. Those stay with your staff and the property system.

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 Move Coordination ↗

Questions and answers

What does approving a move actually cover?
The set for that move: each task and its due date, the credential start or end date, the inspection work order, and the notice text. The proposal shows the lease dates it used and the board entries it found. Approve the set, or approve items one by one.
What record is kept for a move?
A receipt: the lease id and dates, the task or request ids created, the access user or tenant change and its date, the work order id, the message id and delivery event, who approved each item, and how to undo each one.
Does it ever remove someone's access by itself?
Never. An end date on a credential or a tenant removal is written only after a person approves it, once, on the date proposed. If the lease date changes first, the proposal is withdrawn and rebuilt.
Ask about Move Coordination

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