Tracking product preference notes for promise creep in cannabis retail

Question and scope

This study asks whether a dispensary can detect promise creep in patient product preference notes before the note becomes an implicit commitment. The unit is one active preference note attached to one patient profile. The review examines the note's purpose, audience, product reference, expiry, and language. It does not evaluate the patient's clinical needs or the accuracy of a product recommendation.

Set the scope to one store, one patient-record system, and a fixed period. Record the note fields, the roles that can view or edit them, and the store's reservation policy. If the store changes its note template or its product menu during the window, separate the periods. A new field can change the type of promise the note is able to create.

What the sources establish

The Virginia Cannabis Control Authority provides the regulatory context for licensed retail and patient records. The Federal Trade Commission's guidance on advertising and marketing supports accurate claims and clear terms. NIST privacy guidance is relevant to limiting the patient information stored in a preference note. None of these sources defines a preference-note standard or measures promise creep in a dispensary.

The store therefore needs local evidence for its own note practice. Public sources can explain why a note should avoid unsupported product claims and unnecessary patient detail. They cannot show whether a specific note led a patient to expect a product that was not available. The study should define the language it counts as a promise and preserve the note's context.

Definitions and measures

Define a preference note as a free-text or structured record describing a patient's product, format, or service preference. Define promise creep as language that implies availability, reservation, clinical suitability, or a guaranteed outcome beyond what the store has approved. Define audience as the roles allowed to see the note. Define expiry as the date the note should be reviewed or removed.

Measure the number of notes, the number with a stated purpose, the number with an audience field, the number with a product link, the number with an expiry, and the number containing promise language. Report the promise types separately, such as availability, effect, or access. A single flag count hides whether the problem is product stock or clinical language. Report the count and the audience for each promise type.

Sampling and collection

Sample active preference notes rather than patients, then review the note, the patient's authorization, and the product record. Include notes created at the counter, by phone, and through an online account. Stratify by note author role and by product category. Record the sampling rule and the observation window. If the queue is small, review every active note and report the count as a case series.

Collect the note text, the note fields, the product reference, the patient's consent or authorization, and the audit trail. Mask patient identifiers in the analysis table and keep the raw note in the approved system. If the note is stored in a general task tool, record that as an access exception. A note outside the patient record is difficult to review and easier to misuse.

Analysis and reporting

Report the number of notes, the number with a purpose, the number with an audience field, the number with an expiry, and the number with a product link. Show the count of promise-language exceptions by type. Report the number of notes visible to roles that do not need them. A completeness score without the access result does not show the privacy risk.

Inspect the exceptions for patterns. A cluster of availability promises may point to a stock-alert process that staff do not trust. A cluster of effect claims may point to training or script problems. Group the findings and choose one change, such as a required note purpose or a ban on free-text availability language. Do not rank staff by the number of notes they wrote.

Limits and sources of error

The study cannot prove that a patient relied on a note or that a product produced a particular effect. It can show whether the note contained language the store had not approved and whether the audience was appropriate. A note may also be accurate at the time it was written and become stale after a menu change. Report the date and the product context.

The note system may not distinguish a preference from a clinical observation, and the reviewer may interpret a phrase differently from the author. Use a short codebook with examples and test agreement on a small sample. A note that was deleted before the review cannot be assessed. Report the missing evidence rather than assuming the note was harmless. Report the number of notes that could not be assessed.

Review and next action

Choose one change: require a note purpose, add an expiry, restrict the audience, or replace free-text availability language with a link to the approved stock process. Assign the owner and the next sample date. Repeat the review with the same definitions. Keep the change small enough to test in one patient queue. Write the change into the note template so it survives a busy shift.

Close the review when the store accepts the result and schedules the next check. Report the remaining uncertainty beside the note counts. The product preference routine describes the counter practice this review measures. Use the result to improve the note, not to judge the patient's product choice. Schedule the next check and name the person who will run it on the next sample.

Sources

The sources below support the regulatory, privacy, and recordkeeping context for this review. They do not measure this dispensary, and no source is presented as a local benchmark. Each link should be checked for its date and scope before reuse. The operational finding comes only from the store records described in the method. Keep the cited page with the case file until the review closes.

• Virginia Cannabis Control Authority
• Federal Trade Commission, Advertising and Marketing
• NIST Privacy Framework
• GAO, Assessing Data Reliability

This article describes a measurement method rather than legal, medical, or compliance advice. Confirm current requirements with the applicable authority and qualified advisers. Keep the local evidence separate from those requirements. Record the review date and the owner who accepted the interpretation. Store the signed scope note with the review file, and give the owner a copy before the next sample begins.