Operations
Part of Organising creator media kit handovers around evidence, ownership and version control
Carrying an approved creator media kit version from requested change to delivery
Creator media kits operating workflow for England: control incoming changes, preserve evidence and carry the approved portfolio version through to delivery.
A creator media kits operating workflow should make each change traceable from request to receiving copy. Keep the approved portfolio separate from work in progress, and decide who can move a revision into use. This is a proposed internal procedure for England operations, not a legal or regulatory requirement.
What to take away
- Keep the approved portfolio separate from work in progress and decide who can move a revision into use.
- Admit only content supported by evidence, and keep unsupported items outside the proposed release.
- Record the actual output examined so approval attaches to the candidate, not an editable file.
- After approval, return further edited material for review rather than treating the decision as unlimited authority.
Capture the requested change
Start a change note with the affected kit, its current version and the requested outcome. Identify the source of the request and the person authorised to decide it. A new asset, corrected contact detail and refreshed audience statement may need different evidence even when all appear to be small edits.
Example change note: Kit, speaker one-pager; version, v4; requested outcome, update the contact email; evidence, signed brief from the creator dated 12 May 2026.
Capture the requested change
- Name affected kit and current version
- State the requested outcome
- Identify request source
- Name authorised decision maker
- List affected outputs
- Keep distribution question with request
State which output is affected. A hosted page and a previously sent deck need separate consideration. Do not assume that correcting the editing file changes everything a recipient already holds. Keep the distribution question with the request rather than postponing it until the end.
Admit only supported content
Collect the material needed to make the specific revision. For a changed audience statement, ask for the underlying source and its date. For a new work sample, ask what supports the contribution being described. Do not resolve an empty field with a plausible claim or a number copied from an unrelated period.
Admit only supported content
Is the revision supported by evidence?
collect source and date, then proceed
keep item outside release until resolved
CAP's substantiation rules address documentary evidence for objective claims in marketing communications within scope. The proposed evidence check applies that concern to a portfolio operation.
For selected assets, GOV.UK's copyright permissions guidance explains permission and permitted-use routes. Refer uncertainty about the actual rights to a qualified reviewer. Keep the item outside the proposed release until the relevant question is resolved.
Make the revision in a working copy
Retain the current approved material while preparing the change. Record which text or asset was altered and which evidence supports it. Avoid unrelated redesign during a correction unless the owner authorises that broader scope; otherwise the reviewer must assess more than the original request.
Use file names that show kit, version and status, such as speaker-one-pager-v4-draft.pdf for the working copy and speaker-one-pager-v4-approved.pdf for the candidate.
Revise in a working copy
- Retain current approved material
- Record altered text or asset
- Record supporting evidence
- Avoid unrelated redesign
- Preserve context beside item
- Mark unresolved items with internal status
Preserve the context beside the item. Check whether a shortened caption still describes the same contribution and whether a changed metric still carries its period. If the required explanation no longer fits, revise the presentation instead of removing information solely to fit the template.
The working copy can contain unresolved items, but it should not be mistaken for a version ready to send. Use an internal status that the operator and approver understand. Name it so both people know what it means.
Review the version that will be delivered
Generate the proposed receiving output and compare it with the revised source. Check the changed item and nearby content that may have moved. Record the actual output examined so that the decision does not attach only to an editable file that will change again.
Where more than one person works on the account, NCSC recommends separate work accounts. Apply the relevant account controls to the people making and approving changes. The guidance supports accountability; it does not prescribe a particular headcount or guarantee that the selected tool records every action.
Authorise the release and retain the record
Ask the approver to decide on the exact candidate. In a small creator business, the authorised approver is usually the creator or the person who owns the client relationship, not a freelancer who only edits the file. Use this minimal approval record:
Field / Entry
- Candidate examined
- Accepted changes
- Unresolved items
- Date
If further editing occurs after approval, return the affected material for review rather than treating the earlier decision as unlimited authority.
Update the controlled receiving route only after that decision. Note what was replaced and which earlier copies remain relevant. A suspected rights or privacy problem needs appropriate specialist assessment.
Close the request and record the outcome
Keep the request, evidence and release decision together for the owner who will maintain the next version. Record whether any recipient communication remains outstanding without claiming it has already happened.
Before you act
- Start a change note with kit, version and requested outcome.
- Name the request source and the authorised decision maker.
- Collect evidence for the specific revision before editing.
- Prepare the change in a working copy, not the approved version.
- Generate the receiving output and compare it with the source.
- Record accepted changes and unresolved matters separately.
Common questions
What should a change note record at the start?
It should record the affected kit, its current version and the requested outcome. It should also identify the source of the request and the person authorised to decide it. Different edits, such as a new asset or corrected contact detail, may need different evidence.
What happens if editing continues after approval?
The text says to return the affected material for review rather than treating the earlier decision as unlimited authority. The approver should decide on the exact candidate, and accepted changes and unresolved matters should be recorded separately. The controlled receiving route is updated only after that decision.
