Service Lifecycle

Services

From research design to field evidence and final reporting.

Most research and field assignments move through a familiar set of stages: understanding the question, building the tool, preparing the field, collecting information, checking quality, managing the data and turning it into something the client can actually use.

Not every project needs every stage, and not every client comes to MFRS at the beginning. Some arrive with a complete research design and need only field execution. Others need support from the first discussion through final reporting. The lifecycle below shows how those pieces fit together when the full chain is required.

Research Design → Tool Development → Field Planning → Data Collection → Quality Control → Data Management → Analysis → Reporting → Monitoring & Evaluation
← Back to Services
How The Lifecycle Works

A sequence, not a rigid formula.

The stages below represent the typical logic behind a research and field assignment. Their order may overlap, repeat or change depending on the methodology. A pilot can send a questionnaire back for revision. A quality problem can send a team back into the field. Monitoring may continue long after the first report has been delivered.

The important part is not completing nine boxes.

What matters is defining which stages the assignment requires, who is responsible for each stage, what must be reviewed, and what evidence is needed before the work moves forward.

01

Research Design

Research design begins by defining what the assignment needs to answer, whose perspective or data is required, and what evidence will be sufficient for the intended use.

  • Clarification of study objectives and research questions.
  • Identification of target population and respondent groups.
  • Review of geography, sample requirements and expected outputs.
  • Discussion of methodology, timelines and practical field feasibility.
  • Sampling support where this forms part of the agreed scope.
Typical output: Agreed study scope, research questions, methodology and field requirements.
Field reality matters here: a design that is technically sound but impossible to execute in the available geography and timeline still needs to be revised.
02

Tool Development

Once the study questions are clear, they have to become instruments that respondents and field teams can actually work with. Depending on the assignment, MFRS may develop the tool, review an existing one, program it digitally or support only the field-testing stage.

  • Questionnaire or interview-schedule development.
  • Translation and language adaptation where required.
  • Skip patterns, validation rules and response constraints.
  • Digital form programming using appropriate platforms such as KoboToolbox, ODK or SurveyCTO where required.
  • Pilot testing and revision before full deployment.
Typical output: Field-ready questionnaire or discussion tool, with programmed validations and approved revisions where applicable.
A pilot is allowed to expose problems. That is the point of running one before a large field team has already started collecting data.
03

Field Planning

This is the stage where the written research plan becomes an actual operating plan. Team size, supervisor structure, routes, permissions, travel, respondent access and reporting lines all have to be worked out before deployment.

  • Team requirement and field structure by geography.
  • Investigator and supervisor deployment planning.
  • Assignment-specific training and briefing.
  • Route and travel planning.
  • Local permissions and institutional coordination where required.
  • Daily reporting and escalation structure.
Typical output: Deployment plan covering team structure, locations, training, logistics, reporting and escalation arrangements.
Numbers alone do not make a field plan. Twenty investigators in a compact city and twenty investigators spread across remote rural blocks do not represent the same capacity.
04

Data Collection

Fieldwork begins with the approved plan, but it rarely remains completely predictable. Respondents may be unavailable, institutions may need repeat visits, routes may change and teams may encounter questions that were not obvious during training.

  • Household, institutional, facility, community or telephonic data collection.
  • Daily monitoring of completed work against the field plan.
  • Supervisor review of team activity.
  • Documentation of non-response and material field constraints.
  • Escalation of operational or questionnaire issues while teams remain deployed.
Typical output: Completed field records together with progress, non-response and field-issue documentation as required.
Completion is not the same as quality. The number of interviews completed tells only part of the story.
05

Quality Control

Quality control is most useful while there is still time to act on what it finds. MFRS therefore treats field review, validation and verification as part of execution rather than only as an exercise after data collection ends.

  • Supervisor review of completed interviews or forms.
  • Back-checks or respondent re-verification where required.
  • Spot checks and field observations according to the assignment.
  • Review of timestamps, GPS, duration or other digital indicators where these form part of the approved data system.
  • Identification and escalation of suspicious, inconsistent or incomplete work.
Typical output: Reviewed field records, verification findings and documented corrective actions where required.
The method depends on the project. Not every assignment uses the same back-check percentage or the same verification method. Quality controls should match the research design and client requirements.
06

