Deployer, the party that publishes with it
Deployer names the party that takes a system and uses it. A production house generating footage with a purchased tool is almost always here, and the duties that follow are narrower and more immediate than the ones it might assume. As of 2026-09-12.
| What the role turns on | What follows |
|---|---|
| Using a system on real material | Duties about what an audience is told |
| Discharged at publication | Nothing about it is settled by the tool |
| Unaffected by what the file carries | A clean file does not remove the duty |
| Narrower than it sounds | A disclosure, not a prohibition on anything |
Inclusion rule. Consequences of the deployer role as transparency instruments describe it. Order. From the defining condition to the practical scope.
1The tool cannot discharge this one
Whatever a generator applies, the duty to tell an audience belongs to whoever put the work in front of them. A marked file makes that easier and does not do it, and an unmarked file does not remove it.
Which is the single most useful thing to understand before reading any vendor page on this subject. Most of what vendors publish is about their own role, not about the reader's.
2It is the easier of the two roles to satisfy
A disclosure is something a publication can arrange: a line in a description, a card before a video, a notice in the frame. None of it requires a technical capability nobody has.
Productions frequently assume the harder role's duties apply to them and then conclude the whole subject is intractable. The narrower reading is both correct for most of them and far cheaper.
3Timing is part of the obligation
Instruments in this area tend to require the information at the latest on first exposure. Anything arranged after publication is late by construction, and a retrospective note does not repair it.
That makes the deployer duty a workflow question rather than a compliance-review question. It has to be answered before the thing goes out, which means it has to be decided before volume begins.
4Where a register helps and where it does not
It can say what each tool publishes about the help it offers, which is useful for planning. It cannot say what any particular publication owes, because that depends on the material and the jurisdiction.
So the honest division is: vendor pages for what the file may carry, and advice for what has to be said about it. Confusing the two is what makes a product page look like a compliance document.
5Published material behind this entry
A term in this record: what it means, and what the published material says about it, each figure read on 2026-09-12. Related: Disclosure, Interoperable.