Agreed revision rounds versus what actually happens

What a round is

A quote for a video is priced in rounds. Two rounds of revisions included means the client may come back with notes twice; the third time costs money, and every studio knows the third time is the one it either bills for or eats. Most studios track it in a spreadsheet and find out too late.

Tasked does not invent a round to count. A round is one review session: one version of the asset put in front of people. It opens when the review opens and closes when a verdict is recorded, and it is never reopened; the next round is a new session on a new version, which is what keeps the comment history honest. So a round has exactly one verdict, and counting verdicts is counting rounds.

A round belongs to the project it was reviewed for, recorded at the moment it opens. An asset can be moved to another folder next month; the round stays with the project that was quoted. A review of a file under no project belongs to no quote and is not counted anywhere.

Which rounds count

A round counts against the agreed number when its verdict asked for more work. Approved with changes counts, because a yes with notes is still another pass. Rejected counts. A plain approved does not count: the work ended there and nothing was reworked.

A change request from the client portal lands on the same rule. When the approval's task has a review room open, the portal's verdict is recorded in the room as well, so the round it closed is counted exactly as a round the studio closed itself.

This matches how the quote was priced. The second delivery that gets notes is round two; the third is the one that costs money.

The agreed number

Each project carries an agreed number of rounds. The default is 2, which is what a commercial quote usually says. Zero is legal and means no revisions are included, so every round is billable. The ceiling is 50, which is not a product limit but a guard against a mistyped 200.

The number is set on the project by anyone who may edit the project, and every change is audited with who changed it and from what to what. It is a commercial term of the job, and the studio gets a record of it.

Passing the line

Passed means used is strictly greater than agreed. Agreeing two rounds and using two is exactly the deal, not a breach. The overage is a count, used minus agreed, because each extra round is separately billable; it is never a yes-or-no flag.

Three surfaces show it, from one source. The board shows rounds used, rounds agreed and, once over, how many rounds are billable. An audit row is written for every round that lands over the line, with the round count and the review session, which is the record a studio argues an invoice from. And a domain event fires for every extra round, so an automation can act on it: when a project passes its rounds, tell the producer and email the client.

The event fires on every round beyond the agreed number, not once per project. If the client came back three extra times, a rule that says tell the producer says it three times, because each of those is a separate line on the invoice.

Why the count is derived every time

The count is never stored. A stored counter drifts the first time an asset is deleted, a review is removed with it or a project is merged, and a drifted number a studio invoices from is worse than no number. Each time the board or the decide route asks, the count is one query over the recorded verdicts of the project's reviews.

That also makes the count only as good as the review flow. A studio that mails cuts around and never opens a review gets zero rounds counted, which is honest: Tasked can only count what it saw. The way to get the count is to put every version through a review, in the room or through the client portal.

One consequence of deriving it: if the rule for which verdicts count ever changed, every historical number would change with it. That is the price of not storing the count, and it is the right price; the alternative is two eras of rows that mean different things.

Turning it into money

Tasked charges nobody for an extra round. Tasked's own subscription prices the studio's work, and the money for round three moves between the studio and its client, on the studio's own invoice. What the product provides is the number, the flag and the record: a board that says round three is billable, an audit row that says when it started, and an event a rule can turn into an email to the client on the day it happens.

The automation simulator, which replays the last month before a rule switches on, reports zero past firings for a rule triggered on the rounds event, because a round count over a 30-day window is not the project's round count. It says zero rather than a confident wrong number.

• Agreed rounds: default 2, from 0 to 50, audited on change.
• A round counts when the verdict asked for more work; a plain approval does not.
• Over the line: the board says how many are billable, an audit row per extra round, an event per extra round.

Questions that keep coming up

Does a client's request for changes from the portal count as a round?

Yes. It is a verdict that asked for more work on a version, so it closes a round and counts against the agreed number. A plain approval from the portal does not count.

What if we agreed no revisions at all?

Set the agreed number to 0. Every round is then over the line, and each one is flagged and recorded as billable.

Does Tasked invoice the client for the extra round?

No. Tasked flags and records it. The studio bills its client on its own invoice, with the board and the audit row to point at.

What happens if a version is deleted?

The count is recomputed from the recorded verdicts each time it is read, so it reflects what is on record now rather than a counter that stopped agreeing with the data.

Can we get told the moment a client passes the agreed rounds?

Yes. A domain event fires on every extra round, and an automation written in a sentence can notify the producer and email the client when it does.