Data Management

Raw field data is not automatically a final dataset. Before analysis, it may require cleaning, validation, coding, restructuring, de-duplication and documentation of corrections or exclusions.

  • Completeness and range checks.
  • Logical and internal-consistency review.
  • Duplicate and unusual-pattern checks where relevant.
  • Data entry and verification for paper-based assignments where required.
  • Organisation of datasets, codebooks or supporting documentation according to scope.
Typical output: Structured and reviewed dataset, with supporting documentation appropriate to the assignment.
Cleaning should not become silent rewriting. Material changes to collected information need a defensible reason and an appropriate record.
07

Analysis

Analysis begins with the original study questions. A useful output should help the client understand what the evidence says — not simply produce a large number of tables because the data allows it.

  • Descriptive analysis and summary indicators.
  • Cross-tabulation and subgroup analysis where appropriate.
  • Trend or comparison analysis where the study design supports it.
  • Thematic review for qualitative material where included in scope.
  • Data visualisation and dashboards where useful and agreed.
Typical output: Agreed tables, indicators, thematic findings, visualisations or analytical outputs according to scope.
Analysis follows the evidence. A preferred narrative should not determine what the data is allowed to show.
08

Reporting

Different readers need different outputs. A technical research team may need methodology and detailed tables; programme leadership may need the central findings and implementation implications; a policy audience may need a concise brief.

  • Draft and final research or project reports.
  • Executive summaries and management briefs.
  • Policy briefs where appropriate.
  • Case studies and documented programme narratives where included in scope.
  • Presentation of findings where required by the client.
  • Reporting of material limitations and field constraints.
Typical output: Draft and final deliverables prepared for the intended audience and agreed reporting requirement.
A report should not become more certain than the evidence. Limitations remain part of the finding, even when they make the conclusion less neat.
09

Monitoring, Evaluation & Follow-up Support

Some assignments conclude with the final deliverable; others continue through periodic monitoring, verification, follow-up studies or evaluation. Where included in the agreed scope, MFRS can support these subsequent stages as the programme or assignment progresses.

  • Concurrent or periodic programme monitoring.
  • Follow-up verification visits.
  • Indicator and outcome tracking.
  • Midline or endline studies.
  • Review of implementation lessons and changing field conditions.
  • Follow-up technical or implementation support where included in the engagement.
Typical output: Monitoring findings, verification records, evaluation outputs or agreed follow-up technical inputs.
The lifecycle can repeat. A monitoring finding may lead to a revised tool, a new round of fieldwork or another evaluation cycle rather than a simple project close.
Different Ways To Use The Lifecycle

Clients can enter at different points.

The full lifecycle is useful as a map, but it does not mean every client has to buy every stage from MFRS.

Field Execution Support

The client already has the research design and instrument. MFRS supports field planning, training, deployment, supervision, collection and agreed quality processes.

Research & Field Support

MFRS supports selected design and tool-development stages together with field execution, data management and reporting.

End-to-End Assignment Support

Where appropriate to the assignment and available capability, MFRS can support the project from initial scoping through fieldwork, analysis and final reporting.

Quality Across The Lifecycle

Quality is not a separate box between fieldwork and analysis.

Errors can enter a project long before the first interview and long after the last one. That is why quality responsibility changes from stage to stage rather than appearing only under “QC”.

The exact control method is agreed according to the study design, risk profile, data-collection mode and client requirements rather than applied as a fixed percentage across every assignment.

Before Fieldwork

Review the scope, questionnaire, sampling assumptions, team plan, training and deployment readiness.

During Fieldwork

Monitor progress, supervision, back-checks, field issues, respondent coverage and unusual data patterns.

After Fieldwork

Review data, document corrections, assess limitations and check that final outputs reflect the evidence collected.

Problems should travel upward early.

A field issue known on day three is operational information. The same issue discovered after project closure may be a data-quality problem.

A project should leave more than a completed deliverable. The route from the original question to the final evidence should remain clear and defensible.

MFRS connects research planning, field operations, quality control, data management and reporting so that decisions made at one stage remain visible and accountable at the next.

Planning a research, survey, monitoring or field assignment? Share the scope, geography and expected deliverables with our team.

Discuss an Assignment →
Scroll to Top