The formulae from Demand-Based Production from a Flow-Time Versus Need-Time Perspective and Demand-Based Production from a Work-Volume Perspective can now be combined to solve for the Queue Policy (X_{N}). From Demand-Based Production from a Work-Volume Perspective, equation 22:

From Demand-Based Production from a Flow-Time Versus Need-Time Perspective, equation 2:

Therefore:

and the Queue Policy for WC_{N} is given by:

From Demand-Based Production from a Work-Volume Perspective, this value of X_{N} can be used to assign a Pull Tag to WO_{1} when the sum of its Clear Time in WC_{N} (W_{N}) + the queued Clear Times in the WC_{N} queue (Q_{N}) + the sum of the Clear Times at WC_{N} for all authorized UA WOs' (Y_{N}) is less than or equal to that value of X_{N}. This formula, in the limit where all flow-times are 0, sets a "floor" of W_{N} hours, which is needed to avoid "starving" a WC by setting a maximum Queue Policy that is less than the number of hours represented by the next WO to be authorized. All of the stated terms are "knowable" quantities within the construct of most ERP/MRP systems so that this construct is easily implementable.

The question can be raised as to why the formula from Demand-Based Production from a Work-Volume Perspective is re-introduced to define a pull algorithm, or why the flow formula (Equation 2 above) cannot just be used to assign Pull tags. The answer is primarily a matter of visual management in a lean environment. The concept of a maximum Queue Policy is a manageable and understandable concept in the factory environment and one for which the present technology provides management over-rides and/or adjustment factors to accommodate the realities of variability in the individual WCs. This pull-system conforms to the idea that when inventory falls below a pre-determined policy level, a replenishment signal is sent, yet at the same time, by using ideal flow times, it is forcing queued inventory toward zero.