Foundations
Part of UGC marketplaces: setting the foundations for England's 2027 category
UGC opportunities treated as buyer problems, with counter-signals and stop rules
Test UGC marketplace opportunities as buyer problems with limited evidence exercises, accountable owners, counter-signals and clear stop rules.
Test one recent commissioning problem through a permissioned evidence pack before you build anything. Stop if the current process already delivers the outcome. Treat a UGC marketplace opportunity as an untested buyer hypothesis, not as a predicted market gap.
What to take away
- Treat each UGC marketplace opportunity as an untested buyer hypothesis.
- Run one recent commissioning problem through a permissioned record first.
- Give every test a named buyer, a counter-signal, a decision date and an expiry.
- Name an accountable owner for each gate before the first test.
- Stop as soon as the current process already solves the problem.
The admission test before you build
A commission is one asset, one decision and one deadline. Ask which completed commission went wrong, who noticed, and what they did instead. Then run five steps.
- Name the buyer who owns the decision, plus the date they will decide.
- Request one permissioned record from a completed commission.
- Map that record and write down the missing step.
- Write the counter-signal that would show the problem is not real.
- Set an expiry for the test and for the evidence it produces.
The CMA's social-endorsement guidance for brands discusses instructions, incentives, monitoring and correction. It supports a governance interview, not proof of demand.
Budget the test before you run it. Our UGC budget template with cost states and approval gates keeps discovery spend visible instead of buried in a build.
Example: one fictional commission record
Use invented files and label them as fictional. The table below lists the fields a buyer should own for a single commission.
| Record field | Evidence the buyer owns | Counter-signal |
|---|---|---|
| Approved brief | Version and approver named | Undated brief, no approver |
| Claim support | Substantiation held before publication | Claim live without support |
| Incentive note | Paid partnership label agreed in advance | Label added after posting |
| Rights window | Channel, territory and expiry dates | One cleared flag |
| Payment state | Legal payer, amount and period | Gross flow merged with revenue |
In one fictional commission, the brief was approved by email, the claim support sat in a separate deck, and the rights expiry lived in a spreadsheet. The governance lead could not point to one record. That is a testable problem, not evidence of demand.
Rights, privacy and payment gates
The IPO's digital images copyright notice explains that online images can stay protected and that several owners may need to permit use.
Test a structured schedule with invented files and rights holders. It should separate creator ownership, featured-person permission, music, channel and territory. Keep paid use, modification and expiry as separate columns, never one cleared flag.
Personal data in creator content sits under UK GDPR. Stop if the test would centralise more personal data without a necessary purpose. The ICO's data protection guide covers consent and lawful basis for creator content.
Contract terms decide who carries each risk. Our seven contract categories with no model clauses shows where commission, money and rights can be unbundled before anything is signed.
CAP Code section 3 sets the non-broadcast substantiation boundary. An unsupported claim must be pausable wherever it was stored.
| Gate | Who signs | Stop rule |
|---|---|---|
| Advertising | Brand claim owner | A live claim cannot be paused |
| Rights | IP specialist | Expiry cannot be withdrawn |
| Privacy | Data protection lead | No lawful basis for the data |
| Security | Publishing account owner | Credentials cannot be revoked |
| Payment | Finance owner | Legal payer or period unknown |
HOLD continues until every gate has its own accountable approval.
When a test should stop early
A test ends early when the evidence turns against it. Keep the written counter-signal next to the decision date. Do not contact creators or upload real personal data during discovery.
- No documented problem appears in the permissioned record.
- The buyer cannot grant access to the record.
- The current process already handles the step.
- The counter-signal you wrote has come true.
- The decision date passes with no named owner.
Fictional assets keep the test safe. Real personal data turns it into a live processing activity.
If the problem survives, compare how a human veto is protected in automated workflows: testing AI applications with fictional records and a human veto.
Common questions
What counts as acceptance evidence for a commission test?
A buyer-owned export that a second authorised person can follow without asking the original owner. The brand's campaign-governance lead signs it.
When should a rights workflow be stopped?
Stop when complex rights collapse into a single cleared flag, or when an expired export cannot be withdrawn. An IP specialist owns acceptance.
What must a payment reconciliation test trace?
Each invented field from commission to closure, without merging gross flow with supplier revenue. Stop if the legal payer, currency or period is unknown.
Should discovery use real creators?
No. Discovery runs on invented assets and invented rights holders, so it stays outside live processing.
