Standardized Work Combination Table — or SWCT it is a chart used to balance work elements within a production process against takt time.

In plain English

Standardized Work Combination Table (SWCT) is a chart that shows how one person’s work steps fit into a target pace called takt time. It exists so the job can be done the same way each cycle, without overloading the operator or leaving time unused.

It lists each work element and the time it takes. It also separates manual time, walking time, and machine time. Then it adds them up to see if the total fits under takt time. If it does not fit, the work is changed by moving steps, changing the sequence, or splitting work between people. The goal is a stable, repeatable process that meets demand.

What they actually mean

On paper, this table is about balancing work to takt and building a repeatable cycle.

In reality, it often turns into a one-time “lean artifact” made for a kaizen slide deck.

• Times get captured on a good day, with the best operator, with parts staged perfectly.
• Walking gets ignored because it looks bad, so it gets labeled “minor.”
• Machine time gets treated like free time, so more tasks get piled onto the operator.
• The table gets updated once, then the line changes and the table doesn’t.

Uncomfortable truth: if you don’t maintain it, it becomes a story about how you wish the work ran.

You also see it used as a headcount weapon. The table “proves” there is extra capacity, without checking changeovers, breakdowns, rework, or material shortages. It gets confused with a staffing model instead of a process definition tool. Often sits next to weak standard work and gets dragged into “quick” line balancing that ignores real variation.

When done right, it is boring and useful: observed times, clear split of manual vs machine, and a regular cadence to update it when the process or demand changes.

Example

Where you’ll hear it

Used in repetitive production and assembly work to design and maintain a stable operator cycle: assembly lines, packaging cells, machining with operator load/unload, and mixed manual/automatic processes.

Quote: “Show me the combination table. I want to see where the operator is actually busy and where the machine is just running.”

Does it actually matter?

✅ Yes — when you have repeatable cycles and a real takt requirement tied to customer demand.

It matters because it forces you to separate manual work, walking, and machine time, then check whether the operator can actually meet takt without sprinting or skipping quality. It also makes waste visible in a way a simple stopwatch sheet does not. The payoff is stability: fewer surprises, clearer staffing decisions, and a better base for improvement.

⚠️ Watch out: if the process changes weekly, or demand is highly variable, the table needs frequent refresh or it becomes stale and misleading.

Common misconceptions

• Misconception: It is just a time study sheet
  Reality: It is a balance tool against takt with manual/walk/machine split.


• Misconception: If total time is under takt, the process is fine
  Reality: You can still have poor ergonomics, quality risks, and unstable flow.


• Misconception: Machine time is “free”
  Reality: It is only usable if the operator can safely do other work without creating delays or defects.


• Misconception: One measurement is enough
  Reality: You need a defined method, multiple observations, and updates after changes.


• Misconception: It is a headcount calculator
  Reality: It supports staffing decisions, but only after losses like changeover, downtime, and rework are understood.

Toyota Production System explains how standardized work, takt time, and line balance form the backbone of flow. It gives context to tools like the combination table.Toyota Production System: Beyond Large-Scale ProductionTaiichi Ohno--inventor of the Toyota Production System and Lean manufacturing--shares the genius that sets him apart as one of the most disciplined and creative thinkers of our time.Recommended (affiliate)

Red flags

• 🚩 Times were taken only once, during a tour-ready run.
  Problem because the table reflects best-case conditions, so the line misses takt in normal operation.


• 🚩 Walking time is missing or rounded to zero.
  Problem because the “balance” looks better on paper while the operator is still hustling and falling behind.


• 🚩 Machine time is used to justify adding unrelated tasks.
  Problem because it increases context switching and raises defect risk during load/unload and checks.


• 🚩 No link to actual takt or demand.
  Problem because you end up optimizing a cycle time target that does not match what the customer needs.


• 🚩 The table is not updated after layout, tooling, or staffing changes.
  Problem because supervisors manage to a fantasy standard and blame operators for “not following it.”

Worth learning?

4/5

Worth learning because it is a practical way to see whether an operator cycle can meet takt without hidden overload. It pays off when you keep it current and use it to improve the process, not to win arguments.