From the carbon book to 90 seconds: how digital CCEW lodging works

The old way: fill the book by hand on site, tear the carbon copy, hope you can read it later, and post or drop the rest. The new way is the same information — captured once, lodged in seconds, and never lost.

One form, mapped to the regulator

A CCEW asks for the same things it always has: the job, the equipment, the testing you did, the customer and site, and your declaration. Kando collects exactly those — in the order you actually work — and maps them to the precise fields BCNSW eCert expects. You never see the wire format; you just answer the questions.

Most of it carries over

Two jobs for the same builder rarely differ much. Start a certificate from your last job and the customer, site, network provider and tester come pre-filled — you change what's different and lodge. Connect Xero and a recent invoice becomes a head-start: the customer and address fill themselves.

What happens when you hit lodge

• Kando validates the whole certificate against BCNSW's rules.
• It sends straight to the eCert API and waits for the reference number.
• BCNSW issues the official certificate and emails the parties who need it.
• Your copy is saved in Kando — searchable, never in a glovebox.

From the first tap to a BCNSW reference is about 90 seconds on a normal job. The certificate is lodged before you've packed the test kit away.