Running it
Fixed slots, protected days
Availability that responds to demand instead of a plan expands until it owns the week.
Guides on Running it: The admin that turns income into a trade
A weekly rhythm holds when it is designed in advance: fixed reply windows inside peak demand, fixed production sessions, and one day that is genuinely off. Availability that merely reacts to demand does not settle at a sensible level. It expands, because every individual decision to be available for one more evening is reasonable and the aggregate is not.
Designed weeks survive a busy month. Reactive weeks are why people leave this trade at month seven having earned well.
Demand is not flat, and the plan has to admit it
Enquiries in this trade cluster in evenings and at weekends, because that is when the buyers are not at work. Any schedule that ignores that pattern trades away bookings for tidiness.
So the design problem is not "how do I work office hours". It is how to be present in the windows that matter without being present in all of them.
That splits into three kinds of time, and the mistake is running them together.
| Kind of time | When | How much |
|---|---|---|
| Reply windows | Inside peak demand, most days | 30 to 60 minutes, once or twice |
| Production sessions | Anywhere, including off-peak | 2 or 3 blocks a week |
| Off | One full day, fixed | 1 day |
Reply windows have to sit where the buyers are. Production does not, which is the freedom that makes the rest of the week possible - the case for batching production is the mechanism this schedule depends on.
The slots
Pick two reply windows a day inside your peak, and publish your turnaround rather than your availability.
"Replies within a few hours, delivery within two days" is a promise you can keep from a fixed slot. "Usually online in the evenings" is a promise about your presence, and it is the one that erodes.
The distinction matters more than it sounds. Buyers evaluate response time and turnaround; neither requires you to be reachable continuously, and the argument against permanent alertness is the detailed version.
Production sessions go where your attention is best, not where it is left over. For most people that is not late evening after a reply window, which is the slot it defaults to.
The protected day
One day a week with no replies, no production, and notifications off.
Fixed rather than floating, because a floating rest day is the one that gets spent. Announced in your listing if the platform allows it, so it becomes a fact about your service rather than a lapse.
The commercial case is that this trade prices per job and has no sick pay, so your throughput next month is a direct function of whether you are still able to work at your normal speed. Burnout in a per-job trade is not a wellbeing aside on this site, it is a capacity problem with a revenue number attached. Long weeks also carry a health cost that has been counted: a 2021 WHO and ILO analysis linked working 55 or more hours a week to an estimated 35% higher risk of stroke, compared with working 35 to 40 hours.
The practical case is that a fixed day is easier to defend to a buyer than a variable one. Nobody argues with "I do not work Wednesdays".
When the plan meets a busy week
Two rules, and holding them is most of the discipline.
Absorb overflow by extending production sessions, never by adding reply windows. Reply windows are the ones that colonise the week, because each is short enough to feel free.
When capacity is genuinely exceeded, lengthen your quoted turnaround rather than working longer. A slower published turnaround is a price signal and often a correct one - what a queue actually signals covers why being visibly booked is worth more than being infinitely elastic.
Track which days actually produced enquiries for a month before trusting your sense of the pattern. Memory over-weights the evening you were interrupted and under-weights the quiet Sunday that converted. Buyers describe their own commissioning habits fairly consistently, and the buyer-side account of how they pick and when they look is a better starting hypothesis than intuition.
Keep the tracking itself trivial. A tally in one sheet is enough, and anything more elaborate becomes a fourth kind of time - the minimum toolset argument applies to your own admin as much as to the work, and the same is true of gear you were told you needed but which mostly adds setup to every session.
It also has to survive the weeks that break it, which is working while ill or travelling.
The schedule that holds is the one you can describe in a sentence, because that is the one you will still be running in October. Platform-side scheduling controls for judges, including how availability is displayed to buyers, are on Rate Cock's judges page.