Who may enter?
Users, visitor groups, zones and time profiles.
RESULT · Access and authorisation matrix
Define the function.
Make the interfaces explicit.
Planning logic for schools and comparable public buildings. From users and protection goals to operating states, system requirements and evidence.
Discuss your planning questionsSIX QUESTIONS BEFORE PRODUCT SELECTION
A structured starting point.
These questions frame a professional discussion. They do not replace a project-specific assessment or the required approvals.
Who must be able to leave?
Everyday exit, unfamiliar users and evacuation scenarios.
RESULT · Direction-specific escape requirementsWhat protection must the door provide?
Fire, smoke, escape-route and security functions; evidence for the complete assembly.
RESULT · Defined protection requirementsWhat happens after passage?
Closing, latching, re-locking and any authorised hold-open period.
RESULT · Documented operating sequenceWhere does access control act?
Cylinder, fitting, lock, strike or separate locking element; compatibility and feedback.
RESULT · Interface and responsibility scheduleWhat must remain possible during failure?
Power loss, unavailable network, depleted batteries and recovery to normal operation.
RESULT · Agreed failure and recovery conceptFOUR OPERATING SCENARIOS
Describe behaviour, not just hardware.
Consider door position, mechanical locking, access permission and escape-side operation separately in each scenario.
Define the normal position and locking condition.
A door may be closed without being deadlocked. Record closing, latching and locking separately, together with the permitted access direction.
- Door position
- Open / closed: which indication is needed?
- Latch & bolt
- What confirms engagement, if confirmation is required?
- Access
- Who may enter and how?
- Exit
- Which local opening function must remain available?
Describe the complete passage sequence.
An access-granted signal is a permission or command. It does not by itself confirm that the door opened, closed or re-locked.
- Authorisation
- Which credential or release condition applies?
- Release
- Which component changes state?
- Return
- When and how does the door close and re-lock?
- Monitoring
- Is prolonged opening detected and acted on?
Coordinate protection goals before defining commands.
Fire, smoke, evacuation and security events may require different behaviours. Resolve the project-specific sequence and priorities with the responsible planners.
- Scenario
- Which event is being considered?
- Protection
- What does the agreed fire / escape concept require?
- Interfaces
- Which local devices and building systems interact?
- Verification
- Who approves and tests the complete sequence?
Treat failure as a defined operating condition.
Evaluate power, network, server and battery failures individually. Establish what remains available locally and how normal operation is restored.
- Dependency
- What is actually lost in this failure?
- Local function
- How is the required escape function maintained?
- Operation
- Which manual or fallback procedure is available?
- Recovery
- What is checked after power or connectivity returns?
SYSTEM LAYERS & INTERFACES
One door. Several responsibilities.
Agree responsibilities explicitly for the project. The examples below identify typical coordination questions.
| Layer | Question to resolve | Planning output |
|---|---|---|
| Building & use | Who uses the opening; which zones and protection goals apply? | Door profile and operating scenarios |
| Door & hardware | How do leaf, frame, closer, fittings and lock work together? | Coordinated assembly requirements |
| Access control | Where does authorisation act, and what changes mechanically? | Release sequence and rights structure |
| Electrical & building systems | Which supply, signals and dependencies are required? | Interface and responsibility schedule |
| Operator & handover | Which states must be known, tested and documented? | Verification plan and operating information |
Monitoring follows the required information.
A door-position contact does not, by itself, prove deadbolt engagement. Specify the statement needed by the operator and identify suitable evidence for that statement.
FOUR PLANNING GATES
Make decisions in a useful order.
01
Concept
Confirm use, zones and protection goals.
02
Function
Agree operating states and failure behaviour.
03
System
Coordinate components, interfaces and equivalence criteria.
04
Evidence
Define approval, testing, handover and maintenance information.
SCHOOL EXAMPLE · NOT A PROJECT REFERENCEOne building.
One building.
Different door profiles.
- Main entrance: distinguish normal arrival, visitor access, after-hours use and evacuation.
- Classroom: coordinate everyday use, access rights and the agreed incident procedures.
- Technical room: define restricted entry, responsibilities and authorised maintenance access.
- Corridor / compartment door: coordinate passage with the applicable fire, smoke and escape requirements.
Fire- and smoke-protection requirements concern the relevant door assembly and its evidence. Electronic escape arrangements and compatibility must be assessed for the actual configuration.
YOUR FIRST STEPBring the project.
Bring the project.
We help structure the decisions.
Tell us the building’s use, your project phase and the question you need to resolve. Existing plans, a door schedule or a draft specification provide a useful starting point.
We clarify the advice needed and agree the next step with you. Project work may cover a functional concept, technical specifications, tender comparison or coordination through testing and handover.
Enquire about a consultationCONSULTATION
€150 net per consultation appointment, plus VAT
Discuss your requirements, available documents and next planning decisions. Detailed concepts, specifications and further project support are scoped and quoted separately.
Sending an enquiry does not book a paid appointment. The appointment and its terms are agreed with you beforehand.