Why I created GroupGrid

In my first job, I cross-checked event travel with a ruler and a stack of printed sheets. Years later I had outsourced it to vendors, and it still swallowed weeks. We would be reconciling rooming lists, shuttles, and flight bookings right up to the deadline, which is exactly when a mistake costs the most. I could not find software that solved it, so I built it.

The problem never really changed

Every event I ever ran came down to one nervous question in the final stretch: did everyone actually get booked? The answer lived in five places that never agreed. Registration in one export. The flight manifest in another. A rooming list from the hotel. A transfer schedule from the ground vendor. Each file looked fine on its own. The trouble hid in the space between them.

That is where the expensive surprises come from. A guest registered but with no flight on file. A hotel room reserved for someone who cancelled back in March. A VP whose plane lands the day after their room was held. None of it looks like a crisis in a spreadsheet. It looks like a crisis at the front desk, on arrival day, when there is nothing left to do but pay to fix it.

The ruler eventually became VLOOKUPs, and the printed sheets became a dozen browser tabs. The tools got better. The job did not. I was still reading four lists by eye, trying to notice the one thing the eye is worst at noticing: something that is missing.

What GroupGrid actually is

GroupGrid is the cross-check layer between your event systems. It is not another spreadsheet, and it is not a full event platform trying to replace the tools you already have. It sits between them and does the one job those tools never do for each other: it puts every attendee on a single grid and checks each record against the next.

You upload the lists you already keep. Registration is your source of truth, then you add the travel files: flight manifest, hotel roster, car transfers, and abstracts if you have them. Column names do not matter. GroupGrid matches everyone by email first, then by name, and shows you exactly what lines up and what does not.

The output is plain. Most of your list is fine, and GroupGrid says so and gets out of the way. What is left is the short list that needs a human: registered but not booked, booked but never registered, dates that do not agree, someone routed to the wrong airport. Each flag names the record and the gap, so you are not guessing. Check-in December 4, room booked December 5. That kind of specific.

From days to minutes

The whole point is speed, because speed is what makes a problem fixable. Catch a wrong date six weeks out and it is a two-line email. Catch it the night before and it is a change fee, a scramble, and a guest who remembers it. GroupGrid runs the check in the time it takes to upload the files, which means you can run it early, run it weekly, and run it again the week of, instead of saving it all for one long night at the end.

When you find something, you can act without leaving the app. Draft an email to the guest or the hotel, add a note, mark it resolved, and export a clean report for whoever needs it. The reconciliation stops being the thing you dread and becomes the thing you barely think about.

Who it is for

If you are responsible for getting a group of people to the same place at the same time, GroupGrid is built for you. In practice that has meant:

• Event and meeting planners running conferences, user summits, and multi-day programs where arrivals spread across days and the room block has to hold.
• Corporate travel managers who need group travel to stay on policy and on budget, with a defensible record of what was flagged and fixed.
• Executive assistants managing C-suite travel, where one missing room or a flight that lands after check-in becomes a very visible problem.
• Sales and revenue teams getting hundreds of reps to a kickoff in one tight arrival window.
• Pharma and healthcare teams hosting HCPs, where a booking error also distorts the spend you have to report.
• Incentive and President’s Club programs, where the trip is a reward and the logistics have to feel flawless.

Different events, same underlying need. Somebody has to know that what is on the list actually happened.

The promise I wanted for myself

I built the tool I kept wishing someone would hand me. The promise is simple, and it is the one I could never quite give myself with a spreadsheet: did all 300 actually get booked? Now you will know, before anyone travels, while there is still time to fix the few that did not.

That is really all GroupGrid does. It makes the invisible visible, and it does it in minutes. If you have ever stared at four lists at midnight hoping you did not miss anything, I made this for you.