# How to Organize a Corporate Event in 2027

> Organize a corporate event in 2027: choose the format, get sign-off, work with procurement, control who attends, rehearse the door and report to management.

Source: https://laces.run/blog/how-to-organize-a-corporate-event-2027 (HTML version of this page)

To organize a corporate event in 2027, get the business reason, the budget owner and the guest rules agreed first, then build backwards through procurement, invitations and the door. Unlike a public event, your hardest deadlines are usually internal: sign-off, purchase orders and a senior person's diary. This guide focuses on working inside a company, in any country.

[Create your event](https://laces.run/app): Set up the event, share one link and see who is coming as they register. Creating it is free.

If you are planning in Uganda, also read our [corporate event planning guide for Uganda](https://laces.run/blog/corporate-event-planning-uganda), which covers local payments and the reports you can pull.

## Match the format to the business reason

"We need an event" is not a brief. Each common format serves a different purpose, and each is judged differently.

| Format | What it is for | Judge it by |
| --- | --- | --- |
| Staff day or retreat | Alignment and morale | Attendance across teams, what staff said afterwards |
| Training day | A specific skill or process | Who completed it, and whether the work changed |
| Client appreciation | Keeping relationships | Which key accounts came, follow-up meetings |
| Product launch | Awareness and leads | Named prospects, press coverage, follow-up requests |
| Paid industry conference | Income and reputation | Paid delegates, sponsor renewals. See our [conference guide](https://laces.run/blog/how-to-organize-a-conference-2027) |

Pick the measure now, because you cannot collect some data after the day.

## Get a one-page sign-off

A single page saves weeks of emails. It should name the purpose and measure, the date with one fallback, the guest count range, the total budget and its cost centre, one budget owner, and anyone who must approve speakers, branding or messaging.

Get it signed by whoever can stop the event, not just whoever asked for it. Late objections usually come from people who were never asked: legal, communications, or the executive who is meant to speak.

**Book the senior speaker first.** If the event depends on one person, lock their diary before you pay any deposit, and agree who stands in if they are called away.

## Allow time for procurement

Company events run on a supplier process that public events do not have. Ask your finance team these questions in the first week:

- Does each supplier need to be registered with us before we can pay them?
- How many quotes do we need, and above what amount?
- How long does a purchase order take to raise?
- How long after an invoice do we pay, and will the supplier accept that?
- Who signs venue contracts, and does legal need to read them?

Venues often want deposits sooner than a company's payment cycle allows. Find that gap early, and agree the deposit date before you confirm the booking.

If you are also selling tickets, do not plan supplier payments around ticket money you have not received. If the event is cancelled, you owe refunds to participants, even on money already withdrawn.

## Decide who is paying for guests

This choice shapes your registration setup.

**The company pays, and guests attend free.** Create a free ticket with the places you have invited. There is no service fee on free tickets, and guests still get a QR ticket. Your organization still needs Laces payment clearance before registration opens, even for a free event, so apply early.

**Guests or their employers pay.** The participant pays the service fee on top of your price, and you receive the full ticket price. The methods depend on the country: MTN MoMo, Airtel Money and cards in [Uganda](https://laces.run/pricing/ug), M-Pesa and Airtel Money in [Kenya](https://laces.run/pricing/ke), MTN MoMo, Telecel Cash and AT Money in [Ghana](https://laces.run/pricing/gh), MTN MoMo and Airtel Money in [Rwanda](https://laces.run/pricing/rw), and MTN MoMo, Airtel Money and Zamtel Kwacha in [Zambia](https://laces.run/pricing/zm).

**A mix.** Free and paid tickets can sit on the same event, each with its own number of places.

One person can book several colleagues on one order and pay once. Each gets a QR ticket. Ask them to enter every name, because a blank one goes in the buyer's name. Each order gets a receipt, not a tax invoice, so a client who needs an invoice has to be handled outside checkout.

## Control who attends

Be realistic about this, particularly for a staff-only or client event.

- **Treat the event page as public.** Anyone with the link can open it, and events from a cleared organization can appear on the public [events page](https://laces.run/events). Keep a confidential product name, a client list or an unannounced speaker off the page. If an event must stay out of that listing, [ask us](https://laces.run/contact) before you publish.
- **There is no approval step.** Laces does not check each registration for you. If attendance must be approved person by person, do that before you send the link.
- **Use capacity as your fence.** Cap the free ticket at the number invited, so a forwarded link cannot overrun the room.
- **Decide about strangers now.** Agree what the door team does when a name on the list is not one you expected: admit them, or send them to the host.

Collect only what the event needs. Organization and dietary needs are reasonable questions. A home address rarely is. Ask your compliance lead to check your plan against the data protection law where you operate, and do not share the list with partners without the guests' consent.

[Talk to the team](https://laces.run/contact): Send them to us with your event details. We will tell you plainly what Laces does and does not do.

## Rehearse the awkward arrivals

A corporate door has different problems from a public one, because the people involved may be your clients or your boss. Walk your team through these cases before the day.

| What happens | What to do |
| --- | --- |
| An assistant booked for the executive, under the assistant's own name | Find the order by code or name, and let the help desk sort it out |
| A client arrives with an unregistered colleague | Follow the rule you agreed. If you can admit them, have them register on their phone from your link while registration is open, so they join your list. Otherwise note them on your own guest list |
| A phone is dead or the email cannot be found | Search by name or order code in the app |
| The scanner says "Could not check that ticket" | Try again. It means the lookup failed, not that the ticket is invalid |
| The same ticket scans twice | The screen shows the earlier check-in time. Send it to the help desk rather than debating it in the line |
| A VIP should not queue | Plan a host and a separate entrance, and scan them there |

Scanning needs a data connection, so test the venue network at the same hour as your event. Corporate venues often have guest wifi behind a login page, so try it on the actual scanning phones. Keep a mobile data backup.

Give access by job. Invite your team through the app, keep revenue with finance, admin and owner roles, and limit temporary door staff to this one event. Volunteers see no revenue.

## Write the report before the event

Draft the management report with blank figures a month before. Empty cells show what you still need to capture.

A useful report compares the goal on your sign-off page with what happened. Include the invited count, registered count, arrivals, budget against actual spend, and two or three plain lessons. Page views and social reach rarely answer what management asked.

From Laces, the app's orders file gives you paid orders, participants and money collected, followed by one row per order showing the buyer. A group booking is one row, so count people from the participants total rather than from the rows. A separate CSV lists each paid participant by name, phone and ticket type. Neither file holds answers to your questions. If you need an arrivals figure, confirm how to get it from your check-ins [with our team](https://laces.run/contact) before you promise it. For how the records fit together, read about [managing registrations, payments and attendance](https://laces.run/blog/manage-event-registration-payments-attendance).

Within a week, pay suppliers, close the purchase orders and send the report while people still remember the day.

## Frequently asked questions

### Does a free staff event still need payment clearance on Laces?

Yes. Registration stays closed until your organization is cleared, even on free tickets. It costs nothing, but a person reviews it, so apply early.

### Can we make registration invitation-only?

Laces has no approval step. Share the link only with the people you invite, cap the ticket at that number, and agree a rule for unexpected names at the door.

### Can guests register without an account?

Yes. Guests register from a link, with no app or account. They get their ticket by email.

### Will a company get a tax invoice from Laces?

Each order gets a receipt by email and on the ticket page. It is not a tax invoice, so plan for that with any client who needs one.

### How is this different from your Uganda guide?

This one is about running the event inside a company in any country. The [Uganda guide](https://laces.run/blog/corporate-event-planning-uganda) goes deeper on ticket types, roles and reports there.
