Weeks for Hours of Work: Cutting Quote, Order and Approval Lead Times

A customer asks for a quote. Three weeks later, they get it — if they have not already bought from someone faster. Ask anyone involved how long they actually spent on it and the answers add up to a few hours: an estimator pulled costs, engineering checked feasibility, a manager approved the margin, sales sent it out. Everything else was waiting.

The same pattern shows up across the office. Orders sit for days before they are released to the floor. Engineering changes take a month to approve. Invoices go out late because the paperwork from shipping is incomplete. Month-end close takes two weeks of spreadsheets. Nobody is idle — in fact, everyone feels overloaded — and yet the work crawls.

This is the problem Transactional Lean is built to solve. This guide explains why office lead times balloon, how to measure the gap honestly, and the specific countermeasures that shrink weeks back down to days.

The gap between touch time and elapsed time

Every office process has two clocks. Touch time is the time someone is actively working on the item. Elapsed time (or lead time) is the calendar time from request to completion. In most administrative processes we look at, touch time is a small fraction of elapsed time — often well under ten percent.

That ratio matters because it tells you where to look. If a quote takes fifteen working days and contains four hours of work, making the estimator twice as fast saves two hours. Eliminating the queues saves weeks. Most office improvement efforts focus on the work itself — new software, faster people, more templates — when the real opportunity is in the waiting between steps.

Process	Typical touch time	Common elapsed time	Where the time goes
Quote to customer	Hours	1–4 weeks	Engineering review queue, missing specs, margin approval
Order entry to release	Under an hour	Days	Incomplete orders, credit hold, re-keying between systems
Engineering change (ECN)	Hours	Weeks to months	Serial sign-offs, change boards that meet monthly
Purchase approval	Minutes	Days to weeks	Approval thresholds set years ago, approvers traveling
Invoicing / month-end close	Hours per cycle	1–3 weeks	Missing shipping data, reconciliation, manual journal entries

Why office work queues up

Office queues form for reasons that are different from — but rhyme with — the shop floor.

Work is invisible

On the floor, a pile of parts in front of a machine is obvious. In the office, the pile is an inbox, a shared folder or a system status nobody checks. No one can see how much is waiting, how old it is, or where it is stuck.

Batching

People process similar items together because it feels efficient: all quotes on Tuesday, all approvals at the end of the week, the change board once a month. Each batch adds days of waiting to every item in it.

Approvals by habit, not by risk

Many approval steps were added after a single bad event years ago and never revisited. A low-risk, standard quote goes through the same three signatures as a new, high-risk, custom one.

Incomplete inputs and loopbacks

A request arrives missing information. It gets started, stalls, goes back to the requester, waits, comes back, and joins the queue again. Each loopback can add days. In many processes, the rework loop is the single largest driver of lead time.

Re-entry between systems

The same data is typed into the CRM, then the quoting tool, then the ERP, then a spreadsheet for scheduling. Every hand-off is a chance for delay and error.

Overloaded specialists

A single engineer or estimator is the only person who can do a step. Everything waits for them, and they are constantly interrupted.

Step 1: Pick one flow and measure it honestly

Do not try to fix “the office.” Pick one flow that matters to customers or cash — quote-to-order, order-to-release, ECN, procure-to-pay or invoice-to-cash — and define clear start and stop points.

Then pull real data. For the last 30 to 50 items, record when each one arrived and when it was completed. Most systems have timestamps if you look for them. Calculate the median and the spread. A process with a median of eight days and a range of two to forty tells a different story than one that is consistently eight days.

Next, sample touch time. Ask the people doing each step to log actual working time on a handful of items for a week. This does not need to be precise; it needs to be honest. The goal is to see the ratio.

Step 2: Map the flow as it really runs

An office value stream map follows a single item from request to completion. Get the people who do the work in one room — not just the managers — and walk the process step by step. For each step, capture:

• Who does it and in which system
• Touch time and typical wait before it
• Percent complete and accurate (%C&A) — how often the step receives what it needs the first time
• Loopbacks, approvals and hand-offs

