Move-In / Move-Out & Recurring Inspections

REDA can create inspections for you — when a tenant moves in, when they move out, and on a repeating schedule. This article shows you how to wire up all three: how to configure a property so a move-in or move-out inspection appears on its own from the lease's tickets, how to set up a recurring inspection series, and — the one thing that trips everyone up — that recurring inspections don't generate at all until an administrator schedules the background job that produces them. No prior REDA experience is assumed.

Three flavors of automatic inspection

Before the how-to, here's the map:

Configuring move-in / move-out auto-inspections

Move-in and move-out inspections are driven by settings on the property. There are two pairs of fields, one for each event — a template (which checklist to use) and a schedule (how many days from the move date to schedule the inspection):

What REDA creates, and when

The trigger is ticket creation, not ticket completion. The instant a configured property's Move In (or Move Out) ticket is created, REDA builds the inspection:

Because the checklist is pre-built, inspectors should open these inspections and start working — they should not apply a template to them (doing so would rebuild the checklist; see Running Inspections). And if a lifecycle changes course: cancelling the Move In or Move Out ticket automatically sets its non-cancelled inspections to Cancelled.

Setting up a recurring inspection

A recurring inspection is a source inspection that clones itself on a timetable — a quarterly HVAC check, say. Open or create an inspection, then fill in its recurring section:

All three details are required together. Leave one out and REDA responds:

And the start date can't be in the past:

Once you save, REDA works out the next due date from your start date, frequency, and how many copies have already been made.

What each generated copy looks like

On a due day (when the job is running — see the warning below), REDA clones the source inspection into a fresh one:

Each copy also nudges the source's count of generated instances forward, which is how REDA works out the next due date.

The scheduler requirement

This is the part to get right before you set up any series:

Once scheduled, the job runs each day and produces copies for the recurring inspections that are due that day. For the full list of background jobs and a go-live checklist, see Scheduling Background Jobs.

Worked example: a quarterly HVAC series

Meridian Properties wants an HVAC inspection every quarter at Meridian Court. First the setup, then the copies (assuming the job is scheduled):

For move-in and move-out: configure Meridian Court #101 with a "Standard Unit Move-In" template and a "Standard Unit Move-Out" template, each with its schedule offset. When the unit's Move Out ticket is created with a move-out date of 31 Aug 2026 and a two-day offset, REDA creates "Move Out Inspection Meridian Court #101," scheduled for 2 Sep 2026.

Reference: configuration and frequencies

The property's four inspection levers:

Recurring frequencies:

Where to go next

1. Scheduling Background Jobs — required setup: schedule the recurring-inspection job before you rely on a series.
2. Running Inspections — work the inspections REDA creates for you.
3. Building Your Inspection Catalog — the templates the automation applies.
4. Understanding Tickets — the Move In and Move Out tickets that trigger inspections.

Frequently asked questions