Source scope
The material we start with.
Agreed together.- ✓ Approved assets and usage rights
- ✓ Source duration and supported inputs
- ✓ One clear audience and message
- ✓ Handling requirements agreed first
A pilot begins with an agreed job. Availability, usage limits and pricing are confirmed separately.
In development · Interactive examples use fictional dataThe material we start with.
Agreed together.The candidates we need to review.
Let’s define it.The decision and the deliverable.
Agreed together.| Factor | What to establish | Why it matters |
|---|---|---|
| Source material | Asset types, duration and rights | The work starts with content the team may use. |
| Versions and formats | Candidate count and destination frames | Each version needs a reviewable purpose. |
| Review process | Owners, rounds and approval criteria | A final deliverable needs a clear decision. |
| Processing and handling | Supported formats, capacity and storage terms | Availability and limits must be confirmed before use. |
A recurring production job needs more than a count of clips. Name the source, the purpose of each candidate, the formats and the decision that makes the package ready to hand over.
Lead with the first action.
| Part of the work | Question to resolve | Record to keep |
|---|---|---|
| Source ownership | Who can authorize use of the footage? | Source owner and permitted use |
| Input material | Which files and durations belong in the pilot? | Asset list and supported formats |
| Audience | Who should understand this piece? | One audience and a clear question |
| Message | What must stay constant across the set? | The core idea and required context |
| Opening directions | Which creative choices should differ? | Named candidates and intended differences |
| Caption treatment | Which type, placement and language need review? | Approved brand treatment and revision |
| Destination frames | Which aspect ratios need an explicit check? | Frame list and crop notes |
| Review responsibility | Who resolves contradictory comments? | Named owner and review criteria |
| Revision limits | How many rounds belong in the agreed scope? | Revision allowance and change process |
| Approval | What marks a candidate as ready for handoff? | Exact version and approval reference |
| Usage notes | What must the next owner know before publication? | Rights, context and restrictions |
| Final package | Which assets and records are delivered together? | File manifest and next owner |
No. There is no subscription, free trial or checkout on this site. Sending an enquiry creates no account or payment obligation.
No. The cards describe the parts of a pilot scope to agree. Availability, deliverables, limits and commercial terms are confirmed separately.
No. No price or delivery commitment has been established for the product concept. We first need a bounded workflow and clear requirements.
Describe the recurring job, the permitted inputs, the desired handoff and the person reviewing the outcome. Do not send passwords, confidential assets or payment details.
ViralCLI features for a clearer short-form production handoff.
Explore the detail ↗guidesViralCLI guides for a clearer short-form production handoff.
Explore the detail ↗contactDescribe your ViralCLI workflow and discuss a focused pilot. No account, trial or payment is created.
Explore the detail ↗Bring a recurring production job, approved source material and a clear review owner.
Discuss your workflow ↗No account, trial or payment is created by an enquiry.