Distinguish a production partner from a content vendor
A content vendor sells content. A production partner builds the assets, systems and processes that let your organisation produce and maintain content at volume. Buyers often approach this distinction late, after signing for a set of courses and then discovering the organisation still cannot produce the next set without external help.
Clarify which role you are buying. If you need a partner to design, produce and publish a defined body of content, evaluate them as a supplier of outcomes. If you need them to build a capability, add criteria around knowledge transfer, documentation, tooling handover, and how much of the work your own team can absorb afterwards.
This distinction changes the evaluation weightings. A production partner is judged partly on whether they eventually make themselves less necessary, or on whether they make your internal team measurably faster at producing work.
Assess the delivery system, not the individual people
Individual producers are interchangeable; a delivery system is not. Ask how work moves from intake to published asset, who owns each stage, where the source files live, how version history is tracked, and what happens when a subject matter expert changes their mind after a module has been built in three languages.
Look for evidence of process maturity. Mature partners will have a documented workflow, a naming and folder convention, a reusable template library, and a clear handoff package for every deliverable. Ask to see the actual folder structure of a recent project, with client-identifying details removed, and to walk through how one piece of content moved from brief to final.
Partners who are secretive about their process usually have a fragile process. The risk sits in the handoff: source files that cannot be edited, a template that only one person understands, or a build that breaks when a font or plugin is missing from a future team's machine.
Test interoperability and standards compliance
Enterprise content lives in systems the producer does not control. Ask which authoring tools the team is fluent in, which output formats they deliver as standard, and how they handle SCORM 1.2, SCORM 2004 and xAPI packages. Confirm that LMS testing happens in the target platforms before delivery, not only in the authoring tool.
Beyond packaging, ask about asset formats and accessibility. Do they deliver captions to a recognised standard, transcripts, alt text, and keyboard-navigable interactions? Will they work to WCAG 2.2 AA for the deliverable type, and can they show a conformance report rather than a general assurance?
Also test the exit scenario. A partner that publishes content in a proprietary authoring tool creates a dependency you will pay for later. Ask what happens to your content if the relationship ends, and whether source files, project files, and documentation are yours to keep and use with another supplier.
Examine capacity and concurrency
Most disappointments in enterprise content production are scheduling failures, not quality failures. Ask how many concurrent projects the team supports, what the current load looks like, and who covers your work if a key person is unavailable. Ask what the supplier does when two clients want the same week.
Also ask how the partner handles a scope increase mid-flight. A good answer describes a triage or change-control mechanism, a realistic impact on the schedule, and a way to protect already-agreed deliverables. A vague answer about being flexible usually means the original plan is no longer real.
If your programme spans multiple business units, ask how the partner will coordinate across your internal stakeholders. A single accountable project lead with a published escalation path is worth more than a larger team without ownership.
Read the commercial terms for hidden constraints
Beyond price, several contractual terms quietly determine whether a partnership scales. Clarify who owns the intellectual property in source files, scripts, recordings, custom illustrations and templates, and whether ownership transfers on final payment. Check whether the partner claims any licence to reuse your content, your subject matter, or a generic version of your templates for other clients.
Look at liability and warranty in practical terms. What happens if a delivered course contains an accessibility defect that fails an audit six months after launch?
What is the remediation obligation and how long does it last? A partner willing to take a meaningful remediation obligation is behaving like a partner.
Finally, confirm the termination and transition terms. A well-drafted agreement makes it easy for you to leave with usable assets, and that ease is itself a signal of confidence. See our guide on how to compare enterprise content production proposals for a structured way to normalise what suppliers send you.
Commonly overlooked pitfalls
- Evaluating on the strength of individual creatives rather than on the repeatability of the delivery system behind them.
- Overlooking asset handover, so the organisation ends up unable to edit or republish content without the supplier.
- Treating accessibility, captions and transcripts as optional extras that can be added later cheaply.
- Failing to check concurrent capacity, which surfaces only after signature when the schedule is already fixed.
- Accepting IP terms that let the partner reuse your templates or content structure with other clients.
Next steps
- Decide and document whether you are buying a body of content, a production capability, or both.
- Request a redacted folder structure and a walkthrough of one project from brief to published asset.
- Specify required output standards and packaging formats in the request, and require demonstration of a built package.
- Ask every finalist to describe their concurrent capacity and their change-control process in writing.
- Add IP, handover, accessibility remediation, and termination clauses to your standard contract terms.
Related guides
Put this into practice
The vendor evaluation checklist and the RFP template turn a guide into a process you can run this week.