Education IPL Playbook: Educator Capacity

Make the shop easier to use than the workaround.

Teachers, faculty, department leaders, researchers and the administrative cycles. 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 teacher runs a class set on the workroom copier because the portal takes longer than the lesson allows. A researcher sends a poster outside because they are not sure the shop can carry the format. The benefits office uses the same vendor every year because the mailing process is already familiar. A department orders bound readers from a print shop across town, and nobody ever told them not to.

None of those people are being difficult. Each one picked the path that cost them least on the day. This playbook helps you find those workarounds and make the supported path the cheaper one, starting with a single group and what their work actually does today.

Stage 1 of 6 · See the Need

Can people get work into the shop clearly, track it easily, and trust it comes back when promised?

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 course materials into the shop

    One obvious way in, or a different one per department and per instructor.

    Coalition Teachers · Faculty

  • Knowing when a class set will be ready

    Whether an instructor can see where the work stands without calling to ask.

    Coalition Teachers · Department Leaders

  • Getting finished work back to a classroom or office

    The last few feet, across a campus or a district.

    Coalition Teachers · Administrative

  • Mailings that go out to families or alumni

    Recurring cycles where postage and address quality decide what it costs.

    Coalition Administrative

  • Work the desktop cannot produce

    Dissertations, posters, bound readers, anything with a real format requirement.

    Coalition Research & Scholarship · Faculty

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

Which workflow should you improve first? Pick the module that fixes the friction you feel most.

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.

01

Make the portal the default path for every submitter

The clearest way in, and a way to see where the work stands.

What you do: Build intake templates for the recurring jobs that generate the most follow-up, so a course pack or a class set is one choice rather than an email thread. Make service classification a required field, and add the visibility layer: confirmation, status, ready notification.

Proof points

  • bad submission rate
  • status inquiry volume
The full build detail for module 01

Already know you want a portal?

Compare web-to-print software at SumnerOne.com
02

Close the loop with smart-locker delivery

Move collection to a locker people already walk past and the "is it ready?" call stops.

What you do: Walk the campus or the district for the places people already pass through, deploy a locker network with notification and access control, and build chain of custody records on any locker holding student data.

Proof points

  • locker checkout cycle time
  • share of delivered volume routed through lockers
The full build detail for module 02
03

Absorb the mailings that go outside

Presort, address hygiene and variable data bring the recurring cycles back in house.

What you do: Build presort, CASS-certified address verification, NCOA on every cycle and variable data composition tied to the student information system, with FERPA-compliant handling on anything carrying student records.

Proof points

  • automated mailing volume against baseline
  • postage saved per cycle
The full build detail for module 03
04

Carry the specialty workflows the coalition demands

Posters, dissertations and bound readers are where work leaves because nobody knew you could do it.

What you do: Audit the coalition for what teaching, research and the professional schools currently get elsewhere, build those workflows, and document each one as a portal template so the submitter does not have to know the specification.

Proof points

  • first-time-right rate
  • specialty turnaround by workflow type
The full build detail for module 04

Costing out binding or wide format?

Compare specialty finishing at SumnerOne.com

Stage 3 of 6 · Build the Coalition

Who needs to participate, support, approve, or benefit?

Five groups send work to an in-plant, and each tends to measure the shop on a different axis. Rarely do all five 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.

  • Teachers

    K-12 instructional staff. Measure the shop on whether a class set arrives when the lesson needs it, and on how little of the prep period it costs to order.

  • Faculty

    Higher-ed teaching staff. Course packs, readers and exam sets, usually against a term calendar that does not move.

  • Department Leaders

    Chairs and principals, who see the aggregate rather than the job. Care about what the department spends and whether the shop is worth defending at budget time.

  • Research & Scholarship

    Posters, dissertations, grant submissions and journal work. The formats are demanding and the deadlines are set elsewhere.

  • Administrative

    The employee-facing and family-facing cycles: enrollment, benefits, bursar and the recurring mailings that quietly go outside.

Stage 4 of 6 · Run the Test

What focused experiment can you run on one workflow?

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.

What makes it a test

One workflow. One change. A reading before and after. The completed test is the difference between the two readings.

Go back and pick your module

Stage 5 of 6 · Capture the Evidence

What proof will show whether it worked? These are your Outcomes Scorecard rows.

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 class set keeps coming back to us for missing pieces before we can start. Here is how often, and for which building.

Bad submission rate

The number that travels furthest here. It shows whether the intake path is being used or worked around, and the answer is usually upstream of the shop.

An instructor can see where a class set is without calling to ask, and here is how often they still do.

Status inquiry volume

Whether the visibility you built is doing its job. People stop asking when they can see.

From the moment your job is finished to the moment it is in your hands, here is the typical wait now.

Locker checkout cycle time

The last few feet, which is where a job that finished on time can still read as late.

Of the recurring mailing that used to go outside, here is how much now runs in house.

Automated mailing volume against baseline

What the shop took back. It is the clearest money argument on the board, because the outside invoice is a known number.

Of the posters and bound work we produced this term, here is the share right on the first run.

First-time-right rate

Whether the specialty formats are genuinely carried or merely accepted. A format that needs two attempts is not yet a capability.

Through the start of term, here is whether we held our commitments when it mattered most.

Peak-period performance

Whether the shop holds together in the weeks 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

How should the result reach the group that felt the friction?

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.

Mark a job in stage 1 and a group in stage 3, and your note assembles itself here.

Eyes on the prize, not a cost center

Here's how this playbook moves you up the maturity arc.

  1. Cost Center. Submitters run their own print because the supported path is harder than the workaround. Where the arc begins.
  2. Consulted. The shop gets some work, but intake is inconsistent and submitters still chase status.
Here's where you advance

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.

  1. Trusted Producer. A clear path in, formats the shop can carry, and visibility that ends the status call.
  2. Campus Expert. The shop is no longer a destination. It is infrastructure the institution's workflow runs through.

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

Educator Capacity: the questions in-plant leaders ask.

Teachers and faculty sending course materials, class sets, readers and exam material; department leaders who see the aggregate spend rather than the individual job; research and scholarship sending posters, dissertations and grant work with demanding formats; and the administrative side running the recurring employee and family cycles. Each group measures the shop differently, and the thing they have in common is that they judge it on how little of their day it costs.

It measures how often work arrives incomplete or unclear, and it is the most useful single number here because it is a diagnostic for whether the intake path is being used or worked around rather than a measure of how the shop performs. A portal nobody can use produces the same rework as no portal at all. If one building or one department generates disproportionate rework, that 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, whether it landed when the lesson or the term needed it, how many status calls it generated, 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, and the result is the difference between the two readings.

At the Trusted Producer stage there is one obvious way in, the formats teaching and research actually need are carried rather than declined, and visibility has ended the status call. At the Campus Expert stage finished work reaches lockers in the buildings people already walk through, the recurring family and employee mailings run in house end to end, and the shop is part of how the institution operates rather than a place work is sent.

Bring the numbers that describe their department rather than the shop: how much of their work arrived ready to run, how long it waited, how often somebody had to call to ask, and what the department currently sends outside that the shop could carry. A chair is deciding whether the shop is worth defending at budget time, and that decision is made on the aggregate, not on any single job.

When you are ready

This is one path into the In-Plant Outcomes Program.

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.