Written by DROPS.ST.
Before a cannabis business changes a communication-choice form, identify what the wording changes and which actual process records the customer’s response. Review purpose, sender, channel and evidence separately from the appearance of the checkbox. A new sentence should not silently widen an earlier choice.
DROPS connects customer and order context with a common product catalogue, and its campaign delivery source checks applicable recorded preferences. Those controls help define what to inspect. They do not establish a native form-version archive, complete consent history or automatic synchronization with another provider.
Name the material change
Compare the current approved wording with the proposed version. Is it clarifying an existing purpose, adding another channel, naming a different sender or proposing a new use?
Record that difference before asking a designer or editor to apply it. A request to “tidy the form” can conceal a substantive change.
Keep required service or verification inputs distinct from optional promotion. Use the business’s actual qualified review rather than declaring every proposed field necessary.
Use a form-change release card
This original card belongs in the approved process; it is not a native DROPS publication or consent engine.
| Change entry | What to establish | Release question |
|---|---|---|
| Identified versions | Current and proposed wording/reference | What actually changed? |
| Purpose and scope | Sender, channel and represented use | Is the new meaning explicit? |
| Qualified review | Actual responsible reviewers and conditions | Which unresolved questions remain? |
| Evidence treatment | How the supported process identifies the applicable response | Can old and new scope be explained? |
| Existing choices | Actual prior evidence and proposed treatment | Is earlier scope being widened without review? |
| Interface and recording | Customer view and resulting supported record | Do they mean the same thing? |
| Release and copies | Publisher, effective use and independent forms | Which version is active where? |
A document date does not prove that a customer encountered that version. Ask what the actual evidence establishes.
Check the interface and the recording path
Use written cases or an agreed contained demonstration. Review a positive choice, a decline and an unresolved response. Inspect which setting or approved record reflects each case.
Check any default selection, hidden condition and difference between the visible explanation and stored result. Do not submit a live form merely to illustrate a test.
The CRTC’s toggling guidance addresses positive action when seeking express consent. Treat it as a requirement to examine the actual mechanism, not proof that every checkbox or other legal basis is valid. CRTC toggling guidance.
Hypothetical example: one channel becomes several
A fictional form’s approved wording covers a stated optional channel. A proposed revision adds broader contact wording.
The reviewer records the changed scope, checks how the supported process would preserve each response and obtains the appropriate decision before release. They do not rewrite old evidence as if every earlier customer saw the wider statement.
This example provides no approved consent text, universal re-consent procedure or native history guarantee.
Keep prior evidence and new authority distinct
Review whether a proposed change affects existing choices and which actual steps are required. Do not assume that updating a form retrospectively updates a customer’s agreement or another provider’s record.
CRTC guidance on consent requests and unsubscribe mechanisms identifies information and process considerations. The actual situation still needs review under applicable requirements. CRTC consent-request guidance.
Canadian cannabis content, privacy and provider/channel scope remain separate from the form wording. A valid choice does not authorize prohibited promotion or an unsupported route.
Give publishing a responsible owner
Name who approves, applies and verifies the change. Shop settings require an administrator, but that does not establish publishing rights in a separately managed form or website.
Catalogue editing also covers customer-account edits and wallet adjustments. Do not broaden access merely to make a form revision easier.
Use the operating-instruction guide for staff explanations around the released version. Use the information-flow map for actual recipients and copies.
DROPS gives the review customer-linked shop context and specific preference controls to assess. Explore DROPS.ST and the shop demos. Bring two fictional wording versions, identify the changed purpose and show what the actual recording process can demonstrate before release.