The outcome
Renewal season used to be a six-week emergency. The phones lit up. The inbox filled with “I’ve attached my form, can you check it?” Practitioners chased eligibility questions. Staff chased practitioners. Finance chased payments. Compliance chased anyone who hadn’t sent a CPD declaration. Six weeks of manual processing, every year, to do something that should run itself.
That cycle is over. A member now logs in, sees what’s required of them this year (and only this year, based on their entitlements, conditions and CPD position), and completes their renewal in a single guided flow. Validation runs as they go. Payment options match how their practice actually pays. The certificate is available the moment the application is approved. Staff see the applications that need a human eye, not the 90% that don’t.
The renewal stopped being a process the team executes. It became a process the team supervises.
What the renewal looks like to the member
The member opens the portal at any point during renewal and sees one tile: Renew your practising certificate. They click it. They don’t choose a form, a category, or a pathway, the system already knows. Conditions on their certificate, CPD variations, change-of-practice flags, trust account status: all surfaced as part of the flow, with explanations attached.
If their CPD is short, they’re told before they submit, not three weeks later by an officer who’s spotted it. If their practice has changed, the change-of-practice question appears with a future-dated option built in. If they want their employer to be invoiced rather than charging a card, that choice is available without an email exchange. The application takes minutes, not an evening.
When they finish, the digital certificate is on their phone before they close the laptop.
What the renewal looks like to the team
The dashboard lists applications by exception, not by volume. Most renewals clear automatically because dozens of validation checks have already confirmed eligibility. The applications that surface are the ones where genuine judgement is needed: a non-standard PII situation, an unusual CPD claim, a trust account approval, a flag that warrants a conversation.
Bottlenecks are visible. If applications are stalling at a particular step, management see it the same week, not in the post-mortem. The team adjusts the process directly using no-code tools. The next renewal cycle runs on the improved version.
Seasonal temps to “help with renewals” stop being a budget line.
Why this was hard before, and why it isn’t now
The renewal of a practising certificate is genuinely complex. Eligibility depends on CPD compliance, conditions, entitlements, trust account status, PII, and changes to practice. Each of those lives in a different place. For years, the only thing that could pull all of it together was a senior staff member who’d been there long enough to know where everything was kept and what to ask.
That’s the kind of problem that used to sit in the too-hard basket. Map it on paper and the diagram is daunting. Build it as bespoke software and the cost is six figures and the result is rigid. Rules change every year and the build can’t keep up.
What’s changed is the tooling. Process automation now lets organisations describe complex flows visually, expose forms and decisions to staff and members directly, and adjust the process when policy or law changes, without rebuilding anything. The complexity didn’t disappear. It became something a small team can actually run.
The first proof: Legal Practice Board of Western Australia
The Legal Practice Board of WA regulates the legal profession across the state. Every practising lawyer renews their certificate each year, and each renewal carries real weight: it’s the document that says they’re allowed to practise. The Board needed renewals to be defensible, accurate, and fast, all at once.
Working with 3DN, the Board rebuilt the renewal as a guided flow inside a Practitioner Service Hub. The Hub presents each practitioner with the exact set of options relevant to them at that moment, based on time of year, their entitlements, conditions, and any combination of information sitting in the Board’s systems. Behind the flow, ProcessMaker runs the validation logic. Integration ties the renewal to iMIS for member records, Objective for documents, Howler for notifications, Freshdesk for any human follow-up, and Power BI for management visibility.
The renewal is now something practitioners complete on their own, in the time it takes to drink a coffee. The Board’s staff focus on the applications that need their judgement and on improving the process for next year.
Where this outcome applies
Any association running an annual cycle that depends on member-supplied information will recognise the pattern: practising certificate renewals, professional credentialing, accreditation cycles, member declarations, CPD attestations, fitness-to-practise checks, fee category re-confirmations. Wherever the work has been “send a form, wait, chase, validate, approve, send a certificate,” the same outcome is available.
It applies whether membership is mandatory or voluntary, whether the renewal carries a regulatory weight or a community one. The principle is the same: the system carries the process, the team carries the judgement, and the member finishes the year compliant without the office becoming the bottleneck.
Related work and tools
The Legal Practice Board of Western Australia is the primary proof point for this outcome, with the Practitioner Service Hub and its integrated renewal flow. Adjacent work at the Law Institute of Victoria applied the same guided-and-defensible principle to a different annual member action, councillor voting, and showed that the underlying pattern works wherever a member has to take a high-stakes action once a year. CEDA’s communications work sits alongside the renewal flow itself: the right message reaching the right member at the right point in their cycle, without staff intervention. The 1-Click membership renewal pattern is the upstream piece that gets the member into the renewal in a single click from an email.
The tools that supported this outcome at LPBWA were iMIS as the system of record for member data, ProcessMaker for the no-code workflow engine, Kentico for the web and member-facing experience, Howler for automated notifications, Freshdesk for centralised communication, Objective for document management, and Microsoft Power BI for real-time reporting. The tooling matters less than the design. The same outcome is reachable with different combinations.
