Use one record to keep the approved source, permitted fields, held field, reviewer, evidence location, stop condition, and recheck together. It prepares a review; it does not choose targets, qualify leads, approve outreach, or change a CRM record.
A preparer may collect approved references, format permitted fields, and flag a gap or conflict. Authorized sales, CRM, data, privacy, security, and compliance owners retain targeting, enrichment, contactability, consent, qualification, outreach, sending, routing, CRM changes, imports, bulk actions, exports, pricing, terms, and customer or prospect commitments.
The source, held field, owner route, evidence, communication boundary, and stop point stay easy to inspect.
Record the approved company or account source, its owner, the date checked, the written field list, and a safe evidence location. Do not paste lead or contact data, raw CRM or list exports, credentials, tokens, restricted screenshots, private attachments, or access details into this record.
State what the approved source shows, then flag a missing, conflicting, restricted, or proposed field. A preparer can format permitted fields and route a gap; they cannot infer, enrich, qualify, or change a record.
Name the sales owner and any CRM, privacy, security, data, or compliance reviewer. Default to no communication authority unless a written owner route says otherwise.
Record the stop condition, safe evidence reference, owner decision reference, permitted next preparation step, and a business-set recheck. Keep targeting, consent, outreach, routing, and customer commitments with authorized owners.
These fictional records show preparation only. On smaller screens, scroll the table sideways to read every field.
| Fictional record | Approved source | Held field or action | Owner route | Evidence and recheck |
|---|---|---|---|---|
| Fictional record LSR-014: public company-source row | A fictional sales owner links an approved public company page and a written field checklist. The preparer records only the permitted company name, public URL, stated industry tag, source date, and a missing-title flag. | Account fit, target-list inclusion, contactability, consent, enrichment, qualification, outreach, CRM changes, and any customer or prospect commitment are held for review. | A fictional sales owner reviews the prepared row. A CRM, privacy, security, data, or compliance owner handles a field, access, or source question; the preparer does not make the decision. | Safe source and checklist references, the owner decision reference, stop condition, and business-set recheck. |
| Fictional record LSR-029: conflicting role-source row | A written approved-source list conflicts with a public role reference for a fictional account. The preparer records the two references and holds the proposed field instead of guessing, enriching, or changing the list. | Targeting, role interpretation, contact selection, consent, sequence enrollment, message approval, sending, CRM update, routing, forecast, pricing, terms, and prospect commitment are held for review. | A fictional sales owner reviews the conflict. The named data or CRM owner decides a record question; a privacy, security, or compliance owner reviews matters in that area. | Safe reference links, the held-field note, owner decision reference, stop condition, and business-set recheck. |
Paste this into the business's approved system. Use safe references, not lead or contact data, raw CRM or list exports, credentials, tokens, restricted screenshots, private attachments, or access details.
LEAD-LIST SOURCE-REVIEW RECORD RECORD CONTROL Record owner: Safe company or account reference: Prepared by: Sales owner: CRM, data, privacy, security, compliance, or other reviewer, if needed: Review date: Status: [Draft / Under review / Held / Source confirmed by authorized owner / Rechecked / Superseded] APPROVED SOURCE AND PERMITTED FIELDS Approved source reference: Source owner and date checked: Written task boundary: Permitted fields: Observed source-linked fact or missing-field flag: Missing, conflicting, restricted, or proposed field: Safe evidence location: BOUNDARY CHECK Does this request decide targeting, account fit, enrichment, contactability, consent, qualification, outreach, messaging, send approval, routing, CRM field or record changes, imports, bulk actions, exports, pricing, terms, or a customer or prospect commitment? Held field, interpretation, or action: Named authorized owner and escalation reference: Communication authority: [None / Draft only under written rule / Authorized owner only] Stop condition: REVIEW AND RECHECK Authorized decision reference: Permitted next preparation step, if any: Recheck owner and date: Recheck outcome: This record prepares approved source references and permitted list fields for review. It does not choose targets, enrich a record, decide contactability or consent, qualify a lead, approve outreach or sending, route work, change a CRM record, run imports or bulk actions, export data, set pricing or terms, or make a customer or prospect commitment. Do not paste lead or contact data, raw CRM or list exports, credentials, tokens, restricted screenshots, private attachments, or access details here.
The full record stays visible and selectable. Nothing is uploaded or saved.
A preparer can collect approved references, state what they show, and flag a mismatch. The authorized owner decides what happens next.
Use the written escalation route when a request reaches consent, outreach, a proposed record change, export, pricing, terms, or a customer or prospect commitment.