Contract end checkpoint

Situation playbook

How to prepare a tenancy application with a fixed term contract

A fixed term is clearest when the confirmed start and end remain visible and any renewal discussion stays separate from the current contract record.

Market: UK
Jurisdiction: United Kingdom
Updated: 2026-07-20

Short answer

Record the contract wording, employer or counterparty as displayed, confirmed start, confirmed end, current status and source date. Map completed pay records to periods inside that term, then place renewal, extension or next role information in a separate pending section. Do not hide the end date, forecast continuation or interpret contract rights inside the tenancy file.

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.

Build your structured application PDF

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 about the end checkpoint without oversharing

If the recipient requests evidence beyond the current term, state what is unavailable and ask which alternative they accept. Do not create a letter, alter a contract or present a manager's informal comment as an issued renewal. Confirm referee permission before sharing contact details.

The ICO data minimisation source supplies the privacy boundary for selected contract and pay material. It does not establish fixed term acceptance rules. Limit personal and workplace information to the stated purpose, ask before changing a requested file and retain the original securely.

Keep personal information relevant to the recipient's stated purpose and avoid adding sensitive material that was not requested.

Unavailable future record
Alternative asked
No informal renewal
Referee consent
Privacy purpose

Useful context

Make the term end visible

Copy the recipient's employment or income question, then extract only the contract facts relevant to it. Record the relationship wording, named organisation, start date, end date and issue date exactly as shown. If the end depends on an event rather than a calendar date, preserve the source wording instead of inventing one.

This page focuses on the application situation created by a visible term boundary. The employment contract summary owns the wider clause and document navigation. This page does not interpret rights, renewal likelihood or how an agent will evaluate the remaining term.

Relationship wording
Start
End
Issue date
Recipient question

Action plan

Build a term runway and evidence coverage line

Place the application date, confirmed contract term and selected completed pay periods on one timeline. Give each event a source key. The runway shows which evidence exists before the end checkpoint and which requested periods remain uncovered; it does not calculate whether the remaining term is sufficient.

Add separate rows for an extension discussion, issued renewal, next role or unavailable information. Use confirmed only when a current source supports it. A conversation, expectation or draft stays pending. If a pay record falls after the stated end, flag the discrepancy rather than silently extending the contract.

Application date
Contract runway
Pay coverage
End checkpoint
Renewal status

Working checklist

Stop at inconsistent or unsupported term facts

Pause when contract dates conflict, a draft and signed version differ, the relationship label is unclear, a pay record sits outside the term or the renewal source is informal. Put each issue in the question log and resolve it before producing a summary.

Trace the final note to the runway and files. Remove irrelevant contract clauses and third party data. After the applicant checks the term facts, RentFiles can organise entered details into a structured application PDF before payment. It does not interpret contracts, verify employment or decide the application.

Date conflict
Version conflict
Label unclear
Out of term pay
Informal renewal

Practical example

Show a current term with an unresolved renewal

Imagine a current contract ending after the application date and three completed pay records within the term. The runway points each event to a source. A renewal conversation appears in the pending section with its date but is not added to the confirmed end.

The short note says what is current, what period the pay records cover and what remains unknown. It does not say the contract will continue or decide whether the recipient accepts the term. If a later issued record changes the end date, the applicant creates a new sourced version.

Current term
Three pay periods
Renewal pending
No continuation claim
New source version

Questions

Common questions

Clear answers for the decisions people usually pause on.

Should I leave the fixed contract end date out?

No. Preserve the confirmed term shown by the source and keep any renewal or next role information in a separate sourced status.

Can a renewal discussion be shown as confirmed?

No. Keep it pending until a current issued record supports the change. Record the discussion only when it is relevant to the recipient's question.

Does this guide interpret fixed term employment rights?

No. It organises applicant controlled facts for a tenancy file and does not offer legal or contractual interpretation.

What if the recipient asks for evidence beyond the term?

State that the record is unavailable and ask which alternative they accept. Do not manufacture continuation or alter the existing contract.

Does RentFiles verify a fixed term contract?

No. RentFiles structures applicant entered details into an application PDF. It does not interpret contracts, verify work or decide the outcome.

Keep building

Browse all resources

Your next step

Put your application documents in one clear pack