Last night an email arrived from IEEE with a certificate attached: EPICS in IEEE Reviewer, October 2026. When I opened my credential wallet I saw it sitting next to two older ones, 2024 and 2025. Three years in a row, then. I had not stopped to count.

EPICS in IEEE is a programme that funds engineering projects built by students together with a community partner. The official site says it was founded in 2009 and has supported more than 255 projects in over 39 countries. Every project falls into one of four areas: access and abilities, education and outreach, environment, and human services. A team needs at least one IEEE member, it must include students, and it must work with a non-profit. A selected project can receive up to US$10,000, plus mentorship.

My part is small. I was trained and certified as a reviewer in September 2024, and since then I read proposals and score them against the programme's rubric: the problem and why it matters, the partner and their role, the technical solution, the project plan, what the students will learn, and how the team will measure impact.

I can't talk about any single proposal. Reviews are confidential, and they should be. But after three cycles I have noticed patterns that I wish every student team knew before writing.

The idea is rarely the weak part

Most proposals start with a real problem and a sincere team. A clinic that loses records. A school with no lab. A village where water is far. Reviewers are not hunting for clever ideas. We are looking for the moment where a good intention turns into something that can actually be checked.

That moment is usually the impact section, and it is where many proposals fade. "The community will benefit" tells me nothing. How many people, doing what differently, and how will you know in six months? A plan to count something, even something small, is worth more than a page of hope.

I took this lesson into my own research. When I evaluated speech recognition models for Sudanese Arabic this year, the first thing I fixed was my own evaluation: my early script had quietly picked its best result on the test set. Reading other people's plans for three years made me less forgiving of my own.

The partner has to be more than a logo

The proposals that convince me are the ones where the community partner is clearly part of the work. The partner said what they need, and they will still be using the thing after the students graduate. You can feel the difference on the page. Compare "we will build a system for the school" with something like "the head teacher told us the attendance sheets get lost every rainy season, so we will...". The second one already sounds like a project that will be used.

This is the same lesson I keep relearning with my own products. When I built Rafu, an offline stock and credit book for small shops, the hardest decisions were about how a small shop really works through its day, not about code.

Small and finished beats big and vague

A modest project with a clear plan, a realistic budget and a named person responsible for each step is easier to support than an ambitious one where nobody knows who does what in week four. The rubric asks for project planning documentation for a reason. Plenty of good projects fail because the plan ends in a sentence instead of a calendar.

Why I keep saying yes

Reviewing is unpaid, and it takes real evenings. I keep doing it because it is one of the few places where I see, every year, how students around the world try to use engineering for their own communities. It also keeps me honest. It is easy to write about impact. It is harder to score someone else's plan for it and then look at your own.

If you are a student with an idea for your community, look at the EPICS in IEEE call and the rubric before you write a single line. Write the impact section first. And if you are an engineer with a few spare evenings a year, reviewing is a quiet way to help someone else's first project get funded.

My three credentials are public: 2026, 2025 and 2024.

Saifuddin Ahmed is the founder of Ishraqa Daily, a community on Google Play, the App Store and the Microsoft Store that manages knowledge and turns it into impact: mentored developer clubs where people build open-source projects, languages, reading and listening together, and scholarships and opportunities. He also built Rafu and founded OtwoX Digital Solutions. More at saifuddin.dev and LinkedIn.

Drafted with help from an AI writing assistant. The three years of evenings were mine.