Dummy Row / Dummy Column: What They Mean in Unbalanced (Rectangular) Assignment Problems
When an assignment matrix is rectangular (workers β tasks), Hungarian and other exact methods are usually applied to a square matrix. A dummy row or dummy column is the standard way to βbalanceβ the matrix without changing the meaning of real assignments.
Practice by running the same examples in the Unbalanced Assignment Problem Calculator. For the balanced base solver with step tables, see Assignment Problem Solver (Hungarian method).
On this page
- Quick takeaway (what dummy rows/cols do)
- Why balancing is needed (square matrix requirement)
- How to add dummy rows/columns (rules)
- Interpretation: what a dummy assignment means
- Should dummy cells be 0? (penalties and modeling choices)
- Worked examples (fully solved)
- Check your answer (calculator + next guides)
- Questions people ask (dummy rows/columns)
- Glossary
Quick takeaway: Dummy rows/columns convert a rectangular assignment matrix into a square matrix. A dummy column represents a βdo nothing / no task assignedβ option for extra workers. A dummy row represents a βno worker availableβ option for extra tasks. In your results table, a βDummyβ match is not a real workerβtask pairingβitβs the modelβs way to express the imbalance.
Why balancing is needed (square matrix requirement)
Concept
Assignment is a one-to-one matching (perfect matching)
The classic linear assignment problem is one-to-one: each worker is matched to exactly one task and each task to exactly one worker. In graph terms, we want a perfect matching in a bipartite graph.
If you have a rectangular matrix (say 4Γ3), a strict perfect matching across original workers and original tasks is impossible
because the two sides have different sizes. Balancing with dummy nodes makes both sides size n = max(rows, cols),
so a perfect matching becomes well-defined.
Learn the full background: unbalanced assignment problem Β· bipartite matching & assignment.
How to add dummy rows/columns (rules)
Rules
Balancing rule (standard)
Let rows = number of workers and cols = number of tasks.
Define n = max(rows, cols).
| Case | What you add | Why | How many |
|---|---|---|---|
| rows > cols (more workers than tasks) | Dummy columns (dummy tasks) | Give extra workers something to match to | rows β cols |
| cols > rows (more tasks than workers) | Dummy rows (dummy workers) | Give extra tasks something to match to | cols β rows |
| rows = cols (balanced) | Nothing | Already square | 0 |
Interpretation: what a dummy assignment means
Interpretation
Reading the final assignment table
In a balanced assignment, every matched pair is βreal.β In an unbalanced assignment, some matches will involve dummy rows/columns:
- Worker β Dummy Task (dummy column): that worker is effectively idle / unused.
- Dummy Worker β Task (dummy row): that task remains unfilled / unassigned.
You can see this immediately in the CalcTypes output: the assignment table marks each row as Real or Dummy. Try it in the unbalanced calculator.
Should dummy cells be 0? (penalties and modeling choices)
Modeling choice
0 is the default βneutralβ dummy, but penalties are often better
Many textbooks use dummy values = 0 because it keeps the balanced model equivalent in a clean, neutral way. But in real life, leaving a worker idle or leaving a task unfilled may have a cost.
| Objective type | Dummy value = 0 meansβ¦ | If βunfilled/unassignedβ is badβ¦ | Common modeling approach |
|---|---|---|---|
| Minimize cost/time | Idle worker / unfilled task has no extra cost | Add a positive penalty in dummy cells | Penalty cost (or a separate constraint/model) |
| Maximize profit/output | Idle/unfilled contributes no profit | Make dummy profit negative (a penalty) | Penalty profit (negative) or alternative model |
Worked examples (fully solved)
Worked examples
Expand only the example you need
Each example below is a lecture-style solution: balance β interpret dummy β compute the optimum by enumeration (small cases). Verify in the unbalanced calculator.
Example 1 β 4 workers, 3 tasks (dummy column β idle worker)
Original (4Γ3) cost matrix:
T1 T2 T3 W1 4 2 8 W2 6 7 3 W3 5 1 4 W4 9 6 2
Step 1: Balance with dummy column D
T1 T2 T3 D W1 4 2 8 0 W2 6 7 3 0 W3 5 1 4 0 W4 9 6 2 0
Step 2: Interpretation
Any worker assigned to D is idle. Dummy contributes 0.
Step 3: Compute optimum by cases (choose the idle worker)
Choose who goes to D, then solve a 3Γ3 assignment (6 permutations). We show the minimum in each case:
Case A: W1βD β min total for {W2,W3,W4}β{T1,T2,T3} is 9
Case B: W2βD β min total for {W1,W3,W4}β{T1,T2,T3} is 7 β best
Case C: W3βD β min total for {W1,W2,W4}β{T1,T2,T3} is 10
Case D: W4βD β min total for {W1,W2,W3}β{T1,T2,T3} is 8
Optimal plan (Case B):
W1βT1 (4), W3βT2 (1), W4βT3 (2), W2βD (0).
Total minimum cost = 7, and W2 is idle.
Example 2 β 3 workers, 4 tasks (dummy row β unfilled task)
Original (3Γ4) cost matrix:
R1 R2 R3 R4 D1 9 2 7 8 D2 6 4 3 7 D3 5 8 1 6
Step 1: Balance with dummy row DW
R1 R2 R3 R4 D1 9 2 7 8 D2 6 4 3 7 D3 5 8 1 6 DW 0 0 0 0
Step 2: Interpretation
If DW is matched to route Rk, then route Rk is unfilled.
Step 3: Compute optimum by cases (choose the unfilled task)
Choose which route goes to DW, then solve a 3Γ3 for the remaining routes. Minimum total in each case:
Case A: DWβR1 β best real-driver total = 10 Case B: DWβR2 β best real-driver total = 15 Case C: DWβR3 β best real-driver total = 14 Case D: DWβR4 β best real-driver total = 9 β best
Optimal plan (Case D):
D1βR2 (2), D2βR1 (6), D3βR3 (1), DWβR4 (0).
Total minimum cost = 9, and route R4 is unfilled.
Example 3 β Unbalanced + forbidden pairs (feasibility risk)
Dummy rows/columns solve the βshapeβ problem (rectangular β square), but they do not guarantee feasibility if many pairs are forbidden. Here is a lecture-style infeasibility demonstration.
Mini-example (4Γ3 with dummy column D):
Allowed sets (after adding dummy column D):
W1 β {T1} (only one real option)
W2 β {T1} (only one real option)
W3 β {T2, D}
W4 β {T3, D}
Reason
W1 and W2 both require T1 (they have no other allowed real task). Only one worker can take T1 in a one-to-one assignment. Dummy column D does not create an extra copy of T1βit only absorbs an extra worker.
Conclusion: infeasible, even after balancing.
Check your answer (calculator + next guides)
Tooling + learning path
Fast verification + what to read next
Verify any rectangular example by solving it in the Unbalanced Assignment Problem Calculator.
Questions people ask about dummy rows/columns
People ask
What is a dummy row in an assignment problem?
A dummy row is an extra row added when tasks > workers to make the matrix square. A dummy-row match means a task is left unfilled because there arenβt enough workers.
People ask
What is a dummy column in an assignment problem?
A dummy column is an extra column added when workers > tasks to make the matrix square. A worker matched to the dummy column is idle/unassigned because there arenβt enough tasks.
People ask
Why do dummy rows/columns often use 0 values?
Using 0 makes dummy assignments neutral in teaching models so optimization focuses on real choices. In applied planning, use a penalty if idle/unfilled is costly.
People ask
Do dummy assignments affect the reported total?
In most teaching models (and in the CalcTypes assignment calculators), dummy assignments contribute 0 by default. The results table reports real versus dummy matches.
People ask
Can an unbalanced assignment still be infeasible?
Yes. Balancing fixes matrix shape, but forbidden constraints can eliminate all perfect matchings. Learn: assignment feasibility / infeasibility.
Glossary
Glossary
- Dummy row: extra row added when tasks > workers; represents βno worker available.β
- Dummy column: extra column added when workers > tasks; represents βno task assigned.β
- Balanced assignment: square matrix (same number of workers and tasks).
- Unbalanced assignment: rectangular matrix; solved by balancing with dummies.
- Perfect matching: one-to-one matching covering all nodes after balancing.
- Forbidden pair: prohibited workerβtask pairing.
Disclaimer
This page is for educational and planning purposes only. Dummy rows/columns are a modeling technique that may not capture real-world constraints (penalties, priorities, fairness, time windows, multi-task workers). For high-stakes decisions, validate with a production optimizer and domain review. Read our full disclaimer.
Sources
- Kuhn (1955). The Hungarian method for the assignment problem
- Munkres (1957). Algorithms for the Assignment and Transportation Problems