01
Book an inspection
- On the property, open Inspections and choose Book an inspection.
- Pick the kind: routine check, move-in, move-out, maintenance follow-up, or compliance/insurer, then the date, notice days and, if you use one, an inspector's name.
- Save it. The tenant is given notice automatically before the visit; if the visit is too soon to wait for that, choose Send notice to give it right away.
02
Close it off with what you found
- After the visit, open the inspection and answer What did you find?.
- Record the outcome, completed or no access, and write up the findings.
- Leave Raise tickets on and Tezeka turns each fault you found into a maintenance ticket automatically, sent into the same triage and vendor loop as an issue logged directly.
NoteMaintenance tickets need an active plan with maintenance logging. Every plan has it, but if tickets ever cannot be raised, Tezeka still saves the inspection and tells you so, rather than losing the findings.
03
Preventive maintenance schedules
- Choose Add schedule, name the asset, pick how often it needs doing, and set the next due date.
- When it is done, choose Mark done; the next due date rolls forward on its own cadence.
- Pause a schedule for an asset that is out of service, and Resume it when it is back.
For recurring servicing, a borehole, a generator, a water tank, Preventive maintenance on the property keeps a due date that alerts you in Guardian and on WhatsApp when it lapses, instead of relying on memory between tenant reports.
If something goes wrong
I cancelled an inspection the tenant may already know about.
Tezeka warns you before cancelling one that notice may already have gone out; tell the tenant directly if it has.
A schedule shows as due but the work was already done.
Choose Mark done on that schedule. Recording it elsewhere, such as a maintenance ticket, does not move this due date on its own.
Still stuck? Contact support.