Reference · built on requestOperator by FibricProperty & tenants

Shutdown Notice

Turns a planned shutdown work order into tenant notices timed to each lease's notice period, for your approval before anything sends.

Request accessPricing ↗

About

A riser is drained, an elevator is taken down, a switchgear is serviced. The work order says when. Each lease says how much notice its tenant is owed, and the answer differs from suite to suite. Shutdown Notice reads scheduled work orders from your CMMS, finds the leases in the affected spaces through your property system, and looks up the notice period each lease requires in the abstract you keep.

For every shutdown it proposes a notice per tenant with a send date that satisfies the longest lead time on the floor, and a scheduled send through your email or SMS provider. If the work order moves or is cancelled, it proposes a revised notice. Nothing goes out until you approve the text, the recipients, and the time.

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

  • Planned shutdown work orders: Facilio work orders with scheduledStart, estimatedEnd, and site; Corrigo WorkOrder with DtDue and WorkZone; MaintainX and UpKeep preventive maintenance schedules
  • The building, floor, or space each work order affects: Facilio site, building, floor, and space records; Corrigo Space and WorkZone
  • Leases in the affected spaces and their tenant contacts: Entrata getLeases and getCustomers, Buildium leases and tenants, AppFolio occupancies, Facilio tenant and tenantcontact
  • The notice period each lease requires, from your abstract in a SharePoint list or Google Sheet, with a default per property
  • Changes to the work: Corrigo On Hold, Cancel, and Assigned webhook events; Facilio records changed since a timestamp; MaintainX WORK_ORDER_STATUS_CHANGE
  • What happened to notices already sent: SendGrid Event Webhook delivered and bounce events, Amazon SES Delivery and Bounce events, Twilio message status

Proposed actions

  • Target capability: propose a notice per affected tenant, with a send date set from the lease's notice period and the shutdown start, for your approval
  • Target capability: propose a scheduled send through Twilio SendGrid with send_at and batch_id, or a same-day Amazon SES SendEmail tagged with the work order
  • Target capability: propose an SMS through Twilio for tenants who asked for text, and an xMatters scheduled message to on-site staff
  • Target capability: propose a revised or withdrawn notice when the work order's date changes or it is cancelled, with the original attached
  • Target capability: propose a note on the work order in Corrigo or Facilio recording which tenants were notified and when

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

What you can build

  • Notify a floor before the water goes off

    A Facilio work order on a riser carries a scheduledStart. Entrata lists the leases on that floor. The operator proposes one notice per tenant and a SendGrid batch with send_at set to the earliest lead time.

    With Facilio, Entrata, Twilio SendGrid

  • Re-notice when the work moves

    A Corrigo webhook reports the work order On Hold, then a new DtDue. The operator proposes a revised notice to the same Buildium tenants through Amazon SES, with the original notice attached.

    With Corrigo Enterprise, Buildium, Amazon Simple Email Service

  • Text the tenants who asked for it

    AppFolio tenants who chose SMS get a Twilio message on the morning of the shutdown. The operator watches message status and lists any that failed so a person can call.

    With Twilio, AppFolio Property Manager

  • Tell the site team as well

    For a MaintainX shutdown the operator proposes an xMatters scheduled message to the building staff group, timed to land before the first tenant notice.

    With xMatters, MaintainX

Requirements

  • A CMMS or work order connector with scheduled dates and locations: Facilio, Corrigo Enterprise, MaintainX, or UpKeep
  • A property management connector for leases, spaces, and tenant contacts: Entrata, Buildium, or AppFolio Property Manager
  • The notice period per lease, or a default per property, in a SharePoint list, a Google Sheet, or your lease abstract
  • A messaging connector with a sender you have set up: Twilio SendGrid, Amazon Simple Email Service, or Twilio for SMS
  • A mapping from work order locations to units or suites where the CMMS names spaces differently from the property system
Authentication
Shutdown Notice has no credentials of its own. Work orders, leases, contacts, and delivery events come through the CMMS, property, and messaging connectors you attach, and each notice is sent only through the messaging connector after you approve it.

Limits

  • The notice period comes from your abstract. Where a lease is silent, the property default applies, and the proposal says so.
  • A shutdown in a space mapped to no lease reaches no tenant. The proposal lists the unmapped spaces so a person can add recipients.
  • SendGrid schedules a send no more than 72 hours ahead. Notices due sooner are re-proposed inside that window, or sent same-day through Amazon SES.
  • It drafts and schedules notices. It does not move the work, widen the shutdown window, or answer tenant replies.

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 Shutdown Notice ↗

Questions and answers

What exactly do you approve?
The notice text, the recipient list, and the send time, per shutdown. The proposal shows the work order, the spaces it affects, each lease with its notice period, and the contacts found. Edit the text or remove a recipient, then approve, or dismiss.
What record is kept for each shutdown?
A receipt per shutdown: the work order and its dates, the leases and their notice periods, the notice as sent, the send time, delivery and bounce events, who approved it, and the note left on the work order. A revised notice links to the original.
Does it send anything without approval?
No. Nothing is sent until a person approves the notice and its send time. When a work order changes after approval, a revised notice is proposed; the batch already scheduled is cancelled only if you approve that too.
Ask about Shutdown Notice

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