Route-by-purpose communication

Local planning guide

Richmond rental application contact and handoff plan

Questions, attachments and corrections can follow different routes, so each handoff needs its own confirmed destination and current source instead of a general contact assumption.

Market: AU
Jurisdiction: Victoria, Melbourne
Updated: 2026-07-22

Short answer

Create a table with one row for each communication purpose: application question, form access, attachment transfer, correction or follow-up. Record the current recipient, approved channel, source date, item owner and acknowledgement status. Keep sensitive values out of the log. Before sending any file, confirm the row and destination; after sending, record only what is needed to trace the handoff and ask before resending.

Continue in RentFiles

Turn this guide into a clear application pack

Enter and check details before payment, then choose whether to pay for a structured application PDF. RentFiles does not assess evidence, submit the application or decide the outcome.

Fill your application before payment 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.

Useful context

Orient each message by purpose

List the communication tasks for the property and avoid a single catch-all contact row. A viewing question, application support query and sensitive attachment may have different intended recipients or channels. The table should show those differences without claiming that Richmond properties follow one shared communication model.

Record the source for each route, such as the current form, recipient message or confirmed reply. Mark a route unknown when it comes only from an old listing or another application. Do not test an uncertain destination by sending private material; ask a non-sensitive routing question first.

Communication purpose
Named recipient
Confirmed channel
Source date
Route status

Working checklist

Map item ownership and destination

For every outgoing item, name the applicant-controlled source, the person responsible for checking it and the recipient row it belongs to. Keep question text, attachments and correction notices separate so a reply to one task cannot be mistaken as acknowledgement of the whole application.

Use neutral log references instead of copying form answers, identifiers or financial values. The table can say income attachment version two without displaying its contents. Limit access to the working log because even routing metadata can reveal property interest, contact details and application activity.

Item owner
Checked version
Destination row
Neutral reference
Access limit

Working checklist

Handle acknowledgements and corrections

After a handoff, record the time, channel, item label and any explicit acknowledgement. If no acknowledgement exists, use unknown rather than received. Ask what needs resending before duplicating a full pack, and preserve the previous transfer record so the applicant can explain which version went where.

For a correction, identify the affected field or file, the earlier version and the requested replacement route. Do not silently edit an already-sent record or send unrelated documents again. Close the correction row only when the applicant has completed the confirmed step, not when they merely drafted it.

Transfer time
Explicit acknowledgement
Resend question
Correction version
Closed state

Action plan

Prepare a low-risk routing check

Before a first transfer, verify the recipient name, channel spelling, property label and stated purpose against the current source. When a portal or form is involved, confirm that the applicant is using the intended property context. A saved link or autofilled address can carry an old destination into a new application.

If the route is unclear, send a question without sensitive attachments. Record the answer and update the source date. Do not infer that a general acknowledgement means every file was received or readable. Delivery, access and assessment are separate states and should remain separate in the ledger.

Recipient check
Channel check
Property check
Non-sensitive question
State separation

Keep in view

Keep contact claims within evidence

This page names no standard Richmond channel, expected acknowledgement time or preferred routing strategy. The current recipient owns their process. Any rule about communication or application handling needs appropriately scoped authority, and an unanswered routing question must remain unanswered until that authority or recipient responds.

OAIC evidence supplies only the purpose and privacy boundary for applicant information. RentFiles can organise checked details into a PDF but cannot validate an external address, deliver an attachment, confirm receipt, access another system, submit the application or decide the result.

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

No standard channel
No response promise
Recipient process owner
Privacy relevance
External delivery boundary

Questions

Common questions

Clear answers for the decisions people usually pause on.

Should every Richmond application item use one channel?

Not necessarily. Follow the current recipient's instructions and record the confirmed route for each purpose before transferring sensitive material.

Does a general reply confirm every attachment was received?

No automatic inference is safe. Record exactly what the reply acknowledges and ask about any file whose receipt or readability remains unknown.

Should I resend the full application after silence?

Ask which item, if any, needs another transfer and use the confirmed route. Avoid creating unnecessary duplicate disclosures.

How should a corrected file be sent?

Identify the earlier version, affected purpose and recipient-approved correction route, then preserve a clear record of the replacement handoff.

Does RentFiles confirm Richmond application delivery?

No. RentFiles structures applicant-entered details into a PDF. It does not control external channels, confirm receipt, submit applications or decide outcomes.

Keep building

Browse all resources

Your next step

Put your application documents in one clear pack