This week IEEE sent me a certificate for reviewing EPICS in IEEE projects in the October 2026 cycle. It landed in my credential wallet next to the ones from 2024 and 2025.
Since 2024, every review cycle has put between four and ten project proposals on my desk, and some years run more than one cycle. Each proposal is a student team asking for money to build something for a community: a school, a clinic, a village, a group of people with disabilities. Each one gets a careful read and a score.
EPICS in IEEE has been doing this since 2009, with more than 255 projects in over 39 countries. Projects fall into four areas: access and abilities, education and outreach, environment, and human services. Every team must include students and a non-profit partner, and a selected project can receive up to US$10,000 with mentoring.
Reviews are confidential, so I won't describe any proposal. What I can share is the pattern. After this many proposals it is hard to miss.
The idea is almost never the problem
Student teams pick real problems. Water, records, access, learning. I almost never mark a proposal down for its idea.
Proposals lose points where intention has to become evidence. The rubric asks how the team will measure impact, and that is where many go quiet. "The community will benefit" can't be checked. "We will count how many students use the lab each week, starting in month two" can. The second sentence is less inspiring. It is also the one that gets funded.
That habit followed me into my own research. When I tested speech recognition models for Sudanese Arabic this year, the first bug I fixed was in my evaluation: my early script picked its best result on the test set. Scoring other people's plans made me stricter about my own.
A partner is not a logo
The strongest proposals read as if someone from the community dictated the problem. Compare "we will build a system for the school" with "the head teacher told us attendance sheets get lost every rainy season". The first describes the team. The second describes the need, and you can already see who will use the result after the students graduate.
I relearn this with my own products. When I built Rafu, an offline stock and credit book for small shops, the hardest decisions were about how a shop really works through its day, not about code.
A plan ends in a calendar
A modest project with a realistic budget, clear steps and a named person for each step is easier to fund than a bold one where nobody knows what happens in week four. Plenty of good projects fail because the plan ends in a sentence instead of dates.
If this was my last cycle
This may be my last cycle for a while. Reviewing is unpaid and takes evenings, and my own projects and research are asking for more of them.
It gave me more than I gave it. Few things show so clearly how students around the world try to use engineering for their own people. It also kept me honest: writing about impact is easy, scoring someone else's plan for it is harder, and looking at your own plan afterwards is the hardest part.
Thank you to the EPICS in IEEE programme team, who trained us, answered every question and kept each cycle on time, and to the other reviewers whose scores sat next to mine.
For the next reviewers, one thing: read the impact section twice. That is where a proposal shows whether the team will still be there when the community needs them.
If you are a student with an idea for your community, read the EPICS in IEEE call and its rubric before you write anything, and write the impact section first. If you are an engineer with a few free evenings, take my seat. Your careful score can be the reason someone's first project gets built.
My reviewer credentials are public: 2026, 2025 and 2024.
I'm Saifuddin Ahmed, founder of Ishraqa Daily, a community on Google Play, the App Store and the Microsoft Store that turns knowledge into impact: developer clubs where people build open-source projects with mentors, languages, reading and listening together, and scholarships and opportunities. I also built Rafu and founded OtwoX Digital Solutions. More of my work is at saifuddin.dev and on LinkedIn.
Drafted with help from an AI writing assistant. The evenings of reviewing were mine.
Top comments (0)