15.1 Coordinate Work Activities

15.1 Coordinate Work Activities

Quick Answer: Domain 2.4.1 (Management and supervision, roughly 5–15% of FAS Level II) expects you to coordinate work—especially another individual—under limited supervision. Assign tasks inside each person’s competence, sequence multi-person installs so pathways precede devices and programming, communicate clearly with the GC/superintendent, respect material lead times, and route design or scope changes through a documented change-order / RFI process rather than silent field improvisation.

Technical chapters teach what to install and test. This chapter teaches how Level II runs the work when more than one set of hands is involved. NICET performance-measure families for the Fire Alarm Systems path explicitly include coordinating another individual. On the exam, stems often look like jobsite stories: a helper, a tight schedule, a missing part, and a superintendent asking for shortcuts. The correct answer almost always protects competence, documentation, and life-safety sequence—not pure speed.

What “Coordinate Another Individual” Means at Level II

At Level II you are not the project manager of record and not the design engineer. You are the associate technician who can keep a helper, apprentice, or second tech productive and correct while you remain responsible for quality.

Coordination includes:

1. Defining the task — clear scope, location, drawings/sheet references, and stop points.
2. Matching task to competence — training, experience, and site authorization for the work (for example, who may work from a lift, land in a live FACU, or enter an elevator machine room).
3. Providing tools and materials — listed products, correct cable, labels, and the right cut sheets.
4. Checking quality — inspect terminations, heights, addresses, firestopping, and paperwork; do not “trust and forget.”
5. Owning the outcome — if the helper’s work fails inspection, the coordinating tech still owns the correction path.

Trap: “Coordinate” does not mean dump the hardest, least supervised work on the least experienced person so the lead can chase another job.

Assigning Within Competence

Competence is a combination of skill, authorization, and condition of the job:

• Skill — Can they terminate shielded cable, set EOL devices, use a multimeter, or follow a point schedule without inventing addresses?
• Authorization — Site badge levels, hot-work permits, lift cards, LOTO training, manufacturer programming access.
• Condition — Occupied hospital after hours differs from an empty shell; the same person may be competent for one and not the other without extra controls.

Practical assignment pattern

1. Explain the “why” briefly — “These speakers must stay on NAC-2 as scheduled so the candela/load calc still holds.”
2. Show one correct example — first device or first splice done together.
3. Set inspection checkpoints — “Call me before you close the ceiling above Stair 2.”
4. Limit decision rights — “If the box is more than 6 inches off the mark or the ceiling type changed, stop and get me—do not freestyle.”
5. Close the loop — visual/functional check before the area is signed off as complete.

If the only available person cannot perform the task safely and correctly, slow the work or request more qualified labor. Schedule pressure is not a competence upgrade.

Sequencing Multi-Person Installs

When two or more people work a fire alarm install, poor sequencing creates rework and unsafe temporary conditions. Align crew tasks with the same order taught in installation planning:

Recommended multi-person sequence

Scenario: Two techs hang all corridor speakers on Day 1 for “progress photos,” then discover the NAC conduit was never sleeved through a rated wall. Speakers come down, drywall is damaged, and the superintendent blames fire alarm. A coordinated plan would have finished rated pathways and rough-in before finish devices in that corridor.

Avoid parallel work that collides

• Do not program addresses while another person is still swapping device types on the same loop without a communication protocol.
• Do not run 100% notification testing while someone else is opening SLC junctions in the same zone.
• Do not let one person “borrow” scheduled devices from another floor’s staged kit without updating the material plan.

Communicating with the GC and Superintendents

General contractors and superintendents optimize the whole building schedule. Fire alarm is often late in the critical path and easy to squeeze. Level II coordination language should be specific, document-based, and life-safety aware.

What to bring to coordination meetings

• Current approved drawing sheets and revision numbers
• A short area plan for the week (floors/wings, night work, lift needs)
• Multi-trade windows needed (elevator tech, sprinkler fitter for flow tests, HVAC for duct detectors)
• Impairment implications if occupied areas will lose detection or notification
• Material constraints (long-lead FACU, specialty speakers, fiber, cellular communicator)

Communication habits that score on exams and jobs

Trap: Agreeing to “just move the smoke detectors over so drywall can finish” without checking spacing, listing, and design approval. Coordination is not surrender of life-safety geometry.

Material Lead Times and Staging

Fire alarm materials are often listed, manufacturer-specific, and not freely substitutable. Coordination includes logistics:

• Identify long-lead items early: FACUs, voice panels, specialty high-candela appliances, beam detectors, fiber modules, releasing equipment, network cards.
• Stage by area and circuit, not random open boxes.
• Protect devices from construction dust and paint until the area is ready.
• Track serial numbers/software media for panels that must match the approved submittal.
• Flag partial shipments so the crew is not stranded mid-loop.

When a part is late, options are: reschedule the affected area, use an approved substitute through the submittal/change process, or idle rather than install unlisted/unapproved product. “The supply house had something close” is not Level II coordination.

Change Orders and Field Process

A change order (or contract change) adjusts scope, cost, or time when work differs from the contract documents. Level II techs rarely write the commercial change order, but they initiate the field evidence that makes one accurate—or prevent illegal silent changes.

Field process (typical)

1. Recognize a change — extra devices after a remodel, different ceiling type requiring different mounting, owner-requested adds, design errors, differing site conditions.
2. Stop when the approved design cannot be followed — do not install the “obvious” fix if coverage, listing, or sequence of operation is affected.
3. Document — photos, markups, measurements, sheet/detail references, date, and who directed the field condition.
4. RFI / field question to design or GC as the project requires.
5. Proceed only after direction — revised drawing, ASI, approved change, or written owner/GC instruction consistent with contract rules.
6. Update as-builts and material tracking once authorized work is done.

Change orders vs ordinary as-built markups

• As-built markups capture how approved work was actually built (final device locations within design intent, actual conduit routes that still meet requirements).
• Changes alter what was required or paid for. Do not hide scope growth inside as-builts to avoid paperwork.

Daily Coordination Checklist for Level II Leads

1. Assign people by competence; state stop points.
2. Confirm materials for the day’s area are on site and listed/approved.
3. Align with GC on access, lifts, and other trades.
4. Sequence tasks so pathways and energy/impairment controls precede finish and testing.
5. Capture conflicts and potential changes the same day in writing.
6. Inspect helper work before ceilings close or areas are declared complete.
7. Hand off unfinished hazards (open junction boxes, impaired zones) with clear ownership.

Exam Focus

Prefer answers that assign within skill, sequence pathways before finish devices, communicate with the GC using documents, respect lead times and listings, and route scope changes through formal change/RFI processes. Reject answers that abandon supervision, install unapproved substitutes, or treat “the super said so” as automatic design authority without documentation.