What Occupant Age does in Proplix
Occupant Age is part of Proplix Applicants, Renters & Pre-Tenancy and is designed to record optional age information for an additional occupant where there is a legitimate operational reason to request it. It keeps the optional age value and the occupant it belongs to against the applicant and property context that gives it meaning.
Within the wider Occupants & Household workflow, Occupant Age supports the people expected to live at the property before tenancy onboarding begins and should lead towards a more complete household record without treating optional information as universally mandatory without rebuilding the same information from public forms, inboxes or spreadsheets.
Why this capability matters before tenancy onboarding
Occupant Age matters because household context requires age information and the field is appropriate to the workflow. If the optional age value and the occupant it belongs to is scattered across separate records, the next colleague may have to work out which applicant, property and version is current before acting.
A structured Occupant Age record supports a more complete household record without treating optional information as universally mandatory 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 Occupant Age adds operational value
For Occupant Age, this section focuses on record optional age information for an additional occupant where there is a legitimate operational reason to request it while keeping the applicant and property context visible.
The point in the journey
Household context requires age information and the field is appropriate to the workflow. Occupant Age gives that moment a defined place so the applicant and property relationship does not get lost.
The outcome to protect
A more complete household record without treating optional information as universally mandatory. Keep the optional age value and the occupant it belongs to connected to the application so the authorised next action is clear without reconstructing the record from separate sources.
How Occupant Age fits into the workflow
The exact screen and permission path for Occupant Age depends on the user's role, but the applicant, property and application context should remain connected throughout.
- 01
Open the right applicant context
Occupant Age should begin from the applicant, property or application record involved when household context requires age information and the field is appropriate to the workflow. Starting there keeps the optional age value and the occupant it belongs to anchored to the correct pre-tenancy journey.
- 02
Describe the proposed household
Use Occupant Age for the optional age value and the occupant it belongs to only where it is relevant to the property and application. Keep applicant, proposed tenant and other-occupant context distinct where that supports a more complete household record without treating optional information as universally mandatory.
- 03
Make the record understandable
An authorised colleague reviewing Occupant Age should be able to see what the optional age value and the occupant it belongs to means and how it relates to a more complete household record without treating optional information as universally mandatory without rebuilding the story from another system.
- 04
Review occupancy context
For Occupant Age, make sure the optional age value and the occupant it belongs to gives the tenancy team enough context for a more complete household record without treating optional information as universally mandatory without collecting household detail that the workflow does not need.
- 05
Hand off deliberately
If Occupant Age reaches its intended outcome — a more complete household record without treating optional information as universally mandatory — carry forward the applicant and property context needed by the next authorised stage instead of copying the whole application into another uncontrolled record.
What Occupant Age helps the team control
Connected applicant context
Occupant Age keeps the optional age value and the occupant it belongs to attached to the applicant and property context in which it is needed.
Structured information
Instead of leaving the optional age value and the occupant it belongs to in free-form messages, Occupant Age gives it a repeatable structure that supports record optional age information for an additional occupant where there is a legitimate operational reason to request it.
Household clarity
Occupant Age structures the optional age value and the occupant it belongs to so the applicant can be distinguished from other proposed occupants where that distinction matters to a more complete household record without treating optional information as universally mandatory.
Workflow continuity
Occupant Age can carry the context needed for a more complete household record without treating optional information as universally mandatory into the next authorised stage without asking for the same facts again.
What Occupant Age looks like in practice
Consider a case where household context requires age information and the field is appropriate to the workflow. The applicant or authorised team member uses Occupant Age from the relevant property or application context, so the optional age value and the occupant it belongs to 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 a more complete household record without treating optional information as universally mandatory into the next authorised stage.
How to introduce Occupant Age into a live applicant workflow
For Occupant Age, implementation should keep information proportionate to its purpose, clearly owned and dependable through corrections, exceptions and handoffs.
Give Occupant Age a clear owner before rollout. Decide who is responsible for the optional age value and the occupant it belongs to, which values are applicant-supplied and which authorised staff may amend or review them.
Keep Occupant Age proportionate to record optional age information for an additional occupant where there is a legitimate operational reason to request it. 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 Occupant Age before a tenancy is created
Occupant Age supports the authorised people who provide, organise, review or progress this part of the applicant journey.
Keep Occupant Age data, decisions and permissions aligned
Occupant Age can involve personal or financial information. Apply least-privilege access, privacy notices, retention rules and lawful data handling to the optional age value and the occupant it belongs to.
A structured record improves consistency but does not verify the optional age value and the occupant it belongs to automatically; authorised users should correct material errors before relying on it.
Any decision informed by Occupant Age should remain fair, explainable and limited to the legitimate purpose of record optional age information for an additional occupant where there is a legitimate operational reason to request it, while preserving the same applicant and property identity across handoff.
Related features in Applicants, Renters & Pre-Tenancy
These pages sit close to Occupant Age 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 Occupant Age
What is Occupant Age used for in Proplix?
Occupant Age is an Applicants, Renters & Pre-Tenancy capability for record optional age information for an additional occupant where there is a legitimate operational reason to request it. It keeps the optional age value and the occupant it belongs to connected to the relevant applicant and property journey.
When is Occupant Age most useful?
Occupant Age is most useful when household context requires age information and the field is appropriate to the workflow. In that situation, the intended operational result is a more complete household record without treating optional information as universally mandatory.
Who should be able to access Occupant Age?
Access to Occupant Age should be limited to applicants and authorised staff who genuinely need the optional age value and the occupant it belongs to for record optional age information for an additional occupant where there is a legitimate operational reason to request it, according to your organisation's permissions and data-handling policy.
How does Occupant Age connect to tenant onboarding?
If Occupant Age is authorised to progress, the applicant and property context needed for a more complete household record without treating optional information as universally mandatory can support a controlled handoff into the separate tenancy-onboarding workflow. Capturing the optional age value and the occupant it belongs to does not by itself create tenancy approval or a contract.
Explore how Occupant Age fits your applicant journey
See Occupant Age 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.