Disclosure event register
Document workspaceTenancy document sharing checklist for UK applications
A checked document can still be sent to the wrong person, through the wrong route or in the wrong version, so sharing needs a separate control record.
- Market
- UK
- Jurisdiction
- United Kingdom
- Updated
Short answer
Create a sharing ticket for every intended disclosure. Record the recipient, stated purpose, requested file, approved version and confirmed channel before attaching anything. Preview the exact file, check that unrelated personal or third party details are absent, and record the action only after it occurs. Keep unsent drafts separate from completed sharing events and preserve the applicant's original source securely.
Continue in RentFiles
Turn this guide into a clear application pack
Fill your application before you choose whether to pay for a structured application PDF export. RentFiles does not assess evidence, submit the application or influence the agent or landlord's 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.
Working checklist
Inventory originals, derivatives and versions
List the original source under an applicant controlled storage label, then record every derivative used for a request. A derivative might be a selected page set or an applicant written summary, but it must not be passed off as an unchanged original. Link each version to its purpose, creation date and applicant check so the intended attachment is unambiguous.
Open files rather than trusting filenames or thumbnails. Confirm the visible applicant name, period, page count and relevant content. Look for blank pages, hidden scans, comments, unrelated transactions or another person's details. If the recipient requested an original record, ask before changing it or offering a different format, and keep the unchanged source available to the applicant.
- Original label
- Derivative label
- Purpose
- Version date
- Applicant check
Working checklist
Close the ticket with evidence of the actual event
Immediately before sharing, verify the property or application key, recipient, purpose, filenames, page count and channel one last time. After the action, record the actual time, sent version and any acknowledgement. Do not treat a draft, upload preview or automated receipt as proof of assessment or acceptance by the recipient.
If an error is discovered, preserve the event record and note the correction requested or completed. Do not overwrite the history in a way that hides which version left the applicant's control. RentFiles can structure applicant entered details into a PDF before payment, but it does not transmit files, secure an external channel or decide the application.
- Application key
- Sent version
- Actual channel
- Event time
- Correction record
Action plan
Assemble one bounded disclosure package
Create the package from the sharing ticket, not from a general folder. Add only the exact approved versions, then preview the package in its final reading order. Compare each attachment against the ticket and remove duplicates. A cover note can map the request to filenames, but it should not introduce new personal facts or make claims the source files do not support.
Check the destination immediately before the action. Match the recipient label and route to the current request, especially when several applications are active. Keep authentication secrets outside notes and filenames. If the confirmed channel rejects a file size or format, pause and ask what alternative the recipient accepts instead of moving the material to an unconfirmed route.
- Ticket matched
- Approved versions
- Reading order
- Destination check
- Alternative confirmed
Useful context
Define the sharing event before selecting a file
Copy the recipient's request and give it a neutral ticket key. The ticket should identify who is asking, what purpose they stated, which fact or document they requested and the confirmed route for responding. Do not assume that a file shared for one property, agent or stage can be reused for another event without checking the new request.
Distinguish preparation from disclosure. A file can be selected, reviewed and prepared while still remaining unsent. Use explicit states such as candidate, applicant checked, authorised to share and shared. The final state should be recorded only after the applicant completes the action through the intended channel, not when an attachment is merely added to a draft.
- Ticket key
- Named recipient
- Stated purpose
- Requested file
- Event state
Keep in view
Apply a purpose check to every visible field
Review the exact pages and fields that will leave the applicant's control. Ask whether each item helps answer the stated request. Pay particular attention to account references, full transaction histories, workplace contacts and third party information. Do not infer that a sensitive field becomes relevant simply because it appears on the same document as a requested fact.
The ICO source bound to this checklist supports limiting personal information to the stated purpose. It does not identify a universally acceptable redaction, transfer channel or tenancy evidence set. Preserve the original, document the applicant's choice and ask the recipient before altering a requested record or replacing it with a narrower version.
Keep personal information relevant to the recipient's stated purpose and avoid adding sensitive material that was not requested.
- Field purpose
- Account detail
- Third party data
- Original retained
- Recipient question
Questions
Common questions
Clear answers for the decisions people usually pause on.
Can the same tenancy document be shared for several applications?
Check every new recipient and purpose separately. Reuse only the applicant approved version that answers the current request, after confirming it contains no listing specific material from elsewhere.
Should sensitive fields always be removed before sharing?
No universal instruction is asserted. Review relevance, preserve the original and ask the recipient before altering a requested record or supplying a narrower alternative.
Does attaching a document to a draft count as sharing?
Keep it in a prepared state until the applicant actually completes the disclosure. Record the final channel, version and time only after that event occurs.
What should happen if the wrong file version was sent?
Preserve the event record, identify the affected recipient and version, then record any correction steps. Do not erase the history or imply the recipient never received it.
Does RentFiles send tenancy documents to a recipient?
No. RentFiles organises information entered by the applicant into a structured PDF. The applicant controls any later sharing and verifies the recipient and channel.
Keep building
Continue with a related guide
Your next step
Put your application documents in one clear pack
Fill your application before you choose whether to pay for a structured application PDF export. RentFiles does not assess evidence, submit the application or influence the agent or landlord's decision.
Build your structured application PDF