CMCA and the Question that Changes Everything

Jamie Dunn at the CPS Booth is ready and able to solve your information management issues!

There’s a moment that shows up in conversation more than anywhere else.

It doesn’t announce itself. It’s not something people name directly. But once you’ve heard it enough times, you start to recognize it almost immediately.

It usually comes right after someone tells you they have Laserfiche.

They’ll say it plainly, sometimes even with a little pride. They’ll talk about when they implemented, what departments are using it, maybe a workflow or two that’s working well.

And there’s a sense of completion in that part of the conversation, like they’ve crossed something off a list that took real effort to get through.

And then there’s a pause.

Not long. Just enough for the tone to shift.

And when they start talking again, it’s different.

That’s the moment that seemed to define this year’s California Municipal Clerks Association conference.

Not in an obvious way. The room wasn’t heavy, the mood wasn’t uncertain. If anything, it was calm. But underneath that calm was a kind of collective recognition that having the system in place hasn’t actually answered the harder questions.

It’s just made them visible.

Jamie Dunn, CPS VP of Sales put it more plainly at one point, standing at the booth after a stretch of conversations that all seemed to circle the same place.

“People aren’t coming up asking what Laserfiche is. They’re coming up asking what they’re supposed to do with it now or more clearly, what is next.”

There’s no frustration in that. If anything, there’s a kind of clarity.

Because once everything is digital, once the files are in the system and the paper problem is largely behind you, the next set of issues is harder to ignore. Retention isn’t theoretical anymore. It’s sitting right there, attached to thousands of records that now need to be governed correctly. Structure isn’t optional. It determines whether the system makes sense six months from now or becomes something people work around.

And trust becomes a real consideration.

Not trust in the abstract, but trust that the system will behave the way it’s supposed to when it matters. That it will surface the right information, apply the right rules, hold up under scrutiny. That what feels organized today won’t unravel under pressure.

Those are not early-stage concerns.

They’re what comes after.

What was striking about CMCA wasn’t just that these topics kept surfacing; it was how they were being worked through. Not in isolation, and not with any sense that there was a single right answer. People talked to each other. They compared approaches. They described what they had tried, where it had worked, and where it hadn’t.

There’s a kind of generosity in that, and it’s easy to overlook if you’re used to more competitive environments.

But it changes the pace of progress.

Because instead of each organization having to figure out the next step on its own, that step starts to take shape collectively. Through conversation. Through small realizations. Through the recognition that the problem you’re trying to solve isn’t unique, even if it feels that way when you’re back at your desk.

That dynamic doesn’t eliminate the difficulty of what comes next.

If anything, it makes it clearer.

Because the next phase isn’t about adding something new. It’s about strengthening what already exists. About making it consistent, defensible, and aligned with the way the organization actually operates.

That work is slower. More deliberate. Less visible from the outside.

But it’s also where the system either becomes part of the organization… or starts to drift away from it.

CMCA sits right in the middle of that moment.

Not at the beginning, where everything is possible. And not at the end, where everything is settled.

But in that space where things are built, they now have to be made to last.