Run a weekly review of pipeline source evidence

Why this control matters

A useful pipeline source evidence routine starts with a written purpose. Keep each opportunity tied to a verifiable source, then compare the record with that purpose instead of judging the queue by activity alone.

What to check first

Begin with one concrete check: compare the source on the opportunity with the source on the original list. Keep the example that failed, because a named mismatch is stronger evidence than a general complaint about pipeline quality.

Build the routine

Build the pipeline source evidence review into a short weekly slot. Open the queue, apply the check, and write one decision for each item. Keep, correct, or close are all valid outcomes.

Use the specialist service role as a starting point for defining scope and evidence.

Handle the exceptions

Give exceptions their own line in the log. Watch for a record created from a forwarded introduction, and record why it escaped the normal rule. That detail shows whether the fix belongs in the data, the owner, or the review step.

Review the evidence

Keep the evidence small but dated. Store the source URL, date, and first contact beside the opportunity so a later reviewer can reconstruct what was known at the time.

Federal Trade Commission provides public guidance that can help your team test the workflow assumptions.

What to change next

End the review with one controlled change. Use the evidence to remove or correct one unsupported source each week, then set the next review date. If the change does not improve the evidence, reverse it instead of adding more fields.