Short stay chronology
Situation playbookHow to prepare a tenancy application after temporary accommodation
Temporary accommodation is still a known place and period. Describe each stay accurately, then show the handoff to the applicant's present situation.
- Market
- UK
- Jurisdiction
- United Kingdom
- Updated
Short answer
Build one row per temporary stay with the place label, actual occupancy dates, source type, person or organisation named on the record, and whether a contact route is confirmed. Add gaps and overlaps as separate questions. Do not call a booking receipt a landlord reference, do not extend dates to create continuity, and ask how the recipient wants temporary addresses represented.
Continue in RentFiles
Turn this guide into a clear application pack
Prepare a structured application PDF from details you enter yourself. 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.
Keep in view
Treat contacts and alternative records by their real scope
If a landlord style reference is unavailable, identify what each existing source can actually confirm. A booking record may show reservation details, while a payment record may show a transaction; neither automatically comments on conduct or tenancy performance. Ask the recipient whether an occupancy confirmation, correspondence or another source is acceptable before substituting it.
Short stay records can expose host contact details, travelling companions, payment data and precise movements. Use the ICO data minimisation boundary to keep information relevant to the stated purpose. Confirm consent before sharing another person's contact details, ask before changing a requested record and retain the original securely.
Keep personal information relevant to the recipient's stated purpose and avoid adding sensitive material that was not requested.
- Source scope stated
- No false reference label
- Alternative acceptance asked
- Contact consent checked
- Payment data limited
Useful context
Define the temporary accommodation period
Copy the recipient's previous address and reference questions. Then list every known temporary place in chronological order. Use the name shown on the applicant's record or a neutral private label if the public file does not need a commercial name. Record actual check in and check out or occupancy dates, not booking search dates or the date a receipt was downloaded.
Temporary accommodation can include different arrangements, but this guide does not classify their legal status. Its job is to show where the applicant stayed and which source supports each period. A known short stay should not automatically be presented as no rental history, and a booking platform or host should not automatically be described as a landlord or referee.
- Place label
- Occupancy dates
- Source type
- Named counterparty
- Recipient history field
Action plan
Build a place by place ledger
Give each stay one row. Add columns for arrival, departure, record source, address confidence, contact route, purpose in the application and status. Keep booking confirmation, payment receipt, correspondence and occupancy note as distinct source types. If two files cover the same stay, point them to one row instead of creating duplicate accommodation periods.
Mark a gap when no selected source covers the interval between rows. Mark an overlap when the dates genuinely overlap and add a factual explanation only when the applicant knows it. Ask how the recipient wants a partial address, a host's private contact or a sequence of very short stays entered. Do not invent a single permanent address to make the form easier.
- One stay per row
- Arrival and departure
- Distinct source role
- Gap or overlap
- Confirmed contact route
Working checklist
Resolve chronology problems before final handoff
Stop when two place labels may refer to the same stay, dates conflict, an address is incomplete, a third party contact is unconfirmed or the recipient's form has no clear temporary option. Keep a question log and resolve what can be resolved with the applicant's records. Do not hide complexity by deleting a stay or merging unrelated periods.
Before using the application builder, open every selected attachment and trace it to the ledger. Confirm that temporary stays are not described as absent history, that booking and reference roles remain distinct, and that private third party data is bounded. RentFiles can structure checked applicant entries into a PDF; it does not verify occupancy or contact providers.
- Duplicate place question
- Date conflict
- Incomplete address
- Unconfirmed contact
- Unclear form category
Practical example
Turn several short stays into a readable chronology
Consider three consecutive stays supported by two booking confirmations and one direct receipt. The ledger uses the occupancy dates from each record, not their purchase dates. A two day interval has no selected source, so it remains a visible row with a question. One host contact is omitted because the applicant has not confirmed permission to share it.
The context note can say that the applicant used temporary accommodation across the stated period and direct the reader to each source key. It should not call the sequence a continuous private tenancy or imply that every provider can supply a reference. The current address or next target appears in its own row, with confirmed or pending status.
- Occupancy date used
- Purchase date separated
- Gap row visible
- Contact permission absent
- Current status separate
Questions
Common questions
Clear answers for the decisions people usually pause on.
Does temporary accommodation mean I have no accommodation history?
Not necessarily. Record the known place, dates and source accurately, then ask how the recipient wants the period entered. Do not erase a known stay or relabel it.
Can a booking confirmation act as a landlord reference?
Do not make that assumption. Describe what the confirmation shows and ask whether the recipient accepts it for the specific history question.
How should I show several short stays?
Use one row per stay with occupancy dates and a source key. Keep gaps and overlaps visible rather than compressing the sequence into one invented address period.
Can I share a host's contact details?
Confirm the person's agreement and the purpose before sharing their details. If permission is unclear, keep the contact out and ask the recipient about another route.
Does RentFiles verify temporary accommodation records?
No. RentFiles organises applicant entered information into a structured application PDF. It does not verify stays, contact hosts or decide the application.
Keep building
Continue with a related guide
Your next step
Put your application documents in one clear pack
Prepare a structured application PDF from details you enter yourself. RentFiles does not assess evidence, submit the application or decide the outcome.
Fill your application before payment