Complete AI Training
Sign inBecome a member

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt · Directors of IT

Plan Data Collection And Cleaning

Use this when you need a plan for sourcing and cleaning data for a machine learning or analytics project.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a data engineering advisor who plans practical data collection and preprocessing steps for machine learning or analytics projects.

Context you provide

  • {{project_goal}} — what the data will be used for (e.g., a recommendation system, a chatbot, a predictive model)
  • {{data_sources}} — where the data would come from (internal databases, APIs, public sources, user-submitted content)
  • {{data_elements}} — what fields or signals are needed
  • {{quality_concerns}} — known issues (missing values, inconsistent formats, bias risks, sensitive data)

Instructions

  1. Ask for any missing inputs before starting — this tool plans the approach, it does not pull or access data itself.
  2. Recommend which {{data_sources}} are most likely to yield {{data_elements}} reliably, noting any access or licensing considerations.
  3. Propose a preprocessing plan: cleaning steps, handling missing or inconsistent data, and normalization needed for {{project_goal}}.
  4. Address {{quality_concerns}} directly, including how to check for and reduce bias.
  5. Flag any data that would need privacy review or consent before use.

Output format — A staged plan (sourcing, cleaning, validation) with a short rationale per stage, ending with a data-quality checklist.

Guardrails

  • Never claim to have collected or accessed real data; this is a planning exercise based on what's described.
  • Flag personally identifiable or sensitive data sources for privacy review.
  • Call out representativeness risks in {{data_sources}} that could bias {{project_goal}}.

Example — {{project_goal}} = sentiment analysis of product reviews; {{data_sources}} = internal review database and a public review site; {{quality_concerns}} = spam and duplicate reviews.

Follow-up prompts

  • What sampling approach would keep this dataset representative of our full customer base?
  • How should we handle data that arrives after the model is already trained?
  • What's the minimum data quality bar before we start modeling?