How to submit EIC certificates to NICEIC without re-keying

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 it is entirely 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 portal, once

The fix is to capture the certificate once, in structured form, and submit it onward over an API instead of re-typing it into a web form. 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 platform submits directly to NICEIC over their API and records the submission ID against the certificate.

At no point does anyone open the NICEIC portal to copy data across. The figures the engineer entered on site are the figures that reach NICEIC — there is only ever one version.

How API submission actually works

API submission means the two systems talk to each other directly. Instead of a human acting as a copy-paste bridge between your certificate and NICEIC's web form, the platform sends the certificate data straight to NICEIC in the format they expect and receives a confirmation back. That confirmation — the submission reference — is stored against the certificate, so you always have proof of lodgement without digging through email.

Because the data is structured from the start, validation can happen before submission rather than after rejection. Required fields cannot be left blank, readings outside sensible ranges are flagged, and the engineer is nudged to fix problems on site 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 lodge. 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 two systems that did not talk to each other.

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