A 24-hour rush DCP is for one situation: the deadline is real, the screening is close, and failure is not an option. Rush is not “skipping steps.” Rush is priority scheduling and executing the essential technical steps quickly while still protecting playback reliability.
DCP = Digital Cinema Package. It must ingest and run on cinema servers, so rush delivery still needs QC essentials.
What’s included in a 24-hour rush DCP
Rush typically involves:
- priority slot in production queue
- fast sequencing of DCP build + essential QC
- organized delivery steps (stable download or drive handoff)
- strict version control (one final deliverable)
What must be ready for rush to work
Rush succeeds when inputs are clean:
- master is locked (final cut)
- runtime is confirmed
- subtitle SRT is final (if applicable)
- audio delivery is confirmed (5.1 is the cinema-standard)
If the master is still changing, rush often turns into rework.
QC under rush (what cannot be skipped)
QC = Quality Control. Under rush, QC is focused and essential:
- ingest/playback sanity
- audio channel consistency
- subtitle legibility and character integrity (if used)
- framing/safe-area issues that cause theatre cropping
When rush is worth it
Rush is worth it when:
- the screening is tomorrow
- the festival demands DCP immediately
- there is no buffer left
Rush is usually not worth it when:
- picture and sound are not locked
- subtitle text is still changing
- the deadline is flexible enough for standard scheduling
Rush request checklist (copy/paste)
- Deadline (date/time):
- Runtime:
- Master link:
- Subtitles SRT? (yes/no + language):
- 5.1 available? (yes/no):
Link hints (Rank Math)
- Internal link to “DCP rejection reasons.”
- External link to a reputable DCP definition reference.
Need a 24-hour rush DCP now?
Send runtime + deadline + master link. The team confirms availability and replies with timeline and quote.