Property inspection programme Gantt chart template: batches and access notices
An editable Gantt chart for a rolling programme of routine inspections and certificate renewals across a rental portfolio, by area batch, with access notice waits, follow-up repairs and milestones.
What the property inspection programme gantt chart template: batches and access notices process is
A routine inspection programme looks simple until it meets a real portfolio. Every visit needs notice to the tenant, the notice has to run before anyone enters, and the same inspectors and engineers move from one area to the next. A timeline shows how those pieces overlap, so you can start the notices for the next area while the current one is still being inspected.
This template has five groups: Programme set-up, North batch, Central batch, South batch and Follow-up. It has 23 tasks and three milestones, and a total length of 44 working days in the illustrative numbers. "Build the register of properties and certificate dates" (4 working days) is the only starting task. It leads to "Group properties into area batches" (2) and "Book inspectors and engineers" (3), and then to the first milestone, "Programme ready".
Each batch has the same four tasks: send the notices, wait out the notice period, inspect and test, and write the reports. The waits are plain tasks, so "Notice period, north" is 5 working days of nothing to do but wait. The overlap is what saves time. "Send access notices, central" starts 3 working days into "Notice period, north" with a start-to-start link, and "Send access notices, south" starts 3 working days into "Notice period, central" in the same way. But "Inspect and test, central" cannot begin until "Inspect and test, north" has finished, because the same team does both. That team is the real constraint, and the chart makes it visible.
The follow-up group starts before the programme ends. "Sort defects by urgency" (2) begins once "Write inspection reports, north" is done, and "Order repairs from the first two batches" (3) waits for it and for "Write inspection reports, central". "Complete repairs from all three batches" (8) also waits for the south reports, and "Renew expiring certificates" (5) follows the central reports. The milestone "All batches inspected" leads to "Update the register with new certificate dates" (2) and then "Programme closed". How much notice a tenant must be given, and how often each certificate must be renewed, differ by country and by tenancy, so the plan holds your own durations and none of those rules. All durations here are illustrative.
A timeline schedules the visits. It does not tell you which inspections or certificates the law requires for your properties, and it does not record what an inspector found. Keep those in your inspection reports and register. For related work, see /templates/rental-maintenance-request-process for how a defect becomes a repair, /templates/tenant-move-in-inspection-process for the inspection at the start of a tenancy, and /guides/property-portfolio-calendar-gantt-chart for laying a whole portfolio on one calendar. For waits and start-to-start links, see /guides/gantt-chart-dependencies.
What this flowchart covers
In this template
- Five groups, Programme set-up, North batch, Central batch, South batch and Follow-up, with 23 tasks and three milestones: "Programme ready", "All batches inspected" and "Programme closed".
- Overlapping notice waits: "Send access notices, central" and "Send access notices, south" each start 3 working days into the previous batch's notice period.
- One inspection team: "Inspect and test, central" waits for "Inspect and test, north", and "Inspect and test, south" waits for "Inspect and test, central".
- Follow-up that starts early: "Sort defects by urgency" begins after the north reports, and "Renew expiring certificates" begins after the central reports.
- A close-out that waits for everything: "Update the register with new certificate dates" needs both "Renew expiring certificates" and "All batches inspected".
When to use this template
- You inspect a rental portfolio on a rolling cycle and want to plan each cycle by area.
- One team of inspectors or engineers serves every property, and you need to see how the batches queue behind each other.
- You want to know how early the next batch's notices can go out without the notice period running out before the visit.
- You track certificate renewals alongside inspections and want both in one plan.
The plan, task by task
Every task in the chart with its length in working days and what it waits for. A dependency is a step number; SS is start-to-start, FF is finish-to-finish, and +n is a lag in working days.
| # | Task | Group | Working days | Depends on |
|---|---|---|---|---|
| 1 | Build the register of properties and certificate dates | Programme set-up | 4 | |
| 2 | Group properties into area batches | Programme set-up | 2 | 1 |
| 3 | Book inspectors and engineers | Programme set-up | 3 | 2 |
| 4 | Programme ready | Programme set-up | Milestone | 3 |
| 5 | Send access notices, north | North batch | 1 | 4 |
| 6 | Notice period, north | North batch | 5 | 5 |
| 7 | Inspect and test, north | North batch | 6 | 6 |
| 8 | Write inspection reports, north | North batch | 3 | 7 |
| 9 | Send access notices, central | Central batch | 1 | 6SS+3 |
| 10 | Notice period, central | Central batch | 5 | 9 |
| 11 | Inspect and test, central | Central batch | 6 | 7, 10 |
| 12 | Write inspection reports, central | Central batch | 3 | 11 |
| 13 | Send access notices, south | South batch | 1 | 10SS+3 |
| 14 | Notice period, south | South batch | 5 | 13 |
| 15 | Inspect and test, south | South batch | 6 | 11, 14 |
| 16 | Write inspection reports, south | South batch | 3 | 15 |
| 17 | Sort defects by urgency | Follow-up | 2 | 8 |
| 18 | Order repairs from the first two batches | Follow-up | 3 | 12, 17 |
| 19 | Complete repairs from all three batches | Follow-up | 8 | 16, 18 |
| 20 | Renew expiring certificates | Follow-up | 5 | 12 |
| 21 | All batches inspected | Follow-up | Milestone | 16 |
| 22 | Update the register with new certificate dates | Follow-up | 2 | 20, 21 |
| 23 | Programme closed | Follow-up | Milestone | 19, 22 |
How it works
Group your properties
Rename the three batches after your own areas or blocks, and add or remove batches. Each batch is four tasks, so copy the pattern of "Send access notices, north" through "Write inspection reports, north" for a new one.
Set the notice waits
Change "Notice period, north", "Notice period, central" and "Notice period, south" to the notice your tenancies need. This differs by country and by tenancy, so use your own figure. Adjust the 3-day start-to-start links to when you want the next batch's notices to go out.
Size the inspection work
Set "Inspect and test, north" and its two siblings from how many homes each batch holds and how many visits your team makes in a day.
Fix the dates that are real
Give "Build the register of properties and certificate dates" a fixed Start on the day you begin. If a certificate expires on a known date, give the matching inspection a fixed Start so a conflict flag shows when the batch cannot be ready in time. The chart schedules forward from the earliest fixed Start.
Resize the follow-up
Set the repair and renewal tasks from the defects you usually find and from your contractors' lead times, then check that "Programme closed" lands where you need it.
Add owners, share and export
Put the person responsible for each task in People, share the chart as a link with inspectors and contractors, and export a PDF or PNG for the portfolio file.
Frequently asked questions
Does the chart know how often inspections or certificates are due?
No. It holds the durations and dates you enter. How often an inspection or certificate is required differs by country and tenancy, so put your own schedule into the register and use the chart to plan the visits.
Can I run two batches at the same time?
Yes. Remove the link from "Inspect and test, north" to "Inspect and test, central" if you have a second team, and the two batches run side by side. Keep the link when one team does both.
What if a tenant cannot give access on the day?
Lengthen the inspection task for that batch or add a task for rebooked visits. The chart moves the report and follow-up dates after it. See /guides/gantt-chart-critical-path for how a longer task shifts the end date.
Can I use it for a single building?
Yes. Use one batch for the whole building, or batch by floor, and delete the batches you do not need. The follow-up group works the same way.
Can I paste my own list of properties?
There is no file upload. Paste your table of tasks and durations into the spreadsheet view, and the bars and dependencies follow. Dates in ambiguous formats are read in the order your interface language uses.