Reference · built on requestOperator by FibricProperty & tenants

Inspection Scheduling

Sets inspection dates that clear tenant notice rules and technician load, and proposes the entry notice for each unit.

Request accessPricing ↗

About

Inspection Scheduling is an operator job for units that must be entered on notice. It reads the inspections and recurring schedules you hold in Entrata, Buildium, UpKeep, or Limble, the open work each technician already carries, the notice rule you set for each jurisdiction and lease, and the public holidays from Nager.Date that a notice period or a visit date must skip.

For every inspection coming due it proposes a date that clears the notice period and fits a technician's open time, and the entry notice to go with it. The property manager approves the date, moves it, or removes a unit. On approval the visit is written to your maintenance system as a task or work order and the notice is sent once through the messaging connector you bind. A bounced notice comes back as a new proposal.

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

  • Inspections on file in Entrata through getInspections in the maintenance service, filtered by created, completed, or last-updated date
  • Recurring schedules: UpKeep preventive maintenance templates and schedules; Limble tasks of type PM with a scheduled window and location
  • Each technician's open load: UpKeep work orders by worker and team; Limble tasks by assignment and due time
  • Units and the residents to notify: Buildium leases and tenants; Entrata getPropertyUnits and getCustomers
  • Public holidays by country and year from Nager.Date, with regional holidays marked by county
  • Delivery of notices already sent: SendGrid Event Webhook events delivered, deferred, dropped, and bounce, tied back by custom_args
  • Notice rules per jurisdiction and lease: days of notice, permitted hours, and delivery method, in the operator's configuration

Proposed actions

  • Target capability: propose a visit date per unit inside the notice rule and a technician's open time, as a Limble task or UpKeep work order
  • Target capability: propose the entry notice for each unit with the date, the window, and the reason, sent through SendGrid mail/send after approval
  • Target capability: propose a new date and a fresh notice when a technician's load changes or a notice bounces
  • Target capability: propose the day's route per technician: units grouped by building and floor, each as one task or work order in the maintenance system

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

What you can build

  • Schedule annual unit inspections from Entrata

    Inspections due inside the horizon are read from Entrata. For each, the operator proposes a date that clears the notice period and a Limble task for the technician with the lightest load that week.

    With Entrata, Limble CMMS, Holidays & FX Reference

  • Send entry notices for a preventive maintenance round

    An UpKeep preventive maintenance schedule fires for a building. The operator groups units by floor, proposes one work order per unit, and one SendGrid email per resident dated to your notice rule.

    With UpKeep, Twilio SendGrid

  • Reschedule after a bounce

    A notice that bounces in the SendGrid Event Webhook returns as a proposal: the unit, the Buildium tenant record with an alternate contact, and a new date that still clears the notice period.

    With Twilio SendGrid, Buildium

  • Keep visits off holidays

    Nager.Date holidays for the property's country and region are excluded from both the notice count and the visit date. A date that lands on one is moved and re-proposed.

    With Holidays & FX Reference, UpKeep

Requirements

  • A source of inspections due: Entrata inspections, an UpKeep or Limble preventive maintenance schedule, or Buildium tasks
  • A maintenance connector whose tasks carry an assignee and a due time, so technician load can be read: UpKeep or Limble
  • A notice rule per property, entered in the configuration, and the resident contacts from your property system
  • Optional: Twilio SendGrid for the notice itself, and Nager.Date for the holiday calendar
Authentication
Uses the credentials of the connectors you bind, nothing else. Inspections and loads are read, and dates and notices proposed, under the access each connector was given.

Limits

  • Notice periods and hours are rules you enter. The operator does not read tenant law; you set the rule per state, city, or lease
  • Technician availability is inferred from open tasks in the maintenance system, not from a personal calendar
  • Entrata reports dates in Mountain Time unless a method states otherwise; set each property's time zone in the configuration
  • It proposes and sends a notice once after approval. It does not confirm receipt beyond the delivery events the mail connector reports

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 Inspection Scheduling ↗

Questions and answers

What does the property manager see before approving?
A visit date and its notice, per unit, or a whole route for a day. The proposal shows the notice period counted, the holidays skipped, the technician and their load, and the notice text. Approve, move a date, or drop a unit.
What is kept after a visit is scheduled?
The inspection or schedule that triggered it, the rule applied, the dates considered and why one was chosen, the approval with name and time, the task as the maintenance system created it, and the notice with its delivery events.
Does it enter a unit or send a notice without a person?
No. Entry is a technician with a written notice behind them. The notice is sent once, after approval, through the messaging connector you bind. The operator never sends on a schedule of its own.
Ask about Inspection Scheduling

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