TikTok Content Scorecard: A Weighted Framework for Comparing Videos
A TikTok content performance scorecard converts several declared performance measures to a common scale, then combines them using weights chosen by the analyst. It is useful only inside a valid comparison cohort. It is not an official TikTok score, an estimate of TikTok’s recommendation formula or a prediction that a video will receive more distribution.
The scorecard answers a narrow decision question: Which eligible videos best match the objective we declared? It preserves the raw evidence, makes calculated rates and denominators visible, shows how each metric contributes to the result and tests whether the ranking survives reasonable alternative priorities.
Start with Tiksta’s TikTok metrics dictionary when a field name, scope or denominator is unclear. The scorecard below assumes those definitions have already been checked; it owns the separate task of normalization, weighting and rank-sensitivity analysis.
What Is a TikTok Content Performance Score?
A TikTok content performance score is a composite result: several metric values are normalized to a shared scale and combined according to an explicit objective. A scorecard is the complete decision record—not just the final number. It includes the cohort, raw metrics, calculated rates, denominators, normalized scores, user-defined weights, weighted contributions, missing-data rules, confounders and resulting action.
| Term | Plain-language definition | Required record | Common mistake |
|---|---|---|---|
| Objective | The decision the score is designed to support. | One sentence naming the outcome and eligible content. | Calling the objective “overall quality.” |
| KPI | A key performance indicator selected because it represents part of the objective. | Name, source, unit, window and decision use. | Including every available dashboard field. |
| Raw metric | The original observed count, duration or platform-reported rate. | Exact field label and value. | Showing only the final composite. |
| Calculated rate | A measure created by the analyst from a numerator and denominator. | Formula and both source values. | Calling a calculated value a native TikTok field. |
| Post-age window | The same elapsed time after publication used for every video. | For example, publication through exactly day 7. | Comparing lifetime data with first-week data. |
| Comparison cohort | The videos eligible under the same practical rules. | Inclusion, exclusion and sample size. | Scoring every account video together by default. |
| Baseline | A declared internal reference, such as the cohort distribution. | Dataset, period and method. | Treating an internal score as an industry benchmark. |
| Normalization | Conversion of unlike units to one comparable scale. | Method, cohort and directionality. | Adding views, seconds and percentages directly. |
| Weight | The share of the scorecard’s decision emphasis assigned by the user. | Percentage or decimal and stated rationale. | Describing it as TikTok’s platform weight. |
| Composite score | The weighted combination of normalized KPI scores. | Formula, contributions and included weights. | Treating the score as a causal diagnosis. |
| Sensitivity analysis | A recalculation under other reasonable assumptions. | Alternative weights, scores and ranks. | Publishing one arbitrary ranking as certain. |
| Confounder | A competing explanation for an observed difference. | What changed, when and which videos it affects. | Assuming the top score reveals the cause. |
| Decision rule | A predeclared condition that maps evidence to an action. | Threshold, quality gate, owner and review date. | Inventing a universal “good” score band. |
The score is meaningful only relative to its declared rules and cohort. A result of 70 is not automatically good, and a result of 45 is not automatically bad. Change the cohort, normalization method or objective weights and the number can change even when the raw video data do not.
What the Scorecard Can and Cannot Tell You
| The scorecard can | The scorecard cannot |
|---|---|
| Summarize selected evidence according to declared priorities. | Reveal TikTok’s recommendation algorithm or internal weights. |
| Compare videos measured under compatible rules. | Repair an invalid cohort or incompatible reporting windows. |
| Show which KPIs drive each ranking. | Explain why a metric value occurred. |
| Expose how a different objective changes the order. | Prove that one video is universally better. |
| Support a documented content decision. | Predict virality, future distribution or follower growth. |
| Identify rankings that are more or less robust to reasonable weights. | Turn rank stability into causal certainty. |
Governance rule: every published score should be accompanied by its objective, cohort, observation window, normalization method, weights and missing-data policy. If any of those changes, label the result as a different scorecard version.
Define the Decision Before Selecting TikTok Metrics
Write the decision before opening the dashboard. “Find our best video” is too broad. “Choose which seven-day organic tutorial concept to repeat for follower conversion” is usable because it identifies the content, time window and outcome.
Different objectives legitimately produce different metric sets and weights. The examples below are illustrative starting points, not TikTok algorithm weights, universal best practices or benchmarks.
| Illustrative objective | Possible KPI set | Illustrative weights | Important control | Decision supported |
|---|---|---|---|---|
| Content discovery | Fixed-age views; share rate by views; one viewing-depth measure | 50%; 30%; 20% | Same post age, topic, format and paid status | Which discoverable concept to repeat in a matched series |
| Watch depth | One viewing-depth measure; share-rate guardrail; comment-rate guardrail | 70%; 15%; 15% | Narrow duration band; do not include overlapping watch measures by default | Which structure deserves a controlled follow-up test |
| Community response | Comment rate by views; qualified-comment share from a coded sample; share rate by views | 40%; 40%; 20% | Same comment-eligibility and coding rules | Which prompt or topic merits a reply video or deeper discussion |
| Follower conversion | Post-attributed follow rate; profile-visit rate; one viewing-quality guardrail | 60%; 25%; 15% | Use only compatible attribution and denominator fields | Which proposition to repeat for audience growth |
If a required field is not available on the selected reporting surface, do not substitute a different-looking field after seeing the results. TikTok Studio provides account and content analytics, but tools and fields can vary across app, web, region and eligibility conditions.[1] Revise the KPI set for the entire cohort, use another approved compatible source or report that version of the scorecard as unavailable.
Build a Comparable TikTok Video Cohort Before Scoring
A weighted formula cannot repair an invalid comparison set. Begin with videos that answer the same practical question: tutorials from one campaign period, product demonstrations measured after seven days, commentary posts in a comparable duration band or videos designed for the same funnel objective.
| Eligibility dimension | Compatible rule | Why it matters | Example exclusion note |
|---|---|---|---|
| Analytics source | One named surface, export and retrieval method | Similar labels can use different definitions or refresh schedules. | Excluded: value came only from a different dashboard. |
| Field definition | Same exact native field or same calculated formula | A changed numerator or denominator changes meaning. | Excluded: “engagement” used a different action set. |
| Post-age window | Every video measured at the same elapsed age | Older posts have had more time to accumulate results. | Pending: video has not completed day 7. |
| Retrieval rule | Same timezone, cutoff and latency policy | Two captures may not represent equally complete data. | Flagged: export was captured before normal refresh time. |
| Organic or paid status | Separate organic, promoted and mixed records | Acquisition conditions are different. | Excluded: Promote campaign ran during days 2–5. |
| Format | Comparable tutorial, commentary, demonstration or other format | Viewing behavior and intent differ by format. | Excluded: photo post in a video cohort. |
| Duration band | A predeclared narrow range | Completion and watch measures depend on available length. | Excluded: 95 seconds versus a 25–40-second rule. |
| Topic and objective | Same decision context and audience promise | Demand and desired actions differ. | Excluded: trend reaction in an evergreen tutorial cohort. |
| Account conditions | Comparable account stage, access and policy status | Major account changes can alter exposure and available data. | Flagged: collaboration created unusual outside traffic. |
If the decision concerns view accumulation rather than multi-metric ranking, use the separate TikTok content lifespan method. A33 uses one fixed compatible window; it does not reproduce the repeated-snapshot lifespan analysis.
Choose Metrics Without Double Counting the Same Behavior
Choose a small set of KPIs from distinct performance families. More columns do not automatically add more information. Closely related metrics can give one underlying behavior several votes in the composite.
| Metric family | Possible evidence | Question answered | Redundancy risk |
|---|---|---|---|
| Exposure | Fixed-age video views or a compatible unique-audience field | How much measured exposure occurred? | Views and total watch time can both rise mainly because exposure rose. |
| Viewing depth | Average watch percentage or average watch time within a tight duration band | How much of the video did a recorded view consume on average? | Average watch time and watch percentage encode overlapping behavior. |
| Completion | Platform-reported completion or calculated complete views divided by views | How often did a view reach the end? | Completion can overlap with average watch percentage. |
| Distribution-oriented action | Shares or share rate by views | How often was the Share action recorded? | Do not include shares and an engagement rate that already contains shares. |
| Revisit-oriented action | Favorites or favorite rate where available | How often was the Favorite action recorded? | Favorites do not prove that a viewer returned. |
| Conversation | Comments, comment rate or a separately coded comment-quality measure | How much or what kind of conversation occurred? | Comments plus a combined engagement rate count comments twice. |
| Audience conversion | Compatible post-attributed follows divided by views or unique viewers | How often did the declared audience outcome occur relative to exposure? | Do not borrow account-level net followers and assign them to individual posts. |
Use a correlation review as a warning, not an automatic deletion rule. If two candidate KPIs move almost identically across the cohort and describe the same underlying behavior, keep the one that is closer to the decision or lower their combined emphasis. The OECD/JRC composite-indicator handbook treats variable selection, normalization, weighting, aggregation and sensitivity as separate design choices and warns that a poorly constructed composite can invite simplistic conclusions.[3]
Normalize TikTok Metrics to a Common 0–100 Scale
Views, seconds, comments and rates have different units. They cannot be added directly. A normalized metric score converts each KPI to a shared scale inside the eligible cohort while preserving the raw value beside it.
Percentile or Rank-Based Scoring
A simple rank-normalized method orders videos from best to worst for one KPI. Assign rank 1 to the best value and use average ranks for ties.
Here, n is the number of eligible videos with that KPI and rank is the video’s average rank after applying the declared direction. With five videos, ranks 1 through 5 become 100, 75, 50, 25 and 0. This method is comparatively robust to the magnitude of one extreme value because only order matters. It is also easy to explain.
The tradeoff is loss of distance information. A tiny lead and a huge lead can receive the same rank gap. Small cohorts create coarse scores, and ties need an explicit rule. If n = 1, a comparative rank score is unavailable.
Min–Max Scaling
Min–max scaling preserves the relative distance between the cohort minimum and maximum. For a higher-is-better KPI:
Value is the video’s raw KPI value; cohort minimum and cohort maximum are the lowest and highest eligible values for that KPI. The minimum becomes 0, the maximum becomes 100 and the other values fall between them.
For a lower-is-better KPI, reverse the direction:
Use lower-is-better only when the interpretation is defensible—for example, an error rate under a stable audit definition. Never reverse a metric merely to make the desired video rank higher.
If the maximum equals the minimum, the KPI contains no cohort-level discrimination and the denominator is zero. Predeclare one of two policies: give every video the same neutral score, such as 50, or remove that KPI from the entire scorecard version and publish a revised common weight set. Do not assign different handling by video.
Min–max scaling is sensitive to extremes. A single very large maximum can compress ordinary values near zero. Flag the observation, validate it and rerun the scores with a rank-based method or a justified alternative cohort as a sensitivity check. Do not delete an unusual observation only because it is inconvenient; NIST notes that outliers may be errors, random variation or substantively interesting and recommends investigation rather than automatic removal.[2]
Assign User-Defined Weights, Not “TikTok Algorithm Weights”
A weight states how much emphasis the analyst gives a KPI for this decision. A 30% share-rate weight means share rate contributes 30% of the declared scorecard. It does not mean TikTok gives shares a 30% recommendation weight.
- Choose weights before reviewing the composite ranking.
- Link every weight to the written objective.
- Use percentages that total 100% or decimals that total 1.00.
- Check whether several correlated KPIs receive excessive combined emphasis.
- Version the weight set whenever the objective changes.
- Keep at least two reasonable alternatives for sensitivity analysis.
Equal weighting is also a choice, not a neutral truth. It may be a clear base case when no defensible reason exists to favor one KPI, but it still says that every included metric receives the same decision emphasis.
Calculate the Weighted TikTok Content Score
Use either decimals or percentages consistently. If all five intended metrics are present and decimals total 1.00, the denominator is 1.00. If percentages total 100, the numerator can be divided by 100. The result remains on the 0–100 normalized scale.
For each KPI, save the weighted contribution: normalized score multiplied by weight. Contributions reveal why the final scores differ. A composite score without them hides the model.
If a metric is legitimately excluded for every video in a new reduced version, update the common denominator and label the version. If one video alone is missing a KPI, dividing by its remaining weights silently increases the importance of those available metrics. That video may no longer be comparable with complete records. Use such renormalization only when the policy was declared, the omission is disclosed and the decision remains defensible; otherwise leave the composite unavailable.
Handle Missing Values and Outliers Before Ranking
Missing is not zero. Zero means the compatible field was observed and its value was zero. Missing means the value was unavailable, not collected or not valid under the declared definition.
| Policy | When it may be defensible | Comparability effect | Required disclosure |
|---|---|---|---|
| Exclude the video | The missing KPI is mandatory for the decision. | Preserves one complete schema but reduces the cohort. | Video ID, exclusion reason and missing field. |
| Use a reduced common KPI set | The same smaller set is complete and adequate for all videos. | Restores like-for-like scoring in a new version. | Removed KPI, revised weights and version label. |
| Create separate scorecard versions | Two legitimate source or availability groups exist. | Scores are comparable only within each version. | Version-specific cohort and method. |
| Renormalize included weights | The omission is minor, predeclared and does not alter the decision construct. | May make the affected video different from complete records. | Original and included weight totals plus a comparability warning. |
| Report score unavailable | No defensible common comparison remains. | Avoids false precision. | Missing field and next retrieval date. |
Do not replace a missing value with zero, the cohort average or an invented estimate in a practical creator scorecard. Formal imputation requires a justified model, assumptions and validation; a reduced common set or unavailable result is usually safer.
For outliers, keep the raw record, confirm the source, record any paid or external exposure and compare at least two treatments: the declared base case and a sensitivity case using a rank-based method or justified exclusion rule. If removal changes the conclusion, the decision depends on that choice and must say so.
Step-by-Step TikTok Scorecard Workflow
- Write the decision objective. Name the content, outcome and action the score will support.
- Freeze the cohort rules. Define source, format, topic, duration, post age, publication period and paid status.
- Record the governance fields. Save retrieval time, timezone, owner, review date and version.
- Preserve native values. Copy exact platform field names before calculating anything.
- Calculate transparent rates. Store every numerator and denominator from the same source, scope and window.
- Select a limited KPI set. Remove or reduce overlapping measures.
- Declare directionality. Mark higher-is-better or justified lower-is-better before scoring.
- Check missingness and outliers. Apply one documented policy before normalization.
- Normalize inside the eligible cohort. Use one declared rank or min–max method for each scorecard version.
- Apply user-defined weights. Calculate and retain every weighted contribution.
- Run sensitivity scenarios. Recalculate with at least two other reasonable objective-based weight sets.
- Interpret rank stability. Identify stable positions and metric-dependent reversals without claiming certainty.
- Log confounders. Record promotion, collaborations, trend events, account changes, latency and outside traffic.
- Choose one measurable action. Name the owner, future cohort, expected direction and review date.
Hypothetical Worked Example: Four Seven-Day Tutorial Videos
Hypothetical example only: every value below is invented to demonstrate the method. The figures are not Tiksta research, typical account performance, a TikTok benchmark or evidence about platform distribution.
The decision is: Which seed-starting tutorial concept should the team adapt for its next organic video? The cohort contains four organic, English-language tutorials published during one campaign period, each 30–40 seconds long and measured exactly seven days after publication.
Source assumption: one team-controlled CSV captured from TikTok Studio web post analytics at 09:00 Europe/Istanbul time on day 7. For this fictional account, the approved extract is assumed to contain the native fields Video views, Complete video views, Shares, Comments and New followers attributed to post. This example schema does not claim that every TikTok Studio surface exposes those labels. In a real scorecard, preserve the exact available field names and omit unsupported KPIs.
Raw Values Before Normalization
| Video | Fictional concept | Duration | Video views | Complete video views | Shares | Comments | New followers attributed to post | Status |
|---|---|---|---|---|---|---|---|---|
| A | Seed-starting checklist | 34 seconds | 10,000 | 4,000 | 200 | 80 | 100 | Organic; complete |
| B | Soil-mix demonstration | 36 seconds | 8,000 | 4,400 | 120 | 96 | 64 | Organic; complete |
| C | Watering mistake | 32 seconds | 14,000 | 4,900 | 350 | 70 | 84 | Organic; complete |
| D | Transplant timing | 38 seconds | 6,000 | 3,000 | 60 | 90 | 72 | Organic; complete |
Calculated Rates and Denominators
The scorecard uses five KPIs: fixed-age views, completion rate, share rate by views, comment rate by views and post-attributed follow rate by views. It does not add a combined engagement rate because that would count shares and comments again.
Share rate by views = Shares ÷ Video views × 100
Comment rate by views = Comments ÷ Video views × 100
Post-attributed follow rate by views = New followers attributed to post ÷ Video views × 100
The view-based follow rate is an exposure-normalized outcome, not a unique-person conversion rate, because one person may create more than one view. The example treats comment volume as higher-is-better only because the fictional team’s objective values relevant conversation and has already reviewed comment quality; a raw comment count does not reveal sentiment or usefulness.
| Video | Completion calculation | Completion rate | Share-rate calculation | Share rate | Comment-rate calculation | Comment rate | Follow-rate calculation | Follow rate |
|---|---|---|---|---|---|---|---|---|
| A | 4,000 ÷ 10,000 | 40.00% | 200 ÷ 10,000 | 2.00% | 80 ÷ 10,000 | 0.80% | 100 ÷ 10,000 | 1.00% |
| B | 4,400 ÷ 8,000 | 55.00% | 120 ÷ 8,000 | 1.50% | 96 ÷ 8,000 | 1.20% | 64 ÷ 8,000 | 0.80% |
| C | 4,900 ÷ 14,000 | 35.00% | 350 ÷ 14,000 | 2.50% | 70 ÷ 14,000 | 0.50% | 84 ÷ 14,000 | 0.60% |
| D | 3,000 ÷ 6,000 | 50.00% | 60 ÷ 6,000 | 1.00% | 90 ÷ 6,000 | 1.50% | 72 ÷ 6,000 | 1.20% |
Min–Max Normalization
All five KPIs are higher-is-better for this declared objective. For views, the cohort minimum is 6,000 and the maximum is 14,000. Video A’s normalized view score is:
For completion rate, the minimum is 35% and the maximum is 55%. Video A’s normalized completion score is:
| Video | Views score | Completion score | Share-rate score | Comment-rate score | Follow-rate score |
|---|---|---|---|---|---|
| A | 50.00 | 25.00 | 66.67 | 30.00 | 66.67 |
| B | 25.00 | 100.00 | 33.33 | 70.00 | 33.33 |
| C | 100.00 | 0.00 | 100.00 | 0.00 | 0.00 |
| D | 0.00 | 75.00 | 0.00 | 100.00 | 100.00 |
Base-Case Weighted Score
The illustrative base case uses equal 20% weights. This is a transparent neutral starting assumption for the example, not evidence that the five KPIs are equally important to TikTok.
| Video | Views contribution (20%) |
Completion contribution (20%) |
Share contribution (20%) |
Comment contribution (20%) |
Follow contribution (20%) |
Weighted score | Rank |
|---|---|---|---|---|---|---|---|
| A | 10.00 | 5.00 | 13.33 | 6.00 | 13.33 | 47.67 | 3 |
| B | 5.00 | 20.00 | 6.67 | 14.00 | 6.67 | 52.33 | 2 |
| C | 20.00 | 0.00 | 20.00 | 0.00 | 0.00 | 40.00 | 4 |
| D | 0.00 | 15.00 | 0.00 | 20.00 | 20.00 | 55.00 | 1 |
For Video A, the unrounded calculation is (50 × 0.20) + (25 × 0.20) + (66.6667 × 0.20) + (30 × 0.20) + (66.6667 × 0.20) = 47.6667, displayed as 47.67. Contributions were calculated from unrounded normalized scores; displayed components may differ by 0.01 after rounding.
Sensitivity Analysis and Rank Stability
The base case is only one statement of priorities. Scenario A emphasizes discovery: views 40%, completion 15%, share rate 30%, comment rate 5% and follow rate 10%. Scenario B emphasizes community and conversion: views 10%, completion 15%, share rate 10%, comment rate 25% and follow rate 40%. Both are illustrative user choices.
| Video | Base case score; rank |
Scenario A: discovery score; rank |
Scenario B: community/conversion score; rank |
Rank range | Main driver | Interpretation | Next action |
|---|---|---|---|---|---|---|---|
| A | 47.67; 3 | 51.92; 2 | 49.58; 3 | 2–3 | Above-minimum shares and follows without leading one KPI | Middle position is comparatively stable across these priorities. | Keep as a reference concept; no objective makes it the clear winner. |
| B | 52.33; 2 | 41.83; 3 | 51.67; 2 | 2–3 | Highest completion and solid comment rate | Also stays in the middle; weaker discovery emphasis reduces its score. | Use as the watch-depth control in a follow-up test. |
| C | 40.00; 4 | 70.00; 1 | 20.00; 4 | 1–4 | Highest views and share rate; lowest other three normalized scores | Ranks first only when discovery receives high combined emphasis. Its position is strongly assumption-sensitive. | Do not declare it the universal winner; retest the concept with a conversion-oriented call to action. |
| D | 55.00; 1 | 26.25; 4 | 76.25; 1 | 1–4 | Highest comment and follow rates but lowest views and shares | Ranks first for balanced and conversion-led decisions, but last for discovery. | Adapt it only if community or follower conversion is the declared objective. |
Videos A and B have relatively stable middle positions, with rank ranges of 2–3. Videos C and D are unstable: each spans ranks 1–4 because their KPI profiles are polarized. The instability is useful. It shows that asking “Which video won?” hides the real choice between discovery and conversion.
Rank stability means the ordering survives the tested assumptions. It does not mean the score is causal, statistically significant or certain to repeat. The alternative weights must also be reasonable for the decision; testing absurd weight sets does not add rigor.
The measurable decision is to create one new 30–40-second organic tutorial that adapts Video D’s conversion proposition while using Video C’s clearer shareable problem framing. Measure it at day 7 using the same five raw inputs. Predeclare follow rate as the primary KPI, share rate as the guardrail and do not claim causation from one follow-up post.
Reusable TikTok Content Scorecard Template
Scorecard Governance
| Field | What to enter | Why it matters | Blank spreadsheet entry |
|---|---|---|---|
| Scorecard version | Stable version name or ID | Separates changed methods. | [Version] |
| Decision objective | One action-oriented question | Controls metrics and weights. | [Objective] |
| Cohort definition | Eligible format, topic, duration, period and objective | Defines the comparison population. | [Definition] |
| Inclusion rules | Every rule a video must meet | Prevents result-driven selection. | [Rules] |
| Exclusion rules | Predeclared reasons for removal | Preserves an audit trail. | [Rules] |
| Analytics source | Exact surface, export or approved integration | Keeps fields compatible. | [Source] |
| Retrieval date and time | Exact timestamp | Documents data freshness. | [YYYY-MM-DD HH:MM] |
| Timezone | Named zone | Fixes boundaries. | [Timezone] |
| Observation window | Fixed post age or account period | Equalizes opportunity. | [Window] |
| Minimum required metrics | Mandatory KPI list | Controls score eligibility. | [KPI list] |
| Metric directionality | Higher- or lower-is-better with rationale | Prevents arbitrary reversal. | [Direction by KPI] |
| Normalization method | Rank, min–max or another declared method | Makes scores reproducible. | [Method] |
| Weight set | Metric weights and objective rationale | Exposes decision emphasis. | [Weights totaling 100%] |
| Missing-data policy | Exclude, reduce, separate, renormalize or unavailable | Stops missing values becoming silent zeros. | [Policy] |
| Outlier policy | Validation and sensitivity rule | Stops convenience-based deletion. | [Policy] |
| Scorer or owner | Accountable person or role | Creates ownership. | [Owner] |
| Review date | Next decision checkpoint | Connects analysis to action. | [Date] |
Video-Level Evidence
| Field group | Field | What to store | Blank spreadsheet entry |
|---|---|---|---|
| Identity | Post ID or URL | Stable identifier | [ID/URL] |
| Content | Format | Declared format label | [Format] |
| Content | Topic | Main subject or query | [Topic] |
| Content | Duration | Video length in seconds | [Seconds] |
| Time | Publication timestamp | Date, time and timezone | [Timestamp] |
| Acquisition | Organic, promoted or mixed | Status plus campaign dates | [Status] |
| Source evidence | Raw metric value | One column per exact native field | [Value] |
| Calculated evidence | Rate numerator | Exact compatible count | [Numerator] |
| Calculated evidence | Rate denominator | Exact compatible base | [Denominator] |
| Calculated evidence | Calculated rate | Formula result and unit | [Rate] |
| Scoring | Normalized metric score | 0–100 result per KPI | [Score] |
| Scoring | User-defined metric weight | Declared percentage or decimal | [Weight] |
| Scoring | Weighted contribution | Normalized score × weight | [Contribution] |
| Scoring | Total score | Weighted composite or unavailable | [Total/NA] |
| Scoring | Rank | Rank within this version and cohort | [Rank] |
| Quality | Missing or outlier flag | Field, reason and treatment | [Flag] |
| Context | Confounder notes | Promotion, external traffic, trend, collaboration, latency or account change | [Notes] |
| Quality | Confidence or data-quality note | High, medium or low with evidence-based reason | [Level; reason] |
| Decision | Resulting action | Repeat, revise, test, monitor, wait or exclude | [Action] |
This template works in any spreadsheet that supports arithmetic, ranking and sorting. A dashboard may display the results, but the underlying rows remain the source of truth. Keep raw evidence visible; do not replace it with a chart or composite alone.
Decision Table and Action Log
The score summarizes selected evidence; the action log converts that evidence into an owned decision. If the scorecard is part of a broader operating cadence, place the result inside Tiksta’s weekly TikTok analytics audit rather than rebuilding the full audit in this file.
The tools have different jobs. A dashboard displays selected evidence; the scorecard applies the declared normalization and weights; the action log records who will do what and when; and an experiment log preserves the question, hypothesis, changed variable, comparison cohort, primary KPI, guardrail, result and confounders for a planned test. A forecast estimates a future result under assumptions. A scorecard ranks observed eligible videos and must not be relabelled as a forecast.
| Observed result | Data-quality condition | Interpretation | Decision rule | Action | Next measurement |
|---|---|---|---|---|---|
| One video ranks first in all reasonable scenarios. | Complete compatible inputs; no dominant unresolved confounder | The ranking is robust to the tested priorities. | Act only if the objective and effect size are practically relevant. | Adapt one defined feature in the next matched cohort. | Same KPI set and post-age window. |
| A video ranks first only under one heavily emphasized KPI. | Inputs valid, but profile is polarized | The result is objective-dependent. | Select it only when that KPI matches the decision. | State the dependency and add a guardrail KPI. | Primary KPI plus guardrail at matched age. |
| Ranks change after an outlier treatment. | Extreme value validated but influential | Normalization choice materially affects the result. | Do not publish one ranking without the sensitivity result. | Collect more comparable videos or use rank scoring. | Expanded cohort and both normalization methods. |
| A required KPI is unavailable for one video. | Missing, not zero | No fully comparable composite exists under the base schema. | Apply the declared missing-data policy. | Wait, exclude or rebuild a common reduced version. | Field retrieval or new version review. |
| Two scores differ by a small rounded amount. | Inputs rounded or cohort small | The numerical order may not be practically meaningful. | Treat as a tie unless a predeclared decision threshold is met. | Use qualitative context or collect another matched observation. | Unrounded inputs and next cohort. |
Action Log Template
| Action-log field | Required entry | Blank value |
|---|---|---|
| Action ID | Stable identifier | [ID] |
| Scorecard version | Exact model and cohort version | [Version] |
| Observation | Score, rank, driver and sensitivity result | [Observation] |
| Decision | Act, test, monitor, wait or reject | [Decision] |
| Planned change | One specific content change | [Change] |
| Owner | Accountable person or role | [Owner] |
| Due date | Implementation date | [Date] |
| Future comparison cohort | Eligibility rules for the follow-up | [Cohort] |
| Primary KPI | Metric selected before publication | [KPI] |
| Guardrail KPI | Metric that should not materially worsen | [KPI] |
| Expected direction | Directional expectation, not a guarantee | [Direction] |
| Review date | Matched observation point | [Date] |
| Actual result | Raw values, rates and comparison | [Result] |
| Confounders | Competing explanations | [Notes] |
| Follow-up | Repeat, revise, stop or collect more data | [Next action] |
If the selected KPI is a standard engagement calculation, Tiksta’s TikTok engagement rate calculator can support that separate calculation. Record its formula, inputs and denominator; do not present the calculator output as the content scorecard.
Limitations and Common Misinterpretations
- The weights belong to the analyst. They are not TikTok algorithm weights or estimates of platform importance.
- The score is not a diagnosis. It summarizes selected evidence but does not explain the cause of views, watch behavior, actions or follows.
- The objective is not universal quality. Discovery, conversation, viewing depth and follower conversion can produce different rankings.
- A baseline is not a benchmark. The cohort supplies a local reference; it does not establish what is good for other accounts.
- Normalization is cohort-dependent. Add or remove a video and every min–max or rank score may change.
- Min–max scaling is outlier-sensitive. Validate extremes and show an alternative treatment when they drive the ranking.
- Ranks hide distance. First and second may be nearly tied or far apart.
- Small samples create coarse results. Avoid decimal-level confidence when only a few videos are eligible.
- Missing is not zero. Silent substitution or reweighting creates false comparability.
- Overlapping KPIs double count behavior. Do not include component actions and a combined rate that contains them without a specific rationale.
- A stable rank is not certainty. It is robust only to the assumptions tested, not every possible model or future condition.
- A numerical difference is not automatically meaningful. Data latency, rounding, cohort size and practical effect size matter.
- Observational comparison is not causal proof. Paid activity, external traffic, topic demand, collaborations and account changes may confound the result.
- No score threshold predicts virality. Do not invent “good,” “bad” or “will go viral” bands.