I Thought Choosing Dinner Would Take Five Minutes. Then I Sent the Menu to My Family.

The hibachi catering menu was open on my phone in the supermarket beside the paper plates. My niece's birthday was four days away. Nine people were coming. One more might come after work.

I thought the food decision would take five minutes.

Chicken for the children. Steak for my brother. Shrimp for my mother. Something without meat for one guest. I was already arranging the answer in my head when my sister asked about noodles.

Then my mother called.

"If I choose steak and shrimp, is that two choices?"

I looked at the little line on the menu and could not tell. I promised to check before she picked.

The first reply looked useful. It was not.

I sent the menu to the family group chat on Monday morning. My brother replied "steak" so quickly that I assumed he had not read the rest. My niece picked chicken. Her younger brother copied her. My sister wanted noodles. Someone sent a lobster emoji and disappeared.

The guest who did not eat meat said nothing.

That last part bothered me. The people typing the most were not necessarily the people I had to plan around most carefully.

I put a small star beside that name so it would not disappear beneath the louder requests.

At home, I opened a notebook. The first page already had errands on it, so I turned it over. No spreadsheet. No color system. The pen was almost dry.

The base meal described by Hibachi X includes two protein choices per person, fried rice, vegetables, and a side salad. I wrote that across the top of the page. Under it, I put chicken beside the children, steak beside my brother, and a question mark beside my mother.

Her request was probably simple. I just did not want to turn "probably" into a promise.

I left three questions underneath:

Does steak and shrimp fit within the two choices?

What happens if someone wants another protein?

Are noodles part of the regular meal?

I left those questions on the page and stopped asking the group chat to solve them.

My mother was not trying to make the order fancy

I had put a small star beside my mother's name because I assumed steak and shrimp meant an upgrade. Then I thought about it again. She was not building a luxury meal. She liked both and did not want to pick one.

The Hibachi X menu lists two protein choices per person. Her combination may fit. I still planned to ask before confirming it.

I did not write, "Mom's order costs extra." I wrote, "I am checking how the two choices are counted."

After that, I looked at the other choices with less drama. Chicken, steak, shrimp, scallops, and tofu may be available. For my table, chicken and steak covered most people. Shrimp covered the seafood requests. Tofu covered the one guest who asked for it.

The lobster question kept returning. My cousin sent a picture. My brother asked about filet mignon. Noodles appeared again while I was washing a mixing bowl.

Filet mignon, lobster, an additional protein, and noodles may be available as upgrades. I put them in the margin instead of making them the center of the order. One special item for the birthday girl could be nice. Or I could spend that money on cake, drinks, or the chairs I still needed to borrow.

No guest would know which steak was the expensive one. The vegetarian guest would know if I had not thought about her food until the last minute.

That was how I ranked the choices.

The quiet request became the important one

The guest who did not eat meat finally replied after I wrote to her separately. Tofu was fine. She wanted to know whether she needed to say anything ahead of time. I moved that question to the top of the page.

I had been treating the menu like a list of things people could point at. For a group dinner, I also had to remember who needed what. I wrote one clear note for the booking details. The seafood request went underneath it: shrimp, but not a heavy plate. Another person was happy with whatever was easiest.

The patio rejected my first plan

On Tuesday, I carried the notebook outside. The patio table was too close to the side gate, and the cooler was in the walking path. Two chairs would face the side of the grill.

I moved the table toward the fence. That blocked the driveway. I moved it back. The final arrangement looked slightly crooked. It worked.

Hibachi X brings the chef, grill, food, sake, and entertainment. I still provide the tables, chairs, utensils, drinks, and table setup. Drinks beside the cooking area would create a constant reach across the grill. A blocked view would put the children on their feet.

The patio made those decisions for me.

Live cooking also gave the dinner a schedule. A late guest might miss part of it. Someone leaving early would change the timing. If I only wanted food on the counter, drop-off catering would be simpler.

For this birthday, I wanted people to stay near the grill. That was the part I could not get from a regular tray.

I sent questions, not a perfect order

By Wednesday, the group chat could stay unfinished. I had the date, address, guest count, main protein choices, and one vegetarian request.

I checked the current service areas, then put the details into the booking page. My message asked how the two proteins were counted, which upgrades were available, and how to note the mixed group.

The phrase private chef hibachi menu had sounded like something I would search once and understand. In practice, it became a stained notebook, a crooked patio table, and five questions.

I still did not know who sent the lobster emoji. I decided that could wait.