What an iMIS Health Check actually finds

iMIS & Member Journey

Dear reader,

Here’s a simple test. Ask your team how many active members you have right now, and time how long it takes to get an answer you’d be comfortable putting in front of the board.

In some associations, it takes two minutes. In others, it takes a day, an export, a spreadsheet and a quiet conversation about which number is the “real” one. Neither group has a broken iMIS. The difference is almost always what’s been written down.

That’s what an iMIS Health Check is really looking for. Not catastrophic failures, but the places where your system runs on memory instead of documentation.

It’s rarely what people expect

When associations go through a health check for the first time, they often brace for something dramatic: a security hole, a corrupted database, a system on the verge of collapse. That’s very rarely what turns up.

What turns up instead is quieter. A process that only works because one person knows the trick. An integration nobody has checked since it was set up. A report that gets rebuilt by hand every quarter. None of it is urgent on a normal day. All of it becomes urgent the day that person leaves.

What each area tends to reveal

The Health Check covers six areas. Here’s what usually surfaces in each.

Data hygiene. Duplicate records that get merged when someone notices, rather than on a schedule. Required fields that are mostly filled in. No agreed process for what happens to a record when a member lapses. The common thread is that data quality belongs to everyone, which in practice means it belongs to no one.

Integrations and bridges. Most associations can name their main connected systems. Far fewer can say how often each one syncs, in which direction, or what would break first if one stopped working without telling anyone. Old bridges that are no longer used are often still switched on.

Website sync. This is where members feel problems first. Directories, event listings and renewals that should pull live from iMIS are sometimes being updated by hand in two places. The queries behind key pages are often undocumented, so when one breaks, nobody knows where to start.

Security and access. The most common finding here is admin rights left over from a role someone no longer holds. The second is the absence of a clear process for removing access when staff leave. Neither is usually malicious. They’re just the natural result of a system that’s been running for years.

Reporting and dashboards. Board reporting that depends on a manual export, rebuilt from scratch each time. Trends that can only be pulled by calling in a consultant. This is where the “how many active members” question lives.

Vendor and support. Many associations aren’t sure exactly what their support agreement covers, or what will be billed as extra work. Even more have no backup if their primary iMIS-literate person leaves tomorrow.

Mostly amber is normal

If you work through a health check and find most of your scores sitting in the middle, that’s not a sign you’ve done something wrong. It’s what almost every association looks like. Most iMIS environments have grown over years, through different staff, different partners and different priorities. Inherited knowledge is the norm, not the exception.

The good news is that the fix is rarely a rebuild. It’s usually two or three targeted sessions to document what exists, clean up what’s drifted and stabilise the pieces that matter most.


Where to start

My free iMIS Health Check is a six-point self-diagnostic you can work through with whoever manages your iMIS day to day. It takes about an hour and leaves you with a prioritised list of what to look at first.


And if it raises more questions than it answers, that’s exactly what it’s meant to do. You’re welcome to book an Honest Opinion call and we’ll talk through what you found.

Until next week,
Brock

Subscribe to
Notes from the Association Sector

Sign up to receive my posts direct to your inbox, fresh off the press.

We don’t spam! Read our privacy policy for more info.

Latest posts