blog, webdesign, to blog, wordpress, website, blogger, write, communication, designer, web design, together, www, web, publication, schreiber
Photo by tsmr on Pixabay

Reviews

Part of How to set evidence labels before choosing a creator media kit tool

How we review creator media kit tools, and where the documentation ends

Creator media kits review methodology for England: separate provider documentation from test evidence and record the limits before approving a portfolio verdict.

Creator media kits review methodology should define the evidence needed for a verdict before a reviewer opens the product. A source page can support an account of what a provider documents. It cannot establish the experience of making, maintaining or delivering a creator portfolio. Use the proposed protocol below to keep those findings separate.

What to take away

  • Define the evidence needed for a verdict before opening the product.
  • Separate first-party documentation from independently collected observations in a claim log.
  • Design the review task and receiving format before running any test.
  • Evaluate the receiving copy to confirm samples, captions and navigation work.
  • Write a verdict that distinguishes documented features, observed behaviour and suitability judgements.
  • This is a methodology, not a product review, so it does not report tool findings.

Specify the review commission

For this protocol, the commissioning publication is creatorportfolio.co.uk. No independent reviewing body has been appointed, and the named human reviewer and credentials remain unassigned. This is AI-assisted methodology drafting based on sources examined on 6 September 2026, not an executed product trial.

Review commission record

  • Named media-kit product and configuration
  • Application version or stated limitation
  • Device, browser and review date
  • Exact kit task and intended decision
  • Excluded outreach, payments, campaign functions

The subject of a future review must be a named media-kit product and identifiable configuration. Record the plan, application version where available, device, browser, review date and exact kit task. If a hosted service exposes no version number, record that limitation instead of inventing one.

Write the intended decision, such as whether a candidate can support a specified portfolio handover. Keep unrelated outreach, payments and campaign-management functions outside the commission unless separately authorised and researched.

Assign a source class to each statement

Mark provider help pages and sales descriptions as first-party evidence. Mark independently collected observations separately, including who collected them and under what conditions. Do not treat a testimonial displayed by the provider as independent verification of the proposed workflow.

Source classes and evidence limits

First-party evidence

What it is
Provider help and sales pages
Conditions
Not stated by provider
Testimonial
Not independent verification
Claim log
Source URL and access date

Independent observation

What it is
Collected by named reviewer
Conditions
Recorded by collector
Testimonial
Requires separate evidence
Claim log
Affected statement and boundary

For example, Canva's flattened-PDF instructions document an export route. Reading that page establishes what the help record describes; it does not show what happened to a particular kit's links, text or accessibility. A later reviewer would need to inspect the actual output to address those questions.

Maintain a claim log with the source URL, access date, affected statement and evidence boundary. A changed or unavailable page needs rechecking before release, even if the earlier draft cited it correctly.

Worked claim-log entry:

Statement
a flattened PDF export is documented.
Source URL
canva.com/help/download-flattened-pdf-variantb.
Access date
6 September 2026.
Evidence boundary
the page records an export route but does not show what happened to a particular kit's links, text or accessibility.

Design the task before running it

Use material the reviewer is authorised to handle and define the requested receiving format. Specify which content changes must be attempted, which output must be inspected and how another person could reproduce the steps. Decide in advance what constitutes an unresolved result.

Design the task first

  1. Use authorised material only
  2. Define requested receiving format
  3. Specify content changes to attempt
  4. State output to inspect
  5. Make steps reproducible by another person
  6. Decide what counts as unresolved

For trial material, GOV.UK's copyright page sets out ways to obtain permission and circumstances in which permission is not needed. It does not clear a specific image for a trial. Obtain the necessary rights decision for actual portfolio samples rather than assuming research use permits copying everything a creator has published.

Separate a planned activity from a completed observation in the log. Record the actual time and result only after performing the step. Do not populate blank fields with estimates of how an experienced user might fare.

Evaluate the receiving copy

Ask whether the proposed reviewer can locate the work samples, understand their captions and follow the intended navigation in the exact output. Retain any relevant settings and limitations. A successful action in an editing workspace would not by itself settle the receiving-copy question.

Government accessible-document guidance supplies principles for document structure and checking. Its government-publishing context must remain visible when applying it as a house review safeguard. It neither certifies a private kit nor establishes that a product has passed accessibility testing.

Where specialist assessment is needed, name the reviewer and method before making a conformity claim. Leave unperformed checks untested, without converting them into either a pass or a product failure.

Write a verdict proportional to the record

Summarise the tested task and configuration before stating a finding. Distinguish a documented feature, an observed behaviour and a judgement about suitability. Explain what remains unknown and whether it prevents the intended selection decision.

This draft involved no account use, subscription, file creation, export, support contact or user feedback. It has no supplied trial or affiliate recommendation; publisher relationships still require confirmation. Consequently, it supplies a review procedure and withholds all product-performance conclusions. Complete named authorship, fact-checking and methodological review before publishing the protocol or commissioning a claim-bearing review from it.

Before you act

  • Commission recordproduct name, version, device, browser, review date and exact kit task.
  • Claim logsource URL, access date, affected statement and evidence boundary.
  • Task scriptcontent changes to attempt, output to inspect and reproduction steps for another person.
  • Receiving-copy recordsample locations, captions, navigation and retained limitations.
  • Verdict recorddocumented features, observed behaviour and suitability judgements, with unknowns.
  • Authorship and fact-checking recordnamed reviewer, credentials and review date.

Common questions

What should a reviewer do if a cited source page changes or becomes unavailable?

A changed or unavailable page needs rechecking before release, even if the earlier draft cited it correctly. Maintain a claim log with the source URL, access date, affected statement and evidence boundary to track such changes.

More in Reviews