Published: December 18, 2025
What are Script revision colors? Definition & Meaning
Script revision colors are the standard labels used to track approved script changes during production, so you can identify the newest pages and replace only the pages that changed while page numbers stay consistent.
You will hear crew members say “blue pages.” You might also hear “pink” or “yellow” revisions. The color is a version label. It tells you which revision cycle a page belongs to.
The standard revision color order
Many U.S. productions follow a common revision color sequence. Other productions can swap the early order, such as Pink before Blue, or repeat colors with labels like “Second Blue.” Your master reference is the title page revision list for your project.
Digital scripts are often plain white pages. The system still works because the header shows the revision label and date. Treat the label as the color.
If you want a refresher on standard screenplay layout, start with our script formatting hub. If you want a quick example of a “slugline” format, see our guide to scene headings in a script.
If you write in dedicated software, revision tools can label drafts and track changes in a clean way. See our guide to professional scriptwriting software for common options and features.
Why script revision colors exist
Once a script goes into production, departments annotate it with cues, notes, and references they need for the shoot. Departments also rely on stable page and scene references for breakdowns, shot planning, and daily work.
If page numbers shift every time a line changes, notes, schedules, and callouts stop matching across departments. That problem shows up fast when documents pull data from the script, like a call sheet or a shooting schedule.
Revision colors help keep page numbers stable after the script switches to locked pages. The script department can send a small revision packet of replacement pages. You replace the matching page numbers in your binder or update the pages in your PDF set. You stay on the same version as everyone else.
What you receive during production
Revisions usually arrive in one of two forms. Knowing which one you have tells you whether to swap pages or replace the whole script.
Revision packet: A cover memo lists the page numbers that changed, and the packet includes replacement pages for those exact numbers. You remove the old pages and insert the new ones.
Full-color draft: The whole script is reissued under one revision label, like a full Blue draft. This happens when changes touch many pages, or when too many A-pages and inserts make binders inconsistent.
Crew slang can be loose here. “Blue pages” can mean a revision packet or a full Blue draft. Do not guess which version is current. Confirm the current revision on the title page revision list.
How to verify you have the newest pages
You can confirm a script version in seconds if you check the same three things every time. Check the title page, the page header, and the revision marks.
Check the title page revision list
Most production scripts list revisions on the title page. You will often see each revision color with a date. That list is the reference the production uses to define the current revision.
Read the revision slug on the page
A revision slug is the header label for a revision set. It usually includes a color name and a date, like this:
BLUE REVISIONS 12/18/25
If your page number matches, but the revision slug is older, you are holding the wrong page.
Scan the margin for revision marks
On many productions, changed lines are marked in the margin. Many scripts use asterisks. The marks help you spot what changed without rereading the whole page.
This matters because set paperwork also relies on stable identifiers. Your film slate logs scene and take data, and your notes about each take need to match the correct page and scene version.
Break-out box: The 10-second revision check
- The title page shows the newest revision color and date.
- The page header matches the same revision slug.
- The page number matches exactly. This includes A-pages like 25A.
- Margin marks show where the text changed.
Locked pages and A-pages
Locked pages are a way to freeze page numbering during production. The goal is stable page and scene references for every department. When pages are locked, later pages should not renumber just because a scene got longer.
This is also why scheduling steps often start with “lock the script.” If you are building a plan from the page, our shooting schedule guide shows how scene numbers and page counts feed into the schedule.
What A-pages are
A-pages are inserted pages that keep numbering stable. If page 25 needs more space, the script can add 25A, then 25B. Page 26 stays page 26.
Here is a simple A-page example. You had page 25 and page 26. A revision adds dialogue that no longer fits on 25. The packet includes a revised page 25 plus a new page 25A. You insert 25A between 25 and 26.
What “OMITTED” means
If material is cut, the script department may issue a replacement page that says OMITTED. That prevents people from thinking a page is missing by mistake. An omitted page confirms the cut was intentional.
What combined pages mean
Some productions issue combined pages when material gets shorter, like “15-16.” Others leave blank space so later page numbers do not shift. The goal is consistent page references. Page references stay predictable for notes and callouts.
How to insert revisions step by step
Use the same routine every time. It helps when revisions come in fast, and it reduces version mismatches across departments.
- Open the title page and confirm the newest revision color and date listed there.
- Read the packet’s cover memo list of changed page numbers.
- Replace pages by exact number.
- Insert lettered pages in the correct spot. Put 25A between 25 and 26.
- Flip each replaced page and confirm the header shows the correct revision slug.
- Scan the margin marks so you notice what changed before you shoot the scene.
Who prepares and sends revisions
The job title varies by project. In many workflows, the script department prepares revisions and sends them out. On set, the script supervisor tracks continuity and notes, and version control helps keep those notes tied to the correct lines and scene beats.
If you want a bigger map of set roles, see our quick guide to below-the-line crew roles.
Common mistakes that cause version problems
These errors are common on set. Each one has a simple fix.
Trusting page numbers but ignoring the revision slug
If two people both have page 25A, but the revision slug differs, you can block and plan different actions. Always match the revision slug, not just the page number.
Assuming the color order is universal
Some productions use a different early order, such as Pink before Blue. Some repeat colors with a “Second” label. Follow your project’s title page list every time.
Mixing old and new pages inside one binder
This happens when your packet did not fully swap in, or when pages were inserted in the wrong order. Use the step-by-step routine above and confirm each header.
Version mismatches also hit continuity. If you block a moment based on older lines, your continuity notes can stop matching what you shoot. If you want a clear example of continuity pressure, see how continuity ties into blocking in film.
Summing Up
Script revision colors are a standard way to label script changes during production. Each color labels a revision cycle, so you can confirm you have the newest pages and replace only what changed. You verify the current revision on the title page, match the revision slug in the header, and insert replacement pages by exact page number. Margin marks help you spot what changed before you shoot the scene.
Read Next: Ready to plan or run your shoot day?
Visit the Project Planning sub-section for scheduling, crew coordination, and pre-shoot logistics — or explore the full Pre-Production category for more resources.
Or head to On-Set Workflow to learn how to keep your set running smoothly — and explore more in the Production section.
