The Job You Clone Every Quarter: Templating Recurring Work
If you rebuild the same BAS or annual-accounts job from memory every cycle, you're paying for work you've already done. Here's how to template recurring compliance for good.
There's a job your firm does every quarter, or every month, or every year. A BAS. A set of annual accounts. A trust distribution minute. An FBT return. You've done it dozens of times. And yet, each cycle, someone sits down and more or less rebuilds it from scratch — creating the tasks, remembering the steps, chasing the same documents, hoping the person who did it last time left good notes.
That's not a workflow. That's institutional memory held together by habit. And it's the single biggest reason recurring compliance work feels busier than it should — and quietly less profitable than it looks.
Recurring work is the opposite of one-off work
Most practices think about work as a stream of jobs to get through. But recurring compliance is different in a way that matters: you already know it's coming. You know the quarterly BAS is due. You know the annual accounts follow lodgment season. You know which clients have which obligations, because the obligations don't change much from year to year.
When you know the work is coming and you know roughly what it involves, there's no excuse for treating it as a fresh event each time. Every time you rebuild a job, you're re-deciding things that were already decided — what steps are involved, who does them, what you ask the client for, how long each stage takes. That re-deciding is pure waste. It doesn't make the work better. It just makes it slower and more variable.
The hidden cost of "we just know how to do it"
Firms that rely on people knowing how to do recurring work face a few predictable problems:
- Inconsistency. Two team members do the same job differently. The output varies, the client experience varies, and the quality depends on who happened to pick it up.
- Fragility. When the person who "just knows" the BAS process is on leave or leaves the firm, the knowledge walks out with them.
- Invisible scope creep. Steps get added informally over the years. Nobody ever writes them down, so nobody ever questions whether they still belong in the fixed fee.
- Missed deadlines. When the job doesn't exist until someone remembers to create it, it's easy for a cycle to slip past unnoticed.
None of these show up on an invoice. They show up as stress, rework and margin erosion — the quiet tax you pay for not standardising.
Productising starts with naming the work
Productising compliance isn't just about pricing. Before you can put a fixed fee on something and sell it confidently, you need to know exactly what "it" is. That means defining the recurring job as a repeatable product: a named deliverable with a defined set of steps, a defined set of inputs you need from the client, an owner at each stage, and an expected duration.
Once you've done that for your quarterly BAS, you've effectively written the recipe. The next time it comes due, nobody reinvents it. They open the template, it's already populated with the steps, the document requests and the deadline, and work begins immediately.
What a good recurring template contains
A recurring compliance job template should capture, at minimum:
- The trigger and frequency. Monthly, quarterly, annually — and the date it should spawn relative to the deadline, so there's a buffer built in rather than a scramble.
- The stages. The real sequence of work: collect documents, prepare, review, send for approval, lodge-or-hand-off, invoice.
- The owner of each stage. So the job never sits in a queue nobody owns.
- The documents you need from the client. Requested the same way, every cycle, instead of one email at a time.
- The expected time budget. So you can compare what the job should take against what it actually took.
Get this right once and you've removed the single biggest source of variability in your practice.
Where the software earns its keep
This is exactly the kind of thing good account practice management software is built to handle. In Finye, recurring jobs are set up once as templates and then spawn automatically on their schedule — the quarterly BAS for every relevant client appears on your boards with its stages, owners and document requests already attached, with the deadline pulled from the compliance obligation you're tracking. You're not rebuilding the job; you're reviewing a job that built itself.
Because the work lives in the same system as your client records, your engagement letters and your invoicing, productising becomes concrete rather than theoretical. The template defines the deliverable, the engagement letter describes it, and the invoice bills for exactly that scope. When those three things describe the same work, you've actually productised the service — not just given it a name on a price list.
And when every cycle runs through the same template, you finally get usable data: how long the BAS really takes, where it stalls, which clients consistently deliver documents late. That's the raw material for sharpening your fixed fees instead of guessing at them.
Start with your most common job
You don't need to template everything at once. Pick the single recurring job you do most — probably the quarterly BAS — and write it down properly. Sit with whoever does it best and capture the real steps, not the idealised ones. Build it as a template. Run it for a cycle. Adjust.
Then do the next one. Within a few cycles, the bulk of your recurring compliance work stops being something people hold in their heads and becomes something the practice simply runs. The work still has to be done well — software doesn't do the thinking for you. But the scaffolding around it stops consuming time it was never meant to consume.
The goal is simple: no recurring job should ever be rebuilt from scratch. If you're creating the same compliance job for the second time, you've already built it once. Capture it, template it, and let it come back to you ready to work — every quarter, every year, without the scramble.