# Eight ways everyday admin wastes time

Find repeated copying, missing information and slow handoffs in admin. Use a simple review to remove wasted effort while preserving necessary checks.

By Daltn editorial team. Published 2026-11-01.
Canonical: https://daltn.tech/feeds/eight-wastes-business-administration/

## How can a small business reduce everyday admin waste?

Everyday admin wastes time when information is wrong, repeated, missing or waiting without an owner. Follow a recent order through the team and identify one frequent source of delay or correction. Remove unnecessary copying while preserving useful checks, then compare errors, handoffs and customer outcomes before extending the change.

## Keep these in mind

- Ohno’s original framework listed seven wastes; unused talent is a later addition.
- Necessary checks should not be removed simply because they take time.
- Measure the whole handoff before automating repeated administration.

## Look at a real transaction

Choose an order that moved through your business yesterday. Follow its enquiry, quote, approval, job instructions, invoice and delivery confirmation. Ask the people involved to show what they actually did rather than what the written procedure says.

The [Lean Enterprise Institute’s eight-waste article](https://www.lean.org/the-lean-post/articles/the-eight-wastes-of-lean/) distinguishes the original seven wastes from the later addition of unused talent. These categories help you notice problems; they do not calculate your savings or prove that a task should disappear.

A payment verification step, for example, may protect the business even though customers never see it. Improve how evidence reaches the reviewer before deciding that the review is waste.

## Translate the categories into office work

Administrative waste often crosses several categories. A wrong delivery address creates a defect. Correcting it requires searching and extra processing.

The customer then waits. Count the original event once when measuring cost, even if several labels help explain it.

Waste | What it can look like | First question
--- | --- | ---
Defects | Incorrect price in a quote | Which source was used?
Overproduction | Reports nobody acts on | Who needs this decision?
Waiting | Unowned approval request | Who can decide?
Unused talent | Repeated issues never heard | Who does this daily?
Transport | Copying the same file between systems | Can one reference travel?
Inventory | Old requests left open | Which items are still valid?
Motion | Searching five chats for a detail | Where should it live?
Extra processing | Reformatting an already approved document | What requirement demands it?

## A quote revision example

In this illustrative case, an administrator enters a requested quantity into a quote. They copy it into a production sheet and a dispatch message. A later quantity change reaches only the quote.

Production makes the old quantity, and dispatch has to call the customer.

The immediate response might be to automate all three copies. First, ask whether the business can maintain one approved quantity with a revision date. Give each team the same reference.

Automation that copies an uncertain number more quickly can spread the error.

The [Lean Construction Institute](https://leanconstruction.org/lean-topics/8-wastes-of-lean/) also treats information movement as a possible source of waste. The specific redesign here is our practical application to an office handoff, not a measured result from that source.

## Run a small waste walk

Spend one short observation session beside the people processing the work. Note each transfer, search, correction and wait. Do not turn the exercise into surveillance or rank staff by clicks.

The aim is to change the system that makes the extra work necessary.

1. Select one repeated transaction with a clear start and finish.
1. Record each handoff and the information it requires.
1. Mark where someone searches, copies, waits or corrects.
1. Ask which steps are required by quality, safety, law or a customer commitment.
1. Test one change and track total completion time plus error rate.

## Check whether the change helped

Suppose a team removes one duplicate entry. Measure whether the downstream person can still find the information they need. If they now send extra questions, the work may simply have moved elsewhere.

Include exceptions and training time in your review.

Useful measures include corrected documents per ten orders, time waiting for approval and orders returned for missing specifications. Keep each definition stable across the trial. A claimed percentage reduction without a baseline tells the team little.

Keep the original request beside the resulting order or task so the next person can check the details. Resolve conflicting quantities before copying them into another document. Assign responsibility for deciding which version is current.

The improvement should reduce needless copying without making it harder to find the source of an important change.

## Common questions

### How do we choose the first admin task to improve?

Start with a frequent error or delay that staff can demonstrate with recent examples. Follow the information through its handoff and identify the decision it should support before changing tools.

### How do we avoid removing a necessary check?

Ask what risk the check controls and what evidence the reviewer needs. Improve the handoff while preserving the control. Compare errors and exceptions afterward, not just processing speed.

## Sources

- [The Eight Wastes of Lean, Lean Enterprise Institute](https://www.lean.org/the-lean-post/articles/the-eight-wastes-of-lean/): Supports the categories and the later addition of unused talent.
- [The 8 Wastes of Lean, Lean Construction Institute](https://leanconstruction.org/lean-topics/8-wastes-of-lean/): Gives process examples including unnecessary information movement.