Guides
How a videography business keeps service quality honest, explained
Videography quality control on the delivered file: a ten-point technical review pass, where each defect was born, and the outcome questions to ask later.
What to take away
- Quality in this trade is checked on the file, not on the feeling. A defined technical pass catches things a client will notice next month.
- Most delivery defects are born on the shoot day and discovered in the edit. Tracing each defect back to its origin is what turns a check into an improvement.
- Two questions need answeringis the file correct, and did the work do what the client hired it to do.
- A quality standard nobody wrote down is a preference, and it changes with mood, deadline and who is watching.
The two checks that are not the same thing
The first check is technical conformance. Does the delivered file meet the specification: runtime, ratio, codec, loudness, captions, safe areas, naming. This is objective, repeatable, and can be done by someone who was not in the edit.
Technical check vs outcome check
Technical conformance
- Question
- Meets spec?
- Speed
- Fast, repeatable
- Who
- Not the editor
- Risk if only this
- Nobody watches
Outcome
- Question
- Did it work?
- Speed
- Slower, softer
- Who
- The client
- Risk if only this
- Wrong export settings
The second is outcome. Did the piece work where the client put it, and would they hire you again. This is slower, softer and more useful for the business.
Run only the first and you get perfect work nobody watches. Run only the second and a client's colleague finds the export error.
The technical review pass
Run this against every file in the deliverable schedule, on a machine that is not the edit machine, by a person who is not the editor.
The pass takes roughly the runtime, plus a second viewing, plus the checklist. A short piece lands under half an hour, which makes the pass the cheapest half hour in the project.
Set the numbers once, in the delivery spec, and quote them in the review notes. Runtime typically has to land within two frames of the approved cut, or within half a second on anything over ten minutes.
Loudness sits near -14 LUFS integrated for web delivery and near -24 LKFS for broadcast, with true peak at or below -1 dBTP. Captions typically run one to six seconds per cue, in at most two lines of about 32 to 42 characters. Titles stay inside the middle 80 percent of the frame.
Where each defect was born
- Caption error -> post problem
- Intelligibility problem -> microphone placement
- Sync problem -> ingest discipline
- Color mismatch -> picture profiles
- Wrong names -> missing client confirmation step
| Check | What you are looking for | Where the defect was born |
|---|---|---|
| Runtime | Delivered duration matches the approved cut within the tolerance above | Edit timeline, or a re-export after a late trim |
| Frame size and aspect ratio | The exact pixel dimensions and ratio the client asked for, with no letterboxing baked in by mistake | Export preset, or a sequence setting chosen at the start |
| Frame rate and cadence | A constant frame rate at the agreed value, with no duplicated or dropped frames after a speed change | Conformed footage, or a mixed-rate shoot day |
| Codec, container and bitrate | The codec and wrapper the spec names, at a bitrate that holds up in fast motion | Export settings, often a platform preset reused from another job |
| Loudness and true peak | Integrated loudness at the target, with no true peak over the ceiling | The mix, or a music bed added after the mix was approved |
| Sync and intelligibility | Sync holds across the whole piece, and dialogue stays clear on a phone speaker | The shoot day, usually microphone placement or a drifted recorder |
| Captions and subtitles | Correct text, correct timing, delivered as the sidecar the spec names | The transcript step, or captions set after a late picture change |
| Safe areas and legible text | Titles and lower thirds inside the safe area, readable in daylight on a phone | Graphics built on the edit monitor and never checked against the crop |
| Color and levels | A consistent look across cameras, levels inside legal range, no clipped skin tones | Picture profiles chosen on the day, or a grade applied clip by clip |
| Naming, metadata and package | File names, version numbers and folders exactly as the schedule lists | The delivery step, usually the last hour before a deadline |
Ten-point technical review pass
- Runtime and structureno black head or tail
- Aspect ratio and safe areastitles and faces
- Audio levels and loudnessconsistent, on target
- Dialogue intelligibilityclear on phone speakers
- Color consistencyskin tones matched across cameras
- Synclips locked at the end
- Captionswording, timing, names correct
- Graphics and namestitles and companies current
The right-hand column is the whole point. A recurring caption error is a post problem. A recurring intelligibility problem is a microphone placement problem, and no amount of checking at the end will fix it.
Checking on phone speakers, and other unglamorous rules
Three habits catch more real defects than any amount of scopes and meters.
Three unglamorous review habits
- Watch on the device the audience will use
- Watch once without stopping for pacing
- Have someone who has never seen it watch cold
Watch the final file on the device the audience will use. Most work now lands on a phone, held at arm's length, in a room with noise, often with sound off for the first few seconds. A cut that only works on a calibrated monitor with headphones is not finished.
Watch it once without stopping. Reviewers who scrub see errors and miss pacing. Both matter, so do both passes separately.
Have someone who has never seen the material watch it cold. They will ask the question the client will ask, a week earlier and for free.
Tracing defects back, month by month
Log every defect you catch, with its origin column filled in. After a month you will have a short list rather than a general anxiety.
From defect log to fix
- Log every defect with its origin column
- Read the list against the day it came from
- Sync in three projects -> fix ingest discipline
- Names wrong -> add written client title confirmation
- Color inconsistent -> revisit picture profiles once
Read the list against the day it came from. A sync problem in three projects points at ingest discipline. Names spelled wrong points at a missing step where the client confirms titles in writing.
Inconsistent color across cameras points at picture profiles, which is a decision made once in the camera, audio and lighting setup guide and then never revisited.
Where the defect came from the shoot day itself, the fix usually belongs in the daily routine rather than in the review, and that is the job of the daily shoot and post routine.
The outcome check
Correct files do not mean good work.
Ask the client three things, a few weeks after delivery, in writing so the answers are reusable:
- Where did the piece actually run, and did the versions you were given fit those places without further editing?
- What did you have to change, explain or apologize for internally?
- What would you have wanted differently, knowing what you know now?
The second question is the valuable one. Clients rarely complain unprompted, and internal friction they absorbed silently is exactly the information you need.
Do not turn the answers into public claims without care. If a client's response becomes a testimonial or a case study, the FTC's guidance on advertising and endorsements requires that claims be truthful, not misleading and supportable, and that material connections be disclosed. Reporting an outcome you cannot evidence is a different kind of quality failure.
Standards, safety and the parts you cannot see
Some quality is invisible in the file and visible in an incident. Cable runs, rigging, working hours, and how a crew behaves in a client's building are all part of what a client is buying, and none of it appears in an export.
Working conditions vary widely by production, as the Bureau of Labor Statistics description of broadcast, sound and video technicians records.
Music rights sit here too. A cut carrying a track not cleared for the client's use is defective even if it looks perfect.
The U.S. Copyright Office's work on the music marketplace sets out how music can involve several rights with different licensing paths. Confirm the license covers the actual use, and take anything commercially significant to a qualified attorney.
Keep the evidence
A quality system that leaves no trace cannot be audited or improved. Keep the review notes, the defect log, the approval message, and the receipts behind licensed material. The IRS guidance on the records a business should keep describes a system that clearly shows income and expenses with documents behind purchases and assets, and license purchases belong in it.
Where a project ran long, the same records tell you why. That feeds back into the schedule through booking shoots without stacking delays and into the wider pipeline described in the shoot-to-delivery workflow.
Common questions
Who should run the technical pass?
Anyone except the person who edited it. Familiarity hides defects, and the editor has watched the piece so many times that errors have become invisible. On a solo operation, leave a gap of at least a night.
Should clients see a technical checklist?
Not usually. It reads as internal process and invites debate about items they cannot judge. What clients should see is the deliverable schedule, which is the promise the checklist verifies.
What if the client approves something that is technically wrong?
Fix it anyway, and tell them you did. The error will surface later, and it will surface in front of their audience rather than yours.
How is this different from expanding the business?
It is the thing that has to work before you do. Quality problems that survive one city multiply in two, because the person catching them is no longer in the room, a point worth reading beside expanding into another market.
