Match each property request to the right file

Rental application requirements can differ between properties and submission channels. A request map keeps the current instructions separate from assumptions carried over from an earlier application. It also exposes gaps while there is still time to clarify them.

Market: AU
Jurisdiction: Australia
Updated: 2026-08-27

Short answer

List every item requested for the property, record where the request appeared and mark it required, optional, unclear or not applicable. Match each requested item to one intended file. Resolve unclear items before adding extra personal material.

Continue in RentFiles

Turn this guide into a clear application pack

Create a private, structured rental application file when you are ready.

Start your rental application Use the free Rental Document Status Check

Prepare a structured rental application PDF with RentFiles.
Fill your application before you choose whether to pay for a PDF export.
RentFiles helps organise the file; the agent or landlord decides the application outcome.

Working checklist

Assign a clear request state

Use four states: required, optional, unclear and not applicable. A required item needs a matching file or an explicit resolution. An optional item can be assessed for usefulness and privacy. An unclear item needs clarification. Not applicable records should not be replaced with unrelated material simply to fill the row.

Action plan

Connect each request to one response

For every included item, name the file or application field that answers it. Avoid attaching three near duplicate records when one directly satisfies the request. If one file supports two rows, record that relationship instead of uploading it twice. The map should end with a clean intended attachment list, not a larger evidence archive.

Useful context

Capture the instructions exactly

Review the advertisement, form, portal and direct messages for explicit requests. Write each request once in a working table and note its source. Do not turn an example into a requirement or assume a previous property used the same process. If two instructions conflict, mark the item unresolved rather than choosing the more demanding version automatically.

Keep in view

Recheck the active property

Before submission, confirm that the address, portal and recipient on the map match the application you are about to send. Remove rows copied from another property. Open the final files and update every status. Keep the map as a private preparation record unless sharing it would genuinely help the recipient understand the package.

A property request map keeps preparation responsive to the real application in front of you. It turns scattered instructions into a bounded, verifiable handoff list.

Practical example

Apply a minimisation decision

Provide information relevant to the recipient's application process and handle identity or financial material carefully.

If a portal asks for current income evidence and lists a reference as optional, the map can connect the income row to one current file and leave the reference row optional. It should not turn the optional example into a reason to upload unrelated history.

Questions

Common questions

Clear answers for the decisions people usually pause on.

What if the advertisement and portal request different items?

Mark the difference as unresolved and seek clarification through the available channel. Do not guess or supply a broader set of sensitive records by default.

Should the request map be sent with the application?

Usually it works best as a private preparation tool. Share it only when its concise structure adds useful orientation and contains no internal notes.

Keep building

Browse all resources

Your next step

Put your application documents in one clear pack