Direct answer: admit only approved briefs to the production backlog, then score each from zero to three for readiness, current promise fit and reuse value. Subtract an effort score from zero to three. Rank the total, apply a documented tie-break rule, and select only the number of briefs your current capacity can complete.
- Eligibility gate: approved concept, creator boundary confirmed and definition of done present.
- Priority score: readiness + promise fit + reuse value - effort.
- Tie-break: current content-library gap, followed by oldest ready brief.
- Output: next, later, blocked or remove, with a reason and review date.
This prioritizer ranks production briefs that already exist. It does not generate ideas, plan a publishing calendar, choose promotion tasks or measure content performance. For questions that still need turning into briefs, start with the fan question content planner.
A backlog should reduce decision friction, not become a graveyard. Every item needs an owner, a useful status and enough detail for a creator to know whether it is genuinely ready.
Separate ideas from the production backlog
Keep unreviewed ideas in an idea bank. A production backlog begins only after a concept fits the selected niche promise, stays inside creator-approved boundaries and has a definition of done. Mixing loose ideas with ready briefs makes a long list look like usable capacity.
Each admitted brief should name its audience job, format, key scene or proof, required assets, estimated effort, reuse possibilities and content-library gap served. If any of those are unknown, mark the item blocked before scoring.
Do not reward an item merely because it has waited for months. First check whether it is still relevant and approved. Old, ambiguous work can consume attention without becoming more valuable.
Create the backlog priority card
Copy these fields: brief ID; working title; date added; owner; audience job; niche promise; definition of done; required assets; boundary confirmed; readiness score; promise-fit score; reuse-value score; effort score; total; library gap; dependencies; status; decision reason; and next review date.
Use zero to three for every factor. Keep one sentence of evidence beside each score. A number without a reason is difficult to review and easy to manipulate when someone already prefers a concept.
The card is the route-specific practical artifact. Keep the original score when a brief enters production and add an outcome note later. Do not rewrite history after the content performs differently from expectation.
Apply the readiness gate before ranking
Readiness asks whether production can start with the people, location, equipment, permissions and source material currently available. Three means ready now; two means one small confirmed dependency; one means several unresolved items; zero means the brief cannot start.
An item with zero readiness is blocked, not low priority. Move it to a blocked view with the dependency, owner and check date. This keeps impossible work from competing with briefs a creator can complete this week.
Do not treat buying more equipment or crossing a creator boundary as a routine dependency. Change the brief or remove it. The backlog exists to organise approved work, not pressure a creator into an unapproved setup.
Score current promise fit
Promise fit measures how directly the brief supports what the profile currently asks subscribers to expect. Three means it clearly advances a recurring promise or current series. Two means it supports the niche but is not urgent. One is an adjacent experiment. Zero is off-promise.
Attach the promise sentence to the score. If the reviewer cannot finish “This fits because ___,” return the brief for clarification. A fashionable format does not earn fit merely because other creators use it.
When the promise has recently changed, rescore the backlog rather than carrying old priorities forward. Archive briefs that no longer belong, with a short reason.
Score reuse value without counting duplicates
Reuse value asks how many distinct approved jobs the production can support after capture: a core post, preview crop, series recap, still image, archive asset or later comparison. Three means several clearly planned uses; zero means a single narrow use.
List the outputs instead of writing “high reuse.” Each output must have a real destination and remain within the content boundary. Cropping the same frame three ways does not automatically create three meaningful assets.
Reuse should not override quality. If capturing extra variations will weaken the core brief or extend the session beyond capacity, reduce the scope and the score.
Subtract effort with creator-entered estimates
Effort includes preparation, setup, capture, changes, editing, quality review and file handling. Zero means a very light task inside the current setup; three means a demanding multi-stage brief. Use the creator's recent time records rather than generic time estimates.
Subtracting effort does not mean complex content is undesirable. It helps compare the work with current capacity. A high-effort brief can still rank first when promise fit, readiness and reuse are strong.
When two briefs share a setup, keep their individual effort scores but note the batching opportunity. Do not quietly cut both estimates before the batch is actually planned.
Calculate, rank and apply tie-breaks
Total = readiness + promise fit + reuse value - effort. The possible range is minus three to nine. Sort highest first, then inspect the evidence rather than accepting the spreadsheet blindly.
For equal totals, first choose the brief that closes the most important verified gap in the content library coverage calculator. If the gap priority is also equal, choose the oldest ready brief. Write any override and its reason.
Never change a factor's definition to make a preferred item win. If the scoring method produces an obviously poor order, discuss the evidence and revise the method prospectively for all items.
Work a three-brief prioritization example
Brief A scores readiness 3, fit 3, reuse 2 and effort 1, total 7. Brief B scores 2, 3, 3 and 3, total 5. Brief C scores 3, 2, 1 and 0, total 6. The current capacity supports two briefs.
A and C enter the next-production column. B remains later because an asset dependency reduces readiness and its effort is high. The creator adds an owner and check date for that asset instead of repeatedly reconsidering B during the week.
These numbers illustrate the worksheet. They do not establish what a creator should produce or imply that lightweight content is generally more valuable.
Limit work in progress to current capacity
The ranked list is not the production plan. Select only as many briefs as can meet definition of done in the current capacity. Extra high-ranking items stay ready for the next pull instead of becoming partially completed work.
Compare the selected set with the content strategy plan. A backlog ranks execution; strategy determines which audience promises and content roles matter now.
When production starts, mark the brief in progress and record the date. When it finishes, record actual effort and any reusable outputs created. Feed those actuals into future estimates.
Review the backlog on a fixed cadence
Run a short review weekly or whenever capacity changes materially. Remove duplicates, update blocked dependencies, rescore changed briefs and archive items that no longer fit. Do not conduct a full strategy debate during every prioritization session.
Track ageing by status. A ready item that never rises may have weak fit or hidden effort. A blocked item with repeated missed check dates may need a smaller replacement brief. Write the decision so the same ambiguity does not return.
Keep removed briefs recoverable with their history. “Removed because the series promise ended” is better than deleting the row and later recreating the same idea without context.
Create an escape route for blocked briefs
For every blocked item, write the smallest acceptable version that could proceed without the missing dependency. A location-heavy brief might have a studio alternative; a complex comparison might become one focused explanation. The smaller version must still meet a real audience job and the creator's standard.
Do not automatically replace the original. Give the alternative its own brief ID, effort estimate and promise-fit score. This prevents a reduced concept from inheriting a high score earned by work it no longer contains.
If neither version can move by the next review date, choose an explicit action: keep blocked with a new external date, remove from the active backlog, or return the audience job to planning. Repeatedly carrying an ownerless block is not prioritization.
Track how many review cycles an item spends in each state. The count is a prompt to inspect the brief, not a rule that older work must win. Repeated ready-but-unselected items may reveal weak promise fit, while repeated blocks may reveal a dependency that needs a different production approach.
Limitations and primary sources
Limitations: scores reflect the evidence and definitions entered by the creator. The method does not predict audience response, content quality or revenue. It can also under-rank experimental work when every factor favours current, ready formats, so deliberate experiments should be commissioned before entering the backlog.
The framework adapts the UK Government Service Manual's guidance that priorities should reflect limited capacity, evidence and regular review, plus its current guidance to plan from understood issues and dependencies. Review briefs against the current OnlyFans Terms of Service before production. The four-factor score and tie-break sequence are original SirenCY editorial tools.