Rental property condition report: move-in and move-out

A photograph of a scuffed wall is not very useful when nobody can tell which room it shows, when it was taken, or whether there is a matching move-in view. A useful rental property condition report gives each observation that context.

The simplest working method is: same room, same order, two dates. Identify the property and handover, record keys and meters, follow one room-by-room route, write neutral notes, record anything you could not see, and repeat the sequence at move-out. The result is a clearer record for human review—not a verdict about cause, safety, charges, or liability.

Start with the job of the report

In this guide, a condition report records what participants submitted about a rental property at move-in and move-out. It is different from a building survey, a maintenance diagnosis, or a safety inspection.

Two official examples show how much the details can depend on place. The Queensland Residential Tenancies Authority says its entry condition report records the property's condition at the start of a tenancy. Its guidance tells participants to go room by room, note what they see, add photographs, and record agreement or disagreement in the report. Those are Queensland instructions, not a universal form or timetable.

In New South Wales, the NSW Government condition-report guidance describes a report completed at the beginning and end of a tenancy, room by room, with details and photographs that may be used as evidence if the parties disagree. That is NSW guidance, not a universal rule for every rental. Local forms, duties, access rules, and timings still need local review.

A condition record helps people review submitted observations. It does not by itself establish when a change happened, why it happened, who caused it, or what outcome should follow.

The move-in and move-out checklist

1. Identify the property, people, stage, and date

Begin with enough context to keep the record unambiguous: the property, the move-in or move-out stage, the observation date, and who recorded or reviewed it. Use only the personal information the process actually needs.

If the property has similar rooms, give each one a stable name such as “front bedroom” or “upstairs rear bedroom.” Reuse that name at move-out. “Bedroom 2” on one date and “small room” on the other creates avoidable uncertainty.

2. Record keys and meters before the room walk

List the keys or access items handed over. For every relevant meter, record the displayed value and a readable photograph that also gives enough context to identify the meter. If a meter is absent, inaccessible, or unreadable, record that gap instead of inventing a value.

AuditIt's current Tenancy move-in & move-out starter includes property address, keys issued, electricity, gas and water readings, and meter photographs. These are starter fields, not a statement that every property has every meter or that every jurisdiction requires the same record.

3. Follow the same route through every room

Choose a route that another person can repeat: entrance and hallway, living areas, kitchen, bathrooms, bedrooms, then exterior or garden where relevant. Take an identifying wide view before adding detail views of a mark, fitting, surface, or item that needs context.

At move-out, follow the route again. A perfectly matched camera angle is not always possible, but the room name, direction, and subject should make the intended comparison obvious. AuditIt's starter provides photo fields for those room groups so the two stages can keep the same structure.

4. Write what is observable

A useful note names the location and visible condition without guessing at cause. For example: “Front bedroom, wall beside window: narrow grey scuff below sill” is more reviewable than “tenant damage.” The first describes an observation; the second assigns responsibility.

Keep reported statements separate from observations. If someone says a mark was present before move-in, label it as their comment unless the earlier record independently shows it. The same applies to explanations about cleaning, missing items, or repairs.

5. Treat cleanliness and fixture entries as recorded selections

AuditIt's tenancy starter provides a cleanliness selection, a fixture-status group covering lights, sockets, taps, heating, appliances and smoke alarms, and a condition-notes field. Those selections capture what the recorder submitted. They are not a professional inspection, a safety certificate, or a compliance decision.

If a fixture could not be viewed or operated within the agreed process, say so. “Not observed” is different from “not working,” just as “selected as working” is different from a qualified safety assessment.

6. Record gaps, comments, and disagreements

Do not hide a missing view behind a general tick. Name the room or item, what was unavailable, and what follow-up—if any—was requested. If participants disagree with a note, keep the original observation and their comment separately identifiable.

This makes the report more honest. A blank, blocked view, or disputed description is still useful context when it is visible; it becomes misleading when silently converted into a positive finding.

7. Repeat the sequence and review differences together

At move-out, return to the same property identifiers, key list, meters, room names, view order, and note style. Review both dates together. A new-looking difference is a prompt for a person to examine the records and surrounding context, not automatic proof of when or why it occurred.

Where a move-in view is missing, state that the comparison is unavailable. Do not turn absence of an earlier photograph into evidence that an item was absent or undamaged.

What belongs in a compact report

For most rental-property workflows, a reviewable condition report needs five groups of information:

• Identity: property, room names, stage, dates, and recorder or reviewer context.
• Handover items: keys or access items and any clearly identified gaps.
• Meter record: relevant readings, readable displays, and meter identity context.
• Room condition: an identifying view, useful detail views, and neutral notes for each area.
• Review context: missing access, participant comments, disagreements, and any later follow-up kept separate from the original observation.

The list is a record-design prompt, not a substitute for a jurisdiction's required form or a qualified inspection. If a local process requires signatures, prescribed wording, safety checks, or specific delivery deadlines, use the applicable current source and an authorized reviewer.

Keep the workflow shape honest

A move-in/move-out record is a paired job: the same property is observed at two meaningful stages. AuditIt's recommended Tenancy move-in & move-out starter therefore uses a before_after workflow.

A mid-tenancy visit or a new-build snagging record is a different job. AuditIt keeps its Periodic property inspection and New-build handover & snagging starters as record_only workflows. Do not squeeze one visit into a two-stage comparison or present a snag list as a tenancy condition report.

If the starter needs to reflect a different room layout or handover process, read how to build an audit workflow template before changing the structure.

Where AuditIt fits

AuditIt can keep the two tenancy stages, room photographs, meter evidence, keys, selections, and notes in one structured condition record for later human review. The value comes from a repeatable capture sequence and visible context, not from turning software into the decision-maker.

AuditIt creates tamper-evident, human-review-ready records. It is not legal certification and does not determine liability.

To set up a structured move-in and move-out record, create an AuditIt account.

• rental property
• condition report
• move-in checklist
• move-out checklist
• property handover