# Finals and requests

> In short: A final is the take a person accepts as a shot's answer. You propose a take, the production checks it, and someone who can approve accepts it; in Solo one click does all three. This page explains the Requests tab, the eight checks, "Not measured", and what you can accept past.

Applies to: v0.13 · Last reviewed: 2026-11-02 · Canonical: https://docs.zymcos.com/product/finals-and-requests/

Every take says which of three it is, in the same word everywhere (on its thumbnail, in History, in Files and on the storyboard): **Draft** (made, not chosen yet), **Circled** (the ★, the shot's pick) or **Final** (accepted under a request). A **circled** take (★) is one you like; you can circle several for one shot. A **final** is different: it is the one take a person **accepted** as the shot's answer. Accepting is a decision, so it is recorded: who accepted which take, when, with which checks in front of them.

## Making a take the final

Open a take on the Viewport and look at the bar under the picture.

- In a **Solo** production (the default) the button reads **Make final**. One click proposes the take, checks it and accepts it. You need the *approve* right.
- In a **Studio** production, and in the review grid of an autopilot run, the button reads **Propose as final**. It opens a **request**; a person who can approve accepts it from the Viewport.

A take can be proposed when it is a picture or a clip, it is on exactly one shot, and it has not been withdrawn. A take that is already a final shows a **Final** mark instead.

## The Requests tab

The **Requests** tab in the right column lists the production's requests, open ones first, each with how its checks came out. Choosing one opens it on the Viewport:

- the **current final** and the **proposed** take side by side (a shot with no final yet says so);
- the **checks**, one row each;
- **Accept as final**, **Run the checks again** and **Close**. A request to change the locked Bible or a script says **Accept this change** instead; a storyboard version put up for approval says **Approve the storyboard** (see [The Sequence](https://docs.zymcos.com/product/the-sequence/#asking-for-a-storyboards-approval)); and a frame move that a locked script refused says **Accept this change** too.

If the proposed take is moved to another shot, withdrawn or erased while the request waits, the request becomes **Outdated**. If another take is accepted for the same shot first, the other open requests for that shot become Outdated too.

## The eight checks

| Check | What it looks at |
| --- | --- |
| **Continuity** | Whether the take holds the look the Bible locked for each character and place |
| **Matches the shot** | Whether its length, shape and size are what the shot asked for |
| **Defects** | Whether the detectors found flicker, freezes or other faults |
| **Provenance** | Whether the take carries content credentials that check out |
| **Rights** | Whether every real person, place or thing in it has a rights basis that has not been revoked |
| **Model terms** | Whether the model that made it may still be used |
| **Cost** | Whether the take was paid for |
| **Production decisions** | Whether it breaks a decision the production recorded |

Each check says **Passed**, **Failed**, **Checking…** or **Not measured**.

**Not measured is not a pass.** It means the platform could not tell, and it says why: either the platform cannot measure that yet (for example, no threshold has been set for a continuity axis), or there is not enough about this take (for example, nobody has scored it). A check that is still **Checking…** (the defect detectors can take a few minutes) usually settles when you run the checks again; after ten minutes it reads Not measured.

## Solo and Studio

A production's **rules** say how strict each check is: **Off**, **Advise** or **Required**. You set them under *Rules* in the Requests tab; only someone who can approve may. You never set a threshold, only how much a check matters.

- **Solo** advises on takes. Make final is one click, and the checks are attached to the final. Every check is required again when you deliver.
- **Studio** requires every check before a take is accepted.

## Changing the locked Bible or a locked script (Studio)

In a **Studio** production, what a lock vouched for is protected:

- Editing an entry the **current Bible lock names** (its reference pictures, rights or voice), and taking the **next lock**, go through a request. When you save such an edit the app sends it as a request instead and tells you so ("Sent as request 4... Nothing was saved to the Bible yet"). The Requests tab and the stage show what would change, before and after.
- A **locked script** is not unlocked. To change one that a lock closes (a commercial, a music video and the like), the change is a request that names the fields and scenes. A locked **screenplay** tracks its own changes as revisions, so it takes no request.

Someone who can approve **accepts** it. Accepting writes the held change, and for a Bible request that asked for it, locks the Bible again as a new version. If the entry or script was changed by someone else after the request was made, the request becomes **Outdated** and nothing is overwritten: propose it again.

Only the rights-bearing fields of a Bible entry are protected; a name, and any entry the current lock does not name, are edited directly. **Solo** edits directly, exactly as before. CODA does not write a protected change itself: it offers a card, and your button on the card sends the request.

## When a check stands in the way

Accept is refused while a **required** check stands in the way, and the request says which one and what you can do:

- A **failed** check can be accepted past: **Accept anyway** asks for a reason in your own words for each one, and the reasons are kept with the final.
- A check that **could not be measured for this take** can be accepted past in a Studio production, with a reason.
- **Rights** and **Model terms** can never be accepted past. They are legal facts.
- A check still **Checking…** cannot be accepted past; run the checks again.

Making a final needs the *approve* right. If you do not have it, the buttons are disabled and say so.

## What a final changes

A final is kept for good. It is never moved to the archive, and the ordinary controls will not move it to another shot, withdraw it or erase it: accept a different take for the shot first, and the earlier final stays on record as replaced. Accepting a take also files its history manifest, the same record circling files, and Files lists it under **Finals**, with **Final — Shot 4** in its location. The **Path to final** figures count finals once a production has any, and show the ★ beside them.

See also [Your files](https://docs.zymcos.com/product/your-files/#finals) and [Version history](https://docs.zymcos.com/product/version-history/).

## Asking CODA

You can ask CODA to **propose the take on the stage as the final**, to say **where a request stands** and **what is in the way**, to **explain why a check failed or was not measured** (and what usually fixes it), and to **write a request's summary**. CODA opens the request and the screen shows it; **accepting is always your click**. CODA cannot accept a take, accept past a check, or change the rules.

## Runs and changes under a final

When an autopilot run finishes making takes for a shot, it **proposes** the best one (your ★ first, then 👍) as a request, and lists the other takes it made; **Use this take instead** swaps the proposal and runs the checks again. The run never accepts, and approving a run's review is not accepting a final.

If something changes under a final after you accepted it, **Finals that need a look** in the Requests tab says what: the rights for someone in the shot were revoked, the model that made it is being retired or has been shut down, or the Bible has been locked again since the shot was cast. Nothing is changed for you; retaking the shot is your call, and CODA can open the request when you ask.
