Source first
Every public record starts from an official circular, prospectus or registrar notice. We capture the document, its URL and the date it was verified.
About
ShikkhaPath is a student-first admission platform for Bangladesh. Our job is not to predict your future — it is to show you the official record, on time, with its source attached.
Admission season in Bangladesh runs on screenshots. A circular is posted, cropped, forwarded and re-captioned until the deadline, fee and eligibility rule no longer match the original. Students pay application fees on the strength of a rumour.
ShikkhaPath keeps the original document attached to every record. If a value is missing, we say “unavailable”. If a deadline has passed, the record is marked historical and never shown as open. If a source cannot be verified, the record does not publish.
We do not sell admission decisions, seats or “guaranteed” chances. Eligibility is a three-state guidance check: eligible only when every published threshold is machine-checkable and met, otherwise check required.
Every public record starts from an official circular, prospectus or registrar notice. We capture the document, its URL and the date it was verified.
A record is published only after an editor checks the field against the source. Fees, seats and deadlines that the source does not state are shown as unavailable.
All countdowns use Asia/Dhaka (BST). International deadlines keep their source time zone and say so explicitly.
Sponsored placements are labelled, contained and never influence eligibility, rankings or verified badges.
Step 1
A circular arrives through the scheduled source check, a manual upload or a student tip. The file is magic-byte validated and stored outside the web root.
Step 2
Text is extracted and compared with the published record. If the content is unchanged, nothing is created. If extraction fails, the document is flagged for manual review — never published empty.
Step 3
An editor sees a field-by-field diff. Every proposed value is validated against that entity’s schema before it can be applied. URL changes require an admin, not a moderator.
Step 4
Publishing writes the record and schedules a cache purge. If the purge fails, the failure surfaces in the admin overview instead of disappearing.