Blog

How to track revision rounds with brand clients without losing feedback

By DevlectaDesigns · October 12, 2026

A single brand deal can mean four videos, two photo sets, three rounds of feedback and a deadline that moved twice. Spread that across several brands and the feedback ends up scattered across emails, DMs and comments on a shared drive. The result is predictable: a missed note, a revision done twice, or a client asking “did you see my comment?”

This guide sets out a simple system for tracking deliverables and revision rounds, plus what to share with the brand and what to keep to yourself.

Track deliverables, not just campaigns

A campaign is too big to track as one item. Break it into deliverables, each with its own:

• Format: for example a 30-second vertical video, a carousel or a set of product photos.
• Quantity: how many of that format were agreed.
• Deadline: the date the brand expects it.
• Status: where it is right now, for example in production, delivered, in revision or approved.

Update the status yourself when something changes. A status you set by hand is only as current as your last update, so make checking it part of each work session.

When a deadline passes and the deliverable is not approved, flag it as overdue. Overdue items are the first thing to look at each morning.

Give every revision round its own record

The core habit: when a brand sends feedback, record it as a new round on that deliverable, with the date and the feedback in their words. Do not overwrite the previous round.

A revision history might look like this:

• Round 1, 3 March: “Show the product label in the first three seconds. Music is too loud.”
• Round 2, 7 March: “Label is great now. Please cut the last scene.”

Keeping rounds separate does three things:

1. You can see exactly what changed between versions.
2. You can point to the dated note if feedback later contradicts itself.
3. You can see how many rounds a deliverable has used, which matters if your agreement includes a fixed number.

Check the number of revision rounds in your agreement with each brand. This guide does not interpret contracts or usage rights; if a request looks outside what you agreed, raise it with the brand directly.

Keep your private notes separate

Alongside the deliverables, you will have information that is useful to you but not to share:

• The agreed fee, currency and payment status.
• Usage terms, such as where and how long the brand may use the content.
• Contacts, and personal notes about how to work with each brand.

Keep these on the campaign for your own reference, but clearly apart from anything you send to the client.

Send a clean client summary

When a brand asks for an update, send a short summary instead of forwarding your whole tracker. Include:

• Each deliverable with its format, quantity, deadline and current status.
• The revision notes for each round, so both sides agree on what was asked.

Leave out your fee and payment notes, usage terms, contacts and private notes. A one-page PDF works well: easy to read, easy to file, and it shows the brand you are organized.

A weekly routine

1. Check overdue and due-this-week deliverables.
2. Log any new feedback as a new revision round, with the date.
3. Update statuses for anything that moved.
4. Send a client summary to any brand waiting on an update.
5. Export a backup of your tracker.

Doing this with Brieva

Brieva, a downloadable HTML app from DevlectaDesigns, is built around this routine. Each campaign holds its brief and deliverables; each deliverable has its own format, quantity, deadline and manually entered status, with overdue labels while you use the app. Revision rounds keep dated feedback notes. You can record deal amounts, currencies and payment or usage notes for your own reference, and the client summary you print or save as PDF leaves those private, payment, contact and usage records out. Deliverables export to CSV, and the whole workspace exports and restores as JSON.

Brieva does not send reminders while it is closed, post content, host files, create invoices or process payments. Your data stays in your browser on your computer, so export JSON backups regularly.

Whatever you use, the principle is the same: one record per deliverable, one dated note per round, and a summary that shows the client only what they need.