Written by DROPS.ST.
When owners give staff contradictory instructions, identify the unresolved decision and the actual authority needed to settle it. Keep proposals separate from the approved operating instruction. Staff should not have to infer company policy from the latest message or whichever owner can edit a setting.
DROPS connects products, Customer Accounts and orders in one shop. For a cannabis business, that gives the discussion a concrete scope: which records, customer choices or staff actions would the proposal affect? Use that common context to explain the change before an authorized decision is released.
Record the disagreement as a decision question
Write a neutral question such as whether a proposed pricing rule should take effect. Preserve each proposal and its reasons without labeling a person as the problem.
Identify what is already approved, what remains uncertain and who needs to provide evidence. Two people may be answering different questions: one concerns the desired policy, another its timing or effect on existing commitments.
Do not invent a voting, veto or tie-breaking rule. Use the business’s actual agreements, authority and applicable obligations. If those are unclear, seek the appropriate review rather than treating software access as the answer.
Keep an owner-decision record
This original record is owner-managed, not a native DROPS governance tool.
| Record field | What to establish | Release check |
|---|---|---|
| Decision question | Exact policy or action in dispute | Everyone is addressing the same issue |
| Competing proposals | Options and stated reasons | Neither is presented as already approved |
| Affected scope | Products, records, staff and commitments involved | Consequences are visible |
| Evidence needed | Facts still missing and responsible people | Assumptions are not disguised as findings |
| Decision authority | Actual authorized process and responsible owner | Approval is attributable and sufficient |
| Interim instruction | What staff may rely on while unresolved | No contradictory temporary directions |
| Agreed release | Accepted outcome, scope and effective use | Staff receive one identifiable instruction |
Record unresolved authority as unresolved. Naming a coordinator helps move the discussion; it does not create legal power to decide it.
Give staff a clear interim position
Obtain an interim instruction through the actual authorized process. State what it covers, which decisions remain pending and where staff should escalate an exception.
Do not quietly apply one proposal to settle the disagreement in practice. Equally, do not assume this worksheet creates an automatic software freeze. Any actual operational hold or setting change needs its own permitted procedure and authority.
Keep the interim position easy to identify. A long discussion thread may explain the debate but still leave staff unable to tell what applies today.
Hypothetical example: a proposed pricing policy
One owner wants a new pricing policy to start immediately. Another wants its effect on existing commitments reviewed first.
The coordinator records the proposed rule, timing question and affected scope. The authorized decision process determines the interim instruction and obtains the missing information. Once settled, the accepted outcome states which circumstances it covers and when staff should use it.
The example supplies no actual price, corporate voting rule or legal approval. It shows how the unresolved proposal stays distinct from the released instruction.
Separate approval from the person applying it
DROPS shop settings require an administrator, and order actions have separate controls. Those access facts do not establish who may approve a business policy.
Catalogue editing also includes customer-account edits and wallet adjustments. Do not grant broad access simply to give an owner’s proposal priority or to let a staff member reconcile the dispute.
Name who applies the authorized change, who checks it and who communicates the instruction. Use the staff permissions guide to examine the actual grant separately from business approval.
Release the agreed instruction once
After the decision, identify the approved version and replace contradictory operational wording within the reviewed scope. Ask affected staff to confirm they understand the change and its exceptions.
The operating-instruction guide helps keep the released version and superseded copies clear. Preserve necessary decision evidence in the approved process without promising immutable native history.
If new facts reopen the issue, identify a new review rather than letting conflicting informal directions accumulate.
DROPS gives the owners and staff common shop records to inspect. Pair that context with attributable authority and one agreed release so daily work follows a clear decision.
Explore DROPS.ST and the shop demos. Rehearse a fictional disputed change, identify its affected records and show how staff would distinguish a proposal from an approved instruction.