Built like coursework, because it is coursework.
Four phases, no ambiguity. Each phase produces artifacts your examiners and audit panels can inspect — that paper trail is the entire point.
Enrollment → modules → evaluation → certificate
- 01
Enroll in a cohort
Pick a track and request a seat. Your college identity is registered on day one — this is what ties every later submission back to you.
Leaves behind- —Enrollment confirmation letter
- —Cohort seat + review slot
- 02
Work the modules
Six numbered weeks. You build, document, and submit — weekly deliverables with guided effort estimates, not video views.
Leaves behind- —Weekly deliverables
- —Submission + check-in record
- 03
Get evaluated
Reviewers check every submission against a published rubric, with one fair remediation if you fall short. Progress counts only reviewed passes.
Leaves behind- —Reviewed submissions with notes
- —Final evaluation record
- 04
Carry the certificate
At six reviewed weeks you receive a verifiable training-completion certificate with a public registry entry — checkable online in seconds.
Leaves behind- —Verified certificate
- —Mandate annexure + T&P report
Four rules that keep certificates honest
Progress is earned, not watched
Progress counts submitted, reviewed work. Attendance alone never completes a week.
Every certificate is checkable
Each certificate carries a public code. Any HoD or employer can verify it without an account.
Reviewers decide, committees trust
Records carry reviewer sign-off, which is why scrutiny committees can admit them at face value — after verifying online.
One standard across tracks
Embedded, full-stack, and VLSI cohorts differ in content, never in audit rigor.
