Enterprise IPL Playbook: Workforce Capacity
Front-line practitioners, specialists, administrative departments, facilities. Build the path of least resistance for every submitter.
People work around the in-plant when the workaround feels faster, clearer, or more predictable.
A clinical team runs materials on the staff room copier because the portal feels slow. A specialist sends work outside because they are not sure whether the shop can handle the format. HR uses the same vendor every year because the mailing process is already familiar. Facilities calls a sign shop because wide format production feels separate from the in-plant.
This playbook helps you find those workarounds and replace them with a better path. Start with one submitter group, track how work really flows, and use what you learn to make the shop the easier choice.
Stage 1 of 6 · See the Need
Start with the work rather than the org chart. Every shop already does all five of these somehow. Mark the ones running well and the ones where you lose people. Nothing is saved and nothing is sent. It points you at the module that fits. One answer per row, and clicking it again clears it.
Getting work into the shop
One obvious way in, or several informal ones that each capture something different.
Coalition Administrative departments · Front-line practitioners
Knowing where a job stands
Whether someone can see where their work is without calling to ask.
Coalition Front-line practitioners
Turnaround people can plan around
Whether a promised date means the same thing to the person who asked and to the shop.
Coalition Specialist practitioners · Front-line practitioners
Getting finished work back to people
The last few feet, and the "where is my job?" call that happens while the work sits finished on a shelf.
Coalition Front-line practitioners · Facilities and operations
Bulk mailings that go out to a list
Annual notices, enrollment cycles and statements, where postage and address quality decide the cost.
Coalition Administrative departments
When one of these does not run cleanly, the work does not stop. It gets done somewhere else, by people who never should have owned it, and that cost gets absorbed quietly rather than counted. That is the DIY tax, and it belongs in the conversation.
Stage 2 of 6 · Select the Module
Each module is one workflow reality you can learn and work on your own. Each one produces a proof point you post to your Outcomes Scorecard, at stage 5. You do not need all four.
Most of the fix starts at intake, before production. A job that arrives without the right file, or with a due date that means one thing to the submitter and another to the shop, is an intake problem first, and that is where every one of these starts.
What you do: Deploy a web-to-print front-end suited to your submitter mix, build templates by submitter type so recurring work is one click, and add the visibility layer: confirmation, status, ready notification, delivery. The path in and the view of where it stands are one module, not two.
Proof points
Already know you want a portal?
Compare web-to-print software at SumnerOne.comWhat you do: Use a small set of service classes (Standard, Rush, Critical, Complex), define each in plain language, and publish them where work is submitted. Simple enough for submitters to use, firm enough for the shop to enforce. A service class framework nobody uses is a wishlist.
Proof points
What you do: Audit your building or campus geography for the zones people already pass through, deploy a locker network with notification and access-control integration, and build chain-of-custody records for any drop holding controlled material.
Proof points
Ready to size a network?
Compare smart-locker delivery at SumnerOne.comWhat you do: Build presort processing, CASS-certified address verification, NCOA on every cycle, IMb compliance, and variable data composition tied to your CRM and HR data, with HIPAA-compliant handling where the data calls for it. Build templates for the recurring cycles.
Proof points
Costing out a mailroom?
Compare mailroom and mailing solutions at SumnerOne.comStage 3 of 6 · Build the Coalition
Four kinds of people send work to an in-plant, and each tends to measure the shop on a different axis. Rarely do all four matter at once. Mark the ones that do where you are, starting with whoever feels the job you just picked. One answer per row, and clicking it again clears it.
Front-line practitioners
Clinicians, caseworkers and project managers who need the work back on time without it becoming another task on the day.
Specialist practitioners
Time-bound, high stakes work with format, quality and sensitivity the routine submitter does not share.
Administrative departments
HR, finance and internal communications, running recurring cycles that get outsourced because nobody asked the in-plant.
Facilities and operations
Signage, wayfinding and field materials, usually tied to a building event or an opening date.
Stage 4 of 6 · Run the Test
A test is not an audit of the whole shop. It is one change, on one workflow, measured against what that workflow was doing before you touched it. The method runs on roughly a quarterly rhythm, in two parts.
First, the baseline
Take the workflow your module touches and write down what it does today: how the work arrives, how complete it is at intake, how long it waits before production starts, whether it landed on time, how many status calls it generated, how it held during your busiest period, and how much of that work still goes outside the shop. If your system already reports that, this is an afternoon. If you have to collect it by hand, give it a few weeks.
Then, the change
Make the one change your module describes, on that one workflow, and hold it long enough for the same measures to mean something.
One workflow. One change. A reading before and after. The completed test is the difference between the two readings.
Stage 5 of 6 · Capture the Evidence
These six are the service delivery rows of your Outcomes Scorecard, and each is written the way you would say it out loud, because that is the form it has to survive in. A metric nobody can pronounce in a meeting is not evidence yet. If you only start with three, start with the first three.
Your team keeps having to redo submissions before we can start. Here is how often, and for which group.
The number that travels furthest here. It shows whether intake is being honored or worked around, and the answer is usually upstream of the shop rather than inside it.
From the moment your job is finished to the moment it is in your hands, here is the typical wait.
The last few feet, which is where a job that finished on time can still read as late. It moves when collection stops being a trip to the counter.
Here is how many "where is my job?" calls we still field in a week. Every one is a minute you spent chasing us.
Whether the visibility you built is doing its job. People stop asking when they can see.
When we promise Critical by Thursday, here is how often we hit it.
Whether the promises attached to the published classes hold when they are tested.
Here is how much work still goes to the hallway copier or an outside vendor, and what it costs to keep it there.
The DIY tax in a number: what the institution is still paying to route around its own shop.
During open enrollment, here is whether we held our timelines when it mattered most.
Whether the shop holds together when the institution is most exposed.
These six are the recurring core. Each module adds its own proof points on top, so the board grows as the shop does.
Stage 6 of 6 · Share the Story
The people who have been working around the shop do not need the playbook. They need to hear that the thing they worked around has changed. So this is the message, already written, with one blank in it for the number your test produced.
Mark as many of these as are true for your shop. A note is about one part of the flow and one group, so if you mark more than one you choose which. We start you on what you said needs work, ahead of what is already running well, because the thing worth telling someone is the thing that changed.
Eyes on the prize, not a cost center
Cost Center and Consulted both still spend your submitters' time. Crossing from Consulted to Trusted Producer is what earns the shop its trust, and it is what changes the conversation at budget time. Working one module all the way to a posted proof point is how you cross it.
You do not have to climb all four levels this year. One module, carried to a number you can post, is the foothold. That is the prize this playbook is built to reach.
Frequently asked questions
Four groups send jobs to the in-plant: front-line practitioners (clinicians, caseworkers, project managers), specialist practitioners with time-bound and high stakes production needs, administrative departments running HR and compliance cycles, and facilities and operations teams producing signage and field materials. Each group tends to measure the shop differently, which is why the intake path that works for one may not work for another.
Bad submission rate measures how often submissions arrive incomplete or unclear. It is the most valuable service delivery metric because it is a diagnostic for whether your intake workflow is being honored or worked around. A portal nobody can use produces the same rework as no portal at all. A single submitter group generating disproportionate bad submissions is usually an onboarding problem upstream rather than a shop problem.
Start with one workflow rather than the whole shop, and run it as a test in two parts. First a baseline reading of that workflow: how the work arrives, how complete it is at intake, how long it waits before production starts, whether it landed on time, how many status calls it generated, how it held during your busiest period, and how much of that work still goes outside. That is an afternoon if your system already reports it, or a few weeks if you collect it by hand. Then make the one change the module describes and hold it long enough to read the same measures again. The method runs on roughly a quarterly rhythm. The result is the difference between the two readings, which is what makes it evidence rather than a number.
At the Trusted Producer stage, there is one obvious way in, bad submission rate is tracked and falling, and visibility has ended most of the status call. At the Operations Expert stage, materials route to smart lockers near where practitioners work and mailing operations run end-to-end with NCOA, IMb compliance, and HIPAA-compliant data handling. The shop is no longer a destination, it is infrastructure.
Bring data specific to the coalition partner's concerns. Bring the numbers that describe their work rather than the shop's. For administrative departments, bring specific examples, such as an HR open-enrollment kit produced in-house or a tax form mailing with documented postage savings, and an offer to audit currently outsourced administrative print for in-house absorption.
When you are ready
The In-Plant Outcomes Program is this same work, self-guided, with SumnerOne available alongside it. You run the module and you own the outcome. Bring us in when you want another set of eyes on the right workflow, on getting a baseline worth measuring against, or on translating the result into the language your institution can use.
One workflow. One module. One quarter. That is enough to begin.