Operations
Part of UGC operations: eight gated states from admitted brief to acceptance, payment and closure
Buyer-owned UGC service measures, from admission decision time to exit completeness
Define buyer-owned UGC service measures with precise events, clocks, evidence, exclusions and recovery, while leaving unsupported thresholds blank.
A service standard should tell the buyer when to act. "Fast delivery" and "high quality" do not. F-UGC-01 is a fictional worked example, not a real England asset. For this fictional England asset, every measure needs an event, eligible population, unit or numerator and denominator, clock, timezone, exclusions, source, owner, blank threshold and failure response.
A field marked intentionally blank is not broken text. The brand leaves it empty until it has its own evidence.
Do not import a supplier headline or industry average. The brand sets thresholds after examining its own risk, operating hours, evidence and recovery capacity.
What to take away
- Every measure needs an event, population, unit, clock, timezone, exclusions, source, owner, threshold and failure response.
- The brand sets thresholds from its own risk, operating hours, evidence and recovery capacity, not supplier headlines.
- File acceptance does not establish ownership or reuse permission, so rights evidence needs its own control.
- A tabletop discussion and a successful technical recovery are different evidence classes for publishing access.
Admission decision time
Decision: can an evidence item enter the commission record?
Measure the elapsed working time from a complete, timestamped submission to a recorded admit, reject or clarification decision. Pause only for a named missing input, and retain the pause event. Exclude test records and withdrawn submissions. The evidence system is the versioned decision log; the commercial owner sets the threshold, which is intentionally blank, and escalation.
Worked example row:
| Event | Clock | Source | Owner | Threshold | Failure response |
|---|---|---|---|---|---|
| Complete timestamped submission | Elapsed working time, Europe/London | Versioned decision log | Commercial owner | Intentionally blank | Escalate to named owner and log the pause event |
This measure says nothing about whether the claim is true. CAP Section 3 supports holding substantiation before distribution, so an unsupported claim should fail the gate rather than be counted as a slow approval.
First-pass asset acceptance
Decision: does the delivered version meet the contracted asset specification?
Use the count accepted on first complete review divided by the number of eligible asset versions submitted for acceptance for the stated period and timezone; both fields are intentionally blank.
Define one eligible version, edit rounds, duplicate handling and buyer-caused interruption. Record the contract and asset identifier. Keep specialist approval out of this denominator: technical acceptance cannot turn a rights or safeguarding fail into a pass.
The IPO's commissioned copyright guidance is why rights evidence has its own control. File acceptance does not establish ownership or reuse permission.
Complete specialist-gate rate
Decision: is a candidate release ready for publishing review?
Use the number of release candidates with every required dated gate decision divided by the number of eligible release candidates; both fields are intentionally blank. The gate set includes claims, recognition, rights, privacy and PECR, safeguarding, accessibility, security and finance. Count FAIL and UNRESOLVED separately. The threshold remains blank; missing evidence is not treated as zero risk.
Correction response clock
Decision: when must the publisher contain a confirmed or suspected defect?
Start at the first recorded alert meeting the buyer's definition. Stop at verified containment, not at acknowledgement. State whether the clock runs continuously or during defined support hours, along with timezone, duplicate-alert treatment and authorised pauses. CMA brand guidance supports checking and correcting improper advertising labels, but supplies no universal response time.
Publishing-access recovery
Decision: can the buyer stop or correct content if an account or supplier route fails?
Measure recovery exercises completed with acceptable evidence, divided by scheduled eligible exercises. Record the exact account, scenario, access path, version and tester. NCSC social media security guidance recommends logging, credential protection and an emergency recovery plan. A tabletop discussion and a successful technical recovery are different evidence classes.
Exit completeness
Decision: can the buyer close the commission without losing control?
Use a field-level register, not a percentage until required fields are fixed. Check contract, brief, authority, rights, accepted asset, reviews, publication, correction, payment, export, retention, deletion and access removal. ICO contract guidance supports return or deletion terms in applicable processor contracts.
Review definitions whenever the workflow, supplier, channel or law changes. F-UGC-01 has no observed events, so every result and threshold remains blank and the service status is HOLD.
Before you act
- Define the event, population, unit, clock and timezone for each measure.
- Set thresholds from your own risk and recovery capacity, not industry averages.
- Keep specialist approval out of the first-pass asset acceptance denominator.
- Count FAIL and UNRESOLVED separately at the specialist gate.
- Stop the correction clock at verified containment, not acknowledgement.
- Review definitions whenever workflow, supplier, channel or law changes.
Common questions
What should a service standard tell the buyer?
It should give the event, clock, source, owner and failure response for each measure. A blank threshold is deliberate and not broken text; the brand sets it from its own evidence.
Why does rights evidence have its own control?
File acceptance does not establish ownership or reuse permission. The first-pass asset acceptance denominator stays technical, so specialist approval cannot turn a rights fail into a pass.
What does exit completeness require?
A field-level register, not a percentage, until every required field is fixed. If a field is missing, the commission cannot close without losing control.
