Back to the Business Playbook
    For established food-truck and catering operators

    Build a food-truck catering dessert package buyers can understand

    Turn one clear dessert experience into a proposal-ready scope: service window, planning estimate, menu, staffing, travel, power, terms, weather, and buyer paperwork—without turning an estimate into a promise.

    Planning guide and reusable template—not a Bloomjoy catering offer, quote, contract, price recommendation, booking forecast, serving guarantee, throughput promise, earnings claim, insurance interpretation, or legal advice.

    Proposal scope card

    One experience. Clear responsibilities.

    Scope

    What is included?

    Timing

    When is service open?

    Estimate

    What guides planning?

    Ownership

    Who provides what?

    Change

    What reopens scope?

    Paperwork

    What is due when?

    A useful proposal makes assumptions and decision owners visible before the event day.

    A different reader job

    This guide starts after you already run an operation.

    Use it to shape one dessert add-on for buyer proposals. If you are forming a portable event business, choosing initial equipment, or learning booking and event-day basics, the startup guide owns that path.

    Read the startup event guide

    Ten scope decisions

    Write the questions a buyer will otherwise ask at the worst time

    Each card separates the buyer’s question, the operator’s decision, and the claim boundary. The result is a concise scope—not a universal package policy.

    Scope 01

    Service window

    Buyer needs to know

    When is dessert service expected to open and close?

    Put in the outline

    State arrival, setup, service, last-order, and teardown windows separately enough that the buyer can plan the venue around them.

    Do not imply

    A scheduled window describes availability. It does not promise how many guests will be served inside that window.

    Scope 02

    Planning volume

    Buyer needs to know

    What guest or serving estimate should guide supplies and staffing?

    Put in the outline

    Record who supplied the estimate, when it must be updated, and how a material change affects the menu, staff, or scope.

    Do not imply

    Call it a planning estimate—not a guaranteed serving count, throughput rate, attendance forecast, or minimum demand.

    Scope 03

    Dessert menu

    Buyer needs to know

    Which one or two choices define the experience?

    Put in the outline

    Name the included menu, how substitutions are handled, when selections lock, and which custom requests sit outside the package.

    Do not imply

    Only offer patterns, colors, ingredients, packaging, or service styles the selected equipment and operating plan can support.

    Scope 04

    Staffing

    Buyer needs to know

    Who owns service, line direction, payment, restock, and breaks?

    Put in the outline

    Name the operator roles included and the buyer or venue roles required. Make any added-staff review trigger visible.

    Do not imply

    Do not infer a safe or guaranteed service rate from a machine cycle alone; the complete staffed workflow controls the result.

    Scope 05

    Travel and load-in

    Buyer needs to know

    Where does included travel end, and what must be true on arrival?

    Put in the outline

    Define the service area or trip basis, parking, access, stairs or elevators, arrival contact, unloading path, and delayed-access response.

    Do not imply

    Published machine dimensions or weight do not approve a transport, securing, mounting, or handling method.

    Scope 06

    Power and setup responsibility

    Buyer needs to know

    Who provides and approves power, placement, protection, and clearances?

    Put in the outline

    Put the agreed outlet or power source, complete-load review, placement, guest flow, weather protection, and venue sign-off owner in writing.

    Do not imply

    Machine volts and watts do not establish generator compatibility, installation approval, outdoor approval, or local acceptance.

    Scope 07

    Payment and deposit posture

    Buyer needs to know

    What confirms the date, and when is each payment milestone due?

    Put in the outline

    State the chosen deposit or retainer posture, invoice schedule, accepted method, taxes or fees, late-change treatment, and final due point.

    Do not imply

    This guide recommends no price, percentage, fee, refundability rule, or earnings target. Use terms reviewed for your business and jurisdiction.

    Scope 08

    Weather and operating conditions

    Buyer needs to know

    Which conditions trigger protection, relocation, pause, or a no-go decision?

    Put in the outline

    Define the decision owner, check time, indoor backup, shelter expectations, and communication path before the event day.

    Do not imply

    Do not imply that a venue, tent, forecast, or customer request makes outdoor operation acceptable for the equipment.

    Scope 09

    Cancellation and reschedule

    Buyer needs to know

    What happens when the date, scope, venue, access, or conditions change?

    Put in the outline

    Write the notice path, reschedule posture, date-availability rule, scope-change trigger, and treatment of committed costs in your own agreement.

    Do not imply

    Present a clear business term, not legal advice. Do not promise that every date or condition can be recovered.

    Scope 10

    Insurance, COI, and buyer paperwork

    Buyer needs to know

    Which documents or vendor steps must be complete, and by what deadline?

    Put in the outline

    Ask about certificate-of-insurance wording, additional-insured requests, W-9 or vendor forms, permits, access credentials, purchase orders, and invoice requirements.

    Do not imply

    A certificate is evidence requested by a buyer; it is not a Bloomjoy approval, coverage interpretation, permit, or promise of venue acceptance.

    Two planning structures

    Choose a commercial structure, then write its boundaries

    Per-serving and fixed-event are ways to organize a proposal. Neither one supplies a recommended price, protects margin automatically, or guarantees demand.

    Planning structure

    Fixed-event structure

    Useful when the buyer wants one understandable scope for a defined date, service window, menu, staffing plan, and setup responsibility.

    Must define

    • What the event scope includes and excludes
    • Which change requests reopen the scope
    • Travel, access, setup, and teardown boundaries
    • Payment, weather, cancellation, and paperwork terms

    “Fixed” describes the commercial structure, not guaranteed attendance, servings, throughput, operating conditions, or operator cost.

    Planning structure

    Per-serving structure

    Useful when the buyer and operator can agree on what counts as a serving and how the count will be observed without disrupting service.

    Must define

    • The exact included serving and counting method
    • Any planning minimum, cap, or reconciliation process you choose
    • Who can authorize a change during service
    • What remains fixed regardless of the final count

    A per-serving basis is not a recommendation for a unit price and does not convert an attendance estimate into a sales or serving guarantee.

    Responsibility map

    Make ownership visible before it becomes an event-day dispute

    Operator owns

    • The dessert menu actually offered
    • Named service and reset roles
    • Equipment, supplies, cleaning, and teardown inside the agreed scope
    • The operator’s own pricing, payment, insurance, and contract decisions

    Buyer or venue owns

    • Accurate event, venue, access, and guest-planning information
    • The on-site contact and agreed arrival path
    • Buyer-controlled approvals, paperwork, purchase orders, and deadlines
    • Any promised venue resource assigned to the buyer in writing

    Confirm together

    • Placement, guest flow, power, protection, and load-in responsibility
    • Service window, menu lock, estimate changes, and scope-change triggers
    • Weather decision timing and indoor-backup posture
    • Cancellation, reschedule, COI, and venue-document expectations

    Reusable package outline

    Copy the structure. Replace every assumption.

    This template is intentionally blank. It is not a Bloomjoy package, offer, contract, quote, price, policy, or performance promise. Your operation supplies the facts and terms; appropriate advisors review the decisions that need them.

    Working template

    Food-truck catering dessert package

    Package name

    [A clear buyer-facing name for this dessert experience]

    Event and venue

    [Date, venue, address, buyer contact, access notes]

    Dessert experience

    [One or two included choices; substitutions and exclusions]

    Planning estimate

    [Buyer-supplied guest/serving estimate; not a guarantee]

    Timing

    [Arrival / setup / service / last order / teardown windows]

    Staffing and flow

    [Operator roles, buyer roles, line and payment responsibility]

    Travel and load-in

    [Included basis, parking, unloading, access, delay trigger]

    Power and placement

    [Provider, complete-load review owner, location, protection]

    Commercial terms

    [Chosen pricing structure, deposit/payment milestones, changes]

    Weather and changes

    [Decision owner, check time, backup, cancel/reschedule posture]

    Buyer paperwork

    [COI wording/deadline, W-9, vendor forms, PO, permits, invoicing]

    Not included

    [Anything the buyer might otherwise assume is part of the package]

    Template only. A planning estimate stays an estimate; package wording does not certify equipment fit, local approval, coverage, servings, throughput, booking, revenue, margin, or event conditions.

    When cotton candy remains the fit

    Carry the scope into a machine-fit conversation

    Use the categorical checker before the quote. If the setup remains worth exploring, Bloomjoy can review a Commercial quote with mobile-food source context. Mini and Micro remain on their product purchase paths.