Industries

Plan restaurant content around the shots you actually need

A shoot can leave you with attractive food photographs and still miss the horizontal image needed for a menu page, the preparation sequence needed for a short video, or a clear view of the dining space. The problem starts before the camera arrives. Restaurant content production needs a defined use for each asset, a workable kitchen schedule, and clear decisions about what belongs in the frame.

If search work is part of the scope, our website rule applies. We only do SEO on a site we built.

Ninetyfifth Marketing would propose a production brief that connects those decisions. We would map the intended placements, identify the dishes and spaces to capture, and define the files required at handover. Photography, video, styling, editing, and caption preparation would be itemized according to the agreed assignment. The restaurant would approve the representation of its food and service.

Start with an asset list, then build the shoot

The first conversation would concern usage. A website header, a menu detail, a vertical social clip, and a printed card each place different demands on composition and delivery. We would ask where the content is intended to appear, whether text must sit over an image, and which placements need room for cropping. That information would shape the capture list.

We would distinguish required assets from optional variations. A required image might show a complete dish in its standard presentation, while an optional frame might explore a closer texture or a different angle. This distinction would appear in the production plan, along with the person authorized to resolve tradeoffs if kitchen timing, access, or available light changes.

Specify the deliverable before discussing quantity

A file count alone does not define a content package. We would specify how many distinct subjects are proposed, what counts as an alternate crop, whether video edits include different durations, and which versions require captions or on-screen text. Draft selection galleries, final edited files, source footage, and working files would be addressed separately in the scope.

Give each dish a place in the production order

A food capture plan would account for preparation time and how the dish changes after plating. The chef or designated kitchen owner would advise on items that need immediate attention, components prepared in advance, and dishes that cannot reasonably be produced together. We would use that information to propose an order of capture and a plating approval point.

The brief would also identify the intended serving vessels, garnishes, portion presentation, and supporting table items. Any styling choices that alter the expected presentation would require restaurant approval. Questions about safe handling, holding conditions, ingredient descriptions, or food suitability would remain with the qualified food safety or kitchen owner. We would record their instructions in the production notes.

• Dish register: approved names, menu references, preparation contacts, plating notes, and whether each subject is essential or optional.
• Capture schedule: proposed preparation windows, set changes, review pauses, equipment access, and the restaurant's agreed limits around service.
• Visual references: direction for backgrounds, lighting, table settings, framing, and the amount of preparation or human activity shown.
• Placement matrix: the intended use, orientation, crop requirements, and delivery format associated with each approved asset.

Decide how the restaurant itself should appear

Rooms, tables, and practical context

Space photography needs a separate list from food photography. We would ask which areas guests should be able to understand: the main dining room, a counter, a terrace, or a group dining arrangement, where relevant. The restaurant would confirm the setup to represent. Proposed frames would distinguish permanent features from temporary arrangements that should not imply everyday availability.

People, sound, and service activity

If staff or other participants are included, we would define their role before scheduling. Hands preparing a dish, a host welcoming a staged arrival, and an interview each need different direction and permissions. The plan would identify who is responsible for releases and privacy review. Live guest capture would require an expressly agreed approach, reviewed by the relevant qualified owner.

For video, we would specify whether the assignment needs spoken audio, ambient sound, or a silent edit. Background music, visible artwork, packaging, and other third-party material would be noted for rights review where relevant. Any music or licensed material proposed for an edit would need usage terms suited to the approved placements.

Keep the shoot plan compatible with service

The proposed call sheet would identify access times, restaurant contacts, preparation responsibilities, equipment areas, and the point when production must clear the space. We would ask the restaurant to identify restricted areas and operational instructions. If the assignment includes service activity, the plan would define what can be staged and what must follow the restaurant's live operating requirements.

Contingencies would be discussed before the date is confirmed. These could include an unavailable ingredient, a weather-dependent outdoor setting, a delayed preparation sequence, or a participant cancellation. The scope would explain how substitutions are approved and when a missing subject becomes a separate capture requirement. Rescheduling and additional production would follow the agreed commercial terms.

Separate visual selection from factual approval

We would propose a review process with distinct decisions. First, the restaurant would select from the agreed presentation of draft material. Next, the designated owner would confirm dish identity, presentation, visible details, and any accompanying language. Editing feedback would then address the selected files. This sequence would be documented with the number of review rounds and the deadline for consolidated comments.

Retouching boundaries would be explicit. The proposal could cover color balance, exposure, framing, and agreed cleanup while reserving substantial alterations for separate approval. For video, the review would address sequence, pacing, titles, captions, audio, and final placement versions. New creative direction after selection would be assessed against the original brief before additional work is scheduled.

Make the handover usable by the next person

Final delivery would follow an agreed folder structure and naming convention. A proposed asset register could identify the subject, version, intended placement, approval status, and any usage restrictions. Web exports and larger files for approved print use would be specified separately. The agreement would also state whether raw captures, editable projects, or archived copies are included.

Usage terms would address the intended channels, permitted users, relevant duration, third-party licenses, and any restrictions on reuse or alteration. We would ask you to identify outside designers or partners who need access. Before a later menu change or new campaign, your team could check the register to decide which assets need factual review or replacement.