Read a TV Availability Sheet Before Copying Its Claims Into a Sales Pitch

A sales line gets written in a hurry. Someone hands you an availability sheet, you find the show, and the row looks generous: a title, a territory, a date, two languages. Two minutes later the draft reads available worldwide, English and French, through 2028, and it sounds like something a buyer could act on.

It isn't. It's a sentence built out of a record whose conditions nobody read yet.

An availability record is a statement of scope by whoever issued it. The job is to find out which scope, on whose authority, and with which parts still open. Start with the record's declared column definitions or its named schema version, not with the row. Fix the exact title, edition and transaction under discussion. Read territory, window, permitted use and language together, because none of them alone is a permission. Keep a language the offer allows apart from a language the supplier intends to deliver, and keep both apart from an asset that actually exists. Leave every unresolved value visible, attached to a question for the person who owns the record. Write only what survives that.

And keep one boundary in view the whole way: reading metadata does not clear rights. Nothing here grants you anything. It tells you what a document says, which is a narrower thing and the only one you can use.

Identify the record you are actually reading

Start with identity, because identity is where conditions get lost.

A finished-series record usually has three layers that look like one. There is the title — Harbor Shift. There is the edition or edit — the original cut, a remaster, an extended version. And there is the manifestation, the particular delivered form. MovieLabs' Avails and Title List specification, version 2.25 (dated 4 December 2025), keeps title, edit and manifestation as separate concepts in its table definitions. The practical consequence is that one name can appear twice in a worksheet and mean two different sets of terms.

So do not carry a territory, a window or a language from one row to another because the titles line up. If this same worksheet also carried a row for a remastered Harbor Shift, that row would be its own record with its own conditions. Nothing transfers.

Next, the transaction. A row is not a statement that something "is available." It is a statement about a kind of deal — in our example, subscription streaming — in a place, over a period. Change any of those three and you are reading a different question.

Then get the definitions. Ask the supplier for the column definitions, or for the named schema version if the file follows one. This matters more than it sounds. An undocumented spreadsheet cannot safely inherit defaults from an XML standard, because a schema's defaults live inside a named version and are often qualified by the agreement behind the deal. A worksheet with its own legend governs itself. A blank cell might mean "not applicable," might mean "take the default from the schema," and might mean "nobody filled it in." Those are three different facts, and only one of them is about the deal.

When a field stays ambiguous after you have the definitions — a value you can't place, a column name the legend doesn't cover — keep it as a question and address it to the record's responsible owner. Don't resolve it by guessing what a similar file did once.

Here is the record we'll work with. It is fictional, invented for teaching, and it declares its own legend rather than claiming to follow any XML schema. The legend comes first, because the row's values point back to it.

The worksheet's own legend, as it declares it

The record row

Read the legend before you read the row. "Worldwide coverage, minus listed exclusions" is a definition, and it is this worksheet's definition — not a universal one. The two language columns are two different columns doing two different jobs. The start is not a date yet. Hold all of that before you try to write anything.

Read territory, window and use as combined conditions

Territory entries usually come in two directions. Positive entries say where the deal applies. Exclusions take pieces away. Under this legend, broad coverage with Canada excluded describes everything except Canada — and that depends on the legend, which is why you asked for it. Another sheet might define "worldwide" as the territories a particular sales agent controls, which is a smaller and stranger shape.

Precedence is the trap here. The MovieLabs version 2.25 specification states that explicit Territory entries take precedence over TerritoryExcluded. That is a rule belonging to that named version, and it may be qualified by the agreement sitting underneath it. It is not a general law of spreadsheets, and neither is its opposite. Do not walk into a supplier's worksheet carrying "exclusions always win" or "inclusions always win." Find the precedence rule in the document that governs your row, or ask which one applies.

The window needs the same care. In TX-01 the end date is declared and the start is awaiting owner approval. Those are not symmetrical facts. A declared end plus an unapproved start means the run has no confirmed beginning, so you cannot say the title is available today, and you cannot say it is available through 2028 as though a clock were already ticking. What you can say is that the record proposes that window and one end of it is unresolved. If a later version of the sheet shows the start approved, that is a new reading, not a confirmation of the old one.

Use is part of the condition, not a formality. Subscription streaming answers a subscription-streaming question. If the buyer is contemplating ad-supported streaming, a linear channel window or a download-to-own release, this row does not answer for it, no matter how close the titles look.

Put the three together and ask one question: does the transaction on the table sit inside all of these conditions at once? For our buyer, that is a subscription-streaming deal, outside Canada, beginning once approval arrives, ending 31 December 2028. Asked that way, the row is useful. Asked as "is it available," it answers nothing.

Separate offered languages from delivery information

Language is where two honest fields get read as one dishonest claim.

The MovieLabs version 2.25 specification defines AllowedLanguage and AssetLanguage as answering different questions. One belongs to the offer: which languages the deal is permitted to be exploited in. The other is fulfillment information: which language assets relate to delivery. A record can answer the first and say nothing about the second. It can also list assets without telling you whether they are finished.

TX-01 offers English and French. Its intended-delivery language field lists English only. Asset readiness is unspecified. So the offer permits two languages, the delivery field names one, and no part of this record establishes that a French dub or a set of French subtitles exists. It doesn't establish that the English deliverable exists either. An intended delivery language is not a delivered one, and a permitted language is not an asset at all.

