pencils, ruler, scissors, notebook, notes, writing, office, pad, student, school, binder, pen, set, pages, document, learning, lines, sketching, supplies, square, object, sketch, studying, triangle, easer
Photo by ds_30 on Pixabay

Tools and providers

Part of Creator media kit tools compared on one capability each, plus rights questions before upload

Creator media kits tool implementation: a preparation guide

Creator media kits tool implementation: prepare authorised content, configure access and map fields, then check a restricted copy before releasing the pack.

Creator media kits tool implementation should move an approved portfolio into a usable workflow without losing the evidence behind it. Name the approval editor who accepts the final pack. This method is proposed for an England creator operation; you must test the retrieval and export steps yourself before relying on the result.

What to take away

  • Work on a restricted trial copy first, and keep the previous authorised route available until the replacement has been accepted.
  • Name the approval editor who accepts the final pack, and use that role for the trial review.
  • Attempt the proposed retrieval process before relying on it, and record what could actually be recovered.
  • Check the rules that apply, including UK GDPR, ICO guidance and ASA rules on commercial relationships.

Prepare the content for transfer

Gather the authorised text, selected assets and source notes in a working folder. Mark which copy is the approved starting point and which files are reference material. Keep private supporting records out of the public-content set unless their disclosure has been separately assessed.

Prepare content for transfer

  • Gather authorised text, assets and source notes
  • Mark approved starting copy versus reference files
  • Keep private records out of public-content set
  • Resolve rights questions before using live assets
  • Create field listbiography, work, metrics, contact
  • Avoid invented statistics or endorsements

GOV.UK's copyright permissions guidance explains that permission or another valid route is needed for protected material. Moving an image into a new tool does not answer whether the proposed display is authorised. Have the responsible reviewer resolve rights questions before using live assets in the trial.

For an England operation, check UK GDPR Article 6 (lawful basis for processing) and the ICO's Guide to the UK GDPR if the kit collects personal data. Check the CAP Code Section 2 (recognition of marketing communications) if the pack includes paid links or gifted items.

Create a field list for the new kit: biography, work description, metric explanation and contact information as required. Decide where each item belongs, including any date or qualification that must remain visible. Avoid filling unused template sections with invented statistics or endorsements.

For example, map the biography field to the About section, the metric explanation to a metrics panel with its date and source, and the business contact email to the Contact area. Keep the same approved wording in each mapped field.

Choose the tool

Compare the workflow, not the template gallery. Named options include Notion, Airtable and Canva for a hosted pack, and Webflow, Squarespace or Wix for a site. Before committing, verify on each supplier's current pricing page: the number of editor seats included, published-page caps, custom-domain availability, export format options and public-sharing limits. Record the plan name and renewal date you find.

A solo creator may need only one published page and one seat; a team with approval steps may require a paid seat for each editor. Confirm the live plan tiers and limits on the supplier's pricing page before you rely on a quote, because figures change by region and billing period.

Accept the tool only if a test export reproduces the approved biography, metric labels and contact route, and the named approval editor can find each item without help. Record the plan name, renewal date and cancellation route.

Configure the people and account

Assign the service owner and the people allowed to edit or approve. NCSC's user-management guidance supports keeping access limited to the permissions needed for a task. Use that principle when configuring the actual account, and document how access will be removed when an editor leaves.

Configure access and accounts

Does the service separate billing from publishing permission?

Yes

Keep billing authority distinct from publish rights

No

Record the limitation and ask owner to decide

Check who controls the recovery route and the email used for service notices. Keep billing authority distinct from permission to publish if the chosen service supports that arrangement. If it does not, record the limitation and ask the owner to decide whether the proposed operating model is acceptable.

Do not connect social accounts simply because onboarding encourages it. Identify the fields needed for the portfolio and review the access request first. A connection that is unnecessary for the approved output should not become a prerequisite through habit.

Build and inspect a restricted copy

Transfer the authorised content and compare the new presentation with the approved source. Check captions, line breaks and any indication of commercial relationships. Pay attention to what an extract leaves out. The named approval editor needs enough context to judge the sample, not merely a recognisable thumbnail.

Inspect the restricted copy

  • Compare new presentation with approved source
  • Check captions, line breaks and commercial relationships
  • Record source and period for imported statistics
  • Pause claims whose definition cannot be explained
  • Inspect receiving version independently of editor
  • Ask someone to locate contact route and qualification

If the tool imports statistics, record the source and the period shown. Compare the displayed meaning with the original record rather than checking only that a number appeared. Pause the affected claim if its definition or update behaviour cannot be explained.

Inspect the receiving version independently of the editor. Use the intended viewing conditions and ask someone to locate the contact route and the qualification beside a claim. These are instructions for a future acceptance exercise, not measured usability findings.

Rehearse a correction and a recovery

Make a permitted change on the trial copy and inspect where it appears. For a downloaded output, generate a revised copy and distinguish it from the earlier file. For a hosted page, check the view the recipient can access. Record any limitation instead of asserting that all copies update together.

The NCSC's cloud-backup guidance recommends exporting essential information, knowing how to restore it and retaining an independent copy. For this implementation, include the approved text and rights references in the recovery plan, not just a screenshot of the finished page.

Attempt the proposed retrieval process before relying on it. Record who performed the exercise, the source version and what could actually be recovered. No successful restoration is claimed here.

Hand over the maintained kit

Give the owner the approved release reference, editing instructions and the unresolved-issue record. Set practical triggers for reviewing the pack, such as a changed permission or a new data source.

The implementation ends with the owner's documented decision on the actual output. Human fact-checking and named specialist review remain publication gates. The procedure does not establish that a supplier or portfolio operation is compliant.

Before you act

  • Gather authorised text, selected assets and source notes in a working folder; confirm rights under GOV.UK copyright permissions guidance.
  • Verify UK GDPR Article 6 lawful basis and the ICO's Guide to the UK GDPR for any personal data in the kit.
  • Assign the service owner, the approval editor and the people allowed to edit; document how access is removed on departure.
  • On each candidate tool's pricing page, record seat count, published-page cap, custom-domain and export limits for the plan you would buy.
  • Compare the restricted-copy presentation with the approved source, including CAP Code Section 2 disclosure lines.
  • Make a permitted change on the trial copy and inspect every location where it appears.
  • Attempt the retrieval process, record who performed it and what was actually recovered.
  • Give the owner the approved release reference, editing instructions and unresolved-issue record.

Common questions

What should happen before live assets are used in the trial?

The responsible reviewer must resolve rights questions first, using the GOV.UK copyright permissions guidance linked in Prepare the content for transfer. No live asset enters the trial until that reviewer has signed off.

How should a correction be rehearsed on the trial copy?

Make a permitted change on the trial copy and check where it shows up. For a downloaded file, produce a revised version and keep it separate from the earlier one; for a hosted page, check what the recipient sees. Note any limits.

What should the recovery plan include?

The recovery plan must include the approved text, rights references and the field mapping—not just a screenshot of the finished page. Attempt the proposed retrieval process before relying on it, record who performed the exercise and what could actually be recovered, and note any gap. No successful restoration is assumed.

More in Tools and providers