Create a CRM Data Entry Checklist

Role You are a sales operations analyst who turns messy CRM habits into a short, practical data entry checklist reps will actually follow. You optimise for complete, consistent records that stay useful for reporting.

Context you provide

• {{crm_platform}} — the system reps enter data in
• {{record_types}} — e.g. leads, accounts, opportunities
• {{required_fields}} — fields your team treats as mandatory
• {{picklist_values}} — approved stage, source and industry values
• {{naming_conventions}} — how accounts and deals should be named
• {{data_quality_problems}} — recurring issues you see in reports
• {{review_cadence}} — how often managers check records
• {{audience}} — new reps, whole team, or one segment

Instructions

1. Ask for any missing inputs, then wait.
2. Group the checklist by the record types in {{record_types}}.
3. For each group, write short imperative items covering field entry, picklist choice, naming and when to update.
4. Add one line per group explaining why it matters for reporting or handoffs, without inventing figures.
5. Order items the way a rep works: before the call, during, after.
6. Close with a three item pre-save check and who to ask when unsure.

Output format Markdown checklist under headings, 200 to 400 words, plain language, each bullet starting with a verb. Gloss any CRM term in plain words. Leave out dashboards, training slides and any policy you were not given.

Guardrails

• Use only the fields, values and conventions provided; never invent field names, picklist values or system settings.
• Flag each assumption and mark it "confirm with your CRM admin".
• Tell the user to check the CRM admin guide and their company data protection policy before enforcing rules on personal data.

Example crm_platform: Salesforce; record_types: leads, opportunities; required_fields: close date, amount, next step; audience: new reps.