First-scan intake checklist

First Scan Intake Checklist Before A Contractor Shares Lead Data

A contractor first scan intake checklist: what to send before a lead cleanup audit, what to hold back, and how redacted lead examples help decide whether the $197 scan is enough.

Plain-English boundary: AI Cleanup Doctor helps inspect follow-up handoffs and buyer-visible evidence. It provides cleanup findings and next-step clarity, not promises about rankings, indexing, AI citations, traffic, leads, revenue, booked jobs, refunds, vendor outcomes, or platform performance.

Short Answer

For a first AI Cleanup Doctor scan, send only enough lead management context to show the follow-up problem.

The safest starter set is:

your business website
the public lead source or page
one stuck follow-up point
one redacted example if it helps

Hold back:

passwords
private customer exports
full call recordings
customer lists
payment data
regulated records
broad CRM or inbox access

That is enough to decide whether the $197 AI Leak Scan is the right first step, whether the scope needs a fit check first, or whether the issue is too broad for a small scan.

This is not a promise that the scan will create leads, lower lead costs, recover jobs, improve rankings, produce AI citations, or make a vendor dispute conclusion. It is a safer way to start a lead cleanup audit without handing over more data than the first review needs.

Why A First Scan Should Not Start With Passwords

A lot of contractors think a lead cleanup audit means sending everything: CRM access, inbox exports, call recordings, ad accounts, customer lists, estimate files, and internal notes.

That is usually the wrong first move.

The first move should answer a smaller question:

Can the follow-up problem be understood from public context, a clear stuck point, and a redacted sample?

Often, yes.

For lead management, the first useful clues are usually plain:

the page or source where the lead starts
who should own the lead
when the first response should happen
whether a second touch exists
what the last meaningful note says
whether the current status is useful or vague

None of that requires a password on day one. A small, safe packet helps George see whether the scan is scoped correctly before the work gets bigger.

The V132 Intake Table: Send First, Hold For Later

The v132 Order page is built around a simple first-order intake decision table. Use the same table before you email materials.

Intake question	Send first	Hold for later
Where does the lead start?	Website URL, landing page, public form URL, Google Business Profile link, or lead source name	Ad account access, CRM access, inbox access, vendor login
What feels stuck?	One sentence explaining the follow-up problem	A full internal history of every lead
What example shows the issue?	One redacted screenshot, status row, or short sample	Customer list, raw export, full call recording, private job notes
What should happen next?	Your intended response rule or owner note	Private staff notes, payroll records, legal records, payment records
What decision do you need?	Whether to start with the $197 scan, request a fit check, or pause	A large workflow rebuild before scope is confirmed

This structure keeps the first review focused. It also protects the buyer from sending sensitive material before anyone knows whether the small scan is enough.

Safe Starter Materials

A good contractor first scan intake checklist should be small enough to send in one email.

1. Business Website

Send the public site first.

Useful pages include:

homepage
service page
location or service-area page
contact page
quote request page
booking page
paid traffic landing page
old estimate or follow-up page

The website shows the buyer path. It also shows whether the page explains what happens after someone calls, submits a form, books an appointment, or asks for an estimate.

2. Public Lead Source Or Page

Name the source you want checked.

Examples:

Google Business Profile calls
website form leads
paid lead vendor inquiries
Facebook messages
referral forms
quote request page
online booking calendar
old estimate follow-up list

If there are several sources, pick one for the first pass. A first scan works better when the question is narrow.

3. One Stuck Follow-Up Point

Write the problem in plain English.

Good examples:

"Website forms arrive, but nobody is sure who owns the first reply."
"Paid leads come in, but the owner cannot tell whether they got a second touch."
"Estimates go out, then the status stays vague."
"Booking requests arrive after hours and the handoff is unclear."
"Several lead sources are mixed together, so reporting does not show what happened after the lead arrived."

This sentence matters. It tells the scan what to inspect first.

4. One Redacted Example If It Helps

A redacted example is useful when a sentence is not enough.

Good examples:

a screenshot of a blank public form
a redacted lead row with name, phone, email, and address removed
a redacted CRM status sample
a lead source table with customer details removed
a short timeline with dates generalized
a screenshot of status labels without private notes

Before sending, remove:

names
phone numbers
email addresses
street addresses
payment details
account numbers
claim numbers
medical/legal/financial records
full recordings
private job notes

The point is not to hide the problem. The point is to show the pattern without exposing a customer.

Hold These Materials Until Scope Is Confirmed

Some materials might become relevant later, but they should not be sent before the first scope decision.

