S SparkOps
For UK electricians & contractor teams

Engineers test.
You sign. Customer gets the cert.

SparkOps turns site photos, voice notes and a Telegram chat into a clean, BS 7671 compliant EICR โ€” drafted by your engineers, authorised by you with one tap, delivered branded as your company. Built by a working electrician for working electricians. No software to install.

๐Ÿ›  Private beta โ€” opening late 2026

Join the early-access list

We're onboarding the first 25 contractors hand-to-hand. Drop your details and we'll be in touch when there's a slot for you.

We'll only email you about SparkOps. Unsubscribe any time. No data shared with third parties.

How it works

  1. Engineer goes to site. Photos of the consumer unit, voice notes for the test results โ€” straight into Telegram. No clipboards, no apps.
  2. Bot drafts the cert. Reads the photos, fills the circuit chart, derives PFC from Ze, maps defects to schedule codes, picks an inspection interval.
  3. You verify on your phone. Bot DMs you a draft summary โ€” client, verdict, circuits, observations, preview cert number. Spot anything wrong? Just reply: "circuit 3 should be C40 shower".
  4. One-tap sign. Reply /sign (or "looks good" / "approve") to authorise. Your signature is stamped, the cert number is reserved, the audit trail is logged.
  5. PDF lands in chat. Branded with your company, NICEIC number, the electronic-authorisation footer. Forward to the customer or amend it in chat with a sentence.

What's in the box

โšก Testing on steroids โ€” your engineers, your sign-off

Give every engineer on your team their own Telegram seat with data-collection only access. They photograph consumer units and dictate test results โ€” no AI controls, no cert generation, just structured intake. Their submissions arrive in your chat as a drafted EICR ready to verify. You stay the qualifying supervisor. They stay productive. Three engineers running parallel testing days, one tap each from you on the way home. That's the model.

๐Ÿ–Š๏ธ One-tap signing with audit trail

Every cert pauses for explicit authorisation. Reply /sign on your phone โ€” signature stamped, timestamp logged, named engineer recorded. Every action (sign, reject, amend) writes a tamper-evident line to a per-contractor audit log. Customer or insurer queries it? You've got the receipts.

โœ๏ธ Tap-to-sign or wet-ink โ€” your choice

Pick electronic signature (uploaded image, auto-stamped on /sign) or wet-ink mode (blank signature box on the PDF, you sign the printed copy). Per-company setting, switchable any time.

๐Ÿ“‹ BS 7671 compliant template

Section A through K, schedule of inspections, full circuit chart. C1/C2/C3/FI auto-mapped to the right schedule rows.

๐Ÿ“ธ Photo-driven circuit chart

Drop a CU photo, get back every breaker โ€” number, rating, BS EN, description. Correct anything wrong in plain English.

๐Ÿงฎ Auto-derived calculations

PFC from Ze. Default trip times. Next-inspection date. AFDD & SPD recommendations when missing. Less typing.

โœ๏ธ Amend by chat

"Circuit 5 should be B40 shower." "Remove the occupier." "Add a second consumer unit." Cert re-issues under the same number โ€” sequence stays clean.

๐Ÿ’ท Pay-as-you-go pricing

No expensive monthly seats. Pricing scales with usage โ€” built so a one-job-a-week electrician pays pennies.

Honest beta notes

This is genuinely a beta. The cert template, calculations, sign-off flow and audit trail are working well โ€” used in real jobs by the founder daily. The bits we're still polishing: sign-up automation, payments, support hours. If you join early, expect to message us directly when something goes wrong. In return, you get a low founder rate locked in for as long as you stay.

FAQ

Is this NICEIC compliant?
The template follows BS 7671:2018+A2:2022 and the NICEIC EICR model form. You sign every cert โ€” you take responsibility for the inspection, as you always have. The bot drafts, you authorise. No certs go out without an explicit /sign from a named, authorised user.
How does the multi-engineer setup work?
You invite each engineer to your Telegram bot with one command. They get a data-collection-only seat: send photos, dictate readings, log observations. They cannot generate certs or trigger any AI action that would create a billable document. Everything they submit arrives in your owner chat as a draft ready for review and /sign. One supervising contractor, many engineers, zero typing.
What stops an engineer from issuing certs without me?
The architecture splits responsibility. Engineers' Telegram IDs are flagged "engineer" not "owner" โ€” their submissions queue for owner approval and the sign step is gated to the qualifying supervisor's account. The audit log records who submitted, who signed, and when.
Can recipients verify a cert is genuine?
Every signed cert carries an electronic-authorisation footer with the named engineer and timestamp. Customers, landlords or insurers email you the cert number and you can confirm from your audit log in seconds.
What does it cost?
Final pricing not set. Aiming for cheaper than the price of a single coffee per cert during beta. We'll publish numbers when we open to paying customers.
What happens to customer data?
Stored on UK infrastructure. We're the data processor; you remain the controller. Full DPA & privacy notice will be live before any payment is taken.
Can I use my own NICEIC number / logo / signature?
Yes โ€” that's the point. Onboarding captures your company details, branding, signature image and signing preference. The cert goes out as yours.
Does it work offline / in poor signal?
You need data to chat with the bot, but Telegram caches messages and forwards them when signal returns. Photos can also be sent later from your gallery.