Pay
A queue is permission to raise the price
A backlog is the only evidence that your rate is below what the market will bear.
Guides on Pay: Pricing, from first principles to the annual review, The ceiling is hours, and it arrives sooner than people expect, What rating work actually pays
If people are waiting to book you, your price is too low. That is not a motivational statement, it is what a queue means: demand at the current price exceeds the supply you can produce, and the only two levers are more hours or a higher number.
Reading the queue honestly
One busy week is not a backlog. A queue is a wait that persists across at least three or four weeks and survives a normal quiet patch.
Distinguish it from two things that look identical from inside.
A scheduling artefact: everyone wants the same evening slot, and your Tuesday afternoons are empty. The fix is availability, not price.
A turnaround problem: the wait exists because each job takes you longer than you advertised. The fix is your process, and raising the price on a late delivery is how a good reputation ends.
A real queue looks like enquiries arriving faster than slots free up, at a rate that holds when you stop doing anything promotional.
Communicating a wait without losing the booking
Buyers tolerate a wait far better than earners expect, provided the wait is a stated number rather than a vague apology.
Say the date. "The next slot is the 14th, delivery by the 17th" holds a booking. "I am quite backed up at the moment, I will let you know" loses it to whoever answers next.
Publish the wait on the listing rather than revealing it in a message. It filters out the people who needed it yesterday before they take up your time, and it makes the wait read as evidence rather than as an excuse. A stated wait also converts into a legitimate premium for jumping it, which is the mechanism behind charging for urgency and the cleanest first step before touching your base rate.
Using it as the trigger, not working longer
The value of a queue is that it turns a price rise from a guess into a decision with evidence behind it.
Raise the number. If the queue shortens to roughly nothing and your income is flat, you found the market price and you now have your evenings back. If it shortens a little and your income rises, raise again. If it vanishes and enquiries stop, you overshot and you can move back, which is a much smaller problem than it feels like at the time - what to do when bookings stop after a rise is the map for that fortnight.
How big a step to take is covered in the first rate rise.
What the queue does not license is a scarcity performance. Regulators treat invented scarcity as misleading: the UK Competition and Markets Authority wrote in 2023 that scarcity "claims that are untrue because the business in fact has plenty of stock are misleading". An invented waiting list is discovered quickly in a trade this small, and buyers comparing who to commission are already reading availability as a quality signal - the buyer-side account of choosing a judge makes plain how much weight sits on being visibly booked.
The awkward case
Sometimes the queue is real and you still cannot raise, because you are early and the reviews matter more than the margin.
That is a defensible choice for a fixed period. Give it an end date, write the date down, and treat the queue as a measurement you are choosing not to act on yet rather than one you have not noticed. Something you can count is worth keeping even when you are ignoring it, which is the same reason logging your own numbers pays off months later, and the general case for treating collected figures as data rather than decoration holds here too.
Where a marketplace surfaces availability and backlog to buyers automatically, that display is a product feature and works differently on each one - Rate Cock's judges page documents how it behaves there. Automated scoring, worth noting, never has a queue at all, and the tooling that provides it is precisely why a human wait has to be short enough to be worth choosing.