The common assumption about catering is that the money is in the big one-time events. Weddings, holiday parties, the occasional corporate blowout. Those are the orders people plan for.
The steadier money in most neighborhoods is a $340 lunch that shows up every Tuesday for nine months, ordered by a school office manager or a law firm administrator who wants to stop thinking about it. That business gets set up in August and early September, and it gets set up on the phone.
The buyer is not a customer, they are an administrator
The person calling you about a weekly lunch drop is not choosing a restaurant for themselves. They're solving a logistics problem on behalf of thirty or eighty people, and they will be blamed personally if it goes wrong.
That changes what they're listening for. Food quality matters, but it's assumed, because they've already eaten at your place or someone recommended you. What they're actually testing on the call is whether you can hit a fixed time every week, whether you'll invoice them or make them put it on a personal card, whether you can handle two nut allergies and a vegetarian without a conversation every time, and whether someone will pick up the phone if a delivery is late.
A restaurant that answers those questions crisply gets the account. A restaurant that says "let me have the owner call you back" often doesn't, because the administrator has three more names on the list and it's already 3:45.
The window is short and it opens early
Schools set up their year in the weeks before it starts, and offices tend to reset routines in the first half of September. The practical window runs from roughly the last week of July through the second week of September.
Inside that window, an administrator working through a list of restaurants makes calls during their own workday, which is often between 8 and 9 in the morning or in the mid-afternoon. Both are hours when many restaurants either aren't open or have nobody positioned to take a real conversation.
That is the mechanism by which most operators lose this business without ever knowing they were in the running. The call rang at 8:20, nobody answered, and the caller crossed the name off. If your phone doesn't cover the hours before service, after-hours phone answering is the specific problem to solve before the season starts, not a general nicety.
What has to be captured on the first call
The facts that make a recurring account work are different from the ones on a one-off catering order, and missing any of them tends to surface in week three rather than week one.
You need the delivery day and the exact time food must be on the table, which for a school is set by a bell schedule and is not negotiable. You need the building access details: which entrance, whether the driver checks in at a front office, whether there's a loading area, who signs. You need a named contact and a backup, because the person who ordered will sometimes be in a meeting when your driver is standing at a locked door. You need the headcount and how it varies. You need the dietary constraints as a written list rather than a verbal aside, since allergen and dietary questions handled loosely on a recurring account eventually produce a serious incident. And you need to know how they pay, since many institutional buyers work on invoices, purchase orders, or a card on file rather than paying at delivery.
That's a long list for a phone call in the middle of a lunch rush, which is why capturing it reliably is worth structuring rather than improvising. The same qualifying discipline described in catering lead qualification applies here, with the addition that the answers become a standing record rather than a one-time ticket.
Recurring orders should not be re-entered every week
Once an account is running, the weekly order is the same until it isn't. Somebody re-typing it every Monday is a defect waiting to happen, and the day it goes wrong will be the day the count changed and nobody caught it.
The workable pattern is a scheduled standing order with a confirmation step. The order exists on the calendar, someone confirms the count and any changes a day or two ahead, and the confirmation goes out in writing so the administrator has a record. Scheduling mechanics for orders placed well ahead of their fire time are in order ahead and scheduling, and the confirmation half is what SMS order confirmations handles.
The written confirmation matters more than it sounds. Administrators forward it. It becomes the paper trail that protects both of you when someone says the order was supposed to be for fifty.
Build the calendar around theirs, too. Schools have in-service days, early dismissals, testing weeks, and two long breaks, and none of those appear in your system. An account that gets a delivery on a day the building is empty has just cost you a full order and made your contact look careless to their own boss. Ask for the school calendar in August, put the closures on your own calendar then, and confirm the week before each break rather than discovering it from a driver standing in an empty parking lot.
Where these accounts actually die
Almost never in a fight. A recurring lunch account usually ends like this: a delivery is fifteen minutes late in October and nobody says anything. It happens again in November. In January the administrator calls a different restaurant, and you notice in February that the Tuesday order stopped.
Two things prevent that. Treat lateness on a recurring account as a real incident, with a call to the contact the same day rather than an apology at the next delivery. And have one direct conversation per term, not a survey, just a call asking whether the timing and the menu are still working. That conversation is also where you find out that the department is growing, or that they're planning something bigger in the spring.
If you want a single test of whether you're set up for this business, try it from the other side. Call your own restaurant at 8:15 on a weekday morning in late August and ask whether you can do a weekly lunch drop for forty people, delivered at 11:40, invoiced monthly, with a nut-free option. If nobody picks up, or if the answer is a callback promise, you already know why the account went somewhere else. The broader version of getting catering calls handled properly instead of squeezed between order-taking is in AI phone answering for catering orders.