NICET certified professionals fill essential, hands-on roles across fire protection, transportation, construction inspection, and other engineering technology disciplines. Just as important as that day-to-day work is their formal place on the Qualified Engineering Team, the group of licensed engineers, certified technicians, and technologists jointly responsible for the design, oversight, and delivery of a project.
That relationship anchored a session at NSPECon26, NSPE's annual national conference, led by Dr. Paul D. Flannigan, EdD, SET, CFPS, CWBSP, Chair of the NICET Board of Governors; John Denhardt, PE, FSPE, vice president of engineering and technical serve at the American Fire Sprinkler Association (AFSA); and Melinda Sprow, a civil engineer for the City of Defiance, Ohio.
The presenters built the session around audience participation, prompting attendees to weigh in on how their own firms define and support the engineering team. The conversational format let PEs and certificants compare notes directly on where responsibilities are clearly drawn and where they tend to blur in practice.
NICET has certified engineering technicians and technologists since 1961, when NSPE established the institute specifically to formalize technicians' standing as an integral part of the engineering team. Since then, NICET has certified more than 135,000 individuals across more than a dozen technical disciplines, with certification progressing through up to four levels, from entry-level (Level I) to senior (Level IV).
The presenters framed this certification structure as the technician-side counterpart to PE licensure: each credential exists to give the public, employers, and regulators a consistent way to verify competence, and each carries its own obligations to uphold that trust.
The session walked through how a well-functioning engineering team distributes work and accountability:
Structure and communication between these roles were discussed as deliberate design choices, not defaults, including how reporting lines, sign-off procedures, and documentation practices are set up to keep both parties accountable. Procedures for escalation and review were presented as the mechanism that catches problems before they become project or ethical failures.
The presenters grounded the discussion in the frameworks that actually govern these roles, rather than treating "teamwork" as an abstraction:
The session tied all of this back to project performance: teams with clear roles, open communication, and adherence to these regulatory and ethical frameworks are the ones that stay aligned with client expectations, meet professional obligations, and avoid the legal and ethical exposure that comes from ambiguous accountability. Attendees discussed how the interaction between PEs and certified technicians, not just their individual competence, is what produces informed, defensible engineering work.
Congratulations to the presentation team on a well-received session.