Version-branch register
Local planning guideCambridge England tenancy application version planning
Alternative scans, summaries and formats need visible parent sources and purposes so the wrong branch cannot become the final application copy.
- Market
- UK
- Jurisdiction
- England
- Updated
Short answer
Give each original applicant source a root ID and every prepared copy a branch ID with purpose, format, creator, date and recipient request. Keep one selected branch per request after confirmation. Before handoff, trace every selected branch to its root and remove superseded or wrong-property alternatives.
Continue in RentFiles
Turn this guide into a clear application pack
Enter and check details before payment, then choose whether to pay for a structured application PDF. RentFiles does not assess evidence, submit the application or decide the outcome.
- 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.
Useful context
Orient originals as branch roots
Record the secure location, owner, visible period and page count for each applicant-controlled original. A root is not automatically shareable. It exists to preserve provenance while working copies, summaries or conversions branch for specific confirmed recipient purposes.
Give every branch a unique neutral ID and record what changed. A renamed file is different from a cropped copy, combined document or applicant summary. Do not describe a derived branch as official, certified or recipient-approved unless the record genuinely supports that status.
Use the Cambridge version-branch register as a working decision panel, not a statement of law. For every row, record the applicant-controlled input, the recipient-process source, any official-source dependency, the person who owns the next action and the observed completion state. Recheck the England label before moving a row to another page or property. If the decision cannot be supported within that nation, leave it open and route it to the correct recipient, official authority or qualified adviser. The panel never assesses acceptance.
- Root ID
- Owner
- Visible period
- Branch ID
- Change type
Working checklist
Map branches to recipient format questions
Copy the requested category and format into the branch register with source date. When format is unclear, keep possible branches unselected and ask. Do not prepare every alternative or infer a Cambridge standard from a previous property.
A source link can be visible while the branch remains locked.
- Requested category
- Format
- Source date
- Pending lock
- Selection state
Working checklist
Select and reconcile final branches
Choose one branch per request and mark alternatives superseded, rejected or retained privately. Compare selected IDs with the form and final file list. Remove unselected copies from the transfer folder and check that each filename belongs to the Cambridge property context.
If instructions change, fork a new branch and return dependants to review. Do not overwrite the selected copy in place. Preserve the earlier handoff record if it was sent so the applicant can identify which version left their control.
- Selected branch
- Alternative state
- file list match
- New fork
- Handoff record
Action plan
Prepare deliberate branches
Create the minimum copy needed for a confirmed purpose, preserve the root and record the method. Preview all pages, orientation, filename and legibility. If a treatment removes or masks information, ask whether the recipient accepts it before selecting the branch.
Keep calculations and explanatory summaries labelled as applicant-created branches. Show inputs and periods where relevant. Do not merge separate accounts, people or date ranges into one source-like file when the combined result could obscure ownership or provenance.
- Confirmed purpose
- Copy method
- Preview
- Treatment answer
- Applicant-created label
Keep in view
Bound branch claims and nation scope
No branch may be labelled compliant with England rules, standard in Cambridge or guaranteed acceptable. Wales and Scotland sources cannot unlock an England branch.
ICO wording supports limiting personal data to the stated purpose. RentFiles can organise applicant-entered details into a structured PDF but does not inspect roots, approve transformations, verify official facts, submit files or decide outcomes.
Keep personal information relevant to the recipient's stated purpose and avoid adding sensitive material that was not requested.
- No compliance label
- No city standard
- ICO privacy
- Product boundary
Questions
Common questions
Clear answers for the decisions people usually pause on.
What is a source root in this register?
It is the preserved applicant-controlled original from which purpose-specific working or sharing copies are derived and traced.
Should several format branches be sent together?
Not by default. Ask which format the recipient accepts and select the minimum relevant branch for that request.
Which source should support a row in this version-branch register?
Use the applicant's own dated record for personal facts and the named recipient's current instruction for its property process. Check current authoritative information for a legal question.
Can a selected branch be overwritten after a change?
Create a new branch and recheck dependants instead. Preserve what was previously checked or sent for accurate traceability.
Does RentFiles ever validate document branches?
No. RentFiles structures applicant-entered details into a PDF. It does not inspect files, approve formats, submit applications or decide outcomes.
Keep building
Continue with a related guide
Your next step
Put your application documents in one clear pack
Enter and check details before payment, then choose whether to pay for a structured application PDF. RentFiles does not assess evidence, submit the application or decide the outcome.
Fill your application before payment