Build a permission and withdrawal ledger
See this course’s project requirements
An unsent fictional two-message campaign with a permission/withdrawal ledger, preference segments, useful message copy, accessible action and opt-out QA, send-calendar holds and a privacy-aware delivered/unique-action review.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- Save four-record permission ledger and policy/jurisdiction boundary; include the original-case decision evidence and a separate changed-case result.
- Save segment rules and excluded reasons by ID; include the original-case decision evidence and a separate changed-case result.
- Save two original unsent messages with clear opt-out placeholder; include the original-case decision evidence and a separate changed-case result.
- Save paper QA findings and hold actual send-readiness claim; include the original-case decision evidence and a separate changed-case result.
- Save revised calendar and exclusions with no auto-send action; include the original-case decision evidence and a separate changed-case result.
- Save permission/segments/copy/QA/calendar/metrics campaign packet; include the original-case decision evidence and a separate changed-case result.
Review and revise
Use these criteria to check your work and choose what to improve.
- The final packet uses the supplied task-specific constraints and all six records agree.
- Every result can be traced to an identifier, input, calculation or stated decision rule.
- Changed-case practice updates dependent records and keeps holds or uncertainty visible.
- The packet states the learner role, authority boundary and specific next verification needed before real work.
Want more background?
The idea in everyday life
Original fictional workplace practice; paper or a local document is sufficient. The rules and records below are supplied for this exercise, not asserted universal workplace policy. Fictional Hazelwood studio unsent marketing plan. Exercise policy requires recorded express permission for chosen content; withdrawal holds are immediate. This is a stricter exercise/provider approach, not claim that U.S.CAN-SPAM requires universal prior opt-in; applicable jurisdiction/provider rules need review. H1 workshops permission Day1 active; H2 no permission; H3 workshops Day1 withdraw Day3; H4 product updates Day2 active.
Campaign eligibility requires a current permission record for the intended content plus no withdrawal; being a customer or having a public address is not permission under this exercise.
Build a permission and withdrawal ledger — worked practice
Campaign eligibility requires a current permission record for the intended content plus no withdrawal; being a customer or having a public address is not permission under this exercise.
Fictional Hazelwood studio unsent marketing plan. Exercise policy requires recorded express permission for chosen content; withdrawal holds are immediate. This is a stricter exercise/provider approach, not claim that U.S.CAN-SPAM requires universal prior opt-in; applicable jurisdiction/provider rules need review. H1 workshops permission Day1 active; H2 no permission; H3 workshops Day1 withdraw Day3; H4 product updates Day2 active. Use paper or a local document. Preserve the original case and make a separate changed-case record.
1. Step 1
Record content, permission date/evidence and current withdrawal state.
You should see: H1 workshops active; H2 none; H3 withdrawn; H4 products active.
Keep the stated identifier, unit and policy alongside this result so another reader can check it.
2. Step 2
Apply workshop campaign eligibility to specific content.
You should see: H1 eligible; H2/H3/H4 excluded for this workshop message.
Keep the stated identifier, unit and policy alongside this result so another reader can check it.
3. Step 3
Keep withdrawals visible without collecting real email addresses.
You should see: Synthetic IDs only; H3 suppression held.
Keep the stated identifier, unit and policy alongside this result so another reader can check it.
4. Step 4
Save four-record permission ledger and policy/jurisdiction boundary.
You should see: One workshop recipient; no actual emails, accounts or services.
Keep the stated identifier, unit and policy alongside this result so another reader can check it.
What to finish
Save four-record permission ledger and policy/jurisdiction boundary; include the original-case decision evidence and a separate changed-case result.
Watch for this
Using a public or customer address as consent or treating an old permission record as current after withdrawal.
How can I tell I understand it?
Using the supplied identifiers, I can save four-record permission ledger and policy/jurisdiction boundary. My changed-case record names the revised condition and explains which dependent decision it changes.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkTools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-10-01
Public agency or educational context; no source exercises are copied and no simulated threshold is presented as an official rule. Page title and relevant content inspected; no interactive controls or credential process tested.
Access: Readable official page retrieved with the web reader on 2026-10-01.
Reuse: All teaching cases, data, worked steps and questions are original. Link and limited paraphrase for context; no copied source exercises.
Source & access notes · checked 2026-10-01
Public agency or educational context; no source exercises are copied and no simulated threshold is presented as an official rule. Page title and relevant content inspected; no interactive controls or credential process tested.
Access: Readable official page retrieved with the web reader on 2026-10-01.
Reuse: All teaching cases, data, worked steps and questions are original. Link and limited paraphrase for context; no copied source exercises.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.