What Non-Lease Occupants does in Proplix
Non-Lease Occupants is part of Proplix Applicants, Renters & Pre-Tenancy and is designed to record whether people are expected to live at the property without being named as tenants. It keeps the occupancy declaration and relevant resident context against the applicant and property context that gives it meaning.
Within the wider Occupants & Household workflow, Non-Lease Occupants supports the people expected to live at the property before tenancy onboarding begins and should lead towards the intended occupancy is explicit before the application progresses without rebuilding the same information from public forms, inboxes or spreadsheets.
Why this capability matters before tenancy onboarding
Non-Lease Occupants matters because the proposed household includes residents who may not be parties to the tenancy agreement. If the occupancy declaration and relevant resident context is scattered across separate records, the next colleague may have to work out which applicant, property and version is current before acting.
A structured Non-Lease Occupants record supports the intended occupancy is explicit before the application progresses while reducing the risk that additional occupants are misunderstood or discovered late because the proposed household was never recorded consistently and keeping human review, privacy controls and the organisation's fair decision process intact.
Where Non-Lease Occupants adds operational value
For Non-Lease Occupants, this section focuses on record whether people are expected to live at the property without being named as tenants while keeping the applicant and property context visible.
The point in the journey
The proposed household includes residents who may not be parties to the tenancy agreement. Non-Lease Occupants gives that moment a defined place so the applicant and property relationship does not get lost.
The outcome to protect
The intended occupancy is explicit before the application progresses. Keep the occupancy declaration and relevant resident context connected to the application so the authorised next action is clear without reconstructing the record from separate sources.
How Non-Lease Occupants fits into the workflow
The exact screen and permission path for Non-Lease Occupants depends on the user's role, but the applicant, property and application context should remain connected throughout.
- 01
Open the right applicant context
Non-Lease Occupants should begin from the applicant, property or application record involved when the proposed household includes residents who may not be parties to the tenancy agreement. Starting there keeps the occupancy declaration and relevant resident context anchored to the correct pre-tenancy journey.
- 02
Describe the proposed household
Use Non-Lease Occupants for the occupancy declaration and relevant resident context only where it is relevant to the property and application. Keep applicant, proposed tenant and other-occupant context distinct where that supports the intended occupancy is explicit before the application progresses.
- 03
Make the record understandable
An authorised colleague reviewing Non-Lease Occupants should be able to see what the occupancy declaration and relevant resident context means and how it relates to the intended occupancy is explicit before the application progresses without rebuilding the story from another system.
- 04
Review occupancy context
For Non-Lease Occupants, make sure the occupancy declaration and relevant resident context gives the tenancy team enough context for the intended occupancy is explicit before the application progresses without collecting household detail that the workflow does not need.
- 05
Hand off deliberately
If Non-Lease Occupants reaches its intended outcome — the intended occupancy is explicit before the application progresses — carry forward the applicant and property context needed by the next authorised stage instead of copying the whole application into another uncontrolled record.
What Non-Lease Occupants helps the team control
Connected applicant context
Non-Lease Occupants keeps the occupancy declaration and relevant resident context attached to the applicant and property context in which it is needed.
Structured information
Instead of leaving the occupancy declaration and relevant resident context in free-form messages, Non-Lease Occupants gives it a repeatable structure that supports record whether people are expected to live at the property without being named as tenants.
Household clarity
Non-Lease Occupants structures the occupancy declaration and relevant resident context so the applicant can be distinguished from other proposed occupants where that distinction matters to the intended occupancy is explicit before the application progresses.
Workflow continuity
Non-Lease Occupants can carry the context needed for the intended occupancy is explicit before the application progresses into the next authorised stage without asking for the same facts again.
What Non-Lease Occupants looks like in practice
Consider a case where the proposed household includes residents who may not be parties to the tenancy agreement. The applicant or authorised team member uses Non-Lease Occupants from the relevant property or application context, so the occupancy declaration and relevant resident context is captured against the record that will actually be reviewed.
A second authorised colleague can see what was provided, identify missing detail and, if the case progresses, hand only the context needed for the intended occupancy is explicit before the application progresses into the next authorised stage.
How to introduce Non-Lease Occupants into a live applicant workflow
For Non-Lease Occupants, implementation should keep information proportionate to its purpose, clearly owned and dependable through corrections, exceptions and handoffs.
Give Non-Lease Occupants a clear owner before rollout. Decide who is responsible for the occupancy declaration and relevant resident context, which values are applicant-supplied and which authorised staff may amend or review them.
Keep Non-Lease Occupants proportionate to record whether people are expected to live at the property without being named as tenants. Make optional detail clear and protect public entry points with appropriate access, transport and rate controls.
Test the normal case and realistic exceptions such as missing information, a correction after submission, an unavailable property or a revoked invitation before handing the context into the next workflow.
Who works with Non-Lease Occupants before a tenancy is created
Non-Lease Occupants supports the authorised people who provide, organise, review or progress this part of the applicant journey.
Keep Non-Lease Occupants data, decisions and permissions aligned
Non-Lease Occupants can involve personal or financial information. Apply least-privilege access, privacy notices, retention rules and lawful data handling to the occupancy declaration and relevant resident context.
A structured record improves consistency but does not verify the occupancy declaration and relevant resident context automatically; authorised users should correct material errors before relying on it.
Any decision informed by Non-Lease Occupants should remain fair, explainable and limited to the legitimate purpose of record whether people are expected to live at the property without being named as tenants, while preserving the same applicant and property identity across handoff.
Related features in Applicants, Renters & Pre-Tenancy
These pages sit close to Non-Lease Occupants in the wider application and pre-tenancy architecture.
Technical flow & related Help Centre guides
Start with the primary guide for this capability, then use the related maintained guides for the surrounding workflow, evidence, access or handoff.
Questions about Non-Lease Occupants
What is Non-Lease Occupants used for in Proplix?
Non-Lease Occupants is an Applicants, Renters & Pre-Tenancy capability for record whether people are expected to live at the property without being named as tenants. It keeps the occupancy declaration and relevant resident context connected to the relevant applicant and property journey.
When is Non-Lease Occupants most useful?
Non-Lease Occupants is most useful when the proposed household includes residents who may not be parties to the tenancy agreement. In that situation, the intended operational result is the intended occupancy is explicit before the application progresses.
Who should be able to access Non-Lease Occupants?
Access to Non-Lease Occupants should be limited to applicants and authorised staff who genuinely need the occupancy declaration and relevant resident context for record whether people are expected to live at the property without being named as tenants, according to your organisation's permissions and data-handling policy.
How does Non-Lease Occupants connect to tenant onboarding?
If Non-Lease Occupants is authorised to progress, the applicant and property context needed for the intended occupancy is explicit before the application progresses can support a controlled handoff into the separate tenancy-onboarding workflow. Capturing the occupancy declaration and relevant resident context does not by itself create tenancy approval or a contract.
Explore how Non-Lease Occupants fits your applicant journey
See Non-Lease Occupants alongside property interest, application information, household context, affordability evidence, review and the later onboarding handoff. A walkthrough can focus on your actual lettings process rather than a generic software tour.