A content operations staffing model that survives eight shows a year

A group editorial lead I know added a fifth writer to a desk covering eight shows and published exactly the same number of pieces the following quarter. The drafts existed. They sat in a queue behind a legal reviewer who worked four days a week and had never been part of the conversation about headcount.

That is the normal outcome, and a content operations staffing model built on ratios will reproduce it every time. One editor per three writers, one designer per portfolio, a reviewer somewhere. Ratios describe an organisation chart. They say nothing about which stage in your pipeline runs out of capacity first, and that stage is the only one where a hire changes output.

Counting touches per published asset

Before staffing anything, count what actually happens to a piece.

A touch is one person handling one asset one time at one stage. Five stages cover most event media desks: commission, draft, edit, review, publish. Review means whatever gate you have between an edited draft and a live page, which might be legal, a technical expert, a show director who wants sight of anything mentioning a sponsor, or all three in sequence.

Take one month of published pieces and reconstruct the touches from the version history and the email thread. A typical result on a desk I have looked at recently, for 32 published pieces:

• commission, 32 touches
• draft, 41 touches, because nine pieces were rewritten from a first attempt
• edit, 74 touches, an average of 2.3 editing passes per piece
• review, 38 touches, because six pieces went round twice
• publish, 32 touches

That is 217 touches for 32 assets, 6.8 per asset. The interesting number is the 74. If editing is running 2.3 passes per piece, either the commissioning brief is thin or the writers are wrong for the brief, and both of those are cheaper to fix than a hire.

Where is the constraint on your desk?

Convert each stage into a weekly throughput, measured rather than assumed.

Four writers producing three usable drafts a week each gives 12 drafts a week. Two editors clearing five pieces a week each gives 10. One legal reviewer, four days a week, clearing two pieces a day gives 8. Publishing clears 20 because it is largely mechanical.

Throughput for the whole desk is 8 pieces a week, the lowest number in that list. Every stage above 8 is running with slack, and the slack shows up as work in progress rather than as idle people, because writers keep writing.

The fifth writer takes drafting from 12 to 15 a week. Published output stays at 8. What changes is the queue.

The arithmetic of a queue, done once by hand

Little proved in 1961, in Operations Research, that for a stable queuing system the mean number of units in the system equals the arrival rate times the mean time each unit spends in it, written L equals lambda W. The proof holds whatever the arrival and service time distributions look like, whatever the number of servers, and whatever the queue discipline, which is why it applies to an editorial pipeline as readily as to a call centre.

Rearranged, the mean time in the system is the work in progress divided by throughput.

Suppose your desk currently carries 40 pieces somewhere between commissioned and published, and publishes 8 a week. Mean time from commission to publication is 40 divided by 8, five weeks. Now add the fifth writer. Drafts arrive faster, nothing downstream changes, and after a quarter the work in progress has settled at 55 pieces. Mean time is 55 divided by 8, 6.9 weeks.

You paid for a writer and bought yourself thirteen extra days of lag between commissioning a piece and seeing it live. On a show brand where a piece commissioned in the agenda-release window has to land before the early rate closes, thirteen days is the difference between a useful asset and a late one.

The same arithmetic run the other way is the argument for the hire you should make. Take review from 8 a week to 12 by adding two days of a second reviewer. Throughput becomes 10 a week, set by editing. Work in progress falls, because arrivals no longer outrun service, and mean time falls with it. Two days of reviewer time bought two extra published pieces a week. A full writer bought nothing.

Why review is the constraint on an event media desk

Three things push the gate to the end of the pipeline in this industry specifically.

The first is that a show brand publishes about its own exhibitors, sponsors and speakers. Almost every piece has a commercial relationship inside it, so somebody commercial has to see it. That reviewer has a day job.

The second is that the expertise is scarce and external. A piece about a regulatory change affecting your vertical needs somebody who knows the regulation, and that person is usually a speaker or an advisory board member rather than an employee. Their turnaround is measured in weeks and cannot be scheduled.

