Skip to content
BoKSA

Data Collection Plan

Data Collection Plan

Project phase: Business and Data Understanding

You write the roadmap for how your team will gather, access, and secure the data your project needs: which sources you'll use, critically evaluated for reliability, which variables and volume you need, and how you'll handle privacy, consent, and licensing. You name a fallback for every major risk you identify, such as a source becoming unavailable, so the plan is transparent enough that someone else could execute it and end up with the same data.

Starting Points

Key Points

  • The plan is a standalone markdown document, stored in the project's GitLab repository.
  • All data sources are clearly identified and critically evaluated for reliability (don't take everything at face value!).
  • The plan specifies the exact variables, volume, and timeframe of the data required.
  • Legal and ethical aspects (privacy, GDPR, consent, and licensing) are fully addressed.
  • A clear method for secure data storage and access control is described.
  • Every identified risk (e.g., unavailable sources) has a concrete fallback plan.
  • The plan is so clear and transparent that another person could execute the collection based on your instructions.