From paper binders to one exportable audit pack

Before F2 Core, SPCC documentation lived in three places at every rooftop: a paper binder at the service drive, a folder on the service manager's laptop, and a copy with the environmental consultant. When an inspector showed up, or when corporate asked for a portfolio view, two things happened: a service manager spent half a day rebuilding the binder, and the regional EHS lead spent the rest of the week reconciling 14 rooftops worth of inconsistent inputs.

Tank inventory was the biggest single gap. New tanks were installed on a Friday and nobody told the consultant until the next audit cycle. Labels faded. Containment notes lived in the head of one veteran technician.

F2 Core's Environmental lane modeled every rooftop's tanks, labels, containment areas, and inspection schedule on one operating record. Each tank was given a QR code that linked back to its record. Inspections were captured during the workflow, not after.

Three operating principles did most of the work. One event creates one ticket meant a new tank install became a ticket with proof attached. Published configurations are immutable meant the SPCC version in force at the time of an inspection stayed attached to that inspection forever. AP closeout is a gate meant vendor-supplied documents were a prerequisite to closing the event — not an optional follow-up.

The Audit Pack Builder bundles SPCC inventory, labels, containment calculations, integrity schedules, inspections, training certificates, proof packages, manifests, and financial history into one exportable pack per rooftop or for the whole group.

• SPCC audit preparation time: 5 days → ~4 hours per rooftop
• Missing tank records at audit time: typical 2–3 per rooftop → 0
• Time to produce a group-wide SPCC export: typical 1–2 weeks → same business day

“The first time an inspector walked in after rollout, my service manager hit one button. That was the moment the team trusted the platform.”