The third is that review is load bearing for search, so removing it is not available as a fix. Google's guidance on creating helpful, reliable, people-first content, in its 2025 revision, asks publishers to consider whether "this content written or reviewed by an expert or enthusiast who demonstrably knows the topic well?" and whether the content "clearly demonstrate first-hand expertise and a depth of knowledge". A desk that solves its throughput problem by dropping the expert gate has solved it against the thing the ranking guidance asks for.

There is a fourth pressure arriving quickly. UFI's 36th Global Exhibition Barometer, published in January 2026 from 378 companies in 57 countries, reports 87 per cent of exhibition companies now using AI, up four points in six months. Drafting capacity across this industry is rising sharply and review capacity is not. If your desk adopts machine drafting without touching the gate, the ratio between arrivals and service gets worse, and Little's formula turns that directly into a longer cycle time. The review design for machine-drafted copy has its own problems, which sit with an editorial review workflow for ai drafts.

What to do when review is the constraint

Adding reviewers is the obvious move and often the wrong first one, because reviewer time is the most expensive hour in the pipeline.

Segment by risk first. Not every piece needs the same gate. A floorplan explainer with no named company in it does not need legal. A speaker interview does. Write a two-line rule that routes pieces into a full gate or a light gate at commissioning, and measure what share goes each way. On the desk above, if 60 per cent of pieces can take the light gate, effective review capacity rises from 8 a week to about 13 without hiring anyone.

Then attack the rework. Six of 38 review touches were second passes, 16 per cent. Find out what the reviewer changed. If it is the same category of thing every time, a named company that needs a disclosure line, a claim about a sponsor that needs softening, that belongs in the brief, and it moves the work from the scarce stage to the cheap one.

Batch the external experts. An advisory board member who will not turn round one piece in a week will often turn round four in a fortnight. Group the pieces that need them and accept a fixed slower lane, which is a worse cycle time on a small subset and a better one everywhere else.

Only then hire, and hire into review. Two days a week of a second reviewer, at a rate above a writer's, will still be the cheapest published piece you buy that year.

What the model looks like written down

A staffing model worth having fits in four lines and contains no organisation chart at all.

Stage capacities, measured, in pieces per week. Current work in progress. Implied cycle time from those two numbers. The one stage you intend to change next quarter and the throughput you expect afterwards.

Recheck it quarterly, because the constraint moves. Fix review and it lands on editing. Fix editing and it lands on the commissioning brief, at which point the problem is portfolio coordination and belongs with editorial operations across event brands. Fix that and it lands on writer supply, which is when the fifth writer finally makes sense.

The publishing rhythm you are staffing towards is a separate decision from the staffing itself. How many pieces a show site needs in the quiet months to hold reader habit and crawl frequency is the subject of publishing cadence between editions, and it sets the throughput target this model has to hit.

Where this stops

Little's formula needs a stable system, and an event media desk is seasonal by construction. In show week your arrival rate triples and your reviewers are on the floor. The mean time you calculated in February describes nothing that happens in September. Run the numbers separately for the peak and the trough, or the average will flatter the peak and slander the trough.

The touch count is also gameable in a way worth naming. Once people know editing passes are being counted, editing passes drop and the changes get made by comment in the document instead. You will see a clean number and no change in cycle time. The defence is to watch cycle time as the primary measure and treat touches as the explanation, since cycle time is measured from timestamps nobody edits.

The deeper limit is that none of this says anything about whether the pieces are any good. A desk can raise throughput from 8 to 12 a week and publish twelve worse things. Throughput is a capacity measure and has to be read next to whatever you use for quality, which for most desks is a slow, noisy signal and needs its own treatment.

Start this week by opening your content management system and pulling two timestamps for every piece published in the last quarter: the date it was commissioned and the date it went live. The median gap is your current cycle time. Divide your current work in progress by weekly published output and see whether the two numbers agree. Where they disagree, you have found work sitting somewhere nobody is counting. The wider approach this sits inside is described on the content studio page.