Scope a custom curriculum request with academic governance

An employer calls with an urgent request. Build a course around their exact tool stack so new hires show up ready to work on day one. The ask sounds reasonable, and it usually comes from a real need. But if you agree before faculty review, learner prerequisites, and vendor licensing are settled, you turn a partnership conversation into a promise you cannot keep. As a Partnership Director, your job is to take the employer's need seriously while keeping the academic process visible in the same conversation, not as a caveat you raise later once a timeline is already locked in.

Why this conversation goes wrong

Most partnership directors want to say yes. An employer with hiring needs and a willingness to fund training is a good problem to have, and the instinct to move fast is not wrong. The trouble starts when a job description gets treated as if it were a finished curriculum. A list of tasks an employer wants new hires to perform is not the same as a set of learning outcomes, and it says nothing about what students already know when they arrive.

The second failure is skipping the vendor question. Employers often assume that because they use a tool internally, the school can teach it freely. Many commercial platforms require separate training or academic licenses, and building a module around a tool you cannot legally teach on wastes everyone's time. The third failure is silence about faculty governance until late in the process. If the employer hears about curriculum committee review for the first time after they think a deal is close, it reads as a stall tactic even when it is standard practice. Naming the process early, before any specifics are agreed, keeps it from feeling like a surprise later.

How to prepare

Before you take the call, gather four things. First, ask the employer for a concrete list of work tasks, not a general description like "proficient in the platform." Second, find out what your current students already know when they finish their core courses, so you can see the actual gap. Third, check with the vendor about training rights. A tool license for internal staff use rarely covers classroom instruction, and you need to know this before you set expectations, not after. Fourth, confirm who owns curriculum approval at your institution and roughly how long that review takes.

Walk into the conversation with a rough sense of the paths available. A short workshop bolted onto an existing course might be enough if the gap is narrow. A revised module could work if the tool overlaps with something already taught. A full program proposal makes sense only if the employer's need reflects a lasting shift in the field, not a one time hiring push. You do not need to pick a path before the call. You need to know that these are the real options so you are not scoping a fantasy fourth option where a full custom curriculum appears in a few weeks with no committee review.

What to say

Talent leader Priya opens the call with pressure built in. "Can you build this for our incoming hires by summer. We need graduates who know our exact tools on their first day."

Director Marcus does not answer the timeline question directly, because he cannot yet. "Before I can talk about timing, I want to understand what your teams actually do with these tools day to day. Can you walk me through the specific tasks, tell me what tool licenses are available for student training, and help me understand what skills someone needs before they even touch the platform."

Priya admits the gaps once asked directly. She says the vendor has not granted any training licenses yet, and no one on the faculty side has seen the competencies she has in mind.

Marcus names the process plainly instead of softening it. "Curriculum changes go through faculty approval here, and the vendor may require training rights separate from your internal license. I cannot promise a summer launch, and I cannot promise a specific level of job readiness on day one. What I can offer is a scoping review with faculty, our curriculum committee contact, and your vendor rep, so we compare the competencies you need against what a real course can teach and what the license actually allows."

That last move matters. Marcus gives Priya a way to stay involved without letting her set the shape of the outcome before anyone with authority over curriculum or licensing has weighed in.

Mistakes to avoid

A few patterns sink this conversation even when the director means well.

1. Agreeing to a date before faculty or vendor questions are answered. A summer launch commitment made in week one becomes a broken promise in week eight when the vendor says no or the committee needs another cycle.

2. Treating the employer's task list as a finished syllabus. Work tasks tell you what people do on the job. They do not tell you what a student needs to learn first, in what order, or how to assess it.

3. Raising governance only when the employer pushes back. If faculty review comes up for the first time as an objection, it sounds like an excuse. Raise it as a fact of how curriculum works, stated the same way you would state any other operational reality.

4. Promising a specific outcome, like graduates who match the tool exactly. You control the design of a course. You do not control what any individual student retains or how fast they apply it on a new job.

5. Leaving the meeting without a named owner for each open question. Vendor licensing needs an owner and a date. Faculty review needs an owner and a date. An open item with no owner quietly becomes a missed commitment.

How to practice and score it

This is a conversation worth rehearsing before you have it for real, because the pressure to just say yes is strong in the moment and much easier to resist on a practice run. DealSpeak lets you roleplay an employer pushing for a fast, exact match curriculum, then scores how you handled it. Set up a scenario where the employer demands a hard deadline and a specific competency match, and see whether you name faculty review and licensing in your first two responses or only after being pushed.

Score yourself, or have a manager score you, on three things. Did you ask for concrete task details instead of accepting a vague request. Did you name the governance process and the licensing question before making any commitment. Did you leave the conversation with a scoping review scheduled and clear owners for the open items, rather than a vague promise to follow up. If you want more reps on adjacent conversations, DealSpeak's Education practice conversations cover related scenarios, including how to discuss data retention during an education technology evaluation and how to discuss a missed application deadline with care.

The goal is not to slow the employer down for its own sake. It is to make sure any curriculum you agree to build actually survives contact with faculty review, vendor terms, and your own students' starting point. Practice the version of this conversation where you say no to a date you cannot promise, and saying it gets easier every time you do it.