The Inception Phase Is Not a Formality: How to Use Your First 90 Days to Actually Build Your MEAL System

I have seen it happen on too many projects: the inception phase gets treated as a waiting room. Teams are still negotiating workplans, offices are being set up, and the attitude is more or less "we will get to MEAL once things settle down." By the time things settle down, the baseline window has closed, the first quarterly report is looming, and the indicator matrix has never been field-tested. You are already behind, and you have not collected a single data point yet. Here is the thing: the first 90 days of a project are not a formality. They are the most consequential window you will ever have. The decisions you make, or fail to make, in this period shape everything that follows: your data quality, your team's habits, your relationships with implementing partners, and your credibility with the donor. Let me walk you through how I would approach this window intentionally, not reactively. Why the Inception Phase Gets Wasted

The most common pattern I see is that MEAL activities are scheduled to begin "after the workplan is approved." But the workplan approval process is itself something that could be used as a MEAL design opportunity. Stakeholder consultations, partner mapping meetings, context assessments, these are not just administrative boxes to tick. They are your first round of qualitative data collection, and if you treat them that way, you can enter implementation with genuine insight rather than assumptions. There is also a tendency to conflate "the MEAL system is documented" with "the MEAL system exists." Having a five-page MEAL plan in a proposal annex is not the same as having tools that work in the field, staff who know how to use them, and partners who understand what they are expected to report and why. ⚠️ Warning: If your only MEAL artifact at the end of inception is a revised indicator matrix sitting in a shared drive, you have not built a system. You have built a document. Phase One (Days 1 to 30): Listen Before You Design The first month should be dominated by listening and learning. This does not mean passive observation, it means structured inquiry. A few concrete things to do in this window: Map your data ecosystem. What data already exists? Are there previous project evaluations, government administrative data, community health worker records, or partner databases that overlap with your indicators? Knowing what exists saves you from duplicating collection effort later. Conduct a stakeholder power-interest mapping for MEAL specifically. Who needs data from this project? Who generates it? Who can block data flow? A program manager and a district government official have very different relationships to your reporting system. Run an informal indicator review with field staff. Sit with the people who will eventually use your tools. Walk them through the draft indicators. Ask what they think they can realistically measure, and what would require them to do something they have never done before. Their answers will save you from designing a system that works on paper but collapses in the field. 💡 Tip: Treat every stakeholder meeting in the first 30 days as a mini key informant interview. You are learning the context, not just introducing yourself. Come with questions, not just a slide deck. The broader principle here is one that holds across many contexts: the first 90 days are not about having all the answers, they are about learning with intention [1]. In MEAL, that learning has to be systematic, not incidental. Phase Two (Days 31 to 60): Design and Test Everything This is where most teams want to start. They want to jump straight to designing tools and building the database. And by day 31, with a solid month of listening behind you, you are actually ready. The critical word in this phase, though, is "test." Every tool you design needs to be piloted before it is deployed at scale. This means: A pilot data collection exercise with a small sample of real respondents, not a mock run with colleagues. A data flow walk-through: from collection to entry to aggregation to reporting. Where does data get stuck? Where does it get transformed in ways that introduce error? A partner reporting template review: can your implementing partners actually fill in what you are asking for, with the information systems they have? 📝 Note: Pilot testing does not need to be a formal exercise. Even a one-day field visit with three households, followed by a debrief where enumerators flag confusion points, will surface issues that months of desk review would miss. During this phase, you should also be building the governance layer of your MEAL system: who reviews data quality, who flags anomalies, who has authority to pause data collection if something is going wrong. A system without governance is just a collection of spreadsheets waiting to accumulate errors. A well-structured 90-day plan, as described in startup and organizational contexts, functions as an "operating system that translates strategic intent into defined outcomes, assigns responsibility, establishes measurement, and enforces a regular decision cadence" [2]. The MEAL inception phase is exactly that, applied to a project's evidence infrastructure. Phase Three (Days 61 to 90): Lock, Train, and Launch

By day 61, your tools should be finalized and your database should be ready to receive real data. This final phase is about two things: building human capacity and making the system official. Training is not a one-day event. A common mistake is to hold a two-day MEAL orientation workshop and then assume staff and partners know how to use the system. Training for MEAL needs to be: Role-specific (enumerators need different things than program managers) Hands-on (people should fill in actual tools with real or realistic data, not just watch a presentation) Followed up (a brief check-in two weeks after training to troubleshoot the first real data collection cycle is worth more than an extra day of initial training) Making the system official means more than getting sign-off. It means the MEAL plan is shared with all partners, the data calendar is agreed upon, and everyone knows what the first reporting deadline is and what it requires from them. Ambiguity at this stage breeds the "we did not know we were supposed to send that" emails that arrive the week before your first quarterly report is due. 💡 Tip: Create a one-page MEAL reference card for field staff and partners: what data they collect, when they submit it, to whom, and in what format. Print it. Laminate it if you have to. It will do more work than any SharePoint folder. The Baseline Timing Problem One thing the inception phase should resolve absolutely: when is the baseline happening, and who is responsible for it? Baseline data needs to be collected before any significant program activities reach the target population. That window is often narrower than people expect. If your inception phase bleeds into month four because of procurement delays or staff onboarding gaps, your baseline may no longer reflect a true pre-intervention state. Baseline planning, including the sampling approach, tool development, enumerator recruitment, and data analysis plan, should begin no later than day 30 and ideally be completed by day 60, so that fieldwork can start while the pre-intervention window is still open. What a Strong Inception Phase Looks Like in Practice Milestone Target Timing Who Owns It Stakeholder and data ecosystem mapping Days 1-21 MEAL Lead Indicator matrix finalized and field-validated Days 20-35 MEAL Lead + Program Team Data collection tools drafted and piloted Days 30-50 MEAL Lead + Field Staff Database / ODK / KoboToolbox setup Days 40-55 MEAL / Data Officer Partner reporting templates agreed Days 45-60 MEAL Lead + Partners Baseline fieldwork completed Days 50-80 MEAL Team + Enumerators Full MEAL training for staff and partners Days 60-75 MEAL Lead MEAL system formally launched Day 90 MEAL Lead + Management The sequence matters as much as the tasks. Each phase builds on the one before it. You cannot train people on tools that are not yet finalized. You cannot set data quality benchmarks before you have piloted your instruments. And you cannot get partner buy-in on a system they had no input in designing. If you want help turning this framework into a live workplan, a training agenda, or a set of field-ready data collection tools, that is exactly the kind of work I can do with you at vera.ignex.io. The first 90 days move fast. Let's use them well. Follow Vera for more on MEL & project management: LinkedIn · Instagram · Facebook · X