checklist workspace for Australian renters
Document workspaceList identity files without copying sensitive numbers
An index can make several identity files easier to review, especially in a joint application. Its usefulness comes from showing owner, file purpose and status. Copying numbers, birth dates or other private fields into the index creates exposure without improving navigation.
- Market
- AU
- Jurisdiction
- Australia
- Updated
Short answer
List only the applicant label, document type, filename and sharing status needed to locate each requested file. Keep document numbers and detailed identity attributes inside the controlled document, and omit any file that does not answer the request.
Working checklist
Leave identity attributes inside the source file
Do not repeat licence numbers, passport numbers, birth dates or signatures in the index. If a recipient needs a specific field, it can be reviewed in the supplied file through the agreed process. Repetition increases the number of places that must be protected and corrected.
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
Handle one file with several purposes carefully
If one permitted document answers more than one requested item, list it once and note the relevant purposes rather than making duplicate copies. If different pages or redactions are supplied, give each output a distinct filename and describe the scope accurately.
Useful context
Define the index as a routing tool
Use columns for owner, document label, filename and status such as requested, supplied or not included. Add a short purpose only when two similar files answer different requests. The index should remain useful even when its links are removed.
Practical example
Example: index a two-person identity set
Em lists em_identity-primary.pdf and em_identity-secondary.pdf; Pat lists pat_identity-primary.pdf. The table records which requested slot each file answers and whether it is ready. It contains no document numbers, date of birth fields or thumbnails of the documents.
Keep in view
Control access to the index itself
Provide information relevant to the recipient's application process and handle identity or financial material carefully.
Store the index with the handoff it describes and remove broken links before sharing. Even a minimal list can reveal names and document types, so do not publish it broadly or retain unrelated entries from earlier applications.
Questions
Common questions
Clear answers for the decisions people usually pause on.
Should the index include document numbers?
No. Use filenames and document labels to route the files, and keep sensitive numbers inside the controlled document where they are actually required.
Do I need an index for one identity file?
Usually not. An index is most useful when several people or several requested files would otherwise be difficult to match. Avoid creating extra records without a navigation benefit.
Keep building