Turn your information governance scorecard into a coalition dialogue.

The Information Governance playbook gives you a scorecard, and the scorecard's voiceover column gives you an opening line for each metric. This guide is the next step: knowing which number to lead with for which partner, what each coalition member is really asking underneath the metric, and what to bring so the number becomes a decision.

Five coalition members judge an education in-plant's information governance posture, each from a different chair. Each measures the shop on a different axis, so the same chain of custody figure lands differently depending on who is across the table. Work one partner at a time. You do not need to socialize the whole scorecard to everyone; you need to carry the two or three numbers that matter to the person who feels them.

General Counsel: where institutional data leaves institutional control

For General Counsel, the question is where institutional data leaves institutional control. When advancement, admissions, athletics, HR, or another office sends a personalized print job to an outside vendor, the source file usually carries donor PII, applicant PII, recruit PII, household relationships, giving history, or financial aid data. The vendor's MSA may say very little about how that data is held, by whom, for how long, or with what destruction terms. General Counsel often finds out the hard way: a vendor breach, a donor call about details that should not have been in the file, or a cyber insurance underwriter asking for the vendor list at renewal.

The in-plant can be the alternative. Variable data work for any office that touches institutional PII can stay inside the institution's data handling envelope. The common objections: "I have not seen a vendor MSA review on the print side." "Our cyber insurance underwriter asked for a vendor list last cycle and the answer surprised everybody." "The variable data composition platform advancement is using sits on a vendor's server with terms I have not reviewed."

Bring to the meeting: a recent variable data campaign produced inside the in-plant with chain of custody documented end to end, the outside vendor data exposure analysis on variable data work, a representative commercial vendor MSA with the data handling gaps annotated, and the CRM integration architecture on the in-plant's composition platform (SSO, role-based access, encrypted file transfer, audit trail).

Compliance officer / FERPA owner: records, not alarm

For Compliance, the question is whether the institution can show what happened when sensitive print work was produced. A compliance officer does not need dramatic language. She needs records. Accommodation print under IDEA carries chain of custody requirements an audit can ask for. FERPA-regulated student records print has delivery documentation requirements a parental complaint can surface. State privacy statutes add a regulatory layer that does not depend on federal FERPA enforcement to bite.

What she wants from the in-plant is chain of custody completeness on regulated content work: enough to answer a regulatory question with documentation rather than reconstruction. Common objections: "The IEP print last semester didn't all match the spec, and I can't tell whether the resource teacher's manual photocopies are still happening alongside the in-plant runs." "Our state's student data privacy statute is stricter than FERPA, and I don't have a vendor disclosure picture that maps to it." "Scan-to-email at the building copiers is wide open, and that is a state statute exposure even before any federal question."

Bring to the meeting: the most recent chain of custody audit results, the accommodation format recipe catalog, a documented incident response runbook for print related data events, and a specific recent example of a regulatory question the in-plant answered cleanly, with time to retrieve under 24 hours.

CFO / business manager: cost visibility and vendor consolidation

For Finance, the question is whether print costs and vendor exposure can be explained. A K-12 CFO is accountable to the board, the taxpayers, and increasingly to FOIA requests. A higher ed CFO is accountable to the trustees, the auditors, and the rating agency that holds the institution's bond. Both share the same operational pain: print spend is real, but rarely visible at the granularity the board or auditor will ask for.

The vendor consolidation case is the strongest argument here. Outsourced print spend goes to vendors that may or may not meet the institution's data handling standards, and the institution is often paying retail on work the in-plant could absorb at production cost. Common objections: "I cannot tell from the current data how much athletics is spending on print versus special education versus the main office." "The board asked what we spend on printing last year and the answer was the lease number, which everyone knew was incomplete." "We have vendors holding print related institutional data and I do not know what their MSAs say."

Bring to the meeting: the cost by cost center quarterly report, the outside vendor data exposure analysis with the data handling audit attached, the vendor consolidation roadmap, and the in-plant's documented savings for the period, paired with a projection for the next budget cycle.

IT director / CISO: the workflow picture behind the devices

For IT, the question is whether print workflows are visible enough to be governed. IT may know which devices are on the network, which are managed, and which have security settings in place. What IT may not know is what those devices actually produce. The in-plant leader does: which workflows involve sensitive records, including accommodation materials, admissions files, donor data, HR information, benefits materials, transcripts, and financial documents.

The right posture is partnership, not platform ownership. IT brings the device data. The in-plant brings the workflow picture. Together that produces a governance view neither side can build alone. Common objections: "The print fleet isn't on my weekly checklist; I don't have a baseline of where it is today." "We had identity authentication on, and then a firmware update reset it and nobody noticed for six months." "Our scan-to-email is wide open; I know it, and I haven't had bandwidth to fix it."

Bring to the meeting: a documented picture of which regulated content work flows through which devices, managed and unmanaged, the shadow print exposure picture, an offer to run a quarterly regulated content workflow review jointly, and a reference to the Print You Can Trust pillar page for the platform depth IT will want.

Audit committee / board IT subcommittee: print as a managed institutional asset

For the audit committee, the question is whether print has been brought into the institution's overall information governance posture. This is a conversation the in-plant leader is almost always carried into by a sponsor, typically the CFO or the IT director. The room is not evaluating fleet specifications. It is evaluating whether the print environment is being managed alongside the institution's other governance categories.

The in-plant's contribution is the governance metrics it owns directly: chain of custody completeness on regulated content work, variable data file chain of custody, and vendor spend exposure. The institutional metrics, including fleet security posture and shadow print exposure, are produced by IT and Finance. Common objections: "The print environment has not been in our annual audit; explain why we should care now." "We have an external IT audit and the print fleet was not in scope; what should we expect the auditor to find when it is?" "We are deciding capital allocation across ten priorities; explain why the variable data composition investment is on the list."

Bring to the meeting: the annual governance report with year-over-year trend on the headline metrics, chain of custody completeness broken out by accommodation, student records, and variable data, the vendor consolidation roadmap with the recommended capital allocation cadence, and the CFO sponsor's cover memo alongside the IT director sponsor's sign-off. The in-plant leader does not walk into the audit committee unsponsored.