A dedicated directory of 75 capabilities for moving an approved applicant through controlled tenancy onboarding, compliance gates, agreements, move-in finance, approval, renewal and termination.
Tenancy onboarding sits between an approved application and the point where the tenancy can be treated as operationally ready. It needs the correct property, landlord, tenant and occupier context, but it also depends on compliance evidence, agreement preparation, financial setup and authorised approval.
This feature area keeps those dependencies visible within one controlled journey. Invitations, onboarding stages, compliance gates, signatures, move-in financial records, status communications, termination and retention can be handled without collapsing them into one opaque status field.
The structure also keeps application intake separate from final tenancy approval. Proplix supports the workflow and evidence trail; authorised users remain responsible for the legal, compliance, contractual and financial decisions that determine whether a tenancy should proceed.
Use the categories below to move from secure entry and onboarding state through parties, compliance, agreements, move-in finance, communications and the later tenancy lifecycle.
A tenancy should not move forward simply because a sequence of screens has been completed. The important question is whether the required parties, property context, documents, compliance position and financial information are ready for the authorised decision.
Proplix therefore separates workflow progression from approval. Gates, snapshots and audit events can make blockers visible while still allowing authorised staff to review exceptions and make decisions in the context of the full record.
When a tenancy is terminated, reopened or renewed, the historical onboarding record should remain understandable. Lifecycle controls preserve the reason for change rather than overwriting the previous operating story.
Onboarding receives applicant context, adds tenancy-specific checks and creates a controlled handoff into agreement, finance, compliance and later tenancy operations.
Resolve the correct property, landlord, tenants and occupiers before final approval so the agreement and downstream records refer to the same tenancy context.
Use visible gates and agreement preparation to show what is ready, what remains outstanding and which authorised decision allows the tenancy to progress.
Carry final financial snapshots, move-in records, retention, termination and audit context forward instead of treating onboarding as a disposable form.
Use these maintained guides to move from the feature-area overview into the practical operating flow, supporting evidence, access and handoff.
Working with the capability
The strongest starting point is the work people actually complete, including the exceptions that rarely appear in a process diagram. This capability belongs inside the daily operating record, where property context, relationships, tasks, documents and decisions can be followed together instead of being reconstructed from separate systems.
Operational staff need a clear next action; managers need ownership and exceptions; clients and external participants need only the information their role permits. The practical value comes from serving those views without creating parallel versions of the truth. For Tenancy Onboarding Lifecycle, that means access should follow an evidenced business need and change when responsibility changes.
A useful workflow records who received the work, what they checked, what remains outstanding and why a decision was made. That creates a handover another authorised colleague can understand without relying on private inbox history. This makes the Tenancy Onboarding Lifecycle record more useful during absence, escalation, service review or a later audit.
Property work includes incomplete forms, late evidence, changed instructions, unavailable suppliers and circumstances requiring discretion. The system should expose those exceptions, preserve notes and direct them to an authorised person instead of silently forcing a misleading “complete” status.
Implementation should begin with real examples from the organisation: a recent case that went well, one that stalled and one that exposed missing information. Those examples reveal the fields, permissions, notifications and escalation points the configured workflow actually needs. Document what remains outside the system as well, so teams understand the boundary between Proplix, connected services and professional responsibility.
A sensible review looks at completion time, avoidable follow-up, unresolved exceptions, record quality and the amount of manual reconciliation still required. The aim is dependable work and clearer service, not automation for its own sake. Review findings with the people completing Tenancy Onboarding Lifecycle work, because a dashboard may not reveal the manual workaround being used beside it.
Ownership, legislation, services and internal policies change. Schedule periodic checks of access, templates, notifications, integrations and retained information. Record material changes and brief affected users so the configured workflow continues to reflect the organisation’s approved way of working.
Proplix supports structured workflow and evidence handling; it does not provide legal advice or remove the need for competent human review. Discuss your organisation, migration or integration requirements through the central secure enquiry route.
Discuss Tenancy Onboarding Lifecycle requirements →Bring a typical case, the systems you use and the main problem you want to solve. Together we can map the records, responsibilities and checks needed for a useful first release.
Explore software integrations, compare enterprise modules or discuss a custom property workflow. The agreed scope will explain what is included, what needs configuration and how your team will be supported.
Plan the right route
Bring one real workflow to a Proplix walkthrough. Explore the records, handovers and decisions that matter to your team, then agree a practical next step.
