Cultiq
Blog/Methodology/Document an artist shortlist decision your team can reuse

Document an artist shortlist decision your team can reuse

A Cultiq workflow for recording why an artist shortlist landed where it did — brief version, candidate outcomes, evidence, disagreements, and refresh triggers.

Document an artist shortlist decision your team can reuse
Key takeaways
  • A shortlist records what you chose. A decision record preserves why — including what you rejected and what you were unsure about.
  • The qualification has to travel with the claim. Strip it once and nobody downstream can tell which numbers were measured and which were modelled.

Most shortlists record the winner and lose the reasoning. A decision record keeps the brief version, the rejected candidates, the evidence, and the disagreement — so the next reviewer can audit the call instead of redoing it.

5
Record sections
4
Candidate outcomes
1
Brief version per decision

A shortlist gets built over days, argued over in a meeting, and reduced to a single slide. Six weeks later someone asks why a particular artist was not on it. Nobody can answer. The evidence has aged, the brief has moved twice, and the person who ran the analysis has moved to another account.

So the work gets repeated. A second research pass reaches a slightly different conclusion, not because anything changed in the market, but because nothing was written down about how the first conclusion was reached.

TakeawayA shortlist records what you chose. A decision record preserves why — including what you rejected and what you were unsure about.

Cultiq gives brand and agency teams a connected place to assemble artist, audience, market, and momentum evidence, and to compare candidates against a campaign brief. The record described here is the layer on top: the short document that makes a decision auditable, reusable, and safe to revisit.

Version the brief before anything else

Every shortlist is only valid against a specific brief. Record which one, in one sentence, at the top:

Brief v[n], dated [date]: an artist for [objective], reaching [audience] in [priority market], during [window], with [essential scope] and [must-not-break constraint].

Give it a version number and a date. This is the single most useful line in the document, because it is what makes a later change legible. When the launch slips a quarter, the priority market moves from London to Los Angeles, or legal narrows the required rights, the next reviewer can see immediately whether the old conclusion was answering the current question.

Name a real buyer market — the United States, United Kingdom, South Korea, Japan, France, Germany, Singapore, Dubai. "Global" is a legitimate answer only when the campaign genuinely has no priority territory; used as a default it hides the market question rather than answering it.

A shortlist scored against v1 and presented against v3 is not a shortlist. It is a stale artifact with a current date on it.

Record an outcome for every candidate

The reasoning lives in the candidates who did not win. Give each one an explicit outcome rather than letting it disappear from the deck.

OutcomeWhat it meansWhat to record
RecommendedAdvancing to outreach or approvalThe campaign role and the evidence behind it
Viable alternateWould work; ranked lowerWhat would have to change to promote it
HeldCannot be assessed yetThe specific unconfirmed item and its owner
Set asideAssessed and not advancingThe brief-relevant reason, in one line

"Set aside" needs the most discipline. The reason must connect to the brief — audience mismatch in the priority market, scope conflict, timing incompatibility, category conflict requiring specialist review. Vague reasons decay fast. "Not the right feel" is unauditable six weeks later, and it is exactly the kind of note that gets re-litigated.

Do not silently drop a candidate a stakeholder expected to see. An absent name reads as an oversight. A recorded outcome reads as a decision.

Attach the evidence, with its qualifications intact

For each advancing candidate, record what the recommendation rests on — and be precise about the type of evidence, not just its conclusion.

Use one line per candidate in this shape:

Current evidence supports [claim] for [market] because [observable signal]; it does not establish [the assumption still to be confirmed].

Then keep three distinctions visible, because they are the ones that collapse under summarisation:

  • Observed versus interpretive. A stored platform figure and a modelled audience estimate are both useful and are not the same class of claim.
  • Global versus territorial. Broad international attention does not establish depth in the one market the campaign needs.
  • Origin versus market. Where an artist is from is a different field from where the campaign has to perform. A Korean or Japanese artist may be the strongest route to a US or UK audience; the origin field says nothing either way.

Where a field is AI-assisted, modelled, incomplete, or pending review, carry that label into the record. A qualification that survives into the document is what stops a soft signal from hardening into a fact somewhere between the analysis and the client deck.

TakeawayThe qualification has to travel with the claim. Strip it once and nobody downstream can tell which numbers were measured and which were modelled.

Record the disagreement

