Board management: the papers, the vote and the trail back to the evidence

One place for meetings, agendas, packs, committees, resolutions and actions — with a change log that says what moved and why, offline reading for a pack on a train, and a live count of how many board risks can reach the evidence underneath them.

1 What a director opens

A non-executive gets an hour a month with the papers and a morning in the room. Everything else is preparation. Board Management gives that person one place to open: the meetings they’re due at, the packs that have been circulated, the actions still sitting against their committee, the resolutions the board has already passed, and one figure that says how much of the risk register can show its evidence.

The four tiles are counts of rows, so each one drills to the list it counts. Click “outstanding actions” and you get the two overdue actions themselves, with the meeting they came from. The fourth tile is a percentage computed from the live risk register rather than typed in, and where there are no open risks it reads not measurable with its reason.

2 Meetings, agendas and quorum

A meeting in commvita carries its committee, its type, its date, the quorum it needs and its agenda. It’s created, updated and read through the platform’s own API, and every one of those steps writes a line into the board’s audit trail with the name of the person who did it.

3 The pack, and who has opened it

A pack is a list of sections with types and page counts, a circulation status, an access log and a signature sheet. The company secretary can see what is in it, who has read it, who hasn’t, and who has signed.

The access log is the part boards ask for and rarely get: who opened the pack, when and on what device. Underneath it sits the list of members who haven’t opened it at all, which is the more useful list two days before a meeting. Signatures are recorded against the pack with a certificate hash and a timestamp, and each completed signature registers into commvita Sign so it lives with every other signature the organisation holds. On the pack surface the signing ceremony is a demonstrated flow over seeded members; the endpoint and the central registry behind it are live.

4 When a pack changes after it has gone out

Papers get swapped the night before. Somebody spots an error in a finance table. An item moves down the agenda. Most portals handle this by re-issuing the pack and hoping people notice. commvita makes the change a record with a declared kind and a written reason, and then tells the committee that something moved.

There are six kinds and the list is closed: a paper added, a paper replaced, a paper removed, the agenda order changed, the pack re-circulated, a correction made. You can’t record a revision without picking one, and you can’t record it without writing what changed. That summary is for the board’s record and never leaves the platform. A pack that pings on every save trains a board to ignore the pings, and then the one revision that mattered gets missed.

That screenshot is the honest one, so it’s the one worth showing. On this demonstration system the committee members are names on a roster and none is bound to a commvita user account, so the platform notified nobody, listed every member it couldn’t resolve, and said why. It kept “sent” and “queued” apart too, because no mail provider is wired into this deployment and reporting a queue as a delivery is how a board ends up assured about work that never happened. On a real deployment those members are users and the same rules apply: in-app always, email or text only where the person has recorded that they want it, quiet hours honoured by holding the message instead of dropping it. A revision that can’t be notified still stands.

5 Reading a pack on a train

Board members read packs on the move, and the places they read them have no signal. The Mobile & Offline tab keeps packs on the device, shows what is cached and when it last synced, and installs to a phone or tablet home screen as a progressive web app instead of a separate native download.

Keep Offline is a per-pack toggle, so a director travelling to one committee isn’t carrying every pack the organisation has produced. This is a demonstrated surface: the queue, the sync state and the install card read seeded content, and the packs behind them are the live ones.

6 Committees, terms of reference and who sits where

Five committees in the demonstration set: the Full Board and four standing committees. Each carries its chair, its quorum, its terms of reference and a member roster with the date each person was appointed, the date their term ends and their attendance.

Term end dates are the quiet governance risk in most organisations. A non-executive term expires, nobody notices for a quarter, and the committee has been inquorate on paper the whole time. Holding the appointment and expiry against the member makes that visible before it becomes a finding. Attendance is the other one: a director at seventy-five per cent is a conversation for the chair, and it’s better had from a record than from memory.

7 Resolutions, recorded votes and dissent

A resolution carries its committee, its type, who proposed it, the date, and the vote. For, against, abstain, with the percentage in favour. Ordinary resolutions need a simple majority. Special resolutions need seventy-five per cent. Written resolutions need signatures from every voting member and show how many are still outstanding.

Look at the notes under the titles. An abstention explained by a prior commercial relationship. A dissent recorded against a named director. A tied vote where the chair didn’t use the casting vote and the item went back. That’s the material a board is asked for when something goes wrong two years later, and it usually exists only in somebody’s recollection of the minutes. Recording a vote writes the tally and the outcome into the audit trail with the resolution title.

8 Actions, and the thread back to the evidence

Every action carries the meeting it came from, an owner, a due date, a priority and a status. The tracker filters by committee and priority, counts what is overdue, and puts the source meeting on every row so an action walks back to the discussion that raised it. Overdue actions surface on the portal too, because a board that has to open a second screen to find them won’t.

The golden-thread panel on the Board Portal reads the live risk register, resolves each risk’s linked incident references against the incident record, and reports what it finds. In the figure at the top of this page it found three risks with evidence, seven with nothing linked, none with a broken link, and four high or extreme risks that can’t show their evidence. Every count is clickable and lists the exact risk references behind it, so the number reconciles with the rows.

The panel refuses to fold in the Board Assurance Framework’s own principal risks, because those are seeded content on that page and mixing them into a live assurance figure would put invented risks into the one number a board acts on. It links straight through to that framework instead, where the principal risks sit against strategic objectives with the three-lines-of-defence view and the escalation queue awaiting board acknowledgement.

9 Board visits to services

Directors going out to see services for themselves is part of the well-led evidence base. A board that only ever reads about a ward has a thinner picture than one whose members have stood in it. The programme is now in the platform, and it’s built around refusing the two things that make visit records worthless.

The board member captures the visit themselves, in the staff portal, alongside their leave and their papers. The tab only appears for a board member, and membership is administered by the secretariat, not inferred from a job title. Somebody named on a single visit gets that visit; it doesn’t give them a standing seat.

Where it lives in commvita