Advice: In-Plant Outcomes Program
The full build detail behind the four Workforce Capacity modules. Each one is work you can do on your own, and each one ends in a number you can post.
The Workforce Capacity playbook names four modules and what each one proves. This is the build detail for all four: what the work actually involves once you decide to start.
You do not need all four. Start where the friction is worst, work that module all the way to a posted proof point, and you have your first foothold up from Cost Center. Modules 01, 03 and 04 can involve a purchase. Everything else here you can do on your own.
Module 01
Deploy a web-to-print front-end suited to your submitter mix. Build templates by submitter type so recurring work is one-click, and make service classification a required field at intake. Then add the basic visibility layer: confirmation, current status, ready notification, and delivery confirmation. Most status calls happen because submitters do not trust what they can see, so the path in and the view of where it stands are one module, not two.
Start with the recurring work that creates the most friction. Build the templates that capture the specs your team usually has to chase, so the submitter picks from what you already know rather than describing the job from scratch every time.
Bad submission rate, submission turnaround, status inquiry volume.
Take the one recurring job that creates the most rework. Build its template, route it through the new path for a month, and count the submissions that came back for missing pieces before and after.
Module 02
Use a small set of service classes (Standard, Rush, Critical, Complex) and define each in plain language. The wording should be simple enough for submitters to use and firm enough for the shop to enforce. A service class framework nobody uses is a wishlist. This module buys nothing; it is discipline.
Write each class as a promise rather than a category: what the shop commits to, what it needs from the submitter to hold that commitment, and what happens when the work arrives without it. Then publish the classes where the work is submitted, so the choice is made at intake instead of negotiated afterwards.
On-time rate by service class, service class adoption rate.
Publish the classes for one submitting department and hold them for a cycle. The number is how much of that department's work carried the right class, and how often you hit the promise attached to it.
Module 03
Audit campus or facility geography for high-traffic practitioner zones. Deploy a locker network with notification and access-control integration, and build chain-of-custody records for any drop that holds controlled material. Where the volume is there, the fraction of "where is it?" calls that never need to happen is measurable.
The last few feet are where a well-run job still goes wrong. Work that is finished on time but sits waiting to be collected reads to the submitter as work that was late, so measure from finished to received rather than from finished to shelf.
Locker checkout cycle time, share of delivered volume routed through lockers.
Route one high-traffic group's finished work through a single locker bank. The number is the time from job finished to job collected, before and after.
Module 04
Build presort processing, CASS-certified address verification, NCOA on every cycle, IMb compliance, and variable data composition tied to institutional CRM and HR data, with HIPAA-compliant handling where the data calls for it. This is the capability that lets the shop take back the annual institutional mailings that often go outside. Build templates for the recurring ones.
Address hygiene is where the argument is won. A list that has not been run against NCOA pays postage on mail that will never arrive, and that is a number the department owning the mailing can check for itself.
Automated mailing volume against baseline, postage saved per cycle, undeliverable rate after NCOA.
Take one recurring mailing that currently goes outside and run a single cycle in house. The number is what the postage came to, against what that cycle cost before.
Back to the playbook
This is the build detail for the Workforce Capacity playbook. The playbook itself carries the scorecard those proof points post to, and the step that turns a number into a conversation with the group that felt the friction. When you want another set of eyes on it, that is the In-Plant Outcomes Program.