LunchLink workplace catering guide
Office catering policy template: orders, caps, approvals and billing
Copy this office catering policy template to define who can order, per-head caps, approval thresholds, P-card use, invoice rules, records, and exceptions.
LunchLink Editorial Team
Research and writing
LunchLink Catering Planning Team
Operational review
Direct answer
The short answer
An office catering policy should say who may order, which meal occasions are allowed, what per-head or per-event cap applies, who approves exceptions, whether the order uses a P-card or invoice, what records are required, and how dietary, delivery, tax, tip, cancellation, and recurring-meal questions are handled. Keep the policy short enough for office managers to use, but specific enough that finance can approve the spend before the meal is ordered.
At a glance
Key takeaways
- Name the order owner, finance approver, onsite receiver, and backup before any meal is requested.
- Use per-head caps as planning controls, not proof that a current menu will fit the final budget.
- Separate P-card rules for small approved meals from invoice rules for larger, recurring, or PO-coded programs.
- Require the catering brief, quote, approval, receipt or invoice, attendee purpose, and exception notes to stay together.
- Write an exception path for urgent orders, headcount changes, premium menus, dietary needs, and cancellations.
Copy this office catering policy template
Use the wording below as a starting point for an internal workplace policy. Replace every bracketed field with your company's finance, HR, procurement, tax, and records requirements before adoption.
Policy purpose: This policy controls company-paid office catering for meetings, training days, employee meals, client sessions, celebrations, and recurring office lunch programs. It is intended to keep meal requests useful for employees, comparable for vendors, and auditable for finance.
| Policy field | Template wording to adapt | Owner to confirm |
|---|---|---|
| Scope | Applies to company-paid catered meals, snacks, beverages, serviceware, delivery, setup, staffing, and related fees for workplace events. | Finance or operations |
| Authorized orderers | Only [roles or named teams] may place catering requests or approve changes with budget impact. | Department lead |
| Eligible occasions | Approved occasions include [meetings, training, client sessions, onsite team lunches, recurring meals, celebrations]. Personal events are excluded unless approved under [policy]. | HR or finance |
| Budget cap | Standard cap is [amount] per expected attendee and [amount] per event, inclusive or exclusive of [delivery, tax, tip, serviceware, staffing]. | Finance |
| Approval | Orders within cap require [approver]. Orders above cap, outside notice, or with premium service require written approval from [role]. | Finance approver |
| Payment route | Use P-card only for eligible one-time orders within [limit]. Use invoice or PO for recurring, multi-department, high-value, tax-sensitive, or contract-supported orders. | Procurement |
| Records | Attach the brief, quote, approval, attendee purpose, receipt or invoice, tax and tip details, and exception notes in [system]. | Finance operations |
Decide who can order and who can approve
A catering policy fails when everyone can request food but no one owns the count, budget, or delivery handoff. Give each meal one order owner, one approver, one billing contact, one onsite receiver, and one backup. The same person can hold more than one role only when the policy allows it.
Separate request authority from approval authority. An office coordinator may gather the brief and work with providers, while a manager or finance reviewer approves the spend. For recurring office meals, name the program owner and the backup who can act before cutoff.
| Role | Owns | Decision limit to define |
|---|---|---|
| Request owner | Brief, headcount, dietary collection, timing, room, provider questions | Can request options but cannot exceed cap without approval |
| Budget approver | Business purpose, cap, exception approval, final acceptance | May approve up to [amount] or [variance] |
| Finance or procurement | Payment route, tax, invoice coding, vendor record, records review | Decides P-card, invoice, PO, or vendor onboarding path |
| Onsite receiver | Delivery count, labels, room setup, issue escalation | May accept delivery but not approve paid additions unless authorized |
| Backup owner | Continuity when the owner is absent | Same or narrower authority than the primary owner |
Write per-head caps without creating a false price promise
A per-head cap is an internal spending control. It is not a guarantee that every current menu, delivery route, dietary requirement, service level, or tax treatment will fit. State whether the cap covers food only or the all-in cost.
Use different caps only when the difference is operationally real. A short boardroom lunch, all-day training, client reception, staffed buffet, and recurring employee meal may need separate limits because they include different responsibilities.
| Cap question | Policy choice to make | Why it matters |
|---|---|---|
| Food only or all-in? | State whether delivery, serviceware, staffing, rentals, tip, tax, and fees are inside the cap. | Prevents a low food subtotal from bypassing the real budget. |
| Per attendee or per event? | Use per-head for variable attendance and per-event for fixed receptions, snacks, or minimums. | Keeps small orders and large meetings comparable. |
| Expected or guaranteed headcount? | Define which count controls the cap and when it becomes final. | Avoids approving spend against an invite list that will not attend. |
| Standard versus exception? | Name the amount or percentage that triggers reapproval. | Protects finance when premium menus or late additions change the total. |
| Recurring cadence? | Set service, weekly, monthly, or department limits where meals repeat. | Controls programs without reapproving the same basic spend every time. |
Choose P-card or invoice before the order is placed
A P-card can be efficient for a one-time, low-risk catered meal that sits inside an approved limit and has a clean receipt. It is weaker when the meal needs a purchase order, multi-department coding, recurring billing, vendor setup, deposits, credits, cancellation records, or detailed tax review.
Invoice or PO handling is usually clearer for larger orders, recurring office lunch programs, client-facing events, production-style schedules, or meals where the payer needs one consolidated record. The policy should say when the organizer must use the invoice path rather than deciding after the meal arrives.
| Use P-card when | Use invoice or PO when | Always record |
|---|---|---|
| One-time order within cap | Order exceeds cap or needs preapproval | Business purpose and approver |
| Approved vendor accepts card with itemized receipt | Vendor setup, contract, deposit, or credit memo may be needed | Quote, receipt or invoice, and tax lines |
| One department owns the spend | Cost must be split by department, office, project, or cost centre | Coding and billing contact |
| No recurring cadence is expected | Daily, weekly, monthly, or program billing is expected | Service dates and accepted scope |
| No special cancellation or change record is needed | Change, cancellation, credit, or exception history matters | Final approved version and exception notes |
Define the approval workflow
The policy should identify the approval moment. Approving a budget range, approving a quote, approving a final order, and approving a day-of change are different controls. Write the minimum evidence required at each step.
For a simple one-time meal, approval may require a complete brief, current quote, cap check, and named receiver. For a recurring office lunch program, approval should also cover cadence, invoice cadence, employee selection method, dietary intake, cancellation rule, and review schedule.
- Brief approval: event purpose, headcount, timing, address, budget, dietary needs, and owner.
- Quote approval: menu, quantity, inclusions, delivery, serviceware, tax, fees, cancellation, and expiry.
- Order approval: final accepted version, final count, payment route, onsite receiver, and escalation contact.
- Change approval: who may accept additions, substitutions, rush charges, credits, or cancellations.
- Program approval: cadence, recurring cap, invoice path, feedback loop, and review date.
Require a complete catering brief for every approved meal
A policy should not ask finance to approve a vague lunch. Require the same basic brief for every request: date, eating time, delivery window, full address, room, headcount, dietary requirements, budget cap, serving format, business purpose, onsite receiver, and billing contact.
For LunchLink requests, this brief connects naturally to the office lunch and corporate catering service pages. The policy controls internal permission; the catering brief gives the planner the information needed to confirm current menus, prices, delivery, dietary handling, and terms.
- Date, eating time, and delivery window
- Expected attendance and final-count deadline
- Full address, entrance, floor, room, and onsite receiver
- Business purpose and eligible meal occasion
- Budget cap, approver, and payment route
- Dietary requirements and label needs
- Serviceware, setup, staffing, and cleanup expectations
- Invoice, PO, cost-centre, or P-card record requirements
Handle dietary needs and alcohol separately from the meal cap
Dietary requirements are not just menu preferences. The policy should require early collection, provider verification, labels, and a protected handoff for separately packed or sensitive meals. It should also state who may approve substitutions if the selected provider cannot verify a requirement.
If alcohol, branded items, gifts, or entertainment are ever included, handle them under a separate company policy. Do not let a general lunch cap silently authorize controlled categories that finance, HR, legal, or procurement would normally review.
- Collect only the dietary information needed for the meal.
- Do not infer allergen-free, gluten-free, halal, vegan, or other status from a dish name.
- Confirm ingredients, labels, substitutions, and kitchen limitations with the selected provider.
- Keep protected meals identifiable at receiving and distribution.
- Require separate review for alcohol, gifts, entertainment, or non-meal expenses.
Write the exception and cancellation rule before it is needed
Most policy disputes happen around exceptions: urgent orders, late headcount increases, no-shows, weather, room changes, premium menus, failed delivery access, cancellations, credits, or a senior stakeholder asking for a last-minute upgrade.
Create a small exception log instead of handling each case from memory. Record the requested change, reason, cost impact, deadline, approver, vendor response, and final outcome. This keeps repeat problems visible and protects the organizer from informal approvals that finance cannot reconcile later.
| Exception | Minimum record | Approver to define |
|---|---|---|
| Rush order | Reason, requested time, provider capacity, cost impact, and risk accepted | Budget approver |
| Headcount increase | Original count, new count, cutoff, incremental cost, dietary impact | Budget approver or program owner |
| Cancellation | Cancellation time, provider terms, food/labour committed, credit or fee outcome | Finance or order owner |
| Premium menu or staffed service | Business reason, full quote, included labour/equipment, all-in cost | Senior approver |
| Delivery issue | Access problem, delay, receiver, provider contact, resolution, service impact | Operations owner |
Keep records that finance can actually use
The record package should explain why the meal was allowed, what was approved, what was delivered, and how it was paid. An itemized receipt alone may not show business purpose, approver, attendee scope, invoice coding, tax treatment, or exception history.
Store records in one place. For recurring programs, keep the standing policy approval and the service-by-service confirmations together so invoice review does not depend on scattered messages.
- Business purpose and eligible occasion
- Approved brief and current quote
- Approver name, date, and approved limit
- Final order confirmation and change notes
- Itemized receipt, invoice, tax lines, tip or service charge
- P-card statement, PO, invoice coding, or cost centre
- Cancellation, credit, substitution, or complaint records
- Post-service notes for recurring programs
Adopt the policy without slowing every lunch
The best policy reduces repeated decisions. Put the standard caps, authorized roles, payment route, and brief fields in a reusable form. Then allow simple meals inside the rules to move quickly while routing exceptions to the correct approver.
Review the policy after several catered meals. Look for repeated exceptions, late approvals, budget mismatches, dietary fulfilment issues, delivery problems, and invoice corrections. Update the policy when evidence shows the rule is too loose, too strict, or unclear.
- Create one request form from the policy fields.
- Predefine standard approvers and backups.
- Use one central file location for records.
- Review exceptions monthly or quarterly.
- Update caps and payment rules only through the policy owner.
- Keep the public catering request separate from internal spend approval.
Frequently asked
Questions workplace planners ask.
It should define eligible meal occasions, authorized orderers, per-head or per-event caps, approval thresholds, P-card versus invoice rules, required records, dietary handoff, delivery responsibilities, cancellation rules, and exception approvals.
The policy must say so explicitly. Some companies set a food-only cap and review delivery, serviceware, tip, tax, staffing, and fees separately; others use an all-in cap. The important control is that organizers and approvers use the same definition.
A P-card is usually best for a one-time, approved, low-risk meal within a defined limit when the vendor provides a clean itemized receipt. Use invoice or PO handling when the order is larger, recurring, cost-coded, contract-supported, tax-sensitive, or likely to involve credits or changes.
The policy should name the budget approver for normal orders and the higher approver for exceptions. The order owner can prepare the brief, but spend approval should come from the person or role accountable for the budget.
Yes, but recurring meals need extra rules for cadence, invoice cadence, employee selections, cutoffs, dietary updates, cancellation credits, feedback, and budget review. A one-time lunch policy is usually not detailed enough for a recurring program by itself.
No. It is an operational planning template. A company's own finance, procurement, HR, tax, and legal reviewers should set the actual caps, approval authority, record-retention rules, tax treatment, and employee-meal policy.
