Private renting application guide for Scotland

Reconcile form fields, applicant sources, exception states, selected versions and transfer route. Exclude later-stage agreement research from the sharing set unless it answers a current request.

RentFiles lets applicants enter and check their own details before deciding whether to pay for a structured application PDF. It does not verify Scottish law, assess evidence, submit applications, influence recipients or promise acceptance.

Record the current form, recipient role, property label, instruction date and response channel. Treat these as process facts for that application only. They do not become Scottish law or a template for another property, and they must be refreshed when the recipient changes the route.

Application work can continue only where it does not depend on the unanswered claim.

Use the Scotland active-process ledger 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 Scotland 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.

Map work, income, funding or savings questions to dated records and covered periods. Keep sources separate and label pending events. Do not produce an affordability verdict, predict future funds or turn the recipient's examples into a Scotland-wide evidence list.

For a missing format or period, describe the applicant's available source and its limitations, then ask what the recipient accepts. Keep payment or later agreement questions in their own queue and do not infer legal status from this pending general Scottish source.

List each requested identity or applicant-information field and the purpose stated by the recipient. Link it to one applicant-controlled source or a clarification question. Do not copy sensitive material into the ledger, and do not assume an England-specific check applies in Scotland.

Preview selected copies for correct name, pages, legibility and property context. Preserve originals and ask before changing a requested source. If the purpose remains unclear, leave the field blocked rather than disclosing additional identifiers in the hope that more information will be preferred.

Search the active workspace for imported England or Wales terminology, unreviewed Scottish rules and generic UK claims without scope. Remove them from action fields.

It does not authorise a tenancy-law conclusion. Keep collaboration tables neutral, restrict access and avoid copying reference content, identifiers or financial values into operational logs.

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

Give every address gap, unavailable contact, name difference or uncertain date an exception ID. Assign an owner and dependent field. Resolve with applicant-controlled sources, permission-aware contacts or a recipient question rather than hiding the issue in a polished narrative.

For example, an unavailable former contact can stay a closed contact route while an address source supports part of the period. The ledger should show what each source can establish. It should not declare the alternative equivalent or accepted without the recipient's answer.