Source-first renter-file method
Situation playbookEngland share code request: a controlled file decision
A Share Code message is a specific handoff request with its own property reference, channel and timing. The England boundary keeps that instruction separate from the identity or financial material that may sit elsewhere in the file.
- Market
- UK
- Jurisdiction
- England
- Updated
Short answer
A Share Code request in an England tenancy application should be handled as a named recipient instruction, not as a reason to send unrelated identity material. Record the wording of the request, the property reference, the way the code is to be shared and any time or channel detail the recipient gives. If the message does not say what is wanted or how it should be provided, ask before substituting screenshots, copies or a general explanation.
Continue in RentFiles
Turn this guide into a clear application pack
Keep your own Share Code request details attached to the correct property and channel, while the recipient remains responsible for their process.
- 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.
Keep in view
Ask when the sharing method has not been stated
Pause when the request does not identify the intended channel, the person who will receive the information or the current step required. Ask a focused question rather than selecting a document by analogy. This guide helps organise a handoff; it does not decide whether a recipient will accept an alternative or complete a check.
Keep personal information relevant to the recipient's stated purpose and avoid adding sensitive material that was not requested.
GOV.UK sets out the current England document-check routes and the recipient's handling of originals and copies.
The request note connects a sharing instruction to one property and channel. It does not validate a code, replace a recipient process or establish an applicant’s status.
Useful context
Treat a Share Code as a route-specific request
A Share Code is useful to the applicant’s file only when it is connected to a current request. Begin the note with who asked, for which property and what wording was used. This avoids copying a code or related identity information into a folder simply because it may be needed later. The relevant decision is about the requested sharing step, not about proving every part of an applicant’s identity history.
Action plan
Capture the recipient, channel and timing instruction
Record the channel the recipient has nominated, such as a portal field or another stated route, and any timing detail that appears in the request. Keep the property reference beside that instruction so a code is not mixed between applications. If the wording names a different check route or asks for an original document, do not collapse the two paths into one generic identity response.
Working checklist
Do not replace a code request with another identity item
A code request should not automatically be answered with a document image, a screenshot of a private account or a narrative about status. Those materials may expose different information and may not answer the recipient’s instruction. Where an alternative is offered, write down the exact alternative and the question it addresses. Otherwise keep the request pending until the recipient clarifies the expected method.
Practical example
Keep generated details separate from the wider file
Keep the request date, any stated deadline and the sharing action in a short timeline. The timeline is useful when an instruction changes or a second property is involved. It should not contain copied account details or a claim that an external check has passed. Its purpose is to show the applicant what they were asked to do and whether that action has been completed.
Questions
Common questions
Clear answers for the decisions people usually pause on.
What belongs in a Share Code request note?
Keep the property reference, recipient wording, sharing channel, timing and any unanswered question. Avoid copying unrelated identity information into the note.
Should I send an ID image if a recipient asks for a Share Code?
Not unless the recipient separately asks for that image or offers it as an alternative. A code request and a document-copy request are different instructions.
Keep building
Continue with a related guide
Your next step
Put your application documents in one clear pack
Keep your own Share Code request details attached to the correct property and channel, while the recipient remains responsible for their process.
Fill your application before payment