MLOps FDP 2026 — Outcomes Report
Joint closure report from the Faculty Development Programme delivered in partnership with Penlio Edufab Pvt Ltd. Participant outcomes, assessment results, and curriculum hand-off.
Available soon →Every Tejomarg engagement closes with a jointly-signed outcomes report. Programmes are governed by milestone reviews, beneficiary tracking, and co-signed closure — not handshakes. The reports below cover work under our Education pillar; Health, Women Empowerment, and Clean Water reporting will begin as those programmes go live in 2026–27.
On World Environment Day, the Foundation led students from local government schools on a guided expedition through Belagavi's Vaccine Depot urban forest — an immersive session on native tree species, the role of urban green cover in clean air, water, and soil, and the everyday habits that help protect it.
Sessions like this ground our work in direct experience — pairing what students learn in the classroom with the living ecosystem around them, and nurturing early environmental stewardship among the next generation.
Engagement closure reports, programme outcomes, and the annual review.
Joint closure report from the Faculty Development Programme delivered in partnership with Penlio Edufab Pvt Ltd. Participant outcomes, assessment results, and curriculum hand-off.
Available soon →District-level hackathon for government school students, co-designed with the Belagavi District Commissioner's office. Beneficiary list, FD structure, and follow-on tracking.
Available soon →The Foundation's first consolidated annual review — programme summary, financial principles, partner network, and the year ahead.
Available soon →Selected feedback from students, institutions, industry collaborators, and government departments across our active Education engagements. Voices from Health, Women Empowerment, and Clean Water programmes will be added as those pillars roll out.
The Design Thinking semester reframed how I approach problems. We shipped a working prototype to the dispensary at our college — it felt like real engineering, not coursework.
Penlio delivered every module on spec, on schedule. The FDP we co-delivered for KLS Gogte was production-grade — none of the watered-down, slide-only nonsense common in this space.
Before the MLOps FDP I'd only deployed models in notebooks. Now I have a CI pipeline running on my GitHub. The teaching style was hands-on from day one.
We've co-delivered with several foundations. Tejomarg is the only one that defines closure criteria up front. That's a competence we benchmark against now.
I came in skeptical about hackathons. Walked out with three teammates, a working AI water-quality model, and a Fixed Deposit waiting for me at age 18.
The graduate hires we've made out of the Tejomarg-trained cohorts hit production-readiness six months earlier than peer hires. That's a hard number we track.
The mentors didn't hand us answers. They asked us "why" until we figured it out ourselves. That changed how I study now.
We've embedded our staff engineers as guest mentors for their hackathons. They come back saying it's the most useful thing they did all quarter.
Our project went from a sketch on a whiteboard to a working API in twelve weeks. We were never doing it alone — the industry mentors were always one Slack away.
The expectation-setting in the first kickoff call is the most professional I've seen in CSR education work. No promises beyond what they can deliver.
The prize structure forced us to think long-term. Knowing the money is locked till 18 for education — that's not a bribe, that's a promise.
Their auditing rigour means every rupee co-spent is documented. As an industry partner, that protects us as much as it protects them.
I'd never written tests for my code before. The MLOps module showed me why that's not optional once you're in production.
We've been involved in three Tejomarg engagements now. The pattern is consistent — clear scope, weekly status notes, signed closure. It just works.
The hackathon was the first time anyone outside my school saw what I could build. My teacher cried when we placed. So did I, honestly.
Their AI hackathon for government schools is the most interesting CSR programme we've touched. We've started benchmarking our own work against it.
The IDT programme didn't just teach methods — it taught discipline. I now keep a research log for everything.
The Foundation's emphasis on outcomes over events is refreshing. We've now adjusted how we measure our own internal training programmes.
Working with real datasets, real bugs, real time pressure — that's the part college doesn't usually give you. Tejomarg did.
In a sector full of vanity metrics, Tejomarg actually reports on beneficiary follow-through. That's the standard we should all be holding.
The Tejomarg engagement gave our faculty exposure to production-grade tooling we'd been struggling to source on our own. Their MLOps FDP raised the floor for our entire CSE department.
The district-level AI hackathon brought our government school students into a conversation we didn't think they'd be part of. The follow-up tracking is what convinced us this was serious work.
What sets the Foundation apart is governance. Every engagement closes with a jointly-signed outcomes report. We've never had a partner this disciplined about closure.
We've worked with many CSR programmes. The Foundation's Fixed Deposit structure for prize money is the first one our department officially endorsed without modifications.
The Innovation & Design Thinking semester is now part of our curriculum, not an add-on. Student project quality has visibly shifted.
Reporting from the Foundation reaches our department on schedule, every quarter. We've stopped having to ask follow-up questions.
Their MoU process was the clearest we've signed in years. No ambiguity on deliverables, timelines, or who reports what.
Their approach respects that government schools have constraints. They don't try to bypass our processes — they work within them. That's why this partnership has lasted.
Our faculty came back from the FDP energised — and more importantly, with a working repo they could keep using. That's rare.
The visibility this programme gives our government school students is meaningful beyond the prize. Several parents have come to me citing the hackathon as the reason their child stayed in school.
For a small institution like ours, partnering with Tejomarg has meant access to industry mentors we could never have engaged directly.
As a public official, I appreciate that every disbursement is auditable. The FD-locked-till-18 structure was their own innovation and we've recommended it to peer districts.
They listen before they prescribe. The first month was them visiting our labs and asking what we actually needed — not pitching a programme.
Their teams operate with discipline. Permissions, communications, school-day disruptions — all handled professionally. We've not had a single complaint from a head master.
The transparency around financials and beneficiary tracking is exemplary. Our trustees were satisfied within a single review meeting.
The Foundation does not seek publicity. That alone tells us a great deal about what they're trying to build.
We extended the MoU after the first year. The decision was unanimous across the academic council — that almost never happens.
For our schools to be part of an AI hackathon — at all — was unimaginable two years ago. Tejomarg made it ordinary.
Their team understands the difference between an academic engagement and a marketing event. That respect for our institution shows in every interaction.
The fact that the prize is education-locked till age 18 means we can speak to parents about it without any hesitation. The structure does the work for us.
Four principles, applied to every engagement — from a three-day FDP to a multi-year MoU.
Every engagement begins with a written scope of work and a defined success criterion. Verbal commitments are not enough.
Mid-engagement reviews against the original scope — co-signed by the Foundation and the partner institution.
No engagement is closed unilaterally. A joint closure report is the only acceptable terminal artifact.
Where applicable, beneficiaries are tracked beyond the close of the programme — particularly in the case of FD-locked hackathon prizes.