Vendor Development

Vendor Development Process

The development team will supplement existing vendor content by adding workplace context, simulation framing, and professional deliverables. The vendor content stays exactly as provided - the team is adding workplace simulation elements around it.

Step 1: Identify the Vendor Asset

What the Team Does: Look at the vendor material being supplemented (slide deck, lab, quiz).

• Note the technical skill it covers
• Note the learning objective it supports
• Don’t rewrite or trim the vendor content

Example: CompTIA Module 1 - “What Does an IT Specialist Do?”

• Technical skill: IT specialist responsibilities and troubleshooting methodology
• Learning objective: “Describe what an IT specialist is and their responsibilities”
• Vendor content: Slides, labs, and quizzes stay exactly as provided

Step 2: Create a Module-Level Workplace Context Wrapper

What the Team Does: Create a comprehensive workplace simulation context that wraps the entire module, not individual assets. This saves time and provides consistent context throughout.

• Introduce a company/role (TechCorp, Junior IT Technician, Hospital IT Support)
• Establish the overall workplace scenario and learner’s role
• Set up team structure with working units and group dynamics
• Define team KPIs and performance metrics
• Create a module introduction that sets the stage for all vendor content
• Keep it to 2-3 slides or a comprehensive instructor script

Example Module Wrapper: View Example: Module Context Wrapper with Team Dynamics and KPIs  - See how to create a comprehensive module-level workplace context wrapper with team structure and shared KPIs.

What the Team Produces: An ideal example of a complete module with workplace context that looks like this:

Step 2.5: Establish Group Work and Team Dynamics

What the Team Does: Encourage group work throughout the module by treating teams as working units with shared responsibilities and accountability.

• Set up teams of 3-4 learners as working units
• Establish team roles and responsibilities
• Create shared deliverables and group assessments
• Use team-based problem-solving scenarios
• Track team KPIs and performance metrics together

Key Elements to Include:

• Team formation and role assignments
• Shared accountability for team KPIs
• Collaborative problem-solving activities
• Peer review and feedback processes
• Team-based assessments and deliverables

Example: Team Dynamics and KPIs Introduction View Example: Team Dynamics and KPIs Introduction  - See how to introduce group work, team structure, and shared KPIs in your module context wrapper.

Step 3: Add Reflection & Discussion Prompts

What You Do: After the vendor content, create 2–3 questions that tie the technical knowledge to real work.

Examples:

• “If this error happened in a hospital, what would be the impact on patient care be?”
• “What would you document or escalate to your supervisor?”
• “How would you communicate this to a non-technical manager?”

What You Produce: A Google Doc that looks like this:

Step 4: Design a Professional Deliverable

What You Do: Turn a vendor activity into a workplace-style output.

Examples:

• Vendor Lab: “Match each component to its function.”

• Add-On: “Complete an inventory report for your supervisor showing components, safety notes, and issues found.”

• Vendor Quiz: “Which component processes instructions?”

• Add-On: “Document your answer in a troubleshooting log entry.”

What You Produce: A professional template that looks like this:

Step 5: Add One Skills-Based Assessment (SBA) Per Module

What You Do: At the module level, design one hands-on SBA that ties everything together.

Example for Module 178: Install and configure OpenEMR locally, create two user accounts, and submit a setup log with screenshots.

What You Produce: An SBA instruction document that looks like this:

Quality Check

Before you publish, run these final checks:

• ✅ All planning objectives covered by vendor content + additions
• ✅ Simulation frame visible in every artifact (TechCorp context)
• ✅ Professional deliverables replace academic assessments
• ✅ Team collaboration and workplace communication included
• ✅ All internal links work and resolve correctly

You’re Ready to Launch

Your vendor curriculum is now ready for learners. You’ve transformed existing content into engaging workplace simulations that help learners build the skills and mindset they need for success in their careers.

Developer Tips

The PS ID Companion builds on these AI best practices and is the development team’s go-to tool for planning, brainstorming, and generating high-quality instructional prompts tailored to Per Scholas modules. Use it to:

• Scaffold learning objectives and daily plans
• Get prompt suggestions for labs, scenarios, and assessments
• Overcome creative blocks or writer’s block
• Ensure prompts are job-aligned and simulation-ready

Try the PS ID Companion

Quality Review Checklist