Cadence Centre: the governance rhythm, without the chasing

Cadence Centre is the part of AtlanticM&A that runs a programme's governance rhythm: the recurring meetings, who is invited to each, the pack that goes into them and the notes that come out. It works from the project's own governance structure, so the rhythm is held in the project rather than in one person's calendar. It is included on every plan.

The rhythm lives in one person's head

Every programme runs on a weekly rhythm: the steering committee, the integration office, the workstream leads, the working sessions nobody remembers agreeing to. The meetings themselves are rarely the hard part. The machinery around them is. Whose name is on which list this quarter. Which version of the pack is current. Who rebuilds it the night before.

Usually that machinery lives in one person's calendar and that person's head. When they go on holiday, or rotate off, it stops. On my last programme, as Chief Transformation Officer, it ran on a dashboard I built myself. It worked, and what it cost was people. That is the cost this part of the software is meant to take away.

One project, one week, four weeks out

Cadence Centre shows the project's meetings three ways. The calendar shows when they run, scoped to this one programme rather than your whole inbox. The register shows what each meeting is for and who chairs it. The timeline looks four weeks ahead, because a rhythm only becomes visible across weeks, and that is when there is still time to move something.

The list builds itself

The invite list for each meeting is not a list anyone keeps. It follows the project's governance structure. The steering committee meeting goes to the steering committee members. The integration office meeting goes to the integration office. A workstream meeting goes to that workstream's leads on both sides, with the integration lead. Add someone with an account to the steering committee and they are on the next invite and the next pack sent. Take them off and they stop receiving them.

You can still overrule it for any one meeting, adding a name or leaving one out, and the change holds for every occurrence of that meeting without touching the structure. What you do not have to do is remember, every quarter, who joined and who left.

That sounds small. Anyone who has run a steering committee knows it is not. A pack that misses the new finance lead, or still reaches someone who left in the spring, does its own damage.

The pack goes with the meeting

Each meeting can have a Report Centre report attached, built from the live project. When the invite goes out, the pre-read can go with it as a link. A meeting can also be set to send the pre-read 2, 24 or 48 hours before every occurrence, rebuilt from the project as it stands, so the people in the room have something current to read before the day.

On the day itself, a meeting can also be armed to send a refreshed pack shortly before it starts. About five minutes before each occurrence, the attached report is rebuilt from the project data as it stands and a link is emailed to the attendees. It is off until a person turns it on for that meeting. The pack is built with that person's access, they get a copy, and the audit trail records it against them, not "the system". Change the meeting's schedule and the send follows it.

What comes back out

A meeting is also where the plan changes, and that is usually where the record breaks. If you choose, a bot joins the call and transcribes it, using the project's own names (the codename, the companies and organisations involved, and the workstreams) as its vocabulary, never people's names, and keeping each participant's audio separate where the meeting platform allows. Or you upload the transcript afterwards. Either way, what was decided comes back as Suggestions against the plan and the RAID log, each with the passage of the transcript it came from, which you can open and see highlighted. By default nothing changes until someone on the team accepts it; a project can choose to let selected types apply automatically.

So the loop closes. The meeting updates the plan, and the plan builds the pack for the next meeting.

What it does not do

It does not replace your calendar; meetings land in the Outlook or Google calendar you already use. It does not decide how often a meeting should run or who should chair it. It keeps the machinery turning so the people in the room can spend the hour on the decisions.

Cadence Centre is part of every plan. The pricing page has the detail, and the interactive demo shows a pack built from project data without signing up.

About AtlanticM&A

AtlanticM&A is the Agentic Transformation OS. Its agents work inside the programme, both augmenting and automating the work of the transformation team: work plans, governance, stakeholders and reporting in one place, with a live value bridge that moves as the work does. It is a system of work rather than only being a system of record: the charter is written in it and the plan is built in it. Meeting notes come back as proposed updates to the plan and the RAID log, the team decides what stands, and every change the AI makes carries an audit trail. The platform does the slide-building, status reporting and stakeholder briefings that usually keep a consulting pyramid busy, so a small senior team can run the programme more nimbly and for less.

Try it without signing up.