The Only System That Knows BS 7671 Table 41.4 by Heart
This isn't just digital forms—it's the industry's first compliance document system that enforces BS 7671, BS 5839, and MCS standards before certificates can be issued. Auto-lookup Zs limits, validate test results, capture GPS-tagged signatures, and maintain immutable audit trails. Your engineers can't accidentally issue a non-compliant certificate.
How it works
Who it's for
- Reduce liability—certificates validated against BS 7671/BS 5839 before issue, engineers can't bypass limits
- Prove compliance—complete audit trail with GPS-tagged signatures for insurance claims and HSE investigations
- Save time—auto-populate certificates from job data, no double entry
- Track remediation—defect-to-quote pipeline ensures C1/C2 observations don't fall through cracks
- Customer acknowledgment proof—can't claim "never received cert", you have timestamp evidence
- Unified platform—CRM + Jobs + Compliance certs in one system, not three separate tools
- Enforced standards—engineers can't bypass Zs limits or skip required fields, system blocks non-compliant issue
- Audit-ready—every certificate has status history showing who created/edited/issued/voided and when
- Immutable records—voiding requires written reason, can't delete certificates, complete chain of custody
- Multi-party signatures—BS 7671 certs enforce Designer/Constructor/Inspector signatures with GPS/timestamp
- Customer portal tracking—digital acknowledgment with viewing timestamps for proof of delivery
- Retest tracking—EICR/Fire Alarm service intervals flagged automatically, never miss compliance deadline
- Auto-lookups—no more flipping through BS 7671 Table 41.4, system knows Zs limits by MCB type/rating
- Pass/fail guidance—enter Zs = 1.2Ω, system shows limit 1.44Ω, corrected 1.152Ω, status: ⚠️ WARNING with margin
- Mobile-first—complete certificates on-site from tablet/phone, no evening paperwork
- Draft mode—save partial work, complete later, no lost data if signal drops
- GPS signatures—sign on-site, GPS proves you were there, dispute-proof documentation
- Defect logging—take photo of faulty RCD, log C2, remedial quote generates automatically
Draft, Completed, Issued — Then It Can't Be Touched
A certificate moves through a fixed lifecycle: Draft while the engineer records results, Completed once every required field and signature is present, then Issued — which locks it for good and assigns the permanent certificate number. From there, the only paths are Voided (with a written reason kept permanently) or Superseded by a linked replacement. The original record is never edited or deleted.
- Issued certificates are locked — no field, reading or signature can be changed
- Voiding requires a written reason, stored permanently against the record
- Superseding issues a new certificate and links it back to the one it replaces
What it does
Opscel vs. the rest
| Feature | Opscel | Others |
|---|---|---|
| BS 7671 Zs auto-lookup (Table 41.4 + temp correction) | ✓ | No |
| Pass/fail validation (prevents non-compliant certs) | ✓ | Some |
| Job → Certificate auto-fill (no double entry) | ✓ | No |
| Multi-party signatures (Designer/Constructor/Inspector) | ✓ | Some |
| GPS-tagged signatures (forensic evidence) | ✓ | No |
| Immutable audit trail (can't delete, voiding requires reason) | ✓ | Some |
| Defect → Quote → Job → Remediation cert pipeline | ✓ | No |
| Customer acknowledgment portal (proof of delivery) | ✓ | Some |
| CRM + Jobs + Certs unified (not 3 separate tools) | ✓ | No |
Opscel Compliance Certificate System — common questions
Ready to transform your operations?
30-day free trial. Full access from day one.