Material	Why to hold it
Passwords	The first review should not need account control.
Two-factor codes	These should never be sent by email.
CRM exports	A broad export usually contains more customer data than the first scan needs.
Full inbox exports	Too much private context, too early.
Full call recordings	A missed-call or callback issue can often start from counts, notes, or redacted summaries.
Customer lists	A first scan needs patterns, not a private list.
Payment data	Not needed for lead follow-up review.
Regulated records	Medical, legal, financial, and similar records need separate handling and are not first-scan material.
Admin access	Only discuss access after the problem and scope are clear.

If the scan cannot move forward without deeper access, that should be discussed separately. It should not be assumed at the start.

How This Helps Decide Whether The $197 Scan Is Enough

The $197 AI Leak Scan is meant to answer a narrow first question.

It is a good fit when the material can show one practical follow-up leak, such as:

a form-to-inbox handoff gap
a missed-call follow-up gap
an unclear owner field
a vague status note
a paid lead source that is hard to judge
an old estimate with no second touch
a service-area page with unclear routing
an AI follow-up idea that needs human review boundaries

It may not be enough when the issue is really a full workflow rebuild, a large CRM migration, a legal/privacy review, a pricing strategy decision, a sales training project, or a broad marketing attribution rebuild.

That is why the intake table matters. It helps George say one of three things before the scope gets messy:

Intake result	What it means
Start with the scan	The issue is narrow enough for a first review.
Request a fit check first	The issue might fit, but the material or scope needs clarification.
Pause or narrow the request	The question is too broad, too sensitive, or not a cleanup scan issue yet.

This is a trust step, not a performance promise. The scan can produce findings and next-step clarity. It is not a promise of rankings, leads, booked jobs, revenue, AI citations, refunds, or vendor outcomes.

Redacted Lead Example Template

Use this simple format if you want to send a redacted lead example cleanup for contractors.

Field	Safe example
Source	Website form, Google Business Profile, paid lead vendor, Facebook, referral
Service type	Roofing repair, HVAC estimate, plumbing emergency, remodeling quote
Date range	Last week, early July, Q2 sample, recent campaign period
Owner	Office, estimator, CSR, owner, sales rep, unassigned
First response	Same day, next morning, unknown, no note
Second touch	Yes, no, unclear
Last meaningful note	"Left voicemail," "sent estimate," "waiting on photos," "no owner note"
Current status	Open, booked, lost, wrong fit, duplicate, unknown
Redaction check	Names, phone, email, address, payment details, and private notes removed

You can send one row like this instead of an export.

That is usually enough to show whether the problem is source quality, routing, ownership, timing, status hygiene, or missing follow-up proof.

When To Ask For A Fit Check Before Paying

Ask for a fit check before paying if any of these are true:

you are not sure whether the issue is a scan, sprint, or something else
you think the first review might require private customer records
the problem spans several systems and no single stuck point is obvious
the question is about legal, medical, financial, or regulated records
the work may require admin access
the issue is really a pricing, refund, vendor dispute, or sales strategy question
you want to know whether the $197 scan is enough before ordering

The safer route is to email George with the website, public lead source, and one plain-English stuck point. Do not attach sensitive material just to ask whether the scan fits.

Start here:

Order page: https://cleanup.stoga.com/order
Buyer FAQ: https://cleanup.stoga.com/buyer-faq
First Scan Readiness: https://cleanup.stoga.com/first-scan-readiness
Sample reports: https://cleanup.stoga.com/sample-reports
Privacy policy: https://cleanup.stoga.com/privacy
Service terms: https://cleanup.stoga.com/service-terms

A Plain-English First Email

Here is a safe first email structure.

Subject: First scan fit check for lead follow-up cleanup

Hi George,

I want to check whether the $197 AI Leak Scan is the right first step.

Business name: Website: Public lead source or page: Follow-up problem to inspect: Redacted example optional:

I will not send passwords, private exports, payment data, or customer lists for the first review.

Thanks, [Name]

That is enough to start the conversation without over-sharing.

Final Check Before You Send

Before sending anything, ask yourself:

Can this be understood from public context first?
Did I remove customer names, phone numbers, emails, addresses, and payment details?
Am I sending one stuck point instead of a full system dump?
Did I avoid passwords, two-factor codes, exports, full recordings, and regulated records?
Am I asking for a scope decision before assuming bigger work?

If the answer is yes, the first scan request is in a safer shape.

If the answer is no, narrow the request first.

Lead management cleanup gets easier when the first packet is small, clear, and safe. Start with the public path, the stuck point, and a redacted example. Then decide whether the $197 scan is enough.

Sources Reviewed

Next step

Start with the public URL and the follow-up issue you want inspected: https://cleanup.stoga.com/order