This is the point where a hurried draft tends to grow a phrase like "with French subtitles." That phrase is a claim about a physical thing — a completed track, in a package, ready to hand over. Nothing in the row supports it. If a sales conversation needs it, ask for asset status specifically: does the French asset exist, is it complete, and is it in scope for this delivery?

And resist the pull of the blank. An unspecified asset-readiness field is unspecified. It is not a quiet no, and it is not a quiet yes. Reading absence as confirmation is the same error as reading absence as refusal, just pointed in a more flattering direction.

Turn unresolved fields into bounded sales wording

Now write the internal readout, which is a different document from the external claim.

Keep conditional and unresolved values visible in the internal version, because that is where they belong and where someone can act on them. Apply a default only when the actual schema version and the agreement context justify it. Anything else stays a question. Then draft a claim scoped to the record and its conditions:

Worksheet TX-01 describes the original edition for subscription streaming outside Canada, subject to unresolved start approval. It lists English and French as offered languages; French delivery is not established by this record.

Every clause is traceable to a field. "Subscription streaming" comes from use. "Outside Canada" comes from the legend plus the exclusion. "Unresolved start approval" comes from the start field. "Offered languages" is the offer column, and the last clause draws the line the record actually draws.

Keep this as a proposed internal readout until the owner confirms what can be represented externally. You may well be the person who understands the record best in the room. That is not the same as being the person authorized to make its commercial claim.

Now set it beside the sentence that started all this: available worldwide, English and French, through 2028. Watch what it discards. "Worldwide" drops the Canadian exclusion. "Through 2028" takes a declared end and reads it as a window already running, which the unapproved start does not support. "English and French" blends an offer with a deliverable, and quietly promotes a permitted language into a finished asset. Three conditions gone, one field misread, and the sentence is more persuasive for it. That is exactly why it is dangerous.

The readout should also carry its open questions, each addressed to the person who can answer it:

• Start. When or whether the owner approves the start date, and what the conditional start means for any window you might describe.
• Transaction scope. Whether subscription streaming is the plan actually on the table, and whether the buyer's territory falls inside the coverage — if the buyer is working in Canada, the exclusion is the answer.
• Language assets. Whether French and English assets exist, are complete, and are in scope for delivery.
• External wording. Who is authorized to state any of this outside the building.

Separate them because they have separate owners. A question about an asset is not answered by a question about a date, and no amount of urgency merges them.

Finally, remember what this document cannot do. An availability sheet is not the offer and not the agreement behind it; if the underlying document says something different, the underlying document governs. Reading a row carefully tells you what that row claims. It is a real skill and it will keep you out of trouble. It is also, and this is the whole point, not a grant of anything.

End where the sheet ends: with a bounded readout, and with every unresolved field assigned to the person who owns it.

Frequently asked questions

Why start with the availability sheet's column definitions or schema version instead of the row?

The row's values point back to the legend or schema. Without definitions, a blank cell might mean not applicable, take the schema default, or nobody filled it in, which are three different facts. An undocumented spreadsheet cannot safely inherit defaults from an XML standard, because schema defaults live inside a named version and may be qualified by the agreement. If a field remains ambiguous, keep it as a question for the record's owner.

How should territory, window, and use be read together?

None alone is a permission. Territory may be broad coverage minus exclusions; under the sample legend, worldwide minus Canada means everything except Canada, but that depends on the legend. Precedence is not general law: the MovieLabs version 2.25 specification says explicit Territory entries take precedence over TerritoryExcluded, and that rule may be qualified by the agreement. The sample row's declared end plus an unapproved start is not symmetrical, so it cannot support available today or available through 2028 as if a clock were running. Use is also part of the condition: subscription streaming does not answer for ad-supported streaming, linear, or download-to-own. Ask whether the transaction sits inside all conditions at once.

What is the difference between offered languages, intended delivery language, and asset readiness?

Offered languages are languages the deal permits exploitation in. Intended delivery language is the language the issuer intends to deliver; it is not a statement that an asset exists. Asset readiness says whether a required delivered asset exists, is complete, and is available; not specified means the worksheet asserts nothing. In the sample row, English and French are offered, intended delivery is English only, and asset readiness is unspecified. The record does not establish that French or English deliverables exist. An unspecified field is not a quiet no or a quiet yes.

How should unresolved fields be handled in a sales draft?

Keep conditional and unresolved values visible in the internal readout. Apply a default only when the actual schema version and the agreement context justify it; otherwise keep a question. Draft a claim scoped to the record: the sample row describes the original edition for subscription streaming outside Canada, subject to unresolved start approval, lists English and French as offered languages, and does not establish French delivery. Every clause should be traceable to a field. Keep it as a proposed internal readout until the owner confirms what can be represented externally.

What are the limits of an availability sheet?

Reading metadata does not clear rights. An availability sheet is not the offer and not the agreement behind it; if the underlying document says something different, the underlying document governs. A careful reading tells you what that row claims, which is narrower than a grant. Open questions about start approval, transaction scope, language assets, and external wording have separate owners and should be addressed to those owners.

Further reading

• Introduce a Film to a Sales Agent Without Sending Only the Creative Deck — The film-side treatment of the same problem: a deck cannot imply availability, and unconfirmed rights wording must give way to the responsible producer's exact statement.
• What Must You Deliver With a Finished Film? — When confirmed availability becomes an obligation to hand something over, this clarifies that delivery is a dated written list, not a property of a finished film.