How to coordinate a house share tenancy application in the UK

Record the actual submission channel, time and person who performed the handoff only after it happens. Keep acknowledgements, corrections and outcomes separate. A coordinated file can reduce confusion for the applicants, but it does not determine how the recipient evaluates individuals or the group.

Once each person has checked their information, RentFiles can organise applicant entered details into a structured application PDF before payment. It does not verify member records, manage consent, submit the application or influence the agent or landlord's decision.

Copy the recipient's instructions about whether applicants complete one coordinated process or separate forms. Record the source, date, property key and confirmed group members. If the structure is unclear, ask before anyone shares identity or financial files with a coordinator.

Create a responsibility board with one owner for each shared question, viewing action, recipient contact and final handoff. Ownership means coordinating the action, not controlling another person's evidence. Keep possible members pending until they confirm participation.

Each person records their own accommodation history, reference permissions and gaps. The shared register records only the agreed target move checkpoint and who will answer a group question. Do not force different histories into one household narrative or list a referee who has not agreed.

If members join from different current addresses, preserve those separate timelines. If one person has no rental history or recent arrival records, route them to the relevant guide. A group note should not expose the reason for another person's gap or transition.

Give each applicant a private checklist for income or funding records requested from them. Do not combine bank statements, pay records or benefit notices into one household total unless the recipient explicitly asks for a calculation and every person agrees to the handling. Use source labels and periods that remain attributable to the individual.

When a student funding source is involved, use the funding summary to preserve award and payment periods. When several income sources belong to one person, use the multiple income guide. The group register should show only completion state and owner, not private values.

Before handoff, confirm the member list, recipient structure, shared answers, action owners and consent states. Each person checks their own fields and attachments. The coordinator checks only that the required status and version are present, unless a member has explicitly authorised a narrower review.

Assign one version label to the shared register and form handoff. Record late changes by owner and affected member, then repeat the relevant consent and personal check. Never overwrite a person's approved file with another version or mark their row complete without their confirmation.

Put only genuinely shared facts in the group register: the selected property, intended move timing as confirmed, agreed contact route and any group answer everyone has checked. Each person's legal name, identity files, contact details and private circumstances remain in that person's controlled record until the recipient's process requires them.

The ICO data minimisation source supplies the privacy boundary for this guide. It does not define how every house share application operates. Record consent before a coordinator handles another person's information, limit access to the stated task and remove copies from the shared workspace when they are no longer needed.

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