Work event sequence

Applicant playbook

How to organise a zero hours worker tenancy application in the UK

Variable work is clearer when an offered shift, an accepted shift, completed work and a paid period are not treated as the same event.

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

Short answer

Copy the recipient's work or income request, then create separate rows for offered, accepted, completed and paid events. Attach the source, period, payer and current status to each row. Present completed pay records as they stand, keep future availability and offered work pending, and do not convert recent hours into guaranteed future income or interpret employment rights.

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.

Practical example

Trace one completed and one offered shift

Imagine a pay record covering completed work and a separate message offering a future shift. The event table attaches the pay period to the completed row and the message to the offered row. It does not add the future shift to money already received or assume that the offer will be accepted.

A new reader can see which event answers the recipient's current evidence request and which event provides only context. If the note blurs those roles, shorten it and restore the table labels. Uncertainty should remain visible instead of becoming an average or prediction.

Completed source
Pay source
Offer source
No future amount
Visible uncertainty

Working checklist

Build the four stage event table

Create rows for selected source records and assign each to one or more stages only when the text supports it. Capture the work period, pay period, payment date, payer and displayed amount label. If a record covers several shifts, preserve the source grouping rather than inventing a shift level allocation.

Mark cancelled, declined or unclear events accurately when relevant. Keep future rotas outside completed and paid rows. If the recipient asks for a period not covered by selected records, show the gap and ask which alternative is wanted rather than extrapolating from recent weeks.

Stage
Source
Work period
Pay period
Status

Action plan

Explain variability through actual events

Start with the current arrangement wording, then list completed work periods and their corresponding pay records. Add one factual cadence note when dates or amounts vary. Put future offers, accepted shifts not yet completed and missing periods in a final pending section.

Do not promise a minimum number of shifts, annualise a short run or describe availability as earned income. If different payers or roles appear, separate them. Route general income presentation to the income evidence page and employment contract interpretation outside this applicant file.

Current wording
Completed periods
Paid periods
Cadence note
Pending section

Useful context

Separate availability from completed work

Begin with the wording used in the applicant's work records. Record the organisation, role or assignment label, payer and any stated arrangement without interpreting its legal effect. The phrase zero hours is not a shortcut for predicting a pattern, employment status or future availability.

The page's job is event separation. Availability may describe when the applicant could work, an offer records a possible shift, acceptance records an agreed action, completion records work done and payment records a later financial event. Each needs its own source and date meaning.

Arrangement wording
Availability
Offered event
Completed event
Paid event

Keep in view

Protect rota and workplace information

Work messages and rotas can expose colleague names, internal contacts, locations and operational detail. Match selected fields to the stated purpose. The ICO data minimisation source supplies the privacy boundary for this page; it does not define zero hours evidence requirements or legal status.

Ask before altering a requested record, keep the original secure and use neutral filenames. Once the applicant checks the event sequence, RentFiles can structure entered details into an application PDF before payment. It does not verify shifts, calculate future income or decide the tenancy outcome.

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

Colleague data checked
Internal details limited
Purpose recorded
Original secure
Future work not predicted

Keep building

Browse all resources

Questions

Common questions

Clear answers for the decisions people usually pause on.

Can an offered shift be counted as completed work?

No. Keep offered, accepted, completed and paid stages separate. A future event should remain pending until an applicant controlled source confirms the next stage.

Should recent hours be turned into guaranteed future income?

No. Present the actual periods and amount labels requested, and ask about any calculation method instead of forecasting future shifts.

Do I need to send a complete rota?

Follow the recipient's request and check for colleague or operational information. Ask whether a narrower applicant controlled record answers the purpose.

Does this page determine my employment rights or status?

No. It only organises the wording and events in applicant controlled records and does not offer a legal interpretation.

Does RentFiles verify shifts or calculate income?

No. RentFiles organises applicant entered details into a structured PDF. It does not verify work, forecast income or decide the result.

Your next step

Put your application documents in one clear pack