Tenancy application organisation guide for the UK

Freeze only when no final field depends on an open question, every selected version has been previewed and the recipient route is current. Compare the field register, source links, version manifest and form. Record the handoff version and close the temporary transfer set after the applicant completes its purpose review.

RentFiles lets the applicant fill details before choosing whether to pay for a structured application PDF. It does not inspect source registers, validate answers, submit the application, control external storage or decide the outcome. This active-workspace guide also sets no document retention period.

Copy each requested field from the current recipient form and assign a neutral ID, response owner, state and source need. Use not started, drafting, checked, blocked or final rather than a single completion tick. A field can be filled but still blocked by an unresolved date or recipient instruction.

Keep the recipient's wording visible and attach its source date. Do not add fields from another application simply because they seem useful. When a form changes, preserve a change note and link affected entries instead of editing the register until no one can tell which version was checked.

Maintain one active application version and record every change that affects an entered answer, file selection or explanatory note. Calculations stay in a labelled working area with their input rows and method visible. Do not paste an untraceable result into the form or treat a calculated summary as original evidence.

When a value changes, trace its dependants and return them to checked or blocked as appropriate. A new filename alone does not require every answer to change, while a corrected date may affect history, notes and selected files. The dependency record tells the applicant which reviews must be repeated.

The source register describes applicant-controlled records by purpose, owner, covered period and secure location. It should not copy full identifiers, balances or unrelated personal detail. Link a field to a source only when the recipient request and the record's visible capability genuinely match.

Keep originals separate from prepared versions. A prepared copy receives its own ID, transformation note and preview status. This distinction makes it possible to correct a crop or filename without altering the underlying source and to remove an obsolete sharing copy without losing the applicant's original record.

Review collaboration access, exported tables, temporary uploads and filenames. Keep coordination metadata neutral and sensitive contents in controlled source locations. Remove duplicate prepared copies and confirm that every active link points to the intended applicant, property and recipient context.

ICO minimisation wording supports keeping personal information relevant to the recipient's purpose. It does not prescribe this workspace or decide which records are required. Organisation cannot replace official authority, recipient clarification or the applicant's own fact check of every entered date, name and selected attachment.

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

Use the question register for missing dates, unavailable references, uncertain formats and recipient clarification. Give each exception an owner and dependent field. Do not bury an unresolved gap in a narrative paragraph or fill it from memory so the dashboard appears complete.

For example, an address end date can block both the history row and a reference period. One question ID links those dependants and records the source answer. When resolved, each affected item still requires its own check; closing the question does not automatically approve every resulting field.