Home
In a survey, the goal is to identify certain characteristics of a large population, but it is almost never possible to do a complete census of the population. Instead, a sample or subset is drawn from the population to collect data on it. Then, results can be generalised, with an allowance for sampling error (usually within 5% at a 95% confidence level), to the entire population from which the sample was selected.
It is critical for understanding the views of affected populations, and how effective programmes are. However, oftentimes, country-level teams do not have technical expertise in sampling. The IFRC Community Sampling Tool supports the sampling design process of deployed personnel (or anyone who wishes to do sampling), by guiding users through a series of questions about their population and its parameters to recommend a sampling method and size.
The tool covers simple random, systematic random, time-location and cluster sampling methods, with plans to expand and improve in the future.
Github Commits
Team Meetings
Development Months
Have a look at our most prominent features below.
Integrate the tool's open API with your own application to further customise to your sampling needs. Call API and get your sampling approach on demand!
Follow the decision tree to learn the recommended sampling method for your project, and receive a sampling plan tailored to your specific population criteria.
Read MoreExport your sampling plan as a PDF report, which includes a record of inputs with a summary of decisions taken.
Browse terms and definitions to learn more about sampling, and find external resources to explore sampling further.
A Quick Review of what we do in these two terms through a 8-min video.
A second-year student at UCL.
He is the lead developer, and the lead client liaison.
A second-year student at UCL.
His role includes UI design and implementation and UI testing.
A second-year student at UCL.
His role includes backend development and testing.
A second-year student at UCL.
His role includes UI design and buiding the portfolio website.
The Gantt chart shows how we divided our workload and identified milestones.
Milestone for solidifying the requirements. This was the first key milestone as it allowed us to start thinking of the project in more concrete terms. For example, UI design, technology stack and overall implementation.
Milestone for setting our development environment and getting ready to start coding. Because non of us have done web development prior to this project, learning React, Django and how they interact was a significant milestone for us.
Milestone for finishing everything coding related. This was the most important milestone as it meant that we have finished implementing the necessary featues and fixed any bugs that became apparent during testing.
Milestone for client handover and submitting our project.