What Pets Allowed does in Proplix
Pets Allowed is part of Proplix Applicants, Renters & Pre-Tenancy and is designed to record the pet-permission state relevant to the property or application. It keeps permission state and any related conditions against the applicant and property context that gives it meaning.
Within the wider Pets & Preferences workflow, Pets Allowed supports pet information and property-related conditions that can be considered before the application progresses and should lead towards applicant and property expectations are aligned earlier without rebuilding the same information from public forms, inboxes or spreadsheets.
Why this capability matters before tenancy onboarding
Pets Allowed matters because a pet has been declared and the property policy or decision needs to be understood. If permission state and any related conditions is scattered across separate records, the next colleague may have to work out which applicant, property and version is current before acting.
A structured Pets Allowed record supports applicant and property expectations are aligned earlier while reducing the risk that the applicant's expectations and the property's pet conditions diverge because the declaration or restriction is not visible early enough and keeping human review, privacy controls and the organisation's fair decision process intact.
Where Pets Allowed adds operational value
For Pets Allowed, this section focuses on record the pet-permission state relevant to the property or application while keeping the applicant and property context visible.
The point in the journey
A pet has been declared and the property policy or decision needs to be understood. Pets Allowed gives that moment a defined place so the applicant and property relationship does not get lost.
The outcome to protect
Applicant and property expectations are aligned earlier. Keep permission state and any related conditions connected to the application so the authorised next action is clear without reconstructing the record from separate sources.
How Pets Allowed fits into the workflow
The exact screen and permission path for Pets Allowed depends on the user's role, but the applicant, property and application context should remain connected throughout.
- 01
Open the right applicant context
Pets Allowed should begin from the applicant, property or application record involved when a pet has been declared and the property policy or decision needs to be understood. Starting there keeps permission state and any related conditions anchored to the correct pre-tenancy journey.
- 02
Record the property-specific declaration
Capture permission state and any related conditions through Pets Allowed against the relevant property and application. That keeps the declaration connected to the conditions that matter for applicant and property expectations are aligned earlier.
- 03
Make the record understandable
An authorised colleague reviewing Pets Allowed should be able to see what permission state and any related conditions means and how it relates to applicant and property expectations are aligned earlier without rebuilding the story from another system.
- 04
Review the property conditions
When Pets Allowed is reviewed, compare permission state and any related conditions with the relevant property policy or approval conditions. The record supports applicant and property expectations are aligned earlier but does not make a legal or suitability decision automatically.
- 05
Hand off deliberately
If Pets Allowed reaches its intended outcome — applicant and property expectations are aligned earlier — carry forward the applicant and property context needed by the next authorised stage instead of copying the whole application into another uncontrolled record.
What Pets Allowed helps the team control
Connected applicant context
Pets Allowed keeps permission state and any related conditions attached to the applicant and property context in which it is needed.
Structured information
Instead of leaving permission state and any related conditions in free-form messages, Pets Allowed gives it a repeatable structure that supports record the pet-permission state relevant to the property or application.
Property-specific conditions
Pets Allowed keeps permission state and any related conditions attached to the property and application that give it meaning instead of turning the declaration into a generic assumption about the renter.
Workflow continuity
Pets Allowed can carry the context needed for applicant and property expectations are aligned earlier into the next authorised stage without asking for the same facts again.
What Pets Allowed looks like in practice
Consider a case where a pet has been declared and the property policy or decision needs to be understood. The applicant or authorised team member uses Pets Allowed from the relevant property or application context, so permission state and any related conditions 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 applicant and property expectations are aligned earlier into the next authorised stage.
How to introduce Pets Allowed into a live applicant workflow
For Pets Allowed, implementation should keep information proportionate to its purpose, clearly owned and dependable through corrections, exceptions and handoffs.
Give Pets Allowed a clear owner before rollout. Decide who is responsible for permission state and any related conditions, which values are applicant-supplied and which authorised staff may amend or review them.
Keep Pets Allowed proportionate to record the pet-permission state relevant to the property or application. 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 Pets Allowed before a tenancy is created
Pets Allowed supports the authorised people who provide, organise, review or progress this part of the applicant journey.
Keep Pets Allowed data, decisions and permissions aligned
Pets Allowed can involve personal or financial information. Apply least-privilege access, privacy notices, retention rules and lawful data handling to permission state and any related conditions.
A structured record improves consistency but does not verify permission state and any related conditions automatically; authorised users should correct material errors before relying on it.
Any decision informed by Pets Allowed should remain fair, explainable and limited to the legitimate purpose of record the pet-permission state relevant to the property or application, while preserving the same applicant and property identity across handoff.
Related features in Applicants, Renters & Pre-Tenancy
These pages sit close to Pets Allowed 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 Pets Allowed
What is Pets Allowed used for in Proplix?
Pets Allowed is an Applicants, Renters & Pre-Tenancy capability for record the pet-permission state relevant to the property or application. It keeps permission state and any related conditions connected to the relevant applicant and property journey.
When is Pets Allowed most useful?
Pets Allowed is most useful when a pet has been declared and the property policy or decision needs to be understood. In that situation, the intended operational result is applicant and property expectations are aligned earlier.
Who should be able to access Pets Allowed?
Access to Pets Allowed should be limited to applicants and authorised staff who genuinely need permission state and any related conditions for record the pet-permission state relevant to the property or application, according to your organisation's permissions and data-handling policy.
How does Pets Allowed connect to tenant onboarding?
If Pets Allowed is authorised to progress, the applicant and property context needed for applicant and property expectations are aligned earlier can support a controlled handoff into the separate tenancy-onboarding workflow. Capturing permission state and any related conditions does not by itself create tenancy approval or a contract.
Explore how Pets Allowed fits your applicant journey
See Pets Allowed 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.