Business as usual (BAU)
Definition
Business as usual (BAU): run-rate work explained
Business as usual (BAU) is the steady, repeatable work that keeps a company running day to day. It covers routine tasks, service levels, and support that continue whether or not a change project is running. BAU is the baseline everything else is measured against.
You’ll hear the phrase most often when something threatens it. A system migration, an acquisition, a storm that closes a Cebu site — leaders promise BAU will hold while the disruption plays out.
BAU is a budgeting term too. Run-rate work sits in the operating budget and recurs every year, while change work draws on a project budget that closes once the work ships.
Key takeaways
- BAU is the recurring, steady-state work that keeps existing services running.
- Project work changes the business; BAU runs it, with different owners and budgets.
- BAU is judged on stability — service levels held, low error rates, no growing backlog.
- Every project eventually becomes somebody’s BAU, so handover quality decides the outcome.
- Providers often absorb BAU volume so in-house staff can concentrate on change work.
How it works
BAU works as a run-rate: a defined set of repeatable tasks, documented in procedures, staffed to forecast volume, and funded from the operating budget. Nothing about it is meant to be novel. Predictability is the point.
Three things hold BAU together: a written procedure for every task, a staffing model with enough shift coverage, and a short list of metrics that flag drift before customers notice.
The procedure layer is where most teams are weakest. A standard operating procedure turns one person’s habit into an asset the next hire can run without supervision.
Staffing is the second layer. BAU volume gets forecast, then covered by full-time employees on fixed rosters rather than borrowed project staff.
Measurement is the third. Pick two or three key performance indicators per process, such as turnaround time, error rate, and backlog age, then review them weekly.
Payroll and workforce platforms are built to record exactly this kind of work performed: repeatable, classifiable, and easy to cost per hour or per transaction.
Funding is what trips people up. BAU costs sit in the operating budget as a run-rate, so a permanent volume increase means a permanent headcount conversation — not a one-off request.
BAU also has a floor and a ceiling. Below the floor, service breaks. Above the ceiling, you pay for capacity that idles, which is why forecasting sits at the centre of every roster.
| Dimension | Business as usual (BAU) | Project or change work |
|---|---|---|
| Owner | Line manager or operations lead | Project sponsor and project manager |
| Funding | Recurring operating budget | Fixed, time-boxed project budget |
| Success measure | Stability: service levels held | Delivery: scope shipped on time |
| End state | Never ends; it is the baseline | Closes, then hands over to BAU |
| Typical staffing | Rostered permanent team | Seconded specialists and vendors |
Read the last row twice. Every project eventually becomes somebody’s BAU, which is why handover documentation decides whether a launch still holds up six months later.
Examples
BAU looks different by function, but the shape stays the same: recurring volume, an agreed service level, and a named owner. Here’s how it plays out in settings you’ll recognise from any operations review.
Contact centre. Answering tickets, hitting an average handle time, and staffing the Monday peak is BAU. Rolling out a new CRM is a project, and the queue still has to be answered while it happens.
Finance shared services. Monthly close, supplier payments, and reconciliations recur on a fixed calendar. An ERP migration sits outside that calendar and needs its own budget and team.
IT service desk work is a clean case. Password resets, patching, and access requests recur forever, while a data centre move happens once and then hands its support load back to the desk.
Retail back office. Stock counts, returns processing, and rostering run on the same weekly rhythm no matter what the strategy deck says.
Philippine BPO delivery. A Manila or Cebu team running an offshore process to an agreed service level is the client’s BAU, delivered by somebody else’s staff.
That’s the quiet logic of outsourcing: one company’s routine workload is another company’s core product, priced per seat or per transaction.
Disruption is the real test. When a storm closes a site, a business continuity plan exists to keep BAU running from home or a second location.
Governance counts as well. The weekly operations review is BAU, and so are the standing corporate meetings where managers sign off performance against target.
Related terms
BAU sits next to several terms operations teams use in the same breath. Knowing where each one starts and stops keeps your reporting honest, especially when project work and run-rate work share the same people.
- Standard Operating Procedure (SOP): the documented step sequence that makes a BAU task repeatable by anyone.
- Key Performance Indicator (KPI): the measure that tells you whether BAU is holding or slipping.
- Business Continuity Plan (BCP): the playbook for keeping BAU running through disruption.
- Full-Time Employee (FTE): the staffing unit BAU capacity is usually planned and costed in.
- Outsourcing: the practice of handing defined BAU processes to an external provider.
FAQ
What does business as usual (BAU) mean?
BAU means the normal, recurring operations of a business — the work that continues regardless of projects, launches, or disruption. It’s the baseline state everything else gets compared against.
How is BAU different from project work?
Project work changes the business; BAU runs it. Projects have a sponsor, a fixed budget, and an end date, while BAU has a line manager, a recurring budget, and no end date at all.
Who owns BAU?
The line manager or operations lead owns it, supported by team leaders on each shift. Ownership matters because BAU has no sponsor to escalate to when its capacity gets pulled into a project.
How do you keep BAU stable during a big change?
Ring-fence the roster so project work can’t borrow the people covering daily volume. Agree in writing which service levels are allowed to dip, and by how much, before the change starts. Then review those numbers weekly.
Is BAU a bad thing?
Not at all. Strong BAU is what lets a company take on change safely, because stable operations free up attention and cash. Teams only call BAU boring when it’s working.
How do you keep a team motivated on BAU work?
Involve everyone in the target, keep the numbers visible, and say thank you out loud when a hard week holds.
If you’re weighing which BAU processes to hand off and which to keep in-house, start your research at Outsource Accelerator.







Independent




