Three-board workflow
Local planning guideCardiff Wales tenancy application planning
Property instructions, later contract-stage questions and payment requests need separate owners so one category cannot silently authorise another.
- Market
- UK
- Jurisdiction
- Wales
- Updated
Short answer
Create a property-process board from the current recipient, a later-stage question board and a written payment-request board. Select applicant files from confirmed application requests, record any charge by amount and purpose without deciding legality, and reject England or Scotland terminology from every board.
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 each item to one board
Classify current form fields, contact routes and property timings as recipient process. Place later contract or handover questions on the stage board. Place every requested payment on the payment board. An item can link across boards, but its source, owner and status must remain visible.
Use Cardiff and Wales scope labels. If an instruction comes from generic UK or another nation, hold it as comparison only.
Use the Cardiff three-board workflow 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 Wales 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.
- Board
- Source owner
- Status
- Wales scope
- Comparison hold
Working checklist
Map current recipient requests
Copy the active application fields and attachment categories from the recipient's current source. Give each an applicant owner, purpose and format question. Do not populate the map from later-stage guidance or assume that a file requested at another Cardiff property is required here.
- Current field
- Applicant owner
- Purpose
- Format question
Working checklist
Reconcile stage before handoff
Check that every final field and file belongs to the active application board. Remove later-stage notes and comparison-only guidance from the transfer folder. Preview property, recipient, source version, filename and covered period and keep unanswered Welsh dependencies visible.
If a recipient request changes stages or a new payment question appears, create a new board entry rather than editing an old answer. Record the transfer route without personal values and preserve the applicant's decision state separately.
- Active-stage check
- Later note removed
- File preview
- New entry
- Transfer route
Action plan
Prepare decision and payment questions
Before viewing or committing to the application route, list unresolved property-process questions separately from legal or payment questions. Record charge amount, purpose, requester, date and written source without deciding whether it is allowed. Seek current official authority or advice where action depends on legality.
Keep personal evidence out of the payment board and payment screenshots out of the applicant evidence folder unless a confirmed purpose requires them. This separation prevents a financial request from becoming proof of application completeness or recipient acceptance.
- Process question
- Payment amount
- Payment purpose
- Written source
- Authority route
Keep in view
Keep Welsh sources pending and private data bounded
ICO wording supports limiting personal information to the recipient's purpose. RentFiles can structure checked details into a PDF after fill-before-payment, but does not review Welsh law, assess evidence, submit applications or decide outcomes.
Keep personal information relevant to the recipient's stated purpose and avoid adding sensitive material that was not requested.
- Nation separation
- ICO boundary
- Product limit
Questions
Common questions
Clear answers for the decisions people usually pause on.
Why use three boards for Cardiff planning?
They separate the recipient's active process, later-stage questions and payment requests so each keeps its proper source and authority.
Does the payment board decide whether a charge is lawful?
No. It records the written request and routes legal questions to current official authority or appropriate advice.
Should later-stage notes be sent with the application?
Not automatically. Include only material that answers a confirmed current recipient request and keep stages explicit.
What should be checked before sharing files for Cardiff tenancy application planning?
Confirm the property, recipient, purpose, filename, covered period and transfer route. Remove unrelated personal material before handoff.
Does RentFiles verify Cardiff application rules?
No. RentFiles structures applicant-entered details into a PDF. It does not verify legal rules, 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