What Address History Table does in Proplix
Address History Table is part of Proplix Applicants, Renters & Pre-Tenancy and is designed to present an applicant's recorded addresses in an ordered review view. It keeps address sequence, residence periods and the existing recorded entries against the applicant and property context that gives it meaning.
Within the wider Address History workflow, Address History Table supports structured residential history that can be reviewed chronologically rather than reconstructed from free text and should lead towards gaps, overlaps or corrections are easier to identify without rebuilding the same information from public forms, inboxes or spreadsheets.
Why this capability matters before tenancy onboarding
Address History Table matters because staff or the applicant needs to review several address periods together. If address sequence, residence periods and the existing recorded entries is scattered across separate records, the next colleague may have to work out which applicant, property and version is current before acting.
A structured Address History Table record supports gaps, overlaps or corrections are easier to identify while reducing the risk that address periods are incomplete, duplicated or difficult to compare because dates and residences are recorded inconsistently and keeping human review, privacy controls and the organisation's fair decision process intact.
Where Address History Table adds operational value
For Address History Table, this section focuses on present an applicant's recorded addresses in an ordered review view while keeping the applicant and property context visible.
The point in the journey
Staff or the applicant needs to review several address periods together. Address History Table gives that moment a defined place so the applicant and property relationship does not get lost.
The outcome to protect
Gaps, overlaps or corrections are easier to identify. Keep address sequence, residence periods and the existing recorded entries connected to the application so the authorised next action is clear without reconstructing the record from separate sources.
How Address History Table fits into the workflow
The exact screen and permission path for Address History Table depends on the user's role, but the applicant, property and application context should remain connected throughout.
- 01
Open the right applicant context
Address History Table should begin from the applicant, property or application record involved when staff or the applicant needs to review several address periods together. Starting there keeps address sequence, residence periods and the existing recorded entries anchored to the correct pre-tenancy journey.
- 02
Build an understandable chronology
Use Address History Table to record address sequence, residence periods and the existing recorded entries with the dates and residence sequence needed for gaps, overlaps or corrections are easier to identify. For Address History Table, the value comes from a coherent address sequence, residence periods and the existing recorded entries history rather than a loose list of addresses.
- 03
Make the record understandable
An authorised colleague reviewing Address History Table should be able to see what address sequence, residence periods and the existing recorded entries means and how it relates to gaps, overlaps or corrections are easier to identify without rebuilding the story from another system.
- 04
Check gaps and corrections
Before relying on Address History Table, review address sequence, residence periods and the existing recorded entries for gaps, overlaps or mistakes that could obscure gaps, overlaps or corrections are easier to identify. When Address History Table facts change, amend the existing address sequence, residence periods and the existing recorded entries entry so the chronology needed for gaps, overlaps or corrections are easier to identify stays coherent.
- 05
Hand off deliberately
If Address History Table reaches its intended outcome — gaps, overlaps or corrections are easier to identify — carry forward the applicant and property context needed by the next authorised stage instead of copying the whole application into another uncontrolled record.
What Address History Table helps the team control
Connected applicant context
Address History Table keeps address sequence, residence periods and the existing recorded entries attached to the applicant and property context in which it is needed.
Structured information
Instead of leaving address sequence, residence periods and the existing recorded entries in free-form messages, Address History Table gives it a repeatable structure that supports present an applicant's recorded addresses in an ordered review view.
Chronological review
Address History Table keeps address sequence, residence periods and the existing recorded entries in an understandable sequence, making the gaps or corrections that matter to gaps, overlaps or corrections are easier to identify easier to identify.
Workflow continuity
Address History Table can carry the context needed for gaps, overlaps or corrections are easier to identify into the next authorised stage without asking for the same facts again.
What Address History Table looks like in practice
Consider a case where staff or the applicant needs to review several address periods together. The applicant or authorised team member uses Address History Table from the relevant property or application context, so address sequence, residence periods and the existing recorded entries 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 gaps, overlaps or corrections are easier to identify into the next authorised stage.
How to introduce Address History Table into a live applicant workflow
For Address History Table, implementation should keep information proportionate to its purpose, clearly owned and dependable through corrections, exceptions and handoffs.
Give Address History Table a clear owner before rollout. Decide who is responsible for address sequence, residence periods and the existing recorded entries, which values are applicant-supplied and which authorised staff may amend or review them.
Keep Address History Table proportionate to present an applicant's recorded addresses in an ordered review view. 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 Address History Table before a tenancy is created
Address History Table supports the authorised people who provide, organise, review or progress this part of the applicant journey.
Keep Address History Table data, decisions and permissions aligned
Address History Table can involve personal or financial information. Apply least-privilege access, privacy notices, retention rules and lawful data handling to address sequence, residence periods and the existing recorded entries.
A structured record improves consistency but does not verify address sequence, residence periods and the existing recorded entries automatically; authorised users should correct material errors before relying on it.
Any decision informed by Address History Table should remain fair, explainable and limited to the legitimate purpose of present an applicant's recorded addresses in an ordered review view, while preserving the same applicant and property identity across handoff.
Related features in Applicants, Renters & Pre-Tenancy
These pages sit close to Address History Table 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 Address History Table
What is Address History Table used for in Proplix?
Address History Table is an Applicants, Renters & Pre-Tenancy capability for present an applicant's recorded addresses in an ordered review view. It keeps address sequence, residence periods and the existing recorded entries connected to the relevant applicant and property journey.
When is Address History Table most useful?
Address History Table is most useful when staff or the applicant needs to review several address periods together. In that situation, the intended operational result is gaps, overlaps or corrections are easier to identify.
Who should be able to access Address History Table?
Access to Address History Table should be limited to applicants and authorised staff who genuinely need address sequence, residence periods and the existing recorded entries for present an applicant's recorded addresses in an ordered review view, according to your organisation's permissions and data-handling policy.
How does Address History Table connect to tenant onboarding?
If Address History Table is authorised to progress, the applicant and property context needed for gaps, overlaps or corrections are easier to identify can support a controlled handoff into the separate tenancy-onboarding workflow. Capturing address sequence, residence periods and the existing recorded entries does not by itself create tenancy approval or a contract.
Explore how Address History Table fits your applicant journey
See Address History Table 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.