In operational terms, here is what the regulatory landscape says about the vendors walking through your building this week: the refrigeration tech needs a federal certification that never expires but must be the right type for the equipment. The elevator mechanic needs a state license that expires on a state-specific cycle with continuing-education strings attached. The general contractor needs a state license whose classification must match the scope of the job, plus insurance that expires annually regardless.

Three credentials, three issuing authorities, three renewal logics, three failure modes — and one party who carries the exposure when any of them lapses: you.

Most operations file all three under one mental category, “vendor paperwork.” The standards don’t. Reading each regime for what it actually requires shows why a single folder — or a single assumption — can’t track three structurally different obligations.

Three credentials, three issuing authorities, three renewal logics, three failure modes — and one party who carries the exposure when any of them lapses: you.

Regime one: EPA Section 608 — federal, permanent, but typed

What most operations believe: the refrigeration vendor “is EPA certified.” What the regulation actually requires: Section 608 certification comes in types — Type I for small appliances, Type II for high-pressure systems (most commercial HVAC), Type III for low-pressure systems (large chillers), and Universal covering all three. A technician holding Type I is federally certified and still not qualified to open your rooftop package unit.

The certification itself doesn’t expire — which lulls operations into treating it as a one-time check — but the matching problem is permanent: every dispatch is a fresh question of whether this technician’s type covers this equipment’s class. The penalty backdrop is the steepest in the building: violations run up to $44,539 per day, per violation, and the AIM Act’s refrigerant transition is tightening scrutiny on exactly this work. “Certified” without “certified for this” is the gap.

Regime two: the elevator mechanic license — state, expiring, education-tethered

Elevator work runs on a different chassis entirely. ASME A17.1 sets the safety code, but licensing is a state function: most states require elevator mechanic licenses that expire on one-to-three-year cycles, with continuing-education requirements tied to code updates — and the 2025 edition of A17.1 makes the education requirement live, not ceremonial.

The failure mode here isn’t type-matching; it’s currency: a license that was valid at onboarding and quietly lapsed, or a mechanic licensed in the state where the vendor is headquartered but not where your building stands. Multi-state portfolios multiply the problem — the same vendor can be fully compliant at your Dallas site and unlicensed at your Denver one, performing identical work.

Regime three: the state contractor license — scoped, classified, insurance-coupled

The contractor license adds a third logic: classification. State licenses come with scope classes — electrical, mechanical, plumbing, general — and monetary thresholds; a contractor licensed for one class performing work in another is, in most states, unlicensed for that job, with consequences that can include your inability to enforce the contract. Coupled to it travels the certificate of insurance, which expires annually on its own clock and, as covered in the silent-Tuesday problem, converts every job performed in a lapse into uninsured work on your property.

Three regimes, one structural conclusion

Lay the three side by side and the tracking problem reveals its real shape. One credential never expires but must be type-matched per dispatch. One expires on state cycles and varies by jurisdiction. One is scoped per job class and coupled to an annually expiring insurance document. No folder checks type against equipment; no calendar reminder knows which state your Tuesday work order is in; no annual review catches a classification mismatch on a job dispatched in March. The three regimes demand three different checks at three different moments — and the only place all three moments exist is the dispatch event itself.

STAGE 1 Structured Vendor Records

Vendor credentials are stored as queryable data specifying type, class, jurisdiction, and expiry date rather than static PDF files.

STAGE 2 Dispatch Rules

The routing engine explicitly cross-references technician qualifications against equipment class, job scope, and site jurisdiction upon assignment.

STAGE 3 Mechanical Consequence

Any unmatched or expired credential strictly renders the vendor ineligible for the job, enforcing compliance before the truck rolls.

Which is the conclusion the title promised: the system that tracks all three isn’t a better spreadsheet — it’s credential logic embedded in the work order router. Vendor records carrying each credential as structured data (type, class, jurisdiction, expiry); dispatch rules that match technician qualification against equipment class, job scope, and site state at assignment; and the mechanical consequence that makes it real — unmatched or expired means ineligible, before the truck rolls. That’s how the vendor network inside Sweven FM treats credentials: not as paperwork on file but as routing conditions, because the three regimes only converge in one place, and that place is the moment of dispatch.

The Credential Audit

The audit takes one work order: pull last week’s refrigerant, elevator, or licensed-trade job and answer three questions an inspector would ask — was the 608 type right for that equipment, was the license current in that state, did the classification cover that scope? If answering requires a phone call, you’ve found which of the three regimes your operation is currently tracking on faith.

Sources: