Caterers: Your Event Sheets Are Eating Your Saturday

It is Saturday morning. You have got a wedding for 120 on Sunday, a corporate lunch Tuesday, and a christening the week after.

And where are you? At the kitchen table with a laptop, rebuilding the same four documents you rebuilt last week. Run sheet. Kitchen prep list. Staff rota. Packing list.

Same event. Same details. Typed FOUR TIMES.

You already have the information. Guest count, menu, venue, arrival time, dietaries, kit list. It came in on an enquiry form or an email or a phone call you scribbled on the back of an invoice. And now you are copying it, by hand, into four different templates, because that is how you have always done it.

I know what your Saturday looks like. I know you told your kids you would be done in an hour. I know you were not.

The Number You Have Never Actually Worked Out

Let us do it now. Right now.

One event, properly documented, four documents. If you are fast, forty five minutes. Realistically an hour and a half, because you are cross checking allergies against the menu and trying to remember if the venue at Kingsway has a service lift.

Six events a week? That is NINE HOURS. Nine hours a week rebuilding documents from information you already typed once.

Over a year that is more than four hundred hours. Four hundred. That is TEN WORKING WEEKS of your life spent as a copy and paste machine.

And price it honestly. Not at minimum wage. Price it at what you are actually worth, because the person doing this is usually the owner, the person who could be out winning the corporate contract that changes the year. At fifty an hour that is twenty grand of your time. Every single year. Gone into retyping "vegetarian x4, one coeliac" into a document that already exists somewhere else.

And here is the part nobody says out loud. The retyping is where the MISTAKES live. The nut allergy that made it to the run sheet but not the kitchen prep list. The chafing dishes that were on last week's packing list and did not get carried over. Every manual copy is a coin flip.

Your Excuse, And Why It Is Rubbish

"Every event is different."

No. Every event has different VALUES. The structure is identical. You are not reinventing anything, you are filling in the same boxes with different numbers. You have been calling repetition creativity because it makes the Saturday feel justified.

"I do not have time to sort this out."

You do not have time NOT to. You are spending nine hours a week to avoid a fix that takes weeks to put in. That is not a time problem, that is a maths problem.

"Software for caterers is expensive and I would have to move everything."

This is the real one and it is the most honest one. You have looked at the big platforms. Thousands a year, six weeks of setup, and you have to abandon the spreadsheet you have been refining since 2019. So you closed the tab and went back to the kitchen table.

Fair enough. That is genuinely a bad deal. But it is not the only deal.

Here Is What Netforge Would Actually Build You

No new platform. No migration. You keep your spreadsheet, your inbox, your calendar, your invoicing tool. We build around them.

Here is the shape of it.

One place where event details go in. ONCE. A simple form, or your existing enquiry form, or a row in the spreadsheet you already live in. Client, date, venue, guest count, menu selections, dietaries, staffing level, kit required. You fill it in when you take the booking, which you are doing anyway.

Then you shut the laptop.

And overnight, the thing we built for you goes to work. It takes those details and generates your run sheet in your format with your timings, built off your standard timeline rules, so a 6pm service means canapes at 6:15 and speeches at 7:30 without you calculating backwards again. It builds the kitchen prep list, portions scaled to head count, allergen lines flagged in red and separated out so nobody misses them. It builds the staff rota against the hours the event actually needs, pulling from your team list and their availability. It builds the packing list from the menu and the venue notes, because it knows a plated dinner at a dry hire site needs different kit than a buffet at a hotel.

Four documents. Formatted the way you format them. In your drive, in your folder structure.

And Monday morning, the chef gets the prep list in their inbox. The team gets their shifts on their phones. You get one message that says "Sunday's docs are ready" with the links.

That is event run sheet automation and kitchen prep list software and staff rota automation, except it is not three products you have to buy and glue together. It is one thing we build, sized to you.

Change the guest count on Thursday because eight more people confirmed? Every document updates. Portions, staffing, packing. You change one number, not four documents.

That is the fix. And it is not clever, it is just not being done, which is why it is worth so much.

How This Actually Goes With Us

It starts with a free chat. Not a demo, not a deck, not a salesperson with a script. You get on a call and describe what is eating your week, and we ask a lot of questions. What does an enquiry look like when it lands? Where does it go? What do you touch it with? Who else touches it?

And sometimes the answer we give you is not the one you came in with. You might come in saying the run sheets are the problem, and forty minutes in it turns out the run sheets are fine, but you are chasing final numbers from clients five days out and THAT is the thing wrecking your week. We will tell you. We would rather fix the real thing than sell you the thing you asked for.

Then we build a small first piece. Small on purpose. Sized to what you can actually spend, because you run a catering business, not a venture fund. Maybe it is just the prep list and the packing list to start. It plugs into what you already use. Nothing gets ripped out.

You see it running within weeks. Not quarters. WEEKS. On a real event, with real numbers, and we sit with you while it goes through its first few bookings and we fix what is off.

Then we hand it back working and we do not vanish. Netforge is a small senior team, so the person who built it is the person who picks up the phone. There is no ticket queue between you and the human who wrote the thing.

And once that first piece is paying for itself, and you can see it clearly on the clock, we grow it. Quotes. Client confirmations. Supplier ordering off the prep list. Whatever the next biggest hole is.

Macro patience, micro speed. Small pieces, shipped fast, that compound.

Picture The Tuesday

Booking comes in Tuesday at 4pm for a sixty head corporate lunch.

You spend four minutes filling in the details. You close the laptop. You go home.

Wednesday morning everything exists. Run sheet, prep list, rota, packing list. Team notified. Chef already ordering.

That is it. That is the whole transaction.

And that Saturday you used to lose? It is yours. Go to your kid's game. Go visit the venue you have never actually walked. Call the three corporate clients you have been meaning to chase for six months, because THAT is the work that grows a catering business. Catering admin work does not grow anything. It just stops you drowning.

Here is the thing about small business automation that people miss. It is not about the hours. It is about what you do with them. Nine hours a week of owner time pointed at growth instead of formatting is the difference between a business that plateaus and one that doubles.

Do This Today

Open the last event you catered. Count the documents you built by hand. Write down the minutes. Multiply by how many events you did this month.

Look at that number. Sit with it for thirty seconds.

Then book a free chat at netforgestudio.com and tell us what your Saturday looks like. No pitch, no pressure. We will ask questions, tell you honestly what we would build and what we would not, and if it is not worth doing we will say that too.

You have got a busy season coming. You can go into it retyping the same details four times like last year.

Or you can spend twenty minutes on a call and go into it with the documents building themselves.

Execution. That is the only bit that has ever mattered.