Plan acceptance testing with the responsible parties

What you should be able to do

Prepare an acceptance-test coordination plan that identifies the scope, responsible people, prerequisites, evidence and closeout process. This is a planning exercise, not a procedure for activating a system or impairing protection.

Why People And Documents Must Match

A fire-alarm system can interact with monitoring, sprinklers, doors, elevators, mechanical systems and emergency communications. The fire-alarm technician may be able to verify an interface command while a specialist is needed to verify the connected system's actual action. A calendar invitation alone does not establish that the required people, equipment and evidence will be available.

Begin with the approved scope, drawings, device list, cause-and-effect matrix, manufacturer instructions and applicable acceptance requirements. Establish the exact revision being tested. Identify what is new, what is modified and which connected functions require coordination. Document exclusions and obtain the responsible decision about them rather than silently omitting difficult items.

Sources

The Coordination Map

Owner or designated site representative: coordinate access, occupancy impacts, operational constraints and site contacts. Identify who is authorized to make site decisions. The owner representative is not automatically qualified to test every technical interface.

Fire-alarm lead: coordinate the defined test scope, qualified personnel, current documents, required equipment and result records. Confirm readiness and unresolved deficiencies before requesting the required inspection or witnessing.

Interface specialists: identify the appropriate parties for each connected function. Examples may include elevator, sprinkler, mechanical, door-control or monitoring specialists, depending on scope. Document where one party's responsibility ends and another's begins.

Reviewing authority and required witnesses: confirm the applicable notification, scheduling, witnessing and acceptance arrangements. A witness requirement must come from the project and applicable authority, not from a generic poster. Identify any designer, manufacturer representative or other required participant separately.

Define A Work Package

For each planned group of checks, identify:

• The system, points and functions within scope.
• The approved drawing and sequence references.
• The responsible test lead and required specialist or witness.
• Prerequisites, access and required equipment.
• Expected results and where observations will be recorded.
• Site-impact coordination and required protective arrangements.
• Restoration responsibility and closeout evidence.
• Open issues and who resolves them.

Do not treat an output command as proof that a connected device performed its required function. The plan should say what evidence demonstrates the required result, who obtains it and how it is associated with the tested condition.

Original Planning Exercise

A fictional project groups its coordination work into four packages:

1. Initiating-point identity and annunciation.
2. Notification performance.
3. Connected-system interfaces.
4. Signal reporting and closeout.

For this desk exercise, each package needs three planning entries: a named responsible lead, a prerequisite record and an evidence-record reference. The deliberately simplified checklist is not the full testing scope.

Worked through

Required entries: 4 packages × 3 entries = 12. Confirmed entries: A has 3, B has 3, C has 2, D has 2. Total confirmed: 3 + 3 + 2 + 2 = 10. Unresolved entries: 12 − 10 = 2.

Suppose C lacks the interface specialist's readiness confirmation and D lacks an agreed evidence-record reference. Record both gaps explicitly. A statement that the plan is “mostly complete” does not resolve them. The exercise counts planning entries, not tested devices or accepted systems.

Prerequisites Before The Appointment

Confirm required installation completion and pretest records, approved documents, device inventories and access arrangements. Identify outstanding deficiencies and how they affect readiness. Confirm whether the required inspection or witness appointment has actually been accepted, rather than assuming a request is a booking.

A pretest record should describe what was performed and any exceptions. It should not claim that an authority witnessed work that the authority did not attend. Similarly, a plan should not mark future observations as passed. Keep planned, performed, corrected, retested and accepted statuses distinct.

Coordinate Impacts

Identify required contacts for occupants, site management, monitoring and affected services. Assign who provides notices and records acknowledgments under the approved process. A sent message is not necessarily confirmation that the intended party received and acted on it.

Any impairment or temporary protective arrangement must follow the applicable authorized process. Do not assume that placing a monitoring account on test, silencing notification or disabling an output are interchangeable actions. This planning lesson authorizes none of them. Lesson 402 addresses impairment coordination in more detail.

Agree in advance how the team handles an unexpected actual alarm, loss of communications, unsafe condition or unplanned equipment response. The site emergency procedure remains controlling; participants must not dismiss a real event simply because testing was scheduled.

Plan Restoration Before Starting

Name the party responsible for verifying normal service and documenting all affected functions after the authorized work. Include required communication with the site and monitoring contacts, records of unresolved conditions, corrective actions and any follow-up testing. Do not assume the task ends when the last test signal is generated.

A normal panel display alone does not show that every external system, reporting arrangement or temporary measure has returned to its required condition. Restoration evidence should match the scope actually affected.

Check Your Understanding

Sources

Where beginners go wrong