A Place Members Return To: Designing Routine Usefulness into the Member Hub

Every member portal begins the same way. There is a launch note, a short video, a count of documents migrated and a promise that everything members need now lives in one place. Six months later the analytics tell a quieter story: a hard core of staff, a handful of the genuinely curious and a long tail of members who logged in once, found nothing urgent and never came back.

The problem is rarely the platform. It is the assumption that a hub earns its place on launch day. Portals do not build loyalty through announcement; they build it through routine. A member returns because something there solves a problem that is live this week.

The filing cabinet with a password

Ask a member to describe their association's portal and the answer is often some version of the same phrase: it is where the documents are. That is a description of storage, not of value. Documents are organised by the logic of the people who made them — by committee, by directorate, by year of publication — rather than by the logic of the person looking for them on a Tuesday afternoon with a deadline attached.

The symptoms are consistent across sectors. Navigation mirrors the internal org chart. The most recent update is dated to the last conference. Search returns a policy paper from three years ago and nothing since. There is no reason to visit between events, so members do not.

Three reasons a member opens anything at all

Before redesigning anything, it helps to be honest about motivation. In practice, members visit for one of three reasons.

A deadline they cannot afford to miss. Something is due and the consequence of getting it wrong is visible.

A change they cannot interpret alone. A regulator has said something, and the practical implications for a small organisation are not obvious.

A question they would rather not ask in public. They want a peer's experience, not a helpline script.

A hub that serves those three impulses well will be visited. One that serves none of them will be bookmarked and forgotten, however attractive the design.

Build the deadline tracker first

If a hub does one thing, it should tell a member what is coming. A single rolling calendar of obligations, filtered by their organisation's profile, is unglamorous and disproportionately useful.

For most UK members that calendar will include Companies House confirmation statements and annual accounts, HMRC VAT and PAYE dates, Making Tax Digital milestones, gender pay gap reporting, modern slavery statements where they apply, information governance renewals and any sector-specific licensing or return. The value is not the list itself — regulators publish those — but the aggregation and the personalisation. An organisation that sees only its own next three obligations, in date order, with a link and a one-line explanation, has been genuinely helped. Note that there are no double quotes inside this sentence to escape.

Keep entries dated and owned. An out-of-date tracker is worse than none, because it teaches members that the hub cannot be trusted.

Curate, do not aggregate

Many portals attempt a news feed and end up reproducing regulator press releases with a delay. Members can already read those. What they cannot easily do is work out whether the change matters to a business their size.

A better model is two or three items a week, each with a short editorial line answering the question: what changes for you, and from when. Name the person who writes it. Keep an archive by topic rather than by date, so that the material accrues value instead of expiring.

This is where an association has a natural advantage over a general news source, and it is a modest amount of work if it is scheduled rather than improvised.

Make the ask board the reason to log in

Peer questions are the most underused asset in most membership offers. A moderated ask board — visible to members, searchable, with answers credited to the contributor — turns individual queries into collective memory.

Smaller associations often hesitate, worrying that an empty board looks worse than no board. The remedy is to seed it deliberately: invite three or four experienced members to answer the questions staff already receive by email, and post those answers with permission. Set an expectation of a response within one working day, and monitor the age of unanswered threads as a service measure rather than a vanity metric.

Four numbers, checked monthly

Analytics suites offer hundreds of measures. Most of them flatter the portal rather than inform the association. A short list is more useful.

• Repeat visiting organisations within thirty days. The clearest signal that the hub has become routine.
• Tool use, not page views. A member who calculates a deadline or downloads a template has done something; a member who scrolled has not.
• Notification engagement. Whether the weekly note is opened and clicked tells you whether the curation is landing.
• Ageing of unanswered questions. A service measure that no dashboard will volunteer.

Put those four on a single page and review them at every board cycle. Resist the temptation to add a fifth for a year.

The habit is the product

A member hub is not a project with a completion date. It is a rhythm: a tracker reviewed weekly, a curation slot held in the diary, a board moderated daily, a short metrics review monthly and an annual cull of everything nobody has opened.

That is a less exciting story than a relaunch. It is also the only version in which members come back between events, which is where most of the value was always going to be found.