Where to start
Properties Management → Requests & Applications → Onboarding workspace → selected pack
Before you begin
Start with the existing property or case so the team keeps one connected history. Use tenant Edit and the existing onboarding within your authorised property scope.
Follow these steps
- Check which household and property the closure affects before confirming it.
- Use the termination control and then check that the tenant relationship changed as intended.
- Keep the landlord and historical evidence connected.
- If the case must continue later, use Reopen when available and review the outstanding steps instead of assuming the old approval still applies.
Check the result
A colleague can find the outcome on the same property or case and see what needs to happen next.
If something does not look right
Give the team the property or case reference and the message shown. Check the saved outcome before attempting the action again.
Fields, rules and limits
- Termination removes the tenant link for the selected context while preserving landlord ownership and history. Reopen is a separate supported workflow action and still validates the current record; it does not restore every downstream financial or signed state automatically.
Questions and answers
What should I check before handing this over?
Make sure the property reference, saved outcome and next action are clear to the colleague taking over.
Should I start again if I do not see a confirmation?
Check the existing record first. It may already have saved, with only a later delivery or file-generation step still pending.
Related technical reference: Britixo's detailed product guide (opens in a new tab). The screens available to you depend on your configured modules, company and permissions.
Useful next steps
- Review due compliance before extending an approved tenancy
- Start a renewal from an approved onboarding pack
- Troubleshoot a duplicate onboarding record
Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.