Ten jobs one week, four the next: stabilising workflow before you hire

Because the work was always uneven. You just could not see it arriving. If you run your diary on a short horizon, anything past the next week or two lives in an inbox, a text thread, a strata portal or someone's head. So a quiet fortnight looks like a demand collapse when it is often approved jobs sitting unscheduled, waiting on access, parts or a body corporate sign-off. An owner on r/Plumbing described the exact shape of it: "Some weeks we’re doing 10–15 jobs, other weeks it drops to 4–5 jobs even though relationships are still there. So workload isn’t completely predictable yet." That last clause matters. The relationships are still there. What is missing is a forward view showing what has been won, what is waiting, and what is likely. That is one owner's account in one public thread, not something measured by a survey. Treat it as a description worth testing against your own data before you make a hiring decision on top of it. The second cause is concentration. If two or three property managers or strata companies send you most of your work, their internal rhythm becomes your rhythm. Their end-of-month approvals, their maintenance budget cycles, their staff leave. You feel a whipsaw that has nothing to do with your market.

Run this test before you spend a dollar on marketing. Pull the last twelve months of jobs from your job management software or your invoices. For each job, record two dates: when the work was approved or requested, and when it was completed. Then plot both by week. If the approval line is steady but the completion line swings, you have a scheduling and visibility problem: the work arrives evenly and you deliver it in bursts. If both lines swing together, you have a genuine demand problem, and marketing or client mix is the answer. If the approval line swings but completions are steady, you are already smoothing, and your constraint is capacity, not demand. The demand is often flatter than the diary suggests. Approvals sit for a fortnight, then three land on the same Tuesday. The same r/Plumbing thread framed the underlying question well: "Where I feel stuck is this transition point between: being a busy plumber vs building an actual company." The transition point is exactly here. A busy tradesperson works the next fortnight. A company works a rolling quarter.

You do not need new software. You need three fields consistently filled in on jobs you already record. Stage (enquiry, quoted, approved, scheduled, done, invoiced) shows the backlog sitting between approved and scheduled. Expected value, rough dollars rather than exact, lets you forecast a floor rather than count jobs. Ready date, the earliest date the job can actually be done, separates waiting on us from waiting on them. Most job management tools already hold these fields in some form, and your accounting system holds the invoice side. Check what yours records and exports. The failure is rarely the tool. It is that the fields are half filled, so no report built on them can be trusted. Start with a weekly summary you actually read. Approved but unscheduled jobs, total value. Jobs blocked on someone else, with who and since when. Quotes sent in the last 30 days with no answer. Three numbers, every Monday, before you get in the van. That report is a good first build because it is boring and repeatable. Someone in your business should own it and be able to change it when the questions change. If it depends on an outside contractor to modify, it quietly stops reflecting reality within a few months.

Because their approval process is a queue you do not control. A strata manager batches work orders. They wait on a committee, an annual general meeting, an insurance assessor or an end-of-financial-year budget. When the batch clears, five jobs land at once. When it does not, you get silence, even though the relationship is healthy. The practical consequences: your peak weeks are set by their admin calendar, not your sales effort; payment terms may be set by their process rather than yours, so a busy month can still be a tight cash month; and losing one such account does not shave a slice off your work, it removes a whole shape from your calendar. None of that is a reason to avoid strata or property management work. It is repeat work, and repeat work usually costs less to win than a stream of one-off residential enquiries. The mistake is treating it as evenly distributed. It is lumpy by construction. The counter-argument deserves airtime. Some owners deliberately run high concentration because the account is profitable and the admin is light. That can be a fine choice. It is only dangerous when it is accidental and unmeasured.

A hire is a fixed weekly cost. Lumpy revenue is a variable weekly income. The gap is the risk. The question is not can I afford this person in a ten job week. It is can I pay this person in a four job week, three months running. So look at your floor, not your average. Recurring maintenance and compliance work is highly predictable and is your floor, so hire against it. Strata and property management reactive work is medium predictability: it fills capacity but arrives in batches. Repeat residential and referral work is steady in aggregate but unreliable per week. One-off jobs from ads or directories are low predictability and are a peak absorber, never a hiring basis. Add up the twelve month revenue that is genuinely recurring or contracted. Divide by 52. If that weekly figure does not cover a wage plus on-costs plus a margin, the hire is funded by your peaks, and peaks do not turn up on payday. The route out is usually to grow the recurring row before hiring: scheduled maintenance agreements, annual compliance checks, backflow and thermostatic mixing valve testing, planned preventative work for the property managers who currently only call you when something breaks.

Answer it with the data from the two tests above, not with instinct. If approvals are steady and completions swing, do not hire yet. Fix scheduling and the forward view. You likely have more capacity than you think. If approvals and completions both swing and your top three clients are more than half your revenue, do not add services. Reduce concentration and win two more accounts of the same type you already serve well. If your recurring floor covers a wage and your calendar is genuinely full at the floor, hire. If you are turning away a specific kind of work every week, that is the case for adding a service or a niche. Anything else is guessing. The same owner opened that post with the underlying question: "I run a plumbing business in Sydney and I’m trying to figure out what the *right next step* is to actually scale instead of just staying busy." The right next step is usually the cheapest one that removes uncertainty. Measurement before hiring. Mix before marketing.

Build the weekly pipeline summary. It is small, and it changes the decision you are about to make. Then automate the two chases that create false lumpiness: quotes sitting unanswered, and approved jobs sitting unscheduled. Both are visible in your existing data. Both currently depend on someone remembering. Whoever builds it should work in the business. A pipeline view built by an outsider encodes assumptions about your job stages that will be wrong within a quarter, and you will not be able to correct them. The skill worth owning is diagnosis and process-mapping, which is what the two tests above actually are. The tool matters far less.

**How much job history do I need before the pipeline view is useful?** Twelve months is ideal because it captures seasonality and end-of-financial-year effects. Six months is enough to see whether approvals are steadier than completions. If you have less than six months of clean data, start recording job stage and ready date now and review it in eight weeks. **Is client concentration always a problem?** No. A concentrated book can be more profitable and much cheaper to service than scattered one-off work. It becomes a problem when it is unmeasured, when payment terms are long, or when you are about to add a fixed wage cost that only the concentrated account can support. **Should I hire a part-timer or an apprentice to test the water?** A part-timer or apprentice lowers the fixed cost, which genuinely reduces risk. It does not remove the underlying question. Calculate your recurring weekly floor first, then choose the smallest hire that floor can cover without relying on peak weeks. **What if my job management software will not export the data I need?** Check whether yours can export a job list to CSV, since most can in some form. If the stage or date fields are empty, that is a data-entry habit problem, not a software problem. Fix the habit for four weeks before you consider changing systems. Switching tools rarely fixes an unfilled field. **Does more marketing fix lumpy weeks?** Only if both approvals and completions swing together, which means demand really is uneven. If approvals are steady, marketing adds work to a queue that is already backing up and can make the peaks worse. Test which case you are in before spending. **Who should own the reporting once it is built?** Someone inside the business who understands the job stages and can change the report when the questions change. Reporting that only an external contractor can modify drifts out of date quietly, and nobody notices until a hiring decision is made on stale numbers.

Quotes in this article come from r/Plumbing, specifically a thread on a growing plumbing business and workflow: https://www.reddit.com/r/Plumbing/comments/1rinzk6/plumbing_business_starting_to_grow_but_workflow/. Quotes are reproduced verbatim and attributed to the subreddit, not to individuals. No survey data or client case studies are cited. The single thread cited is one owner's account, not evidence of how common the pattern is.