Feedback rounds that never end

Leon Silcott

Define a feedback round by its content, owner and stopping point before counting it. Keep corrections, refinements and new work distinct when another list arrives.

The subject line says “final tweaks” again. There are comments in a document, a voice note from the owner and a second list from someone you have not met. Before you can make the changes, you need to work out which comments belong together and whether anyone has resolved their contradictions.

A written feedback process gives that conversation a starting point. It does not make every additional message chargeable or guarantee a quick sign-off. The useful questions are what is being reviewed, who decides and which work was included in the fee.

Define the unit before the limit

“Two rounds included” is incomplete without a definition. Does each round cover the whole project or one deliverable? Does it begin when you receive the first comment or when the client sends a consolidated list? What happens if a late stakeholder contradicts earlier feedback?

For a hypothetical menu-design project, a workable note might say:

“Two consolidated feedback rounds on the three menu cards and specials board are included. Please gather your team's comments into one list per round and identify one person to resolve conflicting requests. New menu formats or a different creative direction will be discussed separately before additional work.”

This is an example of working information, not a complete contract clause. Adapt it to the project and your approved business terms. Avoid implying that a round ends automatically after an arbitrary time if you never discussed that arrangement.

Identify a client feedback owner

Ask who gathers comments and makes the final decision. This can be the same person, but it should not be assumed. A project lead may collect opinions while a director approves the result later.

Find out whether other stakeholders need to review before you start. If a new decision-maker joins halfway through, discuss the likely effect on scope and dates. Do not treat their arrival as an automatic paid extra without checking the actual work and arrangement.

A useful question at kickoff is: “Who needs to see this before the feedback is final, and who will send me the agreed list?” That asks for a process rather than criticising how the client works.

Separate three kinds of comments

Corrections to your work

A misspelt name you introduced or a layout that misses an agreed requirement should not be labelled new scope merely because it arrived in another email. Check the brief and fix the relevant issue through your agreed process.

If responsibility is unclear, discuss it. “That is a third round” does not answer whether the requested correction was already part of the promised deliverable.

Refinements within the agreed direction

Adjusting a heading hierarchy or balancing spacing may fit inside the included feedback round. The scope and round definition should guide the discussion. Use examples relevant to your work rather than trying to make a universal rule for every creative service.

New work or a changed direction

A new language version, an additional format or a replacement concept may change the output rather than refine it. Describe the difference and propose the work, price and date effect before proceeding.

The client's phrase “small tweak” does not determine the category, but neither does your preference to call it extra. Compare the request with the actual accepted work.

A hypothetical fragmented second round

Elena agrees a fixed £850 for three menu cards and a specials board, with two consolidated rounds. Round one arrives as a single list. Round two starts with a message from the owner, then a separate list from the chef with conflicting prices and dish names.

Elena does not invoice an extra round without discussion. She replies:

“I've received the owner's list and the chef's list. Some dish names and prices conflict, so I can't apply both accurately. Please send one agreed second-round list by Thursday, with the final values confirmed. I'll hold this pass until that arrives and then confirm the handover date.”

This identifies the practical blocker. If she has already started on one list, she can explain what was done and discuss any rework rather than retroactively declaring that each fragment was a separate paid round.

Make a late addition a proposal

After the second round, the restaurant asks for a takeaway version. Elena checks the scope and confirms it was excluded. She proposes a new defined output at £120 fixed and explains the delivery date.

“The takeaway version is a new format outside the three cards and board we agreed. I can produce the listed takeaway layout for £120 fixed, with handover next Tuesday. Please review that proposal before I start. If you leave it out, the original menu set remains as agreed.”

The amount is hypothetical. It illustrates the decision, not a recommended rate. Elena should check whether the new format needs new content, printing requirements or another review before offering the actual price.

Apply the AsAgreed revision boundary

Before any new payment report or receipt, AsAgreed supports a complete proposed revised scope and price. The original accepted terms remain until the client explicitly accepts the revision. A comment saying the new format sounds useful is not the same as accepting its proposal.

Once a new payment report or receipt exists, scope and price revisions are unavailable on that agreement. Later extras need a fresh agreement. If Elena's original menu job already has new payment activity, the takeaway version should have a separate record.

Do not make the new proposal repeat the old £850 as another amount owed. Explain which work it covers and keep the original invoice and payment history distinct.

For the next project, write down what a round covers and who will gather the client’s comments before you start.

Write feedback terms for your next project

Feedback windows need an agreed meaning

You may want comments within five working days so you can plan the next pass. Say what you are asking for and how a delay affects scheduling. Do not quietly treat silence as approval of the creative work or an automatic cancellation of the client's feedback rights.

A practical note is: “Please send the consolidated list within five working days of delivery. If that is not possible, tell me when to expect it and I will confirm the revised schedule.” Only offer that arrangement if it matches how you can actually work.

AsAgreed stores revision rounds and feedback windows as written terms. It does not automatically count rounds, enforce quotas or police target dates. Keep your own project-management process and discuss the real state of the work.

Use version labels that help the conversation

Label the files you send and the list they relate to. “Menu set v2, incorporating the first consolidated feedback list” tells the client more than “latest-final-final.pdf”. Keep earlier files where your normal process requires them so you can explain a decision if it is revisited.

When sending a pass, say what changed and what you need next. You do not need to narrate every mouse movement. Highlight unanswered questions or conflicting content so the client knows what still requires a decision.

If a client comments on an old file, point them to the current one and check whether the concern remains. Do not silently apply comments from several versions and hope the result matches their intention.

If an earlier decision is reopened

Ask why. Perhaps new information makes the old choice unsuitable, or perhaps your interpretation missed the brief. Compare the requested change with what was agreed before proposing any cost.

A useful response is:

“We used the layout selected after round one. Are you asking to return to the earlier layout, or is there a particular problem with the current one? I'll check the scope and explain any additional work and schedule effect before proceeding.”

This gives the client a chance to clarify. It avoids declaring that every reopened decision is automatically new paid work, while preserving a route to price a genuine change.

Finish with an explicit handover

At the end of the included process, identify the deliverables handed over, the version and any remaining questions. Ask for a clear response about whether the work meets the agreed brief. Do not make a casual emoji carry more meaning than the conversation supports.

A payment receipt is a separate event. Payments happen outside AsAgreed, and a client report reduces the confirmed balance only after you check and confirm receipt. A final payment does not automatically answer an unresolved quality question or approve a new output.

Likewise, a complete deliverable does not make an estimated price final. An estimate in AsAgreed requires separate acceptance of the final price before a payable balance appears.

Make feedback answerable

When a client says “it doesn't feel right”, ask what task the design or copy is failing to perform. They may be unsure how to express a useful comment. Offer questions tied to the brief: is information missing, is the order confusing, or is an agreed detail wrong?

Avoid supplying an interpretation and treating their silence as agreement with it. Summarise what you understand and ask them to confirm the intended change. A short clarification can prevent you spending the next pass solving a problem the client did not mean to describe.

Review your own side of the loop

Look at whether you sent work ready for review, identified the decision needed and answered the client's previous comments. If you changed direction without explaining it, a fresh list may reflect your process rather than an unreasonable client.

Track actual review time for your own planning. If a recurring deliverable needs more discussion than you priced, use that evidence to adjust future scope or fees. Avoid projecting hypothetical hours into claims about what every freelancer loses annually.

Before the next project, define the round, identify the feedback owner, clarify the outputs and explain how new requests will be proposed. The freelancers page shows these written terms beside scope and deliverables. Keep your creative tools and feedback workflow alongside the shared record.

Set feedback terms for your next project