Fileworkbase · Western Australia
We teach operators and people leads how to model capacity before the vacancy appears. Business consulting for workforce planning, written as programmes you can sit, not slide decks you file.
Flagship
Eight weeks · live tables
A working room for people who already own a roster and still cannot explain why overtime clusters on Thursdays. You leave with a model that survives a board question, not a heatmap that dies in a slide.
Modules cover demand clocks, relief ratios, leave debt, and the awkward politics of publishing a number that implies someone was over-hired.
“Module four forced us to separate coverage from presence. We had been counting bodies in the building as if that were the same as service hours.”
Mara Ellison · operations lead, refrigerated logistics
What you actually practise
These are not generic consulting virtues. They are the checks we run on every Fileworkbase table before it leaves the room.
Demand arrives in hours and seasons. We refuse to start a model from last year’s headcount file.
Leave, training, and absence are not rounding errors. If the ratio is hidden, the roster will steal from weekends.
Shared spreadsheets become folklore. Every driver in a Fileworkbase model has a named steward.
Software will not choose between overtime and delayed service. We make that sentence explicit.
From the reviews page
Helena K., Bunbury, sat the Roster Integrity Clinic and wrote that the homework assumed more payroll extracts than her council could actually export. She still finished. We kept the note because it is true of several regional employers.
Journal
How a Margaret River cellar door team mis-timed casual contracts, and the two numbers that would have shown it.
Why adding two roles can still leave a night shift uncovered if licences and sign-off sit with one person.
Pemberton replies
We read it. A desk brief is a paid conversation, not a sales theatre. Fees are listed plainly.