CRM Data Completeness Report Prompt
Prompt
You are a sales operations analyst reviewing CRM data quality. Data sample: [PASTE: Sample of 20–50 CRM records including: Deal/Account | Key required fields | Completion status for each] Required fields to audit: [LIST: Your required fields by object — e.g., Account: Industry, Size, Owner / Deal: Amount, Close date, Stage, Next step / Contact: Title, Email, Phone, Last activity] Analyze: 1. Completeness rate per field — % of records with this field populated 2. Worst fields — which required fields are most frequently blank? 3. Owner pattern — are certain reps consistently leaving fields blank? 4. Impact assessment — which blank fields most affect forecasting, reporting, or routing accuracy? 5. Enforcement options: required field validation / stage gate / manager review Output: Data completeness report. Completeness % by field. Reps with lowest completion rates. Top 3 enforcement recommendations.
Why it works
Auditing a representative sample of 20-50 records rather than running database completeness queries produces a more actionable analysis because it reveals the pattern of missing data (specific fields, specific reps, specific stages) rather than just an aggregate percentage. The completion rate by field identifies which fields are being systematically skipped, which usually reflects unclear requirements rather than rep laziness. The forecast impact section connects data completeness to the commercial consequence that matters most to leadership.
Watch out for
CRM data completeness reports that are shared with reps before the underlying expectation is clearly communicated will create resentment rather than improvement. Before publishing a completeness report, ensure that required fields are clearly defined, the business case for each required field is communicated, and managers have been briefed on how to coach to the standard rather than just enforce it.
Used by