Portal upload
Document workspaceControl request versions during a portal upload
Attach every file decision to the current property-request version and preserve the prior wording privately.
- Market
- UK
- Jurisdiction
- England
- Updated
Short answer
Compare the active portal wording with the instruction version used to prepare each proposed upload. Attach every file decision to the current property-request version and preserve the prior wording privately. Do not mix instructions from two versions or silently discard a change.
Working checklist
Check the record behind request version control
Diff the current request against the version used for the last review.
Resolve ownership, period and purpose for request version control before deciding that the item is ready.
- Property: keep the relevant address or property identifier beside the selected item.
- Request date: label the relevant period clearly so request version control cannot be read against the wrong dates.
- Changed item: quote the row or document instruction that changed between the two request versions.
- Affected file: keep the selected filename and its visible contents aligned.
- Confirmation: save the portal message, timestamp or request reference that shows which version the property expects next.
Continue in RentFiles
Turn this guide into a clear application pack
Your next step in RentFiles begins once you control request versions during a portal upload. RentFiles can organise the renter’s own details into a structured PDF. It does not decide what the recipient requires, verify evidence or predict the application 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
Control request versions during a portal upload
Each upload decision should trace to the current property instruction while older wording remains in the private change record.
The review is limited to live version selection at upload.
Practical example
How the request version control check works
A portal message changes the requested period after files were prepared. The renter updates the affected row, replaces that file and rechecks the preview instead of mixing both instructions.
Keep in view
Risks to avoid with request version control
Do not mix instructions from two versions or silently discard a change.
Keep personal information relevant to the recipient's stated purpose and avoid adding sensitive material that was not requested.
Key points
Record the request version control decision
A later change should create a new request version control version rather than rewriting the retained decision.
Questions
Common questions
Clear answers for the decisions people usually pause on.
Which version of the request controls this upload?
Property: keep the relevant address or property identifier beside the selected item. Request date: label the relevant period clearly so request version control cannot be read against the wrong dates. Changed item: quote the row or document instruction that changed between the two request versions. Affected file: keep the selected filename and its visible contents aligned.
Should two request versions be mixed or a change discarded?
No. You should not mix instructions from two versions or silently discard a change.
Keep building