Website and product guidance

Search Proplix

Results combine Proplix product pages with detailed Help Centre guidance.

Occupants & Household

Occupant Given Name

A structured way to record the given name of an additional occupant as part of the household information, while keeping applicant, property and pre-tenancy context connected.

What it does

What Occupant Given Name does in Proplix

Occupant Given Name is part of Proplix Applicants, Renters & Pre-Tenancy and is designed to record the given name of an additional occupant as part of the household information. It keeps the occupant's given name and household relationship context against the applicant and property context that gives it meaning.

Within the wider Occupants & Household workflow, Occupant Given Name supports the people expected to live at the property before tenancy onboarding begins and should lead towards the household record is understandable to authorised reviewers without rebuilding the same information from public forms, inboxes or spreadsheets.

Why it matters

Why this capability matters before tenancy onboarding

Occupant Given Name matters because the application identifies another person expected to live at the property. If the occupant's given name and household relationship 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 Occupant Given Name record supports the household record is understandable to authorised reviewers 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.

When it is useful

Where Occupant Given Name adds operational value

For Occupant Given Name, this section focuses on record the given name of an additional occupant as part of the household information while keeping the applicant and property context visible.

The point in the journey

The application identifies another person expected to live at the property. Occupant Given Name gives that moment a defined place so the applicant and property relationship does not get lost.

The outcome to protect

The household record is understandable to authorised reviewers. Keep the occupant's given name and household relationship context connected to the application so the authorised next action is clear without reconstructing the record from separate sources.

How it works

How Occupant Given Name fits into the workflow

The exact screen and permission path for Occupant Given Name depends on the user's role, but the applicant, property and application context should remain connected throughout.

  1. 01

    Open the right applicant context

    Occupant Given Name should begin from the applicant, property or application record involved when the application identifies another person expected to live at the property. Starting there keeps the occupant's given name and household relationship context anchored to the correct pre-tenancy journey.

  2. 02

    Describe the proposed household

    Use Occupant Given Name for the occupant's given name and household relationship context only where it is relevant to the property and application. Keep applicant, proposed tenant and other-occupant context distinct where that supports the household record is understandable to authorised reviewers.

  3. 03

    Make the record understandable

    An authorised colleague reviewing Occupant Given Name should be able to see what the occupant's given name and household relationship context means and how it relates to the household record is understandable to authorised reviewers without rebuilding the story from another system.

  4. 04

    Review occupancy context

    For Occupant Given Name, make sure the occupant's given name and household relationship context gives the tenancy team enough context for the household record is understandable to authorised reviewers without collecting household detail that the workflow does not need.

  5. 05

    Hand off deliberately

    If Occupant Given Name reaches its intended outcome — the household record is understandable to authorised reviewers — carry forward the applicant and property context needed by the next authorised stage instead of copying the whole application into another uncontrolled record.

Core capability

What Occupant Given Name helps the team control

Connected applicant context

Occupant Given Name keeps the occupant's given name and household relationship context attached to the applicant and property context in which it is needed.

Structured information

Instead of leaving the occupant's given name and household relationship context in free-form messages, Occupant Given Name gives it a repeatable structure that supports record the given name of an additional occupant as part of the household information.

Household clarity

Occupant Given Name structures the occupant's given name and household relationship context so the applicant can be distinguished from other proposed occupants where that distinction matters to the household record is understandable to authorised reviewers.

Workflow continuity

Occupant Given Name can carry the context needed for the household record is understandable to authorised reviewers into the next authorised stage without asking for the same facts again.

Real-world workflow

What Occupant Given Name looks like in practice

Consider a case where the application identifies another person expected to live at the property. The applicant or authorised team member uses Occupant Given Name from the relevant property or application context, so the occupant's given name and household relationship 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 household record is understandable to authorised reviewers into the next authorised stage.

Implementation standard

How to introduce Occupant Given Name into a live applicant workflow

For Occupant Given Name, implementation should keep information proportionate to its purpose, clearly owned and dependable through corrections, exceptions and handoffs.

Give Occupant Given Name a clear owner before rollout. Decide who is responsible for the occupant's given name and household relationship context, which values are applicant-supplied and which authorised staff may amend or review them.

Keep Occupant Given Name proportionate to record the given name of an additional occupant as part of the household information. 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 uses it

Who works with Occupant Given Name before a tenancy is created

Occupant Given Name supports the authorised people who provide, organise, review or progress this part of the applicant journey.

Applicants and renters
Lettings teams
Property managers
Authorised reviewers
Operational considerations

Keep Occupant Given Name data, decisions and permissions aligned

Occupant Given Name can involve personal or financial information. Apply least-privilege access, privacy notices, retention rules and lawful data handling to the occupant's given name and household relationship context.

A structured record improves consistency but does not verify the occupant's given name and household relationship context automatically; authorised users should correct material errors before relying on it.

Any decision informed by Occupant Given Name should remain fair, explainable and limited to the legitimate purpose of record the given name of an additional occupant as part of the household information, while preserving the same applicant and property identity across handoff.

Connected Proplix capabilities

Related features in Applicants, Renters & Pre-Tenancy

These pages sit close to Occupant Given Name in the wider application and pre-tenancy architecture.

Frequently asked questions

Questions about Occupant Given Name

What is Occupant Given Name used for in Proplix?

Occupant Given Name is an Applicants, Renters & Pre-Tenancy capability for record the given name of an additional occupant as part of the household information. It keeps the occupant's given name and household relationship context connected to the relevant applicant and property journey.

When is Occupant Given Name most useful?

Occupant Given Name is most useful when the application identifies another person expected to live at the property. In that situation, the intended operational result is the household record is understandable to authorised reviewers.

Who should be able to access Occupant Given Name?

Access to Occupant Given Name should be limited to applicants and authorised staff who genuinely need the occupant's given name and household relationship context for record the given name of an additional occupant as part of the household information, according to your organisation's permissions and data-handling policy.

How does Occupant Given Name connect to tenant onboarding?

If Occupant Given Name is authorised to progress, the applicant and property context needed for the household record is understandable to authorised reviewers can support a controlled handoff into the separate tenancy-onboarding workflow. Capturing the occupant's given name and household relationship context does not by itself create tenancy approval or a contract.

See it in context

Explore how Occupant Given Name fits your applicant journey

See Occupant Given Name 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.

Book a Proplix walkthrough →

Working with the capability

How Occupant Given Name fits into dependable property operations

A credible workflow connects everyday actions with the records and responsibility needed to explain the outcome later. 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.

01 · People and permissions

Give each role enough context to act

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 Occupant Given Name, that means access should follow an evidenced business need and change when responsibility changes.

02 · Handover and evidence

Keep the reason beside the action

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 Occupant Given Name record more useful during absence, escalation, service review or a later audit.

03 · Exceptions

Design for the case that does not fit

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.

04 · Implementation

Configure from representative work

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.

05 · Review

Measure whether the work is improving

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 Occupant Given Name work, because a dashboard may not reveal the manual workaround being used beside it.

06 · Ongoing control

Keep guidance, permissions and records current

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 Occupant Given Name requirements →

Plan your next step

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

See what a more connected property day looks like

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.

UK Property software
by Britixo
Proplix · One Britixo account One account for Proplix and Britixo services Use your Britixo account to manage your companies, services, billing and support. Product access depends on your approved services. Try Proplix free for 14 days · No billing details required · No obligation · Secure email and WhatsApp activation.
Secure and controlled Built for property teams Requirements-led setup
WhatsApp