Solutions
For the teams that answer the notes.
Agencies, post houses and in-house teams all run revision rounds, but the notes arrive differently and different people carry the risk. Here’s where Timbercut is designed to fit for each, in the rounds you already run.
By team
Same problem, three shapes.
Each team below is a composite of how revision rounds commonly run. The scenarios use the fictional sample round from the demo.
Agencies
Client notes from many voices, and one producer who answers for all of them.
The round today
A round arrives as a review link full of timecoded notes, an email from the client’s legal team, a call recap and a few messages in chat. Someone has to merge them, work out which note wins when two disagree, and hand the editor one clean list. If a note slips through, the client finds it before you do.
Who decides
Your creative director makes the subjective calls. The client’s brand and legal owners decide anything that touches their rules. Your producer signs off the round.
Where Timbercut is designed to fit
- Understand
One list from every channel
Notes from review links, chat, email, docs and call recaps become one list of requests. Repeats are merged and every source stays attached.
- Understand
Conflicts settled before the edit
When a client note contradicts the approved brief, the person who owns the brief gets the options. The editor doesn’t have to guess.
- Execute
Routine changes made, judgment calls routed
Supers, captions, swaps and trims go ahead. Subjective, costly or rule-breaking changes wait for the named approver.
- Verify
A round you can show the client
The verification report and audit show what was asked, what changed and what still needs a decision.
Illustrative scenario · Sample data
Round 3 of a 30-second launch film for Corvane, a fictional e-bike brand: 48 notes from 7 people across 5 channels. In the first pass, 34 changes go ahead, 6 wait for a named approver, one conflicts with the brief and one needs a file nobody can find.
Run this round in the demoPost-production
Notes from the agency and the client, landing on an editor’s timeline.
The round today
Your editors get notes second-hand. The agency forwards the client’s comments, adds its own and wants the next version tomorrow. Notes describe shots instead of giving timecodes, and some quietly reverse a decision from two rounds ago. The post supervisor is tracking the same problem across several projects at once.
Who decides
Your editor reviews every applied change. The agency and the client keep their approvals. Your post supervisor signs off delivery.
Where Timbercut is designed to fit
- Understand
Notes pinned to the picture
A note like “the bit on the bridge” is linked to a shot and a timecode before an editor reads it.
- Understand
History before action
If a note repeats a change that was later reverted, the Decision Graph shows when, why and who decided.
- Execute
A new version, never an overwrite
Supported operations are designed to apply to a new version in the editing tool. The previous cut stays exactly as it was.
- Verify
The checks your QC would run
Loudness, captions, file naming and framing are checked against the delivery spec, with evidence for each.
Illustrative scenario · Sample data
In the sample round, “make the logo bigger” repeats a V5 change that V6 reverted under the brand guidelines. Instead of repeating the mistake, Timbercut proposes the largest size the rule allows and asks the brand lead.
See the logo history in the Decision GraphIn-house teams
Stakeholders across the company, and brand rules that can’t slip.
The round today
Product marketing wants a new claim, legal wants the disclaimer on screen longer, social needs vertical versions and the brand team wants the new lockup. Every note comes from someone with real authority, often in a different tool. The video lead has to keep all of it consistent with the brand system and the claims sheet.
Who decides
Brand, legal and product owners keep their approvals. The video lead signs off the round before it goes anywhere.
Where Timbercut is designed to fit
- Understand
Rules that travel with every change
Brand guidelines, approved claims and legal lines are checked on each change, not only at the end of the round.
- Execute
The right approver for each change
A changed product claim goes to legal, a brand exception goes to the brand lead and a subjective call goes to the creative lead.
- Execute
Versions for every placement
A request like “prepare vertical versions” becomes explicit deliverables, with framing decisions marked for review.
- Verify
A record for the next campaign
Decisions stay in the Decision Graph, so next quarter’s team knows why the logo is 16% and who agreed to it.
Illustrative scenario · Sample data
In the sample round, changing “Folds in 10 seconds” to “Folds in seconds” alters an approved product claim, so it waits for legal counsel. The 9:16 and 4:5 versions wait for the creative director, and one of their checks stays blocked until the vertical end card turns up.
Open the claim change in the demoBy role
What changes for you.
Timbercut is meant to take the clerical weight of a round off the people who carry it, and leave the decisions where they are.
-
Producer
What lands on you
Collecting notes from every channel, chasing approvals and answering “did we get everything?”
What Timbercut is designed to take on
One list of requests with their sources, a named approver for each judgment call and an audit to send with the next version.
What stays yours
Priorities, the client relationship and the sign-off.
-
Editor
What lands on you
Decoding vague notes, hunting for the right files and making dozens of small changes by hand.
What Timbercut is designed to take on
Explicit operations pinned to timecodes, routine changes applied to a new version and a check on each one.
What stays yours
The cut, the craft and every call about rhythm and feel.
-
Post-production lead
What lands on you
Versions across several projects, delivery specs and QC before anything ships.
What Timbercut is designed to take on
Versions that never overwrite, delivery checks against the spec and a record of what changed in each round.
What stays yours
Scheduling, quality and final delivery.
-
Creative director
What lands on you
Subjective notes that need a decision, and protecting the idea round after round.
What Timbercut is designed to take on
Proposals with the interpretation labeled, plus the history of what was tried and reverted before.
What stays yours
Every subjective call and the creative direction.
-
Agency owner or head of production
What lands on you
Rounds that run long, and mistakes that reach clients.
What Timbercut is designed to take on
Rounds that show their work: what was asked, what changed and what’s still open.
What stays yours
Client trust and the business decisions.
-
Brand or marketing lead
What lands on you
Checking every version against the guidelines and the claims sheet.
What Timbercut is designed to take on
Rule checks on every change, with exceptions sent to the person who owns the rule.
What stays yours
Brand decisions and approvals.
Fit
Is a pilot right for your team?
Pilots work best with a team that has real rounds to bring and time to judge the result. Here’s an honest check.
A good fit if
- You run several revision rounds per project, and notes arrive in more than one place.
- You have a brief, brand guidelines or delivery specs that every change has to respect.
- You can share one recent round, such as the notes, the brief and a cut list or project file, under terms agreed in writing.
- A producer or editor has time to review what Timbercut proposes and tell us where it’s wrong.
Probably not yet if
- You need a live connection to your review or editing tools today. Those connections are planned, not live.
- You want revisions to reach clients without a person signing off. Timbercut is designed to keep a person on every round.
- Your procurement process requires a security certification. Timbercut doesn’t hold one.
- Your work is mostly before the edit, like scripting or shoot planning. Timbercut starts with revisions in post.
Bring the round your team dreads.
Pilots start with one real revision round, scoped with you before anything is shared.