Labor Standard Benchmarking - A Part of the Process

Although your property’s actual labor performance should be evaluated using labor standards driven by actual volumes, as a part of the development process your models should be benchmarked against your competitive set and applicable industry norms. The trick is to understand the true value of the exercise.

Each job class should be carefully defined in order to fully understand its current labor structure in terms of paid productivity (satisfying volume demand), paid non-productivity (breaks, lunches, pre-shift meetings), and OCS Work (Opening, Closing, and Side Work). Each aspect of the job class labor structure can then be benchmarked against both your competitive set and industry norms, but (and this is a big but), this exercise will only get you so far with overall labor optimization.

Too often I see organizations search for a “quick fix” through benchmarking - without taking the time to ensure that all aspects of labor management are in place. Volume forecasting, employee scheduling, and headcount staffing all have to be correct before labor efficiencies can be realized. Individual components of the job class structure may pass a benchmarking test but this in itself does not ensure that optimum labor efficiencies will be realized.

I am, however, a big believer in benchmarking as the part of the labor standard development exercise because it applies more reality to each aspect of the labor structure I am modeling. Benchmarking can often point me toward efficiency opportunities when I am required to model results that fall outside of my experience with norms (but I also have to be prepared to learn something new when this occurs). I do not, however, view benchmarking as a quick fix or as an easy way to optimization. Benchmarking as a tool can help others to better understand how the current operations "fits" into the its competitive set or within the industry at large but in of itself will not bring about what you are truly looking for - optimized labor effectiveness. It is just a part of the process.