Clear and private filenames

Document workspace

Tenancy application document naming checklist for the UK

A useful filename tells the applicant and recipient what a file is for, which period it covers and whether it is the intended version, without repeating sensitive content.

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

Short answer

Use a consistent four part filename: application purpose, neutral source label, relevant period and version status. Keep the words short, use the date meaning shown by the source, and reserve a unique suffix for genuine collisions. Do not put full names, account numbers, identifiers, health details or outcome claims in filenames, and do not use a tidy name to imply that a document is valid or sufficient.

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.

Fill your application before payment

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.

Working checklist

Inventory existing names and date meanings

Open the final candidate files and record their current filenames, source titles, covered periods, issue or download dates and version states. Decide which date matters for navigation. A pay period, statement period, issue date and download date are not interchangeable. Use the date that answers the manifest request and keep another date inside the manifest if it helps resolve ambiguity.

Identify collisions before renaming. Two files may share a source and period while representing different pages, revisions or purposes. Mark the difference using a controlled suffix such as part number or version status only when the source or applicant can support it. Do not guess that the newest download is the newest record, and do not overwrite the unchanged original during this working step.

Current filename
Source title
Date meaning
Version state
Collision reason

Working checklist

Test the final folder and manifest together

Sort the final folder by filename and check whether the application sequence remains understandable. Open every file from that folder, confirm that its contents match the purpose and period in the name, and compare the exact filename with the manifest. Remove duplicates, working versions and superseded copies. Check that no file extension was changed in a way that makes the attachment unreadable.

Ask a final set of questions. Can every recipient request point to a file or an open question? Does every selected file have a unique and meaningful name? Are date meanings consistent? Is sensitive information absent from the labels? Has the unchanged source been preserved securely? Only after those checks should the applicant use the structured application PDF workflow for their entered details.

RentFiles can help prepare a structured application PDF after the applicant has selected, named and checked their information. The application can be filled before payment. RentFiles does not inspect filenames, verify attachments, submit the file or decide whether a landlord or agent will accept it.

Folder sorts clearly
Contents match name
Manifest exact match
Superseded copies removed
Original preserved

Action plan

Apply one four part naming pattern

Build names in a stable order: purpose, neutral source label, relevant period, then version. For example, the purpose might distinguish income, address or reference material without exposing the underlying personal value. Use lower case words and a consistent separator in the implementation, but keep the reader facing manifest human readable. Choose a period form that remains clear when files are sorted.

Rename a sharing copy, then update the manifest row immediately. If a file contains several pages, use one name for the assembled file and record its page contents in the manifest rather than creating an overloaded filename. If two attachments still collide, add a meaningful part or source qualifier. Avoid arbitrary final, final2 or new labels that lose their meaning after another edit.

Version status should describe what the applicant knows: working, checked, replacement or superseded. Keep superseded files outside the final sharing folder rather than relying on their name alone. A checked label means that the applicant performed the stated file check; it does not mean that RentFiles, an agent or any authority verified the document.

Purpose first
Source label second
Relevant period third
Version last
Manifest updated immediately

Useful context

Define the filename's narrow job

A filename is a navigation label, not evidence about the file's quality. It should help the applicant and recipient connect an attachment to a request, identify its covered period and distinguish the intended version. Begin by copying the recipient's request into the application manifest. Give the filename only enough information to locate the answer to that request.

This checklist does not choose which documents belong in the application, decide whether a record is current, verify its contents or establish what every UK landlord or agent requires. Those decisions remain with the recipient's instructions and the specialist file guides. A clear name must never turn a draft, partial scan or unrelated record into acceptable evidence by implication.

Application purpose
Neutral source label
Relevant period
Version status
Manifest request key

Keep in view

Remove sensitive information from filenames

Filenames can appear in email previews, download histories, shared folders and recipient systems even when the document itself has tighter controls. Check proposed names for full personal names where unnecessary, dates of birth, account or reference numbers, government identifiers, health information, relationship details and third party names. Replace them with a neutral purpose or source label that still supports navigation.

The ICO data minimisation source supplies the privacy boundary for this UK checklist. It does not mandate a naming format, and this page does not claim that a particular pattern satisfies every recipient. Keep personal information relevant to the stated purpose, and avoid placing sensitive values in a filename simply because they also appear inside the source document.

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

No identifier
No account number
No sensitive circumstance
No unnecessary full name
No third party detail

Questions

Common questions

Clear answers for the decisions people usually pause on.

Is there one required filename pattern for every UK tenancy application?

No. This four part pattern is an applicant organisation method. Follow the recipient's explicit upload instructions whenever they specify a different format or character rule.

Should a tenancy application filename include my full name?

Only include personal information that has a clear purpose in the recipient's process. A neutral purpose and period may be enough, so ask when the upload instructions are unclear.

Which date should I put in the filename?

Use the date meaning that answers the manifest request, such as a covered period or issue date. Do not substitute a download date merely because it is easiest to find.

Why should I avoid labels such as final2 or newest?

Those labels become ambiguous after another edit. Use a supported version state or meaningful part qualifier, and keep superseded files outside the final sharing folder.

Does RentFiles check or rename my supporting files?

No. RentFiles organises applicant entered details into a structured application PDF. It does not inspect, rename or verify attachments and it does not decide the outcome.

Keep building

Browse all resources

Your next step

Put your application documents in one clear pack