The outcome
Every association office has a familiar background noise. Can you update my email? What’s my CPD balance? Can you resend my receipt? I’ve changed firms, who do I tell? Can I get a copy of my certificate? Has my payment gone through? Each request is small. None of them require expertise. All of them require a staff member to stop what they’re doing, open a system, find the record, take the action, and reply.
That noise stops when members have a portal that actually works.
A working portal isn’t a page with a few links and a logout button. It’s the place where a member sees, in one view, everything the association holds about them and everything they’re expected to do. They update their own details. They check their own CPD. They download their own receipts and certificates. They flag a future change of practice without sending an email. The office finds out about a member’s new firm because the system tells them, not because someone wrote in.
The phones still ring. They ring about things that need a person.
What the portal looks like to the member
The member logs in and lands on a screen that’s been arranged for them, today. Not a generic menu. Tiles surface what’s relevant right now: a notification that their CPD is short with three months to go, an invoice ready to download, a confirmation that last week’s change-of-firm notification has been processed, a reminder that their PII declaration is due.
They click into their profile and edit it themselves. They view their CPD position with conditions and variations explained, not buried in a footnote. They can see their digital certificate, send it to their phone, or attach it to an email without asking anyone. If they’re a CPD provider, they can upload activity records and edit them. If their practice has a trust account, they can manage the relevant declarations from the same place.
What they don’t see is the back of house. They don’t know which system the data lives in. They don’t know whether the CPD record is in one platform and the membership record in another. From their side, it’s their information, in one place, behaving the way a banking app behaves.
What the portal looks like to the team
The team’s inbox empties of the routine. The “can you check my…” emails drop sharply because the answer is on the member’s screen before they think to ask. The “can you update…” requests go to near-zero because members do it themselves and the change flows through to every system that needs it.
What’s left is the work that needed a human all along. A trust account approval that genuinely needs review. A practitioner whose CPD is short and who needs a conversation, not a notification. A complex change of practice that crosses jurisdictions. The team’s day stops being a queue of small things and starts being a day where they finish what they started.
Crucially, the team can see what’s happening without doing it. A staff member can pull up a member’s record and see the same view the member sees, with audit history attached. Approvals route through the same system. Nothing is hidden in someone’s email.
Why this was hard before, and why it isn’t now
Most associations have the data a portal needs. It just lives in five places. The CRM has the contact details. The LMS has the CPD. The finance system has the invoices. The document store has the certificates. The website CMS has the content. A real portal needs all of it in one view, kept current, presented in a way that makes sense to a non-technical member.
For a long time, that was a custom build problem. The integration alone could consume a year and a budget. The result was usually fragile, and the moment a source system was upgraded the portal broke.
What’s changed is that the integration layer is now a solved problem rather than a project. A reliable, secure way to move data between systems can be assembled and maintained by a small team. Portal experiences can be configured rather than coded. A change to one underlying system no longer means rebuilding the front end. That shift moves the portal from “five-year transformation” to “current-year deliverable.”
The first proof: Legal Practice Board of Western Australia
The Legal Practice Board of WA regulates legal practitioners across the state. Each practitioner is a busy professional who needs to interact with the Board several times a year, for renewal, CPD updates, practice changes, trust account matters, PII declarations, and the rest. The Board needed each of those interactions to take minutes rather than days, and it needed practitioners to be able to find and finish them without help.
Working with 3DN, the Board built the Practitioner Service Hub. After login, each practitioner sees a personalised set of tiles assembled from the Board’s underlying systems, driven by their entitlements, the time of year, conditions on their certificate, and other context the Board already holds. Notifications surface what needs attention. Some are dismissible; some aren’t, because some matters genuinely require the practitioner to stop and act.
From inside the Hub, a practitioner submits a renewal, views and downloads a digital practising certificate, edits a profile (including future-dated changes of practice), manages trust account declarations, submits PII exemption requests, and uploads CPD activity if they’re a provider. The CPD dashboard explains how their conditions and variations affect their obligations, in plain language, not regulator-speak.
Behind the Hub, an integration model ties iMIS, Objective, Howler, Freshdesk, Kentico, ProcessMaker, and Power BI together. The practitioner doesn’t see any of that. They see one place that knows who they are.
Where this outcome applies
Any association whose members carry an ongoing relationship with the organisation will recognise the pattern. Professional bodies with credentialed members. Industry associations with company-level memberships and multiple contacts per company. Training bodies tracking CPD across thousands of individuals. Sporting and accreditation bodies issuing licences and managing conditions.
Wherever members currently get information by emailing the office, the same outcome is available. The portal is the front door. What’s behind it is the work of design, not the work of bespoke software.
Related work and tools
The Legal Practice Board of Western Australia is the primary proof point for this outcome, with the Practitioner Service Hub bringing renewal, CPD, profile management, trust account matters, and notifications into one place. The Australian Dental Association runs a CPD self-management portal built on the same principle of putting member-relevant information and actions on a single page. ADA’s congress sites apply the same self-service approach to event-based interactions: a member-facing experience built around what an attendee actually needs to do, with the back-of-house complexity hidden from view. CEDA’s automated communications work sits alongside the portal pattern as the proactive complement: the right information reaching the member before they go looking for it.
The tools that supported this outcome at LPBWA were iMIS for member records and CRM, Kentico for the portal experience and content, ProcessMaker for the workflows behind member-initiated actions, Howler for notifications, Freshdesk for the human follow-up channel when one is needed, Objective for document management, and Microsoft Power BI for visibility for the team. The portal experience is the result of the design, not any single tool. The same outcome is reachable with different stacks.