The %C&A metric is especially revealing. When a step reports that only 60 percent of what it receives is complete and accurate, you have found a loopback generator. Multiply the %C&A values along the flow and you get the rolled first-pass yield — often shockingly low.

Resist the urge to map the ideal process. Map what actually happens, including the workarounds, side spreadsheets and “I just walk over and ask.” Those are where the time goes.

Step 3: Apply the countermeasures that actually move lead time

Standard intake

Define exactly what a complete request looks like, and do not let incomplete ones into the flow. A quote request template with required fields, an order checklist, an ECN form that captures the reason, the affected parts and the proposed effective date. This one change often removes the largest loopback in the process.

Approvals by risk

Sort work into categories by risk and value. Standard, repeat, low-value items get a fast lane with a single approver or pre-approval by rules. Only genuinely new or high-risk items go through the full review. Revisit dollar thresholds that have not been updated in years. Replace serial sign-offs with parallel review where the approvers are checking different things.

Single entry

Enter data once, at the source, and let it flow. That may mean an integration, but it often just means agreeing which system is the master and eliminating the side spreadsheets. Where re-entry cannot be avoided yet, standardize it and check it once.

Flow instead of batches

Process items as they arrive, or in small, frequent batches. Move the monthly change board to a short weekly — or daily — review. Give approvers a set time each day to clear their queue rather than letting it build.

Make the queue visible

Create a simple queue board — physical or digital — that shows every item in process, what step it is at and how long it has been there. Color-code by age. Review it in a short daily stand-up. Visibility alone often cuts lead time noticeably, because stuck items get noticed and escalated.

Balance and cross-train

If one specialist is the bottleneck, protect their time for the work only they can do, move routine pieces to others, and cross-train a backup. Standard work for common request types lets more people handle them.

Step 4: Run a focused Kaizen on the flow

Transactional flows respond very well to a focused Kaizen event. A cross-functional team spends three to five days mapping the current state, designing the future state and — critically — implementing it during the week: new intake template live, approval matrix revised, queue board up, first stand-up held. For narrower problems, a single A3 owned by a process lead is often enough.

The measures should be set before the event: median lead time, spread, %C&A at key steps and the number of items in queue. Then track them weekly for 90 days.

Step 5: Sustain it

Office improvements decay for the same reasons shop floor improvements do. People revert to email, new approvers add steps, the queue board stops being updated. Build the sustain system in from the start:

• A named process owner for the whole flow, not just each department’s piece
• A short daily or weekly queue review with clear escalation rules
• Lead time and %C&A on the department’s visual board
• 30/60/90-day reviews against the Kaizen targets
• A rule that any new approval step needs a documented reason and an owner

What results look like

When the countermeasures are implemented and sustained, the typical pattern is a large drop in median lead time and an even larger drop in variability. Customers notice consistency first. Win rates on quotes can improve simply because the answer arrives before the competitor’s. Orders reach the floor faster, which gives the plant more time to schedule. Invoices go out on time, which improves cash flow. And the people in the office stop spending their day chasing status.

Common mistakes

• Buying software first. Automating a broken flow just produces the same delays faster, with less visibility.
• Mapping only the ideal process. The workarounds are the process.
• Measuring averages only. The long tail is what customers remember.
• Fixing one department’s piece. Lead time lives in the hand-offs between departments.
• No owner for the end-to-end flow. Without one, improvements erode at the boundaries.

How QMSLean helps

We pick one high-value flow with you, measure touch time against elapsed time with real data, run an office value stream map with the people who do the work, and lead a Kaizen that implements standard intake, risk-based approvals, single entry and a visible queue during the event. Then we put the sustain system in place and review results at 30, 60 and 90 days.

See our situation page: “Our office processes take weeks, but the actual work takes hours.” Related reading: Transactional Lean: Applying Lean Six Sigma to Office and Service Processes and The 8 Wastes in the Office.

Tell us what’s going on

Describe the flow that is taking too long and a Lean practitioner will reply with how we would approach it. Request a Situation Review, try the free ROI Calculator, or contact us at [email protected].