Written by DROPS.ST.
Treat a proposed cannabis-shop launch date as a decision with dependencies, an authorized approver and a defined meaning. Decide what will actually be available on that date, check the remaining conditions and approve the wording before staff repeat it across channels.
DROPS gives the review concrete shop work to inspect: products, units, prices, stock and customer-linked orders share one catalogue and order system across the website and connected Telegram shop. Use those records to check the intended customer journey rather than making the date depend only on a finished-looking page.
The date record coordinates a business decision. It does not establish legal launch approval, a native publishing scheduler or guaranteed availability.
Define what the date refers to
A menu preview, an item becoming selectable and the start of an approved fulfilment service are different events. “Launch on Tuesday” leaves that distinction unresolved.
Write the intended event, products or service scope and customer-facing conditions. Identify the facts that must be established beforehand, including actual stock information, supported ordering steps and staff handling.
Keep product, licence, provider and jurisdiction requirements with their responsible reviewers. Software readiness does not settle them.
Use a date-release card
This original card belongs in the approved business process, not an assumed DROPS calendar.
| Release entry | What to establish | Publication decision |
|---|---|---|
| Event meaning | Exact customer activity the date describes | Avoid one date covering different milestones |
| Affected scope | Products, channels and permitted service | Define what the announcement covers |
| Readiness evidence | Agreed cases and observed results | Separate demonstrated from untested |
| Dependencies | Missing facts, external decisions or staffing | Name each condition and owner |
| Date status | Proposed, approved or under review | Do not present a target as settled |
| Approver and wording | Actual authority and accepted statement | Keep material conditions visible |
| Notices and recheck | Controlled copies, publishing owners and change trigger | Review stale or conflicting dates |
Record the decision date and next review point. A spreadsheet date does not release content or resolve a missing approval.
Test the work behind the announcement
Inspect an ordinary selection, quantity meaning and expected handoff using an agreed safe demonstration. Record unavailable tests as untested rather than counting a walkthrough as completed operation.
Use the checkout acceptance guide for evidence connecting customer choices with staff records. Include actual coverage for questions and exceptions; a supported workflow still needs someone available and authorized to handle it.
GOV.UK’s live-phase guidance connects service readiness with tested user needs and sustainable support. Apply that planning principle without importing its government assessment process into a cannabis shop. GOV.UK live-phase guidance.
Review the public wording separately
Keep an internal target distinct from the approved public statement. A dependency may make a date conditional, or may mean it should remain unpublished until resolved.
Review the actual audience, content and channel. Health Canada’s cannabis-promotion guidance addresses communications in their context; completing a readiness card does not determine whether an announcement is permitted. Health Canada promotion guidance.
Do not borrow another province’s operating model or a vendor’s example as launch authorization.
Hypothetical example: the page is ready, the handoff is not
A fictional team proposes Tuesday as its launch date. The product pages display correctly, but an essential staff-handoff case has not been demonstrated.
The approver records the gap and holds the public-date decision while the responsible owner resolves it. After the scoped case is checked, the team reviews the intended date and wording again rather than treating the earlier target as automatically approved.
This example provides no actual launch timetable, legal permission or zero-downtime assurance.
Keep the approved date identifiable
Give each controlled notice an owner. Check the website, relevant connected Telegram presentation and independent copies your team uses. A shared catalogue does not update every message or external asset.
When a material dependency changes, reopen the date decision and identify the affected wording. Use the service-answer register for current operating explanations.
Preparing the notice and applying shop edits need separate authority. Catalogue editing also permits customer-account and wallet changes; it is not a date-only publishing role.
Choose DROPS when the launch discussion should follow identifiable products and customer-linked order work. Explore DROPS.ST and the shop demos with one proposed event, then decide which evidence supports its date and who may release the final wording.