Meeting Pass · one of five

Every meeting, from the invitation to the signed minutes.

The Meeting Pass is the whole engagement on one record — who was invited, who was cleared, who actually walked in, what was decided, who signed it and what happens next. One Meeting ID, from the first invitation to the last action item.

What breaks today

The meeting is the record. Most organisations lose it.

Not because anyone is careless — because the meeting is spread across five systems that were never designed to talk to each other. Here is what that costs, and what the Meeting Pass does instead.

The problem

The meeting lives in five places.

The invitation sits in a calendar, the approval in an email thread, the room in a booking tool, the minutes in someone's notebook and the action items in a chat group. Nothing reconciles.

With MeetPass

One Meeting ID holds the invitation, the approvals, the room, the agenda, the attendance, the minutes and every follow-up — one record, one place.

The problem

Attendance is whatever the list says.

The attendance sheet is copied from the invitation list. Who actually walked in, who sent a delegate and who never arrived is guesswork by the time the minutes are written.

With MeetPass

Attendance is taken from the signed QR scan at the gate. It is recorded, not claimed — and it lands on the minutes automatically.

The problem

Minutes die in one person's inbox.

A delegate attends on behalf of their ministry or company, receives the minutes, and never forwards them. The organisation loses the record of a decision it was party to.

With MeetPass

The signed MOM is sent to every attendee and to the registered head-office address of each organisation represented — institutional memory, not personal memory.

The problem

External attendees arrive unscreened.

The meeting is booked in one system and security learns about the visitor at the gate. Screening happens under time pressure, in front of the guest.

With MeetPass

External attendees run through the same pre-approval, identity verification and watchlist screening as a Visitor Pass — cleared days before they travel.

The problem

Every follow-up starts from zero.

The second meeting cannot see the first. Context is re-explained, decisions are re-litigated and the open action items are whatever someone remembers.

With MeetPass

Follow-ups thread to the original Meeting ID. The next session opens with the last agenda, the last decisions and every task still outstanding.

How it functions

Seven stages. One continuous record.

Follow a Meeting Pass end to end. Pick any stage — it runs on its own if you leave it alone.

Stage 01 · Create

One meeting, one ID.

A host schedules the meeting, or a guest requests one through the Guest Portal. MeetPass issues a single Meeting ID that every session, room, attendee and document attaches to for the life of the engagement.

  • Meeting ID issued the moment the meeting is created
  • Raised internally by a host or requested externally by a guest
  • Concurrent and recurring sessions share the same ID
  • Classification set up front — open, internal or privileged
Everything on the pass

What a Meeting Pass actually carries.

Grouped by when you use it — before the room, inside it, and after everyone has left.

Before the meeting

One Meeting ID

A single identifier binds every session, room, document and attendee — including concurrent sessions running under the same engagement.

Co-hosts & co-guests

More than one host, more than one guest representative — each with defined rights over the agenda, the minutes and the attendee list.

Room booking

Book against live room availability and capacity, with equipment and layout held on the same record.

Location & directions

The exact building, gate and parking, with a map and access instructions attached to the invitation.

Weather at the window

The forecast for the meeting time, so travel and dress are not a guess for a visiting delegation.

Agenda builder

Build, circulate and version the agenda. Lock it before the session so the minutes have a fixed structure to sit against.

In the room

Verified attendance

Attendance comes from the signed QR scan at the door — the same credential that opened the gate.

Attendee profiles

Role, organisation and LinkedIn profile for every attendee, so nobody walks into a room not knowing who is across the table.

Live Minutes of Meeting

Minutes captured against each agenda item while the meeting runs, with decisions and owners marked as they are agreed.

Privileged sessions

Closed sessions restricted to cleared members, with the minutes segregated from the general record.

After the meeting

Digital signature

The chair — and attendees where required — sign the MOM digitally. Every signature is timestamped and audited.

MOM to the organisation

The signed minutes go to each attendee and to the head-office address of every organisation represented, automatically.

Tasks & action items

Each action item becomes a task with an owner, a due date and a status that survives past the meeting.

Analytics

Meeting volume, room utilisation, attendance rates, decisions logged and action items closed.

The mechanism

One Meeting ID, however many rooms.

A negotiation that runs as four parallel sessions in four rooms is still one engagement. So it gets one Meeting ID. Each session keeps its own agenda, attendees and minutes — and all of them roll up to the same record, the same task list and the same history.

  • Concurrent sessions share the parent ID and roll up together
  • Recurring engagements thread every instance to the same ID
  • Follow-ups open with the previous decisions already loaded
  • One audit trail across every session under the engagement
Meeting ID MP‑2026‑0417
  • Session A · Boardroom 4Minuted
  • Session B · Room 2.1Minuted
  • Session C · Room 2.2In progress
  • Follow-up · 12 MayScheduled
9 action items · 3 open · 1 signature pending
The difference nobody else makes

The minutes reach the organisation — not just the person.

A delegate attends on behalf of their ministry, authority or company. When the minutes are signed, MeetPass sends them to that delegate and to their organisation's registered head-office address. If the individual moves on, forgets or simply never forwards it, the organisation still holds the record of a decision it was part of.

  • Institutional memory — the record belongs to the organisation
  • Sent on signature, not on someone remembering
  • Delivery is logged against the meeting record
  • Head-office address held per organisation, not per attendee
Minutes of Meeting Signed by the chair
Every attendeepersonal inbox
Every organisationregistered head office
Meeting Pass FAQ

Questions about the meeting record.

Yes. A walk-in can be raised at the desk in a few taps and still produces the same record — verified attendee, agenda item, minutes and any actions. You do not lose the audit trail because the meeting was not scheduled.

The chair or a delegate you nominate. The signature is captured digitally against the specific minutes, and the signing event itself is written to the audit trail with the signer and the timestamp.

Nothing breaks. The pass opens in any mobile browser from a link sent by SMS or email, and attendance is still taken from the gate scan. The app is a convenience for hosts and frequent visitors, not a requirement.

Yes. Where a delegate attends on behalf of their organisation, signed minutes can be sent to that organisation's nominated address automatically — with consent, and with the delivery logged against the visit.

The invitation list records who was asked. Attendance is taken from the signed pass scanned at the gate, so the minutes record who was actually in the room. The two are stored separately and both are retrievable.

See a Meeting Pass run end to end.

Book a briefing and we will walk a real engagement through all seven stages in your environment.