checklist workspace for Australian renters
Document workspaceUse a register to control what is included and excluded
A folder can grow faster than the application request. A register creates a deliberate decision for every attachment: what question it answers, who owns it, whether it is current and whether it belongs in the final handoff.
- Market
- AU
- Jurisdiction
- Australia
- Updated
Short answer
Create one row per attachment with filename, owner, purpose, covered date and status. Use statuses such as requested, useful, excluded and replace. Before sending, compare the register with the actual upload list and investigate every difference.
Working checklist
Use statuses that lead to action
Requested means it answers an explicit item; useful means it provides necessary context; replace means the chosen copy is stale or unreadable; excluded means it will not be shared. Add an owner so one person is responsible for resolving every replace or unclear row.
Continue in RentFiles
Turn this guide into a clear application pack
Create a private, structured rental application file when you are ready.
- 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.
Action plan
Capture dates without duplicating contents
Record the covered month, issue date or expiry indicator needed to distinguish versions. Avoid copying balances, identity numbers or transaction details into the table. The register should help select a file without becoming another sensitive financial record.
Useful context
Record purpose before status
Do not mark a file ready until you can state which request or context it answers. A document with no clear purpose should default to excluded while you decide, not to included because it is available. Keep the purpose short enough to audit quickly.
Practical example
Example: stop an unrelated statement from travelling
A register lists a requested payslip, a useful employment transition note and an old bank statement. The statement has no current purpose and is marked excluded. During reconciliation, Kim finds it still in the upload folder, removes it and confirms the remaining filenames against the two included rows.
Keep in view
Reconcile the register with the final folder
Provide information relevant to the recipient's application process and handle identity or financial material carefully.
Sort both lists by filename, confirm that every included row has one readable file and that every file has one included row. Then remove links to excluded material and store the working register privately if it contains names or document types not needed by the recipient.
Questions
Common questions
Clear answers for the decisions people usually pause on.
Is a document register part of the rental application?
It is primarily an organising tool. Share an index only when it improves the requested handoff; otherwise keep the register private and send the selected documents.
What should I do with an optional document?
Give it a specific purpose and assess whether that context is genuinely needed. Availability alone is not a reason to include it.
Keep building