This article covers the detailed behaviors and trigger logic for automated inspection scheduling in the Yardi integration. For a high-level overview, see the Yardi Integration Overview →.
How Inspection Scheduling Works
HappyCo checks your Yardi data once per day and automatically schedules inspections based on unit activity. Up to three inspections can be triggered per unit move-out cycle, depending on your template configuration:
| Trigger | What It Detects | When the Inspection Is Scheduled |
|---|---|---|
| Move-In | Resident's scheduled move-in date | At the move-in date |
| Notice For | Resident's scheduled move-out date | When a resident is placed on notice |
| Notice On | Resident's notice-to-vacate date | At the notice date |
Trigger Type Details
Move-In inspections are scheduled when a new resident's move-in date is set in Yardi. The inspection is created in HappyCo for the move-in date so your team can inspect the unit before or at turnover.
Notice For inspections are triggered when a resident is placed on notice and a scheduled move-out date exists. This allows you to schedule an inspection aligned with when the resident is expected to vacate.
Notice On inspections are triggered at the date the notice to vacate was submitted. This captures the start of the notice period and is useful for initial condition assessments.
Scheduling Cadence
HappyCo checks for new notices and move-in dates once per day. Inspections are created in HappyCo when the trigger condition is met. If a move-out date changes in Yardi, the corresponding inspection in HappyCo is updated to reflect the new date.
Floorplan Sections
When an inspection is automatically scheduled, HappyCo uses the unit's floorplan to pre-populate the inspection template with the correct sections. If the unit's floorplan is not mapped to a template section configuration in HappyCo, the inspection will still be created but may not include floorplan-specific sections.
Multiple Inspections Per Unit
If more than one trigger type is enabled for a property, a unit going through a full move-out cycle can generate up to three separate inspections — one per trigger. Each inspection is created independently and linked to the unit.