Introduction – The Building Has Changed. Has the Fire Alarm System?
A warehouse has been divided into new storage bays. Office partitions now run along one wall, and production equipment has moved to the far end. The contractors have left. The existing Edwards EST fire alarm configuration and detector layout, however, still reflect the previous arrangement.

That mismatch creates a verification requirement. A system designed and commissioned correctly for the original building may no longer deliver its intended performance once partitions, device positions, interfaces or operating conditions change. A panel showing normal status confirms communication, not continued suitability.
This does not mean every modification makes a system non-compliant. Many changes have limited impact. The impact must be assessed, documented and, where affected, revalidated.
A building modification is not complete from a fire safety perspective until the affected fire alarm functions have been assessed and appropriately revalidated.
After a building modification, review and verify detector locations and coverage, device addresses and descriptions, alarm zones and sequences, notification appliances, input/output interfaces, wiring and circuit integrity, and drawings and configuration records. Confirm that devices operate and that their positions and logic still suit the revised building. The extent of testing depends on the scope of the modification, the approved design, applicable standards and the authority having jurisdiction. Partial testing is acceptable only where a documented impact assessment supports it.
Why Building Modifications Can Affect an Existing EST Fire Alarm System
Detector layout, zoning and alarm strategy rest on assumptions about the building. These changes can invalidate them:
- New or removed partitions, which alter airflow and smoke paths.
- Changed ceiling height, new suspended ceilings or concealed spaces.
- Relocated machinery and storage racks.
- Changed room use or occupancy.
- New electrical and mechanical equipment, including heat or dust sources.
- Extensions and additional floors.
- Altered escape routes and evacuation arrangements.
Each can affect detector suitability, zone boundaries, notification coverage or cause-and-effect logic. Reassess the design basis against the building as it now exists, not as it was drawn.
What Must Be Revalidated After Building Modifications?
| System element | What must be reviewed | What should be verified |
|---|---|---|
| Smoke detectors | Position, spacing, obstructions, environment | Suitability and coverage under revised layout |
| Heat detectors | Location and application | Continued suitability for changed conditions |
| Manual call points | Accessibility, escape route relationship | Correct location and identification |
| Device addresses | Changes from additions or replacements | Correct device identification |
| Device descriptions | Building, floor, room and area labels | Consistency with approved drawings |
| Alarm zones | Revised layout and operational areas | Correct zone identification and indication |
| Notification appliances | New partitions, occupancy, acoustics | Intended audible and visual coverage |
| Input/output modules | Modified connected equipment | Correct input monitoring and output operation |
| Interfaces | BMS, smoke control, access control, lifts | Required signal transmission and response |
| Wiring and circuits | New routes, joints, extensions | Correct installation and circuit integrity |
Not every item needs identical testing on every project. Define scope through a documented impact assessment against applicable requirements. In practice, physical checks (position, obstruction, labelling) come first, functional checks (alarm, fault, output) follow, and interface checks need the system owner’s involvement.
Detector Relocation and Coverage Reassessment
A detector moved a short distance can still change performance. Review new room geometry, partition height and arrangement, ceiling obstructions, HVAC air movement, equipment heat or dust sources, changed storage configuration and any concealed or newly created spaces.
Verifying that a relocated detector communicates with the panel is not the same as verifying that its location suits the revised detection strategy. Communication proves addressability. Suitability requires design review.
Hypothetical example: During an office fit-out, a ceiling detector is moved to clear new lighting. The panel shows it is normal, and a functional test passes. But a new full-height partition now separates it from the occupied area it was meant to cover. The device works; the design intent is no longer met.
This article sets no spacing or placement values. Use applicable codes, approved design documents, manufacturer instructions and qualified design review. For Edwards SIGA smoke and heat detectors, follow the relevant installation documentation.
Reviewing EST Programming, Device Identification and Cause-and-Effect Logic
Physical changes often require configuration changes. Review:
- Newly added or removed devices
- Address and description changes
- Revised alarm zone mapping
- Input/output module changes
- Updated cause-and-effect relationships
- Alarm routing or supervisory arrangements
- Control sequences for interfaced systems
Verify the actual system response against the approved cause-and-effect matrix, not against the old configuration. EST3 and EST4 are product families. Follow the applicable manufacturer documentation for configuration procedures, using authorised personnel and tools.
Testing Notification Appliances and Building Interfaces
Detector tests do not prove the modified system works.
Notification appliances: Check audible and visual notification in modified rooms, the effect of new partitions and acoustic obstructions, and changed occupancy or evacuation arrangements.
Building interfaces (project-dependent): BMS signals, smoke control, HVAC shutdown, access control release, lift fire response, and PAVA or emergency communication where applicable. Where these use monitor or relay modules, verify the module function too.
Verify the end-to-end signal path: initiating device, panel, module, third-party system and final action. Coordinate with system owners and test under an approved test plan.
A Practical Revalidation Workflow for EST Systems
- Review the building modification: Identify changes to building, equipment, occupancy and layout.
- Perform a fire alarm impact assessment: Identify affected devices, zones, circuits, interfaces and sequences.
- Compare documentation: Review approved drawings, device schedules, cause-and-effect matrices and configuration records.
- Define the testing scope: Decide what needs inspection, testing or broader revalidation.
- Verify field installation: Check positions, identification, wiring changes, accessibility and installation quality.
- Test affected devices and functions: Verify operation, panel indication, notification and interface responses.
- Perform integrated testing where required: Confirm affected sequences work across interconnected systems.
- Close documentation and handover: Record results, discrepancies, approvals, revisions and open actions.
Competent, authorised personnel must plan and carry out testing under applicable project requirements and procedures.
When Is Partial Testing Enough, and When Is Broader Revalidation Needed?
| Modification type | Potential impact | Suggested assessment |
|---|---|---|
| Minor non-structural room changes | Local detector or notification impact | Assess affected area and functions |
| Detector relocation | Coverage and device identification | Review design; test device and functions |
| New partitions or ceiling changes | Detection and notification coverage | Reassess affected spaces |
| New building extension | Added devices, circuits, zones, interfaces | Wider system and integration assessment |
| Panel or network configuration changes | Communication and system logic | Configuration review and functional testing |
| Smoke control or access control changes | Cause-and-effect and interface behaviour | Coordinated integrated testing |
This is an illustrative planning framework, not a substitute for project-specific engineering assessment or statutory requirements.
Common Mistakes During Post-Modification Fire Alarm Testing
| Mistake | Corrective action |
|---|---|
| Testing only new detectors | Assess surrounding areas and connected functions |
| Ignoring new partitions | Reassess coverage in affected spaces |
| Skipping notification review | Check audible and visual coverage in modified areas |
| Leaving old panel descriptions | Update labels to match drawings and room names |
| Not updating the cause-and-effect matrix | Revise, approve and test against it |
| Ignoring BMS or smoke control interfaces | Test with the system owners |
| Testing devices without the full signal path | Verify end-to-end to the final action |
| Not updating as-built drawings | Issue revised drawings before handover |
| Closing without test evidence | Record results and approvals |
Post-Modification EST Testing and Documentation Checklist
- Building modifications reviewed and recorded.
- Fire alarm impact assessment completed.
- Existing and revised drawings compared.
- Detector locations and coverage reassessed.
- Manual call point locations reviewed where affected.
- Device addresses and descriptions verified.
- Alarm zones reviewed.
- Notification appliance coverage assessed.
- Modified circuits and wiring inspected.
- Relevant input/output modules verified.
- Cause-and-effect matrix reviewed.
- Affected interfaces tested.
- Integrated testing completed where required.
- Deficiencies recorded and closed.
- Configuration and drawings updated.
- Test results and approvals included in handover records.
Key Takeaways
- Assess impact before deciding test scope.
- Normal panel status does not prove continued suitability.
- Device operation and design suitability are separate questions.
- Partitions and ceiling changes can affect detection and notification.
- Review configuration and the cause-and-effect matrix, not just hardware.
- Test complete signal paths, including interfaces.
- Keep scope proportionate, but document the reasoning.
- Update drawings, descriptions and records.
- Retain test evidence for handover.
Read Also: Fire Alarm Device Naming Standards: Why Consistent Labels Matter Across Large EST Networks
Read Also: The ELV As-Built Gap: Why Approved Drawings Can Differ from the Installed Infrastructure









