Preflight checks for lead assignment: 10 automated validations small teams should run before any marketing→sales handoff

Ten preflight validations (what to check, how to run it, fail action, priority

• Completeness — required fields present (name, email, phone, product interest).
• Low‑code: CRM list/filter or workflow enrollment criteria that only admits records where required properties are not empty; Zapier/Make step can reject if fields missing.
• On fail: put into a "quarantine / backfill" list, create a short task for data backfill or send a polite verification email.
• Priority: High — missing basics immediately wastes sales time.

• Consent / opt‑in — lawful marketing consent and subscription status.
• Low‑code: single canonical consent property; block enrollment in sales assignment if not true (workflow gate) or use a webhook to verify subscription status.
• On fail: suppress from outreach, route to consent backfill flow or manual verification queue.
• Priority: High in the UK/EU (GDPR) and for email deliverability.

• Duplicate risk — matching email, phone or company domain likely duplicate.
• Low‑code: CRM duplicate rules or a webhook call to a simple dedupe service; Zapier filter to detect existing email/company before forwarding.
• On fail: add to a merge/duplicate review queue and pause assignment until reviewed.
• Priority: High — duplicates lead to mixed messages and wasted calls.

• Ownership resolved — a clear owner, team or fallback queue assigned.
• Low‑code: workflow that sets owner by territory/team rules or assigns a default "unassigned" bucket if blank.
• On fail: place in an "unassigned leads" view and create a short SLA task to assign within X hours.
• Priority: Medium — prevents leads slipping between teams.

• Recent activity — evidence of engagement within a sensible window (form submit, reply, site visit).
• Low‑code: compare last activity timestamp property against threshold in a workflow or Make scenario.
• On fail: send lead into a short nurture stream or human review if sales should still contact.
• Priority: Medium — helps avoid handing stale leads to sales.

• Source sanity — source / campaign fields populated and match expected patterns (UTMs present or dropdown values).
• Low‑code: dropdowns for source with validation; a regex step in a webhook or Make to validate UTM format.
• On fail: quarantine to a "source cleanup" list and create a quick backfill task.
• Priority: Medium — important for attribution and correct routing.

• Score threshold — lead score meets minimum for sales contact.
• Low‑code: workflow gate on score property or a score check inside Zapier/Make before assignment.
• On fail: move to nurture track or flag for SDR review rather than direct assignment.
• Priority: Medium — reduces low‑value interruptions to sales.

• Company match (B2B) — company record exists and domain / company size roughly matches qualification.
• Low‑code: company lookup/association rule in CRM or a Make step to cross‑check domain to company; Marketo/Pardot users mirror with list segmentation.
• On fail: flag for account research, associate to "company verification" queue.
• Priority: Medium/Low depending on how much of your pipeline is true B2B.

• Do‑Not‑Automate / sensitive flag — VIP, legal, or manual‑only records.
• Low‑code: boolean property "do_not_automate" used as a workflow exclusion filter.
• On fail: always route to manual handling; never auto‑assign.
• Priority: Low for volume but critical for risk management.

• SLA / backstop checks — timers ensure assignment happens within target and escalate if not.
• Low‑code: SLA timer property with workflow escalation; if your integration supports it, a dead‑letter queue in Make or a scheduled list export can act as a backstop.
• On fail: escalate to manager, notify via Slack/email and change lead status to urgent.
• Priority: High for small teams where fast response matters to conversion.

Low‑code implementation patterns and platform examples

Use the same operational principles across platforms: gate -> quarantine -> human review. In practice that looks like lists and workflow gates in CRMs, or a Zapier/Make filter + webhook that returns a pass/fail.

HubSpot example: build active lists for each validation (e.g., "Missing email") and use workflow enrollment criteria to prevent assignment if any list applies; failed records can be routed to a HubSpot task and a quarantine pipeline stage. Salesforce example: use validation rules or Process Builder/Flow to check required fields and set a "quarantine" record type or queue; create a Case or Task for backfill.

If you use lightweight middleware (Zapier/Make) place validation steps early in the flow: filters for completeness and consent, a dedupe lookup call, then either continue to CRM assignment or POST the record to a "quarantine" webhook that writes to a sheet or queue. Marketo/Pardot implementations mirror this with smart lists and automation rules gating syncs.

Which three checks to add first, rollout steps and local notes

For most small South Coast teams (Fareham/Hampshire) the fastest impact comes from adding: 1) Completeness, 2) Consent, 3) Duplicate risk. These three stop the most obvious causes of wasted sales time and compliance risk.

A simple day‑one rollout:

• Create three CRM lists/views for missing fields, no consent and duplicate hits.
• Build three short workflows that gate assignment: if any condition is true, set lead stage to "quarantine" and create a task for a named owner to review within 4 business hours.
• Add a lightweight alert (email or Slack) for the quarantine queue and a short SOP: how to backfill, merge or grant consent.

Small teams can expand incrementally: add score gating and SLA timers next, then company match and source sanity. If you prefer hands‑on help with setup, workflow automation for small teams on the South Coast is a useful next step — Optira can assist as a practical, delivery‑focused helper to get these gates in place without overengineering.