When a client says they want "the data behind the shot," they rarely mean a cryptic folder of RAW files. They mean usable deliverables that make the images searchable, licensable, and ready to drop into marketing or asset management systems. This article walks through what clients are actually asking for with the phrase commercial photography deliverables clients ask data and how we should deliver it on-site and after the shoot.
This is written for field operators: photographers, on-site project managers, inspectors, and anyone who moves images from camera to client handoff. You’ll get clear definitions, practical rules to put in contracts and call sheets, a delivery workflow that scales, and a short case showing exactly what we push to the client after a tricky warehouse roof capture. If you need a quick primer on what principals clients actually want from visual deliverables, that field guide summarizes stakeholder expectations and common handoff formats.
1. Start by naming what "the data" actually is
Stop treating "data" as a buzzword. Break it into discrete, non-negotiable pieces and spell them out for the client before the job starts. The main categories we always document are final image files, source files on request, metadata, technical specs, and delivery packaging. If you don’t make this list explicit, the client will assume they get everything and you’ll be fixing scope issues after delivery.
File types and what to expect
- Final images: Deliver professionally edited JPEGs or TIFFs per the client’s spec. These are the assets they use day-to-day.
- Source/working files: RAW or DNG files are source material. We treat these as special—available only if contracted and often for an extra fee.
- Editable master files: PSD or layered TIFFs for campaigns that need future retouching or versioning.
Metadata: the make-or-break piece
Clients who manage large libraries need embedded metadata. We always include EXIF and IPTC/XMP fields filled with practical info: creator, copyright statement, caption or short description, keywords, shoot location, and usage notes. You don’t need to be poetic—use plain tags that match the client’s DAM or CMS vocabulary.
Technical specs clients actually use
Set the specs in writing: required color profile, pixel dimensions or longest edge preference, and preferred compression level for web. If the client asks for print-ready deliverables, specify that they want lossless formats and confirm whether they need bleed or crop marks. Put these in the brief and in the delivery manifest so there’s no guesswork.
2. Put deliverables and rights into the contract, not email
Clients will ask for more than they pay for. Keep it simple and make the contract the source of truth. We’ve learned the hard way that vague language equals scope creep. Spell out which files are included, what metadata will be embedded, whether RAW is provided, and the limits of licensing.
What to call out specifically
- Included deliverables: say exactly what file types and folders the client will receive at final delivery.
- Optional deliverables: RAW, PSDs, or extended metadata exports—list them and their extra fees or conditions.
- Licensing terms: duration, geography, exclusivity, and permitted use. If you have usage fees tied to distribution or ad spend, put that language in now.
- Turnaround and revisions: be explicit about how many rounds of edits are included and what constitutes a revision versus a new job.
3. Build delivery workflows that are reliable in the field
Clients don’t just want the files; they want a predictable handoff. That means a simple, repeatable workflow that we can execute between call time and invoice. Pick tools that are robust and that the client can actually use.
Practical delivery pathways
- Branded galleries: Use galleries to let clients review, select, and request crops. They’re good for approvals but not for long-term asset storage unless tied to a DAM.
- Cloud transfers: Use secure cloud folders for the final deliverables. Keep the folder structure consistent across projects so the client knows where to look.
- Physical media: For clients who need an offline handoff, a properly labeled drive is fine—just document the contents and hash the files before shipping if the client cares about integrity.
To help clients understand the operational difference between an internal photo folder and a client-ready handoff, our guide on photo folder vs client-ready deliverable explains how to structure assets so intake teams can ingest them immediately.
Delivery manifest
Always include a manifest file with every delivery—plain text or CSV. It should list filenames, embedded metadata highlights, color profile, final color space, and a short note on what’s included and what isn’t. This simple file prevents endless email threads about what was or wasn't delivered.
4. Capture practices that make data tidy from the start
Half the time we’re fixing avoidable stuff in post. Spend a few minutes on these capture habits and post will be faster, cheaper, and less opinion-heavy.
Tethered capture and on-set sorting
Tether when the client needs immediate picks or when final crops matter. Tethering gives you instant review on a bigger screen and lets you flag frames as selects. If tethering isn’t possible, use a reliable in-camera rating system or a field laptop to sort selects and apply basic metadata tags before you leave site.
Immediate backups and folder structure
We use at least one verified backup before leaving the location. Keep the folder structure predictable: project-name / date / shoot-day / camera / selects / finals. Don’t leave a client with a root full of random filenames. If you can’t verify a backup on site, don’t hand off the job until you can.
Shot logging and short captions
Use a simple log: camera timestamp, short caption, location note, and whether the frame is a select. Your future self and the client will thank you. For formal reproducibility and audit trails, see our piece on photo logs with GPS and timestamps, which covers timestamping and location best practices.
5. Mini case: Warehouse roof survey for an insurance client
We did a roof survey where the client specifically asked for "the data behind the shot" so they could attach imagery to claim records and feed a maintenance system. The on-site realities were windy conditions, limited access points, and a requirement to show both damage and context photos that tie to plan coordinates. Here’s how we structured delivery so the client could drop files into their system without back-and-forth.
On-site decisions that mattered
- We shot contextual images and close-ups for problem spots and logged a short caption for each image that matched the client’s internal naming scheme.
- We embedded location notes in IPTC/XMP fields and included a plain-text manifest that matched the client’s database field names.
- We tethered a tablet for the client to approve selects, then confirmed backup to two separate storage devices before leaving site.
When documenting damage for claims, the field guide on making damage photos defensible shows the angle, scale, and metadata details that adjusters rely on.
What we delivered and why it worked
Final deliverables included edited JPEGs for the client portal, lossless masters held on a secure server, and a CSV manifest that mapped image filenames to short captions, location tags, and suggested usage (e.g., report photo, archive photo). Because we matched the client’s database vocabulary in our metadata and manifest, their intake team could ingest files automatically and start processing the claim immediately. The client paid extra for the masters, and the listed metadata avoided a lot of clarification calls.
Practical tools and templates to use on your next job
We keep a small toolbox and a few templates that we reuse. You don’t need fancy software—just consistent output that maps to the client’s process.
Templates you should have ready
- Deliverables checklist: A short list that you and the client sign off on before shoot day. It covers final file types, whether RAW is included, metadata fields required, and delivery methods.
- Manifest template: A CSV template with columns that match the client’s DAM or claims system: filename, caption, keywords, location, usage notes, and color profile.
- On-site log sheet: A simple form for notes, selects, and special instructions tied to timecodes or timestamps.
If you want quick wins for field consistency, the 7 field documentation habits article lists repeatable routines that reduce post work and improve perceived professionalism.
Field software that earns its place
Use software that lets you batch-write XMP/IPTC fields and export CSVs quickly. If a client needs a branded gallery, use one that can export metadata and keep folder structures intact. The goal is not the flashiest tool—it’s the tool that saves you edits and keeps the client moving.
Key takeaways
- Spell out what "data" means before you shoot: file types, metadata, rights, and delivery method.
- Put deliverables, RAW access, and licensing terms in the contract to avoid scope creep.
- Use predictable folder structures, a manifest, and embedded IPTC/XMP so the client can ingest assets without manual rework.
- Adopt simple on-site habits—tether/selects, immediate backups, and short captions—to reduce post hours.
- Keep templates for manifests and deliverables checklists; reuse them every job.
FAQ
What exactly do clients mean by "the data"?
They usually mean anything that helps their systems ingest and manage images: final images in agreed formats, embedded metadata, a manifest mapping filenames to captions and tags, and sometimes the source files if contractually agreed.
Should we ever hand over RAW files by default?
No. RAW files are source assets and should be treated as optional deliverables. Make RAW availability, usage limits, and any extra fees explicit in the contract.
How much metadata is enough?
Enough to make the image searchable and legally usable: creator, copyright, short caption, keywords, location, and any usage restrictions. Focus on fields your client’s DAM or CMS actually uses.
What if the client changes their delivery requirements after the shoot?
Refer back to the contract. Minor tweaks are fine, but significant changes that require new file exports or metadata work should be treated as change orders and billed accordingly.
Can I automate metadata and manifest creation?
Yes. Batch tools and scripts can populate IPTC/XMP fields and export manifests. Automate what you can, but always validate with a quick manual spot-check before final delivery.