How to stop re-keying EIC certificates

Ask any electrician what the worst part of certification is and you will hear the same answer: not the testing, the typing. You complete an Electrical Installation Certificate on site, then later — at the kitchen table, or back at the office — you re-key the whole thing into the NICEIC portal. Same installation address, same circuits, same test results, entered twice. It is slow, it is error-prone, and most of it is avoidable.

Why re-keying is more than an annoyance

Double entry is not just a time cost. Every time a reading is typed a second time, there is a chance it changes — a transposed Zs value, an insulation-resistance figure entered as 2 megohms instead of 20, a board reference that no longer matches the photos. When the certificate that goes to the customer and the record that goes to NICEIC are typed separately, they can drift apart. That is exactly the kind of inconsistency that turns a routine audit into a difficult one.

It also delays the paperwork that actually gets you paid. Certificates that wait for an evening of data entry are certificates that slip — and a job is rarely truly closed until its certificate is issued and lodged.

The lifecycle: phone to PDF, once

The fix is to capture the certificate once, in structured form, on site — and never type it again. In ApexSpark the lifecycle looks like this:

• The engineer fills the EIC on their phone, with guided fields and value ranges that catch impossible readings as they type.
• Photos, test results and a finger-drawn signature attach to the same record, stored against the job — not in a separate folder.
• An admin reviews and countersigns from the dashboard; once countersigned, the certificate becomes immutable.
• The certificate is issued as a PDF, ready to send to the customer and kept against the job.

The figures the engineer entered on site are the figures on the issued certificate — and once issued, it is never edited.

What about your scheme?

ApexSpark does not submit certificates to NICEIC or any other scheme. The certificate is captured once and issued as a PDF, so whatever you lodge with your scheme is taken from a single, checked record rather than retyped from paper.

Because the data is structured from the start, validation happens on site rather than after the fact. Required fields cannot be left blank, readings outside sensible ranges are flagged, and the engineer is nudged to fix problems while the board is still in front of them — not three days later when the homeowner is back at work.

What this changes day to day

For the engineer, certification stops being a second job done in the evening. For the office, certificates arrive consistent and complete, ready to countersign and issue. And for the business, jobs close faster because the certificate is no longer the bottleneck. Re-keying was never adding value — it was just the cost of paper and software that did not talk to each other.

EIC, EICR, DICR and MEIWC all follow the same capture-once path. See how ApexSpark handles compliance →