The Agency UGC Operating System
How to run UGC programmes for many brands from one operating model: a workspace structure that keeps clients apart, a weekly report that writes itself, an onboarding template, and the data-protection line between agency and brand.
- 9 min read
- For: agency
Playbook · 9 min readThe Agency UGC Operating System
What you’ll learn
- A multi-brand workspace structure: one account per brand, named owners per account, and access reviewed whenever the roster changes
- A templated weekly report per brand (top posts, conversion and revenue per visitor, rights queue, next action) that can land in each client's own Slack channel
- A brand-onboarding template that front-loads sources, layouts and rights terms into the first week
- Where the agency and the brand sit under UK GDPR, and what that means for the contract and the rights flow
Chapter previews
- Chapter 01
Workspace architecture
One account per brand, named owners, per-brand integrations, and an access review every time a client or team member joins or leaves.
- Chapter 02
Templated weekly report
Top posts, conversion and revenue per visitor, rights queue and one recommended action, sent to each brand's own channel.
- Chapter 03
Brand-onboarding template
Source presets, layout choices and rights-flow wording agreed in week 1, so week 2 is building rather than chasing decisions.
- Chapter 04
Rights, data and the client contract
Controller and processor roles, whose name is on the rights request, and disclosure for gifted creators.
Inside the playbook
In this article
An agency running UGC for two brands can get by on memory and a shared login. At six it cannot, and the failures are predictable: a post approved for one client shows up in another's gallery, a rights request goes out under the wrong brand, a weekly report is late because the account manager is rebuilding it from scratch. This guide is the operating model that removes those failure modes. It is tool-agnostic where it can be and specific about Idukki where that helps; if you want the commercial side of running an agency practice, the agency and partner UGC playbook covers packaging and pricing.
Workspace architecture
One account per brand, always. Each client brand gets its own account with its own sources, product catalogue, galleries, rights records and analytics. It feels like overhead at setup; in practice it is what makes offboarding a client a clean operation, lets a brand's own team log in without seeing anyone else's data, and keeps one brand's hashtag from pulling content into another's queue. In Idukki, one login can be invited into several brand accounts and switch between them, and team members are invited to and removed from each account individually.
Named owners on both sides. Every account has an agency owner (usually the account manager) and a brand owner (the client-side person who approves content and answers rights questions). Write both names into your client roster alongside the account. When someone leaves, the roster tells you which accounts need an access change that day.
| Task | Agency AM | Agency specialist | Brand owner |
|---|---|---|---|
| Connect sources and catalogue | Accountable | Does it | Provides access |
| Daily moderation queue | Reviews weekly | Does it | Escalation only |
| Rights requests | Accountable | Sends | Approves wording once |
| Product tagging | Spot-checks | Does it | Flags errors |
| Layout and placement changes | Proposes | Builds | Approves |
| Weekly report | Owns and sends | Prepares data | Reads and replies |
| Takedown requests | Accountable, same day | Executes | Informed |
| Access review | Does it on every roster change | Confirms client users |
Integrations per brand, not per agency. Connect each brand's Slack workspace, analytics property and ecommerce store to that brand's account only. It is tempting to route every alert to one agency channel; resist it for anything containing client data, and keep the agency-wide view to an internal roster of which accounts need attention.
Templated weekly report
The weekly report is where agencies either build trust or leak hours. The fix is a fixed format that takes minutes to fill because every number comes from the same place each week, and that ends with one recommended action rather than a list of observations.
| Section | Content | Where it comes from |
|---|---|---|
| Headline | One sentence: the week in plain words | The account manager |
| Top posts | Three posts by clicks or attributed revenue, with creator and product | Content performance report |
| Conversion | Conversion rate and revenue per visitor on pages with UGC; A/B result if a test is running | Analytics and A/B testing |
| Collection and rights | New posts collected, rights requested, approved, pending, expiring soon | Moderation queue and rights ledger |
| Issues | Takedowns, flagged content, broken tags; blank if none | Moderation and alerts |
| One action | The single change you recommend this week, and what you need from the client | The account manager |
Automate the numbers, write the words. If each brand has Slack connected to its own account, Idukki posts a weekly digest into that brand's channel covering attributed sales, experiment activity, leads captured and similar sections when there was activity (Idukki for Slack lists what the alerts include, and each brand can route to its own channel). Rights answers and flagged content can also post as they happen. The account manager's job then shrinks to the headline and the action, which is the part the client actually values. For quarterly reviews, the CMO quarterly report template extends the same structure to a board read-out.
Brand-onboarding template
Most onboarding delays are decisions, not setup. The brand has not agreed which hashtags count, who approves rights wording, or which pages get a gallery, so week 2 is spent waiting. The template below front-loads those decisions into a single kickoff and a short checklist, so the build can start as soon as access arrives.
Onboarding a new brand
- 01
Kickoff (day 1)
Agree goals, the pages that will carry UGC, brand hashtags and handles, content no-go rules, and who approves rights wording.
Decisions logged
- 02
Access (days 1-3)
Create the brand account, invite the brand owner, connect social sources, the store and product catalogue, and the brand's Slack channel.
Connected
- 03
Presets (days 3-5)
Apply your standard moderation rules, layout choices for the vertical, and the rights request wording approved by the brand.
Configured
- 04
Build (week 2)
Moderate the first batch, send rights requests, tag products, and place galleries on staging for client approval.
Staged
- 05
Launch and test (weeks 3-4)
Publish, start an A/B test on the main placement, and send the first weekly report.
Live
- Sources. Brand handles, campaign hashtags, review sources, and any content that must be excluded (competitor tags, sensitive topics).
- Catalogue. Store connection or product feed, plus the collections that matter most for tagging.
- Layouts. Your house defaults per vertical (for example a PDP gallery for fashion, shoppable video for beauty), adjusted to the brand's theme.
- Rights wording. Your template request, edited once and approved in writing by the brand, naming the brand, the uses and the term.
- Creator guidance. If the brand gifts products, a short brief covering disclosure and brand style; see our creator style guide.
- Measurement. The baseline conversion rate for the pages that will change, recorded before launch.
Rights, data and the client contract
Who is the controller. The ICO defines a controller as the body that determines the purposes and means of processing personal data, and a processor as one that processes it on the controller's behalf. In a typical agency UGC engagement the brand decides why customer content is collected and how it is used, so the brand is the controller and the agency is a processor. The ICO says that relationship must be governed by a written contract covering the Article 28(3) points, including the subject matter, duration, nature and purpose of the processing and the types of data involved. Your agency master agreement or a separate data processing agreement should cover this for every client. This is general guidance, not legal advice; your own counsel should confirm the roles for your engagements.
Rights requests go out in the brand's name. The creator is agreeing to let the brand use their content, so the request should name the brand, link the brand's terms and privacy notice, and route replies to an inbox the brand can access. If the brand relies on consent, the ICO's test applies: specific, informed, given by a clear affirmative act, recorded, and as easy to withdraw as to give. If you use a registration page, it should carry the brand's identity. Rights Management in Idukki records each decision per brand account with its source, consent document and expiry (two years by default), and the audit log exports as CSV, which gives the brand its own record when you hand the account over.
Disclosure travels with the content. Agencies often run gifting and seeding for the same brands whose UGC they collect. The US FTC's guidance treats free or discounted products as a material connection that must be disclosed clearly, using plain terms like "ad" or "sponsored" or a simple thank-you to the brand for the free product, placed so it is hard to miss. If a gifted creator's post goes into a gallery or an ad, check that the disclosure is still visible in the format you are republishing.
Agency UGC operations maturity
- 1
Ad hoc
You’re here ifShared logins, reports rebuilt each week, rights requests sent from personal accounts.
Next moveSplit into one account per brand and write the client roster with named owners.
- 2
Structured
You’re here ifSeparate accounts, a report template, but numbers still copied by hand and onboarding varies by AM.
Next moveConnect each brand's own channel for automated digests and adopt the onboarding template.
- 3
Systemised
You’re here ifAutomated weekly numbers, standard onboarding, rights requests in the brand's name with a DPA in place.
Next moveRun an A/B test on every client's main placement so each account has a tested result.
- 4
Accountable
You’re here ifEvery client has a tested lift, a clean rights ledger and a quarterly read-out.
Next moveUse tested results to price retainers on outcomes, not hours.
FAQs
Should an agency use one UGC account for all its clients?
No. Give each brand its own account with its own sources, catalogue, rights records and analytics. It keeps client data separate, lets brand teams log in safely, and makes offboarding a clean handover.
What should a weekly UGC client report include?
A one-line headline, the top three posts, conversion and revenue per visitor on pages with UGC, collection and rights counts, any issues, and one recommended action with a question the client can answer quickly.
Is the agency or the brand responsible for GDPR?
Usually the brand is the controller because it decides why and how customer content is used, and the agency is a processor acting on its instructions. The ICO says that relationship needs a written contract covering the Article 28(3) points. Confirm the roles for your engagements with counsel.
Whose name should be on a UGC rights request?
The brand's. The creator is granting the brand permission to use their content, so the request should name the brand, link its terms and privacy notice, and route replies somewhere the brand can access.
How long should onboarding a new brand take?
With decisions made at kickoff and a standard template, a typical plan is access and presets in week 1, the first moderated and tagged batch on staging in week 2, and launch plus a first A/B test in weeks 3 and 4.
More on agency operations: the Idukki agency programme, why agencies are back in the middle of creator marketing, and moderating UGC at scale.
Sources and further reading
Send the link to your inbox.
The full playbook is on this page. Drop your email and we’ll send you the link so you can come back to it. One email, no drip sequence.
- A multi-brand workspace structure: one account per brand, named owners per account, and access reviewed whenever the roster changes
- A templated weekly report per brand (top posts, conversion and revenue per visitor, rights queue, next action) that can land in each client's own Slack channel
- A brand-onboarding template that front-loads sources, layouts and rights terms into the first week
