Some property viewings need arrangements that differ from a branch's ordinary appointment procedure. A tenant may have agreed a particular access window, a communal entrance may be temporarily unavailable, or a surveyor might require permission different from that granted for an accompanied buyer viewing. These conditions become dangerous when hidden in old correspondence. A viewing access exception register brings the relevant difference to the attention of the person making a booking, without replacing the full instructions or physical key-custody records.
The Property Ombudsman's residential estate-agency Code addresses access to premises, consultation with occupiers where appropriate, secure handling of coded keys and records of issue and return for participating agencies. These requirements need to be considered in their professional and jurisdictional context. A digital appointment is not itself permission to enter, and a warning recorded by one employee does not establish that the access arrangement is legally valid. The proper register identifies what must be checked and who can confirm it.
Define an exception relative to the normal procedure
A register loses value if it repeats every standard access step for every house. The agency should already have a general booking policy, secure key procedure and normal seller or occupier instruction. An exception is a specific departure from that baseline: for example, an entrance that cannot currently be used, a required confirmation with an occupier, or a restriction on visits to one part of the property. Record only what differs and link to the controlling operational document.
Give each exception a property reference, short description, current status, originating instruction, responsible person and review trigger. Specify which stage it affects: offering an appointment, confirming it, arriving at the property, entering, showing a particular room or completing the visit. A warning saying 'access issue' is insufficient. It may cause employees to ignore the alert or cancel appointments unnecessarily because they cannot see the actual consequence.
Keep standard instructions separately. A note that everyone should lock the door after a viewing belongs in training and operating procedure; a particular door that fails to secure belongs in an exception and may require a specific escalation. The distinction protects the visibility of genuinely unusual conditions.
Confirm who supplied and authorised the condition
Exceptions may originate with a seller, occupier, building manager or an employee observing a practical problem. These sources do not all have identical authority. Preserve the original message and check its relevance to the actual instruction and circumstances. A tenant's request about an occupied home should not be dismissed as an inconvenience, and a building worker's suggestion should not become an indefinite restriction without appropriate confirmation.
If there are competing instructions, record the conflict rather than selecting whichever makes scheduling easier. Some matters require legal or professional advice; an estate agent should not assume that a marketing instruction gives unrestricted access to a tenanted property. Explain to staff what requires clarification and who may approve the proposed arrangement. A tentative request should remain pending until the agency has a sound basis to act.
Record the effective date. A note made during building works six months ago may no longer reflect the present route. Equally, a newer general note does not necessarily cancel a property-specific restriction. An evidence trail enables a colleague to distinguish a verified change from an assumption.
Connect each exception to the affected appointment decision
An exception needs to appear where the employee actually makes a relevant choice. If access requires occupier confirmation, flag that dependency before a booking is confirmed. If a route is blocked only on certain days, show the restriction when the diary displays those slots. A register located in a separate folder that nobody consults can create the illusion of control without changing behaviour.
Keep the visible message concise and safe. 'Additional occupier confirmation required before booking' may be sufficient in a general diary, with detailed instructions behind a permissioned link. Publishing private routines, key locations or alarm details in calendar text is unnecessary and risky. The system should distinguish an unconfirmed request from a final appointment and allow a human decision-maker to stop an unsafe booking.
Where several visits are pending, verify each as necessary. A permission granted for one surveyor's visit does not automatically cover a later contractor or buyer. The exception should show its scope and not turn a narrow approval into continuing authority.
Separate access exceptions from actual key custody
A note about which door to use must not be mistaken for evidence that keys are available. Physical issue, transfer and return require their own controlled register. Check the current custody status before promising a viewing. Where an unusual key release is necessary, confirm the appropriate permission, recipient and authorised duration; an exception note alone is not a substitute for these controls.
If a key is missing or an entry device malfunctions, stop relying on the original arrangement. Record the observed issue, assign an owner and determine whether appointments need to be suspended or moved. The TPO Code describes secure coded keys and separate issue/return records; these are useful professional benchmarks, but the practical response depends on the actual security and occupancy context.
Keep sensitive information separate from widely visible records. The exception can tell an employee to contact the responsible colleague, without exposing the location of a spare key or revealing when an occupied property is empty.
Give temporary restrictions an explicit review trigger
Not every condition is permanent. A damaged gate may be repaired, a lift may return to service, or an occupier may agree a different appointment window. Record when and how the restriction should be reviewed: an actual repair confirmation, revised authorisation or a scheduled human check. A review date is not permission for software to delete the exception automatically.
When a condition changes, verify the new position from an appropriate source, record the decision and update related access instructions and bookings. If the exception previously blocked appointments, ensure the diary is reconfigured only when relevant permissions are satisfied. If the reason remains unresolved, extend the exception with a documented owner rather than letting an expired timestamp imply unrestricted access.
Preserve historical status where needed for an earlier complaint or incident review. The fact that a restriction was valid on Monday and lifted on Thursday can explain different treatment of two appointments without suggesting staff acted inconsistently.
Prepare colleagues who did not create the original note
Access arrangements often fail during cover shifts, branch transfers or staff absence. The register should let an authorised replacement employee understand the current departure from normal practice and the required next action without searching an individual's messages. Include the responsible contact, the source reference and whether the exception blocks booking entirely or permits a specified alternative.
Train employees to check the actual status rather than simply acknowledge an alert. A warning dismissed with one click does not mean the occupier approved the proposed time. A good handover makes uncertainty visible and provides a route to confirmation. Review how notifications behave on mobile devices; staff working away from the office need sufficient information to recognise a genuine restriction.
Privacy is also a training issue. Colleagues should not repeat an occupier's personal reason for limited availability to prospective buyers when a neutral explanation will do. ICO data-protection guidance applies where the system handles personal information, and access permissions need to be enforced by the underlying application.
Test difficult cases before relying on automated scheduling
A useful trial should cover several realistic scenarios: an occupier changes an access window; a surveyor asks for unattended entry; a communal door is temporarily unusable; a key is out with another negotiator; and an old restriction is no longer valid but has not been formally reviewed. Ask whether the system blocks unsafe confirmation, identifies the authoritative source and directs the employee to an appropriate person.
Conventional rules in a CRM may perform these tasks more predictably than a generative assistant. AI may help summarise an approved access note or suggest which appointments might be affected, but should not invent permission or certify that an entrance is safe. Test it with conflicting messages and missing sources. Where confidence is not justified, escalation is preferable to an automatic answer.
For a purely illustrative calculation, suppose a branch spends 35 hours each month resolving unusual access arrangements. A better register saves twelve initial hours but adds five hours of checking and coordination, leaving seven possible hours before training, support and licence costs. These are hypothetical figures rather than measured industry savings.
Close only when the current working arrangements agree
Before resolving an exception, check whether the original cause has actually changed, the current instruction is confirmed and any affected diary, key or property-access record is updated. Someone should verify the result, and the history should indicate why earlier bookings were handled differently. Removing a warning because several visits happened to succeed is not reliable evidence that a restriction has disappeared.
Track meaningful outcomes: appointments confirmed with appropriate authority, avoidable access failures, repeated exceptions, unresolved ageing and security incidents. Avoid using raw alert counts as a success measure. More warnings might reflect a clearer view of risk rather than worsening practice; fewer warnings might simply mean staff have stopped recording problems.
The best register is small enough to use, specific enough to support a decision, and accountable enough to challenge. It highlights what makes one property's access different today, without turning a temporary instruction into a permanent hidden rule.
Sources: The Property Ombudsman residential estate-agent Code, March 2026, access-to-premises section (professional scheme context); TPO jurisdiction-specific current Codes; ICO organisational data-protection guidance (where the register involves personal data). These sources do not prescribe the proposed software design.
What belongs in an exception register rather than the standard access procedure?
Repeated standard steps and property-specific deviations need different governance. Showing every routine instruction as an alert makes real restrictions harder to recognise.
| Criterion | Normal operational procedure | Property-specific exception |
|---|---|---|
| Source | Agency policy and approved normal property instructions. | Specific seller, occupier or verified operational condition. |
| Visibility | Staff training, standard booking controls and reference material. | Prominent relevant warning at affected booking decision. |
| Scope | Routine permissions, security and access requirements. | Clearly limited time, place, visitor or activity affected. |
| Authority | Ordinary authorised booking process. | Named person verifies additional permission or restriction. |
| Review | Regular policy and source-record maintenance. | Explicit review trigger without automatic removal. |
| Closure | Proper completion of routine appointment and custody process. | Verified change, connected record updates and preserved history. |
Decision: Alert staff to the actual departure from standard practice, not to every ordinary procedure. Professional basis: TPO Code March 2026, access and keys; it provides relevant professional controls, not this table's specific classifications. Privacy: ICO organisational guidance, relevant to private contact/occupancy notes. This qualitative comparison is original editorial operational guidance.