Most shortlists involve a genuine split — a strategist and a creative lead who rank two candidates differently, or a client contact who prefers the more famous name. Recording it costs three lines and prevents a recurring argument.

Capture:

  • The position. What was argued, in one sentence.
  • Whose it was. So the next conversation includes the right person.
  • What would resolve it. The specific evidence or confirmation that would settle the question.

That last item converts a preference into something testable. "Prefers a higher-tier artist" is a mood. "Would advance the higher-tier candidate if the Q4 budget increases or if territory evidence for the alternate stays thin" is a condition someone can actually check.

An objection that never got written down does not disappear. It comes back later as doubt about the whole process, usually at the least convenient moment.

Separate the confirmation list from the analysis

Keep one clearly bounded section for everything the team cannot answer from evidence — and does not have the authority to answer at all.

That list typically includes availability for the window, representation authority for the territory and deal type, category exclusivity status, rights and usage scope, approval timelines, and fees. Public information can sharpen these questions. Only authorized parties can close them.

Give every item an owner and a date. An unassigned confirmation list is a decoration; an assigned one is a plan. And keep it visibly separate from the analysis, so no reader mistakes an open question for a settled finding.

Set the refresh triggers

Close the record by naming what would make it stale. This is what turns a document into something reusable rather than something that quietly expires.

Useful triggers include:

  1. The brief changes — objective, audience, priority market, window, scope, or constraint.
  2. A recommended candidate's representation, format, or activity materially changes.
  3. New territory evidence appears for the priority market.
  4. A category conflict or public issue emerges for an advancing candidate.
  5. The decision date moves far enough that current momentum evidence no longer covers it.

Pair the triggers with the outcome each one implies — retain, re-score, or hold. Re-scoring on every new signal is as unreliable as never re-scoring: it makes the comparison move for reasons unrelated to the brief. When a trigger does fire, the evidence freshness audit covers the refresh pass in detail.

Keep the record beside the work

Store the record with the shortlist itself rather than in a personal folder. Saved candidates live in Matches, and the comparison that produced the ranking lives in FitMatrix — the record should point at both, and both should point back at the record.

When a decision is revisited, add a dated note rather than editing the original conclusion. The change history is the valuable part: it shows a reviewer that the recommendation moved because the brief or the evidence moved, not because someone quietly rewrote the reasoning to match a later preference.

Common decision-record mistakes

  • Recording only the winner. The rejections carry the reasoning; without them the record cannot answer the question it will actually be asked.
  • Omitting the brief version. A conclusion with no stated question behind it cannot be audited.
  • Summarising away the qualifications. Modelled and observed evidence must stay distinguishable.
  • Leaving disagreement out. Unrecorded objections return as challenges to the whole process.
  • Mixing confirmations into findings. An unconfirmed item inside the analysis section reads as established.
  • Overwriting instead of appending. Editing the original conclusion destroys the trail that makes the record trustworthy.

What a good record buys you

A useful decision record answers five questions without anyone reopening the research: which brief this decision answered, what each candidate's outcome was, what the recommendation rested on, where the team disagreed, and what remains unconfirmed.

Build the comparison in FitMatrix, keep the candidates in Matches, and write the record while the reasoning is still fresh — not after the meeting, when only the conclusion survives.

Availability, rights, fees, conflicts, and approvals are still settled directly with representation. The record is what makes those conversations short, and what makes the next shortlist faster than this one.

For wider entertainment-partnership strategy and market context, visit WENOTIFT Insights.

Frequently asked questions

Why record rejected candidates at all?

Because the rejections carry most of the reasoning. When a stakeholder asks why an obvious name is missing, a recorded outcome and reason answers it in seconds. Without one, the team re-researches a candidate it already assessed, often reaching a different conclusion for no new reason.

What makes a decision record different from a shortlist deck?

A deck argues for a recommendation. A record explains how the recommendation was produced — which brief version applied, what evidence supported it, what was still unconfirmed, and where the team disagreed. A deck persuades; a record lets someone audit.

Should a dissenting view go in the record?

Yes. An unrecorded objection tends to resurface later as a challenge to the whole process. Recording the disagreement, whose it was, and what would resolve it turns it into a testable question instead of lingering doubt.

Does a decision record replace verification with representation?

No. Availability, fees, rights, conflicts, and approvals are confirmed with authorized parties. The record is where you track which of those confirmations are still outstanding and who owns each one.