Pip: Welcome to the Globibo Blog recap — where corporate governance meets the internet, and somehow everyone ends up in the right Zoom room.
Mara: Today we're looking at what it actually takes to run a high-stakes virtual AGM for a publicly listed company — the logistics, the voting layers, and the coordination work that keeps it from falling apart.
Pip: Let's start with the meeting itself.
Running a Virtual AGM for a NASDAQ-Listed Company
Mara: The question here is what "reliable" actually means when a NASDAQ-listed company needs to conduct its Annual General Meeting in a fully virtual environment — shareholders, auditors, regulators, and share registrars, all in one structured digital space.
Pip: Globibo sets the stakes early in the post: the client "placed strong emphasis on consistency, governance, and effective coordination among stakeholders across regions, including regulators and share registrars." That's not a one-time setup — that's a five-year relationship built around repeatable execution.
Mara: Right, and the scope reflects that. Services covered registration management, video conferencing integration, speaker coordination, voting administration across both pre-event and live voting, Q&A management, audit reporting, event analytics, participant support, and a full AGM recording. That's the full event lifecycle, not just a platform hand-off.
Pip: The platform hand-off is actually where things get interesting — or at least where they get complicated.
Mara: The trickiest operational challenge was the voting structure. The AGM ran three distinct voting groups: the Board of Directors, shareholders who had submitted votes in advance, and shareholders participating in live voting during the meeting. Some individuals belonged to more than one group simultaneously.
Pip: So the same person might be a board member who also pre-voted and wanted to vote live. That's the kind of overlap that quietly derails a compliance-sensitive event if nobody catches it.
Mara: Globibo caught it. The post describes how the team identified all overlapping participants, flagged them to the client, and structured separate registration confirmation templates for each group so every attendee received communications matched to their actual role and voting status.
Mara: The team fielded this with three remote roles: a technical support lead managing platform infrastructure, a streaming manager coordinating live slide sharing and scripting with the client, and a participant support role handling the technical chat during the event itself.
Pip: Thirty participants, four pieces of equipment, two hours — and a 99% recommendation rate. Small event, high stakes, tight margins for error.
Mara: The post frames the outcome plainly: participants could engage, access relevant information, and complete voting activities as planned. For a governance event, that's exactly the bar.
Pip: Governance at a distance turns out to require more scaffolding than most people expect — the voting overlap alone could sink an unprepared team.
Mara: Next time we'll see what other operational territory the blog is covering. Stay with us.
