People and Permission Map
Applicant playbookSouth Brisbane student rental application workflow
A supporter, referee or institution can own different facts, and permission to make contact does not automatically authorise sharing every related document.
- Market
- AU
- Jurisdiction
- Australia
- Updated
Short answer
List each person or institution connected to the current South Brisbane application and record the exact fact they own, why the recipient asks for it, the permission state and the accepted collection route. Keep applicant-entered facts separate from another person's statement or file. When purpose, permission or route is uncertain, ask the recipient and the person concerned before adding contact details or sensitive material.
Continue in RentFiles
Turn this guide into a clear application pack
Enter and check your details before payment, then choose whether to pay for a structured application PDF. RentFiles does not assess evidence, submit the application, make or influence the rental decision.
- 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
Build the People and Permission Map
Give each row separate states for contact permission and document permission. Agreed contact means the person accepts a defined approach; it does not mean the applicant may upload any file about them. Agreed document means a specific item and purpose are understood. Pending or declined must remain visible without pressure or invented consent.
Add the recipient's accepted route and a last-confirmed date. Where direct collection is possible, ask whether the person can provide their information straight to the recipient instead of circulating it through the applicant's folder. Do not claim that direct collection is required; use it only when the parties and current process support it.
- Contact permission
- Document permission
- Accepted route
- Confirmed date
- Direct collection
Action plan
Order the student profile by ownership
Present applicant-owned study, funding and accommodation facts first. Then identify any recipient-confirmed third-party step without writing the person's answer for them. If a supporter arrangement is relevant, state only the applicant's factual understanding and keep the other person's independent confirmation in its own route and ownership lane.
Avoid embedding phone numbers, emails, account values or private messages in a summary. Use the map to manage handoffs, not to become the handoff record itself. Select person-specific files only after checking their exact purpose, pages, permission and destination, then store them separately from general applicant sources.
- Applicant facts
- Independent response
- Support boundary
- Sensitive value excluded
- Separate storage
Useful context
Separate roles before gathering details
Copy the recipient's current student-related questions and identify whether the applicant, supporter, referee or institution owns each answer. One person can appear in several roles, but each role needs a defined purpose. A family member who discusses accommodation does not automatically own a funding fact or agree to provide financial information.
Keep names and contact details out of the planning map until their purpose is confirmed. Use role labels and neutral references first. This reduces unnecessary copying and lets the applicant discover whether the recipient prefers direct contact, an invitation, an applicant-uploaded record or another controlled route.
- Requested fact
- Person role
- Fact owner
- Purpose
- Possible route
Keep in view
Audit people, purpose and destination
Before finalising the application, trace every third-party reference from recipient question to role, permission and selected route. Remove unused contact details, declined requests, private messages and files whose document permission is missing. Confirm the destination again before transferring anything sensitive and record only a neutral handoff status.
Stop when one permission is stretched to another purpose, the applicant is writing in another person's voice, a route is unconfirmed or an institution record contains unnecessary data. RentFiles can organise applicant-entered details into a structured PDF but does not obtain permission, contact third parties, submit files, assess evidence or make the rental decision.
- Role trace
- Purpose trace
- Permission trace
- Destination check
- No borrowed voice
Key points
Use official sources without overreach
Start from the supporter or referee question actually shown in the South Brisbane application. Confirm the intended contact route and document purpose with the recipient, then obtain the other person's permission before sharing their details. This consent map does not create a local supporter, referee or student document rule.
Provide information relevant to the recipient's application process and handle identity or financial material carefully. That verified OAIC wording supplies a purpose boundary, not personalised permission or legal advice. If rights or obligations are disputed, use an appropriately qualified source rather than treating this workflow as a legal conclusion.
Follow the current instructions for this property, confirm the recipient's requested fields and file formats, and ask directly before supplying anything the application does not clearly request.
Provide information relevant to the recipient's application process and handle identity or financial material carefully.
- Queensland route
- No student rule
- Relevant purpose
- Permission boundary
- Qualified source
Keep building
Continue with a related guide
- Continue with the Fortitude Valley student change register
- Continue with the South Brisbane self-employed period reconciliation table
- Continue with the Toowong self-employed variance log
- Continue with the Brisbane CBD accommodation context ladder
- Build a first rental application from evidence you actually have
Questions
Common questions
Clear answers for the decisions people usually pause on.
Does permission to contact someone cover every document?
No automatic inference is safe. Define the contact purpose and any specific document permission separately before sharing another person's information.
Can an applicant write a supporter's statement?
Do not present applicant-authored text as the supporter's independent confirmation. Use the route accepted by the recipient and person concerned.
Should a full institution record be uploaded?
Only select material that answers a stated request, and check pages, purpose and sensitive surplus before preparing a sharing copy.
What if a proposed referee or supporter declines?
Record the route as declined, remove their unused details and ask the recipient how it wants the resulting gap handled.
Does RentFiles collect supporter permission for applicants?
No. The applicant manages permission and sources. RentFiles structures applicant-entered information into a PDF without contacting or assessing third parties.
Your next step
Put your application documents in one clear pack
Enter and check your details before payment, then choose whether to pay for a structured application PDF. RentFiles does not assess evidence, submit the application, make or influence the rental decision.
Fill your application before payment