Label AI Recommendations Separately From Business Rules
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
An assistant tells a sales representative that calling the customer is mandatory before sending a proposal. A call might help, but unless an applicable instruction requires it, the assistant has turned advice into an obligation. The reverse error is equally important: suggesting that the representative might obtain approval can make a documented requirement sound optional.
The practical fix is to classify each statement before choosing its wording. Separate supported facts, authoritative rules, recommendations, and optional preferences. Where authority is unresolved, preserve that uncertainty instead of inventing permission or a new restriction.
This article uses a fictional proposal review to show how. The filled annotation table is reusable: replace its evidence and statements when reviewing another answer. The goal is not more cautious language everywhere. It is language whose force matches its evidence.
1. Separate authority from confidence
An assistant can be confident that an action would help without having evidence that anyone requires it. Conversely, an awkward or inconvenient requirement does not become optional because the assistant prefers another approach.
Use four basic statement types:
- Fact: A supported observation about a record, document, event, or state. State the limits of what was inspected.
- Rule: A requirement established by an identified authority, with conditions that make it applicable.
- Recommendation: A suggested action supported by a reason or trade-off, not presented as compulsory.
- Preference: An optional choice attributed to a person or team, with evidence that it is optional.
Not every instruction fits neatly into those categories. A manager's request for a particular format could be a task-specific instruction rather than standing policy. If its force is unclear, report who requested it without deciding that it is either mandatory policy or a preference.
Unknown is an evidence status, not a source of authority. An unresolved instruction should remain unresolved until someone with the relevant responsibility clarifies it.
2. Establish what supports mandatory wording
Before writing that someone must act, cannot proceed, or may skip a step, check the basis for that claim. Permission language deserves the same scrutiny as prohibitions.
- Authority: Which document or responsible owner establishes the instruction?
- Scope: Which team, transaction, threshold, or exception makes it applicable?
- Status: What establishes that the instruction is current, superseded, incomplete, or disputed?
- Timing: At what stage does the requirement apply?
A recent file date alone does not establish authority. Look for evidence such as a maintained policy register, an effective date, or confirmation from the responsible owner. These are evidence sources to seek, not controls assumed to exist in any product.
Timing can change the meaning substantially. Approval before sending does not necessarily mean approval before drafting. Likewise, a discount threshold above 10% is not the same as a threshold of 10% or more. Preserve the actual condition rather than replacing it with a convenient approximation.
When evidence is missing, describe the gap. An inability to verify a requirement is not evidence that no requirement exists.
3. Use a filled answer-annotation table
Fictional worked example: All documents, people, dates, thresholds, records, and operating details in this example are hypothetical. They are not Alactic policies or customer results.
A representative asks whether a discounted proposal is ready to send. The hypothetical evidence bundle contains:
- Proposal Policy, version 3: Requires manager approval before sending proposals with discounts above 10%.
- Policy register: Lists version 3 as active, effective 1 April 2026, owned by Sales Operations. A hypothetical owner confirmation dated 6 April verifies that status.
- Proposal record: Shows a 12% discount and an unresolved scope question. No approval appears in the material available to the assistant.
- Team lead's note: Explicitly identifies a one-page summary as preferred, not required.
- Older onboarding guide: Mentions director review for discounted proposals. Its continuing applicability has not been confirmed.
The active policy and owner confirmation establish the manager-approval requirement. Neither addresses director review or says whether the onboarding instruction is superseded. The assistant therefore has evidence for one requirement and an unresolved question about an additional one.
The table below is the reusable artifact. Its six rows show how evidence changes the appropriate wording. On narrow screens, scroll the table horizontally.
| Statement type | Supporting evidence | Misleading wording | Corrected phrasing |
|---|---|---|---|
| Fact | The proposal record lists a 12% discount. | This proposal has an excessive discount. | The proposal records a 12% discount. |
| Company rule | The active policy requires manager approval before sending proposals above a 10% discount. The register and policy owner confirm its current status. | You may want to get approval. | The current proposal policy requires manager approval before this proposal is sent because its recorded discount is 12%. |
| Fact with limited visibility | No approval appears in the available proposal record. | Your manager has not approved it. | I found no approval recorded in the proposal record available to me. |
| Recommendation | The scope question remains unresolved; a call is one possible way to clarify it. | You must call the customer first. | I recommend a customer call to clarify scope. I have not established a company requirement to call. |
| Preference | The team lead explicitly describes a one-page summary as optional. | Company policy requires a one-page summary. | The team lead prefers a one-page summary, but the note says it is not required. |
| Possible additional instruction; applicability unknown | The older guide mentions director review. The active policy and owner confirmation do not address that instruction. | Director review is optional. | The older guide mentions director review. I cannot verify whether it remains an additional requirement; ask the policy owner to clarify. |
For another review, retain the columns and replace the rows. If a sentence mixes several types, split it first. A factual observation followed by an unsupported command should not receive one reassuring label for the whole sentence.
4. Rebuild the answer around the decision
The representative needs to understand what prevents a readiness decision, not merely receive a list of categories. Put the applicable requirement first, then the available record, unresolved instruction, and optional advice.
For the same fictional example, the rewritten answer could read:
Manager approval is required before sending. The active proposal policy requires it for discounts above 10%, and this proposal records a 12% discount. The policy register and Sales Operations confirmation establish that this policy is current.
I cannot confirm readiness from the available evidence. I found no approval in the proposal record available to me. If approval was given elsewhere, identify that evidence rather than treating this record's omission as proof that approval never happened.
Director review remains unresolved. An older onboarding guide mentions it. The current policy's status is verified, but neither that policy nor the owner confirmation addresses whether director review is an additional requirement. Ask Sales Operations to clarify this before treating the review requirements as settled.
My recommendation: Clarify the unresolved scope with the customer; a short call is one option. I have not established that a call is mandatory.
Optional format: The team lead prefers a one-page summary, but explicitly says it is not required.
This answer does not certify the proposal as ready or claim authority to release it. It identifies what the evidence establishes and what the representative still needs to resolve. In a shorter answer, the labels can become ordinary prose, provided the distinctions remain visible.
5. Resolve conflicts without creating a new rule
The apparent conflict in this example has two separate questions: is manager approval required, and is director review required as well? Evidence answering the first does not automatically answer the second.
A useful clarification request to the hypothetical policy owner would be:
Proposal Policy version 3 is confirmed active and requires manager approval before sending proposals above a 10% discount. The older onboarding guide also mentions director review. Does that instruction still apply in addition to manager approval, or has it been superseded? Please identify the controlling document and relevant scope.
This asks for a resolution without suggesting that either interpretation is already established. Do not silently choose the stricter instruction, assume the newest-looking file overrides everything, or combine the documents into a newly invented approval chain.
Once clarification arrives, update only the affected conclusion. If the owner confirms that director review remains applicable, add it with its stated conditions. If the owner confirms that it was superseded, record that basis. If the response remains ambiguous, preserve the unresolved status.
The same discipline applies to missing transaction details. If a rule depends on proposal type, obtain that classification rather than guessing. These checks concern how an answer conveys authority; they do not establish system permissions or authorise execution.
6. Catch authority hidden in ordinary language
Commands are not the only source of confusion. Review phrases that quietly imply a universal process, permission, or completion:
- The correct process: Name the documented process, or describe the approach as a recommendation.
- We always: Repeated behavior does not by itself establish a standing requirement.
- You can skip: Missing evidence of a requirement does not establish permission to omit the step.
- Best practice requires: Separate the reason for the advice from any actual obligation.
- Approved means ready: Identify what was approved and what remains unchecked.
An external requirement also needs attribution. For example, the WhatsApp Business Messaging Policy is the relevant authority for its messaging requirements, not an assistant's preferred workflow. If an answer discusses a template, approval must not be described as a guarantee of delivery. A suggested internal review can remain advice without borrowing the platform's authority. Check the current official policy for precise requirements.
7. Correct the specific authority error
If the reader has already received misleading wording, correcting the underlying document alone is insufficient. Identify the affected statement and explain how its authority changes.
For the fictional proposal example, a correction could say:
I previously described a customer call as mandatory. I did not have evidence of a company requirement for that call. It is my recommendation for clarifying scope. The separate manager-approval requirement before sending still applies, and the director-review instruction remains unresolved.
For the reverse error, explicitly restore the requirement: explain that the earlier wording made a mandatory step sound optional, then identify its source and applicable conditions.
Keep the original statement, correction, supporting evidence, and unresolved questions together in the review record. If someone may already have acted, direct the business question to the responsible owner rather than inventing a remedy. A language correction does not establish whether a completed action can be reversed.
8. Check whether the revised answer works
Use a bounded review rather than counting how often the assistant says must. In a hypothetical pilot, reviewers could annotate 10 answers containing instructions or advice using the table's four columns.
- Split each answer into statements and identify its decision context.
- Record the evidence supporting each statement's type and force.
- Flag unsupported obligations, softened requirements, unverified preferences, and claims that exceed available visibility.
- Rewrite the flagged statements without weakening supported requirements.
- Ask another reader to identify what is required, recommended, optional, and unresolved.
Track those error types separately. Fewer mandatory phrases could indicate improvement, or simply show that real requirements have been weakened. Reviewer disagreement is useful evidence: it can reveal ambiguous wording, missing scope, or unsettled documentation.
The observable outcome is whether a reader can identify both the source and force of each consequential instruction. When they cannot, the annotation table points to a specific repair rather than a general request to make the assistant sound less confident.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications