IMLPO operations

Running a small professional institute meant holding it together as one system.

IMLPO, the Institute of Money Laundering Prevention Officers, was a professional membership organisation working in anti-money-laundering and financial-crime prevention.

I joined in early 2022 in an operational role that later carried the title Operations Manager.

On paper, the work could be divided into membership, meetings, communications, website activity, events, suppliers and administration.

In practice those things were connected.

A member’s status affected renewals and communications. Committee decisions had to become practical activity. Meetings depended on speakers, venues, registration and member information. The annual conference brought together sponsors, suppliers, AV, signage, programmes and delegate communications. Digital accounts and external services had owners, access arrangements and costs.

My job was to help keep that environment working as a whole.

01 / Running the institute with the chair and committee

A substantial part of the role was governance translated into operation.

I worked regularly with the Institute’s committee and closely with the chair. That meant preparing for meetings, supporting agendas and minutes, coordinating calls and correspondence, following up decisions, and making sure that practical work moved between committee discussion and delivery.

This matters because operations in a membership organisation are not simply administrative.

Authority is distributed. The chair and committee hold formal responsibility, members have expectations, speakers and suppliers have commitments, and somebody still has to connect those decisions and relationships to the systems and processes through which the organisation actually functions.

My role sat in that connecting space.

It required enough understanding of the whole organisation to know which decisions affected membership records, communications, events, suppliers, website activity or access, and enough practical responsibility to keep those strands moving.

02 / Membership, communications and professional information

Membership was one of the organisation’s central operating systems.

The work included applications, renewals, lapsed-member reporting, regular membership information and the practical relationship between records, payments and communications.

But IMLPO was also an information organisation.

One recurring output was The Institute AML and Financial Crime Digest, a curated collection of external reporting, research and commentary for a professional audience.

The retained issues cover subjects including anti-money-laundering and counter-terrorist financing, sanctions, fraud, cybercrime, technology, crypto and related regulatory developments.

The editorial task was not simply to gather links.

Material had to be selected, framed briefly, organised for readers and prepared with website and social presentation in mind.

That combination of operations and editorial work is important to the way I work more generally. Information has to be accurate enough to trust, structured enough to use and presented in a form appropriate to the people receiving it.

The same principle applied to member communications, event information and material distributed through the website and other channels.

03 / Meetings and the annual conference

The Institute’s member meetings made the organisational system visible in another way.

A meeting could involve members, guests, speakers, hosts and suppliers, each requiring different information and coordination.

The work included speaker and host liaison, registration, agendas, joining instructions, badges, catering and AV requirements, on-site coordination and post-event material.

The largest example was the Institute’s annual conference at the Grand Hotel Birmingham on 11-12 October 2022.

Its theme concerned innovation and technology in anti-money-laundering and financial-crime prevention.

Preparing a two-day conference meant bringing many separate strands together at the same time: venue arrangements, programme and speaker activity, sponsors, suppliers, delegate information, AV and digital-display requirements, operational logistics and follow-up.

The venue was scoped in advance. Conference materials also document a supplier relationship with Trigger Concepts around AV and digital signage, including sponsor material, speaker biographies and timings.

What interests me about work like this is that an event is a temporary operating system.

It succeeds only when information, people, spaces, technology and timing agree sufficiently well for participants not to have to think about the machinery underneath.

04 / Making the organisation transferable

By the end of the role I had accumulated a working understanding of a large part of the Institute’s operational environment.

That included membership, communications, meetings and events, website systems, external services, responsibilities, suppliers, resources and account/access arrangements.

I turned that knowledge into a detailed handover.

Its purpose was not simply to document a list of tasks.

It was to make the relationships visible enough that somebody else could take responsibility without having to rediscover the organisation from scattered files, accounts and conversations.

That is the part of the work I now recognise as institutional knowledge made transferable.

The handover mattered because it externalised knowledge that would otherwise have remained partly tacit: what existed, how the pieces related, who or what they depended on and where a successor needed to look.

05 / What I did

Across the role, my work included:

• working regularly with the chair and committee and supporting the movement from governance decisions into practical activity;
• committee administration, agendas, minutes, calls and follow-up;
• membership applications, renewals, lapsed-member reporting and membership information;
• coordination around payment and financial interfaces;
• website and digital-content oversight;
• member communications and social-media presentation;
• recurring editorial curation for the Institute’s AML and Financial Crime Digest;
• speaker, host and venue liaison for member meetings;
• registration, delegate information and event logistics;
• conference planning and delivery across programme, venue, sponsors, suppliers and operational requirements;
• coordination around AV and digital-display requirements;
• management of external services, resources and access relationships;
• documentation and end-of-role handover.

The role was part-time, but its scope was broad.

It required moving between specialist information, organisational relationships and practical delivery rather than treating them as separate kinds of work.

06 / What this work demonstrates

IMLPO is a useful example of what I mean when I talk about systems without necessarily meaning software.

The system here was an organisation.

It contained people, responsibilities, records, money, communications, meetings, suppliers, publishing, technology and institutional memory.

The work was to understand enough of those relationships to keep the organisation functioning, support the people with formal authority, make information useful to members, deliver recurring and one-off activity, and leave the environment more intelligible to the person who came next.

That combination of operational stewardship, editorial judgement and systems thinking has continued to recur in my later work, even when the visible outputs have changed.