A controlled CRM duplicate-cleanup plan for a Philippines admin team

The route-local operating guide

Start with the business outcome, not a generic job description. For this CRM data hygiene lane, delegated work is to find candidate duplicates, compare approved match fields, prepare a survivor, document conflicts, and route merge approval. Write the expected result and what must remain unchanged. A narrow scope makes training, review, and escalation practical; it also stops a growing queue from quietly becoming broader authority.

Create one controlled intake record. Capture record IDs, dates, verified contacts, relationships, consent flags, opportunities, owners, source systems, and merge rules. Link to approved systems instead of copying restricted material into chat, personal notes, or unmanaged sheets. Mark unknown, conflicting, and not-applicable values differently so a blank never becomes an invented fact. Record the source, cutoff, and time zone.

Define ready before work begins. An item must be in scope, attributable to a permitted source, assigned to a named worker, and paired with a verification method. Reject duplicates and keep incomplete requests visible. Do not restart difficult work in a cleaner record that loses history.

Preparation and authority are different. The specialist may gather evidence, apply explicit rules, prepare the next action, and route exceptions. Consequential interpretation and approval remain with the CRM, privacy, or revenue owner. Urgency, familiarity, seniority, or approval on another item does not silently expand authority.

Place an item on hold when identifiers conflict, active work has different owners, consent states differ, or an integration may recreate the record. A useful hold states observed facts, safe work that may continue, the exact decision needed, its owner, and next review time. Include the item and its age in normal reporting; an exception queue must not become a hidden backlog.

Consider a practical case. Two contacts share a surname and switchboard but have different names and emails. The specialist keeps both intact because similarity is not identity. This control is not ceremonial. It prevents a plausible shortcut from changing money, access, customer expectations, legal position, or sensitive records before an accountable owner sees the evidence.

Privacy and security belong in the default path. Use individual accounts, minimum necessary access, approved storage, and tested removal. Keep passwords, full identity documents, payment details, health information, privileged material, and irrelevant personal data out of the work record. Escalate unexpected sensitive content.

Review quality against a defined population and cutoff. Check source identity, required fields, rule version, boundary compliance, destination state, and communication. Record the precise defect and affected item. Counts need denominators; a risk-weighted sample is not a score for work that was never inspected.

Completion means you reopen the survivor, confirm history and restrictions, check integrations, and sample completed merges. A sent message, saved form, changed label, or checked box is an event, not proof of the result. Record who verified the destination, when, and with what limitation. If verification is unavailable, keep the item open with a named recovery action.

After the first week, review missing inputs, unclear rules, permission mismatches, reopened work, and ownerless decisions. Improve the intake field, example, access rule, or review cadence that caused repeated friction. Expand the lane only when routine work is reproducible and exceptions stay visible.

Use FTC business data-security guidance as an authoritative starting point for the control it supports. Record the relevant proposition and retrieval date. Apply it through current company policy, contracts, jurisdictions, and qualified advice; a public source does not grant the specialist extra authority.

Define intake and authority

For CRM data hygiene, write the eligible population, source systems, cutoff, expected output, and reviewer before assigning live work.

Use safe examples of ready, blocked, and out-of-scope cases. Explain the reason for each status.

Keep exceptions accountable

When identifiers conflict, active work has different owners, consent states differ, or an integration may recreate the record, preserve the evidence and route the smallest clear decision request.

Name safe completed steps, unresolved risk, owner, and next review time in every handoff.

Verify before closeout

Close only after you reopen the survivor, confirm history and restrictions, check integrations, and sample completed merges.

Report the eligible population, period, failures, reopened items, and limitations so managers can improve the lane without overstating results.