A creative approval workflow that ends feedback chaos
Feedback on a draft arrives as email replies, chat messages, PDF comments and proofing-tool notes from several stakeholders who disagree. We build a creative approval workflow that gathers comments from every channel into one list per round, flags contradictions and requests that look like new scope, routes the round to the right approver and records final sign-off. A typical build costs $1,000 to $2,500 per workflow and takes about three to four weeks.
The problem
Why client feedback rounds keep multiplying
A campaign draft goes to the client and comes back from four directions: the marketing manager replies by email, the CEO comments on the PDF, legal sends a chat message and the brand lead uses the proofing tool. Designers end up working from whichever comment they saw last.
Without a recorded sign-off, disputes are hard to settle. Did the client approve version three or four? Was the extra headline set part of the brief? An approval workflow keeps versions, comments and decisions in one place.
What we build
What our creative approval workflow includes
Feedback from every channel
Comments from email, Slack or Teams, and proofing tools such as Filestage gathered into one list per round.
Version control
Each round tied to a version, with comments that refer to old versions marked.
Conflict and scope flags
Contradicting comments and requests that look like new deliverables highlighted for the account manager.
Approver routing
Rounds sent to named approvers in order, such as brand then legal, with reminders.
Recorded sign-off
Final approval captured with name, version and time before anything goes live.
Change request draft
Out-of-scope requests turned into a draft change request for the account lead to send.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Draft shared
A new version is shared through the proofing tool or project task.
-
02
Automated
Feedback gathered
Comments from all channels are collected into one list for that round.
-
03
Automated
Conflicts flagged
Contradictions and possible scope changes are highlighted.
-
04
Account team review
Account manager resolves
The account manager confirms the list with the client and briefs the team.
-
05
Account lead or agency owner decides
Sign-off and scope
Final approval comes from the client; change requests are agreed by the account lead.
How it behaves
How the approval workflow behaves
What the client sees
- Drafts in the place they already review
- One consolidated summary per round to confirm
- A clear request for final sign-off
What the agency sees
- One list of comments per round and version
- Conflicts and scope flags called out
- A sign-off record for every deliverable
What the automation does
- Gathers comments from every channel
- Groups them and flags contradictions
- Routes approvers in order and logs sign-off
Edge cases and fallbacks
- Comment refers to an old version
- Marked as outdated for the account manager to confirm.
- Approver is away
- Reminder, then the account manager is asked who can approve instead.
- Feedback arrives after sign-off
- Logged as a new request, not merged into the approved round.
- Proofing tool or email API down
- Comments are collected when it returns; the round stays open meanwhile.
Architecture
A creative approval workflow at a glance.
- Input
- Logic and services
- AI step
- Data
- People
- Output
How it flows
- 1 Comments arrive from the proofing tool, email and chat for a shared version.
- 2 n8n gathers them into the right round, and an AI step groups them and flags conflicts and scope.
- 3 One round list lands in the project tool for the account manager.
- 4 The account manager resolves it with the client, and final sign-off is recorded with the version.
Project planner
How the project runs, phase by phase.
Creative approval & feedback workflow project plan
Typical time to launch: about 3 weeks, then support
-
01
Discovery
2 to 3 days
Current review channels, proofing tool, approver chains and how sign-off is recorded today.
-
02
Design
2 to 3 days
Round rules, approver order, scope flag rules and sign-off record.
-
03
Build
About 1 week
Channel connections, round lists, sorting, routing and sign-off capture.
-
04
Shadow run
About 1 week
Run on live projects with the account manager checking every list.
-
05
Launch
1 to 2 days
Switch on for new projects and brief clients on the process.
-
06
Support
Ongoing
New channels and approver chains as clients change.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Channels, approver chains and sign-off record.
$300 – $500
-
Build
Round lists, sorting, routing and sign-off capture.
$400 – $1,150
-
Integrations
Proofing tool, email, chat and project tool.
$150 – $450
-
Testing and shadow run
Live projects checked by the account manager.
$100 – $250
-
Launch and training
Switch-on and client briefing.
$50 – $150
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Proofing tool, AI usage and n8n are billed to you directly.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- Proofing tool: Your proofing vendor's own plan, if you use one.
- n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
- AI model usage: Billed by the provider per use; small at agency comment volumes.
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
US: endorsement disclosures
The FTC expects material connections with a brand to be disclosed clearly with the endorsement itself, so influencer and partner creative is checked for disclosure before sign-off.
Source: ftc.govUK: advertising codes
Non-broadcast ads in the UK are covered by the CAP Code, so claims questions are routed to people who know it, not answered by automation.
Source: www.asa.org.ukUnreleased client work
Drafts and comments are confidential client material, so AI and storage vendors work under processor terms.
Source: gdpr-info.euFree tools
Try these first, free.
Guides to read first
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Creative approval & feedback workflow questions, answered.
A defined path for drafts: who reviews, in which order, where feedback goes and how final approval is recorded. Automating it means comments land in one list per round and sign-off is never in doubt.
Not necessarily. If you use Filestage or another proofing tool, we connect to it. If clients insist on email and PDFs, the workflow gathers those too.
It flags requests that look like new deliverables against the brief or SOW. The account lead decides whether it is a change request and how to raise it.
It can include a compliance step, such as legal or regulatory review, in the approver order. Automation routes and records; people with the right knowledge make the call.
No. They can keep replying by email or commenting in the proofing tool. The change is on the agency side.
Rounds per deliverable, time from draft to sign-off, conflicting comments caught and change requests raised.
Free 20-minute call
Want this for your marketing agency?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for marketing agencies
All servicesCRM automation for marketing agencies: new business pipeline
Track every enquiry, referral and pitch in one agency CRM pipeline, with research briefs before discovery calls, proposal follow-ups and a clean handover to onboarding when a client signs.
From $1,000 · About 4 weeks Details
Client onboarding automation for agencies
Turn a signed contract into a kickoff checklist, access requests for ad and analytics accounts, a welcome pack and scheduled reminders, so the first month goes on strategy instead of chasing logins.
From $1,000 · About 3 to 4 weeks Details
Automated client reporting with draft commentary
Pull GA4, Google Ads, Search Console, Meta and LinkedIn data into branded monthly reports, with anomalies flagged and first-draft commentary the account lead rewrites before anything is sent.
From $1,000 · About 4 to 5 weeks Details