Pilot Objective

This pilot is intentionally narrow. The goal is not to digitize the entire skill ecosystem. It is to prove three outcomes clearly: schools can capture student skills beyond academics, students can build digital skill portfolios from Grade 6 onward, and schools can issue verifiable skill credentials aligned with NSQF.

3
Core outcomes to prove

Skill capture, portfolio creation, and credential issuance.

6
Months for execution

Short enough to move fast, long enough to produce evidence.

500-1000
Students with records

A practical proof-of-concept volume across selected schools.

1000+
Credentials issued

Enough activity to validate teacher adoption and platform readiness.

6-Month Pilot Timeline

Month 1

Setup and Teacher Orientation

  • School onboarding through eSquareERP relationships.
  • Teacher orientation on simple SOLO workflows.
  • Pilot skill domains and school cohorts confirmed.
Months 2-5

Skill Activity Capture

  • Teachers add workshops, projects, and competitions.
  • Students start building visible digital skill records.
  • Evidence can be uploaded where needed, but remains optional.
Month 6

Credential Issuance and Showcase

  • Schools issue final pilot credentials through SOLO.
  • Students present mini skill portfolios.
  • Program outcomes are consolidated into a pilot report.
eSquareERP logo
SOLO logo

ERP-led adoption with SOLO as the skills infrastructure layer

eSquareERP owns the institutional relationship, school onboarding, and teacher coordination. SOLO provides the credential engine, digital portfolio layer, verification, and basic NSQF mapping. That split keeps the pilot operationally light and commercially realistic.

Pilot Guardrails

  • Target only 3-5 innovative schools already comfortable with EdTech.
  • Focus on Grade 6-8, where teachers have more flexibility and exam pressure is lower.
  • Limit the pilot to 3-5 skill domains instead of broad competency architecture.
  • Do not run this as a full academic-year rollout in phase one.

What the Pilot Includes

The pilot stays intentionally small so schools can execute it with consistency. Activity design, teacher effort, and final outputs are all constrained to what schools can realistically sustain.

Schools and Grades

  • 3-5 innovative schools.
  • Priority schools already running coding, robotics, or innovation programs.
  • Grade 6-8 only.
  • Avoid Grade 10 and Grade 12 exam cohorts.

Skill Domains

  • Coding: simple games or app logic.
  • Robotics: basic build-and-test activities.
  • Design Thinking: local problem-solving projects.
  • Entrepreneurship: student-led mini initiatives.
  • Community Innovation: solving school-level issues.

Activity Types Captured

  • Skill workshops.
  • Student projects.
  • Competitions and hackathons.
  • No full competency tracking in this phase.

Student Outputs

  • A SOLO skill portfolio for every participating student.
  • Project-linked records from Grade 6 onward.
  • End-of-pilot verifiable credentials.
  • A compact learner record that can grow over time.

Credentials, Roles, and Success Metrics

The operational design is intentionally simple. Teachers do only the minimum required actions, partner responsibilities are clearly separated, and success is measured by adoption and credential issuance rather than complex analytics.

Teacher Responsibilities

  • Add activity.
  • Select students.
  • Upload evidence when useful.

eSquareERP Responsibilities

  • Introduce SOLO to schools.
  • Train teachers and support onboarding.
  • Own school-side coordination and collect feedback.

SOLO Responsibilities

  • Credential engine.
  • Skill portfolio platform.
  • Verification layer.
  • Basic NSQF skill mapping.

Credential Examples

  • Coding Fundamentals.
  • Robotics Explorer.
  • Design Thinking Innovator.
  • Each includes learner, school, evidence, and verification link.

Proof of Concept Targets

3-5 active schools, 500-1000 students with skill records, and 1000+ credentials issued across the pilot period.

Strategic Output

A final NEP Skill Portfolio Report with stories and metrics such as skill-area exposure, credentials issued, and innovation projects completed.

Market Positioning

If successful, SOLO can be positioned as NEP Skill Passport Infrastructure for Schools working alongside ERP systems, skill programs, and vocational pathways.