Permission-aware contact directory
Document workspacePrevious landlord details summary for UK applications
A contact directory is useful when it tells the recipient who may be contacted, for which period and through which agreed route without pretending to be the reference itself.
- Market
- UK
- Jurisdiction
- United Kingdom
- Updated
Short answer
Start with the recipient's exact history and contact fields. For each prior address, record the applicant-checked period, the contact's role as understood by the applicant, permission status, agreed contact route and facts the person can reasonably know. Keep private working notes outside the transfer view. Mark unavailable or unconfirmed details honestly, and never write a testimonial or guarantee a response on the contact's behalf.
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.
- 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
Gather field-level source material
Record where each address, date, name and contact route came from: applicant record, direct confirmation or recipient form. Check spelling and period boundaries against the source. Do not paste full correspondence, account information or old application material into the directory merely because it contains one useful detail.
Ask the contact whether they agree to the intended recipient and route before marking them available. Note the permission date and scope without reproducing private conversation. If they agree only to email or only to confirm a particular period, keep that limitation visible and do not broaden it for convenience.
- Field source
- Spelling check
- Period check
- Permission date
- Agreed scope
Working checklist
Run the final directory check
Reconfirm address dates, name spelling, role label, permission state and intended route shortly before sharing. Compare the transfer view with the current recipient form. Remove contact records no longer relevant to an active request and ensure a missing response is not shown as consent or availability.
Stop if a person has not agreed, a period is guessed, a private note appears in the transfer view or the summary reads like a testimonial. RentFiles can structure applicant-entered details into a PDF but does not verify former contacts, obtain permission, send reference requests or decide the application.
- Dates confirmed
- Name confirmed
- Permission confirmed
- Private note removed
- No testimonial
Action plan
Assemble working and transfer views
Maintain a working view with unresolved questions and a smaller transfer view containing only requested details that are ready to share. Give every transfer field a provenance link. Exclude internal notes about responsiveness, relationship quality or why the applicant prefers one contact unless the recipient asks for relevant first-person context.
Use one row per address-contact relationship rather than copying the same person across periods they may not know. When a contact covers several addresses or periods, show the actual scope explicitly. When no contact is available, preserve the history row and ask which alternative route the recipient accepts.
- Working view
- Transfer view
- Provenance link
- Actual scope
- Unavailable route
Useful context
Define the directory's limited job
Copy only the fields the recipient requests and separate accommodation history from contact information. The address period belongs to the applicant's history; the person's name and route belong to a consent-controlled contact record. Joining them in one row should not imply that the person has agreed or can confirm every applicant statement.
Use neutral role wording based on the applicant's records or relationship, without making legal classifications this page cannot support. If the arrangement was informal or the role is uncertain, preserve that uncertainty. A summary designed for navigation should not settle the legal nature of a past occupancy.
- Requested field
- Address period
- Contact role
- Permission state
- Role uncertainty
Keep in view
Protect contact and history information
Contact details are another person's personal information. Limit the directory to the agreed recipient and purpose, store it in the applicant's controlled workspace and remove abandoned sharing copies. Do not expose private phone numbers or email addresses inside filenames, analytics fields or general collaboration notes.
ICO minimisation wording is the authority boundary used here. It does not make contact mandatory, verify a previous landlord or state what details a recipient may insist upon. Any query-specific requirement or legal issue needs appropriately scoped authority rather than an inference from this privacy principle.
Keep personal information relevant to the recipient's stated purpose and avoid adding sensitive material that was not requested.
- Agreed recipient
- Stated purpose
- Controlled storage
- Neutral filename
- Authority gap
Questions
Common questions
Clear answers for the decisions people usually pause on.
Must a previous contact agree before their details are shared?
Ask them about the intended recipient, purpose and route. A past housing relationship does not automatically authorise a new disclosure.
Is the details summary itself a landlord reference?
No. It is a contact-and-period directory. Do not present it as another person's assessment, statement or promise to respond.
What if previous landlord contact details are unavailable?
Keep the address history accurate, mark the contact route unavailable and ask the recipient which alternative or explanation they accept.
How should an informal past arrangement be labelled?
Use the supported neutral description and avoid legal classification. Record the period and contact scope without renaming the arrangement.
Does RentFiles verify previous landlord details?
No. RentFiles organises applicant-entered details into a structured PDF. It does not authenticate contacts, obtain consent, send requests or decide outcomes.
Keep building
Continue with a related guide
Your next step
Put your application documents in one clear 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