“Around seven” was the first thing I crossed out.

It sounded friendly on the invitation. It gave me almost nothing to work with. The children would be hungry before then, one guest needed to leave by nine, and somebody else was driving in from out of town. They could all read “around seven” differently and be perfectly reasonable about it.

I had been asking “How long does a hibachi party take?” because I thought a duration would let me finish the invitation. What I actually needed first was a clear dinner time.

I could leave the rest of the visit fairly loose. I couldn't have half the group treating seven as the time to leave home while the other half expected to be eating.

The Guest Who Needed to Leave at Nine

I kept coming back to that departure time. It was a real limit, unlike most of the schedule I was inventing for myself.

A late meal at our hibachi birthday party could leave that guest missing the part I'd invited them to enjoy. Telling them we would have cake afterward didn't help much if they couldn't stay for it. I needed to explain the likely order of the evening and find out whether the meal itself fitted their plans.

There wasn't a useful promise I could make about exactly when every plate would be finished. I hadn't confirmed the cooking arrangement or how the group's choices would affect it. Saying we'd definitely be done by a particular minute would have been convenient for the invitation and rather less helpful on the day.

So I separated what I could tell people from what I still needed to ask.

The reservation time belonged in the message. The expected cooking and dining window was a question for the booking team. Cake could follow the meal without becoming another appointment everyone was obliged to keep.

I also checked the address against the Hibachi X service areas. There wasn't much point getting everyone's evening organized before confirming whether the requested location and date could be accommodated.

The guest driving from out of town needed those practical details more than a cheerful invitation saying we'd eat sometime that evening.

Twenty Minutes for Things That Weren't Dinner

I allowed twenty minutes between guest arrival and the reservation. That was my choice for this group, not an estimate of how long the chef would take.

I also needed to know what would happen if the out-of-town guest was late. I couldn't make that decision for the chef or promise the group we'd hold dinner. It was a question worth asking before putting a time in writing, rather than trying to negotiate a delay with hungry children already at the table.

People would put down bags, find drinks, settle the children, and decide where to sit. I know how easily those little jobs fill a gap. I didn't want to be looking for a chair while somebody was trying to bring cooking equipment through the entrance.

The arrival guidance in my planning notes mentioned roughly ten minutes before the reservation, with a short setup. I couldn't count those minutes twice. They weren't also time for me to move the table, lay out utensils, or ask where everyone wanted to sit.

I wanted the host's part finished earlier. Chairs in place, table ready, access clear. Then there could be a few ordinary conversations at the door without every one of them making us later.

The drinks table had to move, too. The patio was close to the kitchen, which normally made everything convenient. With cooking outside, a trip for another drink could take somebody straight across the working area.

Moving the drinks was a small job I could finish in advance. I preferred that to spending dinner asking people to take a different route.

I was trying to remove things I would otherwise have to interrupt the evening to sort out. I wasn't interested in announcing a new instruction every five minutes.

The Meal Choices Were Already Taking Up Time

One guest wanted to switch from chicken to steak after hearing another person's choice. That was exactly the sort of question I hoped to deal with before everyone was hungry.

I added it to the booking notes and went back to the menu. I wanted a clear record of the choices and any additions that needed confirming. I didn't need another round of suggestions just as cooking was due to start.

The menu wasn't something I could use to calculate the evening by myself. Counting courses or protein choices wouldn't tell me the provider's planned service time for our group. I needed to ask about that arrangement directly.

For guests, the useful message was simpler: arrive before dinner and have your meal choice settled.

If people wanted to come and go at unrelated times, I would consider a different kind of catering. Trays of prepared food would suit that sort of gathering more easily. With live cooking, I wanted people there to watch it, talk, and eat together. Otherwise, I wasn't sure why I was organizing that format.

That didn't mean everyone had to stay in the same chair all evening. I just didn't want to arrange the main activity for a time when half the guests couldn't be present.

Cake Could Wait Until We Had Eaten

I moved the birthday cake to after the meal. There was no need to stop cooking for another gathering around the table, then try to get everyone settled again.

I took other activities out of the dinner slot as well. A game could happen earlier or later. I wasn't going to ask the children to leave something they were enjoying just when the chef was ready, or ask the chef to wait while we finished it.

The booking inquiry included our guest count, the planned arrival period, the dinner time, and the early departure I was trying to accommodate. I asked what cooking and dining window to allow for that group.

I still hadn't given the party a precise finishing time. I had given people enough information to decide when to leave home and whether they could stay for dinner.

The revised invitation had two times instead of one vague phrase. I left cake after the meal, without a time beside it.