← Folderly Launch AuditSAMPLE / NO CUSTOMER DATA

The deliverable, made concrete

Evidence. An owner.
A next action.

Each observed blocker connects to its evidence, the person who can change it, and the check that closes it.

Illustrative example only. The reserved example.com domains and results below are fictional teaching data. No scan, customer payment, remediation or successful delivery occurred.

01 / Scope

One sending path

From domain: newsletter.example.com. Direct marketing email through one ESP. Sender volume and exact provider are confirmed during intake.

Evidence: sanitized authentication results. No raw email, credentials or recipient information.

Example conclusion: authentication blocker observed. Overall inbox placement and reputation are outside this conclusion.

02 / Evidence register

Separate failure from missing evidence

CheckExample resultEvidence and implication
SPF authenticationPASSIllustrative receiver result: spf=pass smtp.mailfrom=bounce.esp.example. Authentication alone does not establish alignment.
SPF alignmentFAILbounce.esp.example does not align with newsletter.example.com.
DKIMFAILIllustrative dkim=fail. Reason and selector require more sanitized evidence; no DNS record is invented.
DMARCFAILIllustrative dmarc=fail header.from=newsletter.example.com. Neither aligned SPF nor aligned DKIM passes.
Unsubscribe requirementsUNKNOWNVolume and sanitized unsubscribe evidence are missing. Applicability and compliance remain unverified.

A real report adds a captured timestamp, source reference, sending path and observed value to each row. Missing evidence stays unknown.

03 / Operator handoff

Prioritized actions, not a generic score

  1. ESP operator: identify the selected signing domain and DKIM selector; supply sanitized authentication results.
  2. Authorized DNS owner: compare the published record with the verified provider instruction. Fix only demonstrated mismatches, preserving unrelated senders. The auditor does not change production DNS.
  3. ESP operator: verify successful aligned DKIM or configure the authorized aligned return path, then capture the next DMARC result.
  4. Agency lead: confirm volume and stream type; collect unsubscribe evidence where applicable.

Real reports list up to five blockers, each with owner, priority, evidence and recheck. Exact records require verified provider instructions and current setup.

04 / Acceptance & recheck

A clear end to the job

Review the report in one 45-minute handoff. After your operator acts, request the included verification within seven days of the report. The final record says resolved, still failing, or waiting on evidence/action.

Acceptance confirms the scoped evidence and action plan were delivered. It does not certify inbox placement, reputation recovery or every part of a launch.

Read the launch guides for the alignment comparison, provider requirements, and a reusable operator handoff worksheet.

Method reference: Google’s email sender requirements. Applicability depends on recipient service, message type and volume.

Prepare your scope request →