SimplBrain
When Approved Business Sources Conflict, Which Rule Should an Employee Assistant Use?
SimplSolutions Editorial Team · 8 min read
Published

The problem is not retrieval—it is authority
An employee asks, “Which leave rule applies to me?” The assistant finds two approved sources. One is a policy approved last month. The other is an older HR procedure that still appears in the company knowledge base and gives a different answer.
Both documents may be authentic. Both may have passed an approval process. That does not mean they are equally authoritative for this question.
The operational risk is not simply that the assistant retrieved the wrong passage. The deeper problem is that the organization has not given the assistant a reliable way to determine which source governs, whether the sources apply to the same population, or what to do when the conflict remains unresolved.
A responsible assistant needs a decision rule before it needs a more fluent answer.
What the NIST AI RMF contributes—and what it does not decide
The NIST AI Risk Management Framework is voluntary guidance for managing risks to individuals, organizations, and society associated with artificial intelligence. NIST says the framework is intended to improve an organization’s ability to incorporate trustworthiness considerations into the design, development, use, and evaluation of AI systems.
That makes the framework relevant to governed employee assistants. It supports treating answer quality, accountability, evaluation, and risk management as operating responsibilities rather than as purely technical search problems.
NIST does not provide a universal hierarchy for a company’s HR policies, operating procedures, contracts, or internal notices. The organization still has to define which source wins, who owns the decision, and when the assistant must stop. That local governance is the missing decision layer.
Start with a source authority hierarchy
A useful hierarchy should be written down, approved by the relevant business owners, and applied consistently. The exact order will differ by organization, but a starting point might distinguish among:
- Binding external requirements. Applicable law, regulation, collective bargaining terms, or contractual obligations should be handled through the organization’s legal and compliance controls.
- Enterprise policy. A formally approved policy generally establishes the organization-wide rule and its boundaries.
- Domain standards and procedures. HR, finance, security, or operations procedures explain how a policy is carried out within a defined process.
- Temporary, scoped instructions. A formally issued exception, emergency notice, or business-unit directive may override a normal process for a stated population and period.
- Explanatory material. FAQs, training slides, summaries, and manager guidance can clarify a rule, but should not silently replace it.
This is a governance pattern, not a claim that every organization should use this exact ranking. For example, a collective agreement or a formally approved exception may control a question that a general enterprise policy does not.
The important point is to separate authority from convenience. A source should not win because it is longer, easier to retrieve, more recently edited, or written in a confident tone.
Check four conditions before selecting a rule
1. Authority
Who approved the source, under which governance process, and with what authority? An undated team document should not silently overrule a controlled policy merely because it contains more operational detail.
2. Scope
Do the sources apply to the same employees, location, legal entity, employment type, process, or business event? Apparent conflicts often turn out to be scope differences.
“Employees may carry over five days” and “employees in the United Kingdom may carry over ten days” are not necessarily contradictory. The assistant must identify the population before presenting a rule.
3. Effective date and supersession
A publication date is not always an effective date. The record should distinguish when a source was created, when it became applicable, whether it expires, and which earlier source it replaces.
A newer document should not automatically win if it is a draft, applies only to a pilot group, or has a future effective date. Conversely, an older procedure should not remain authoritative simply because nobody archived it.
4. Specificity and exception status
A general policy and a narrow, approved exception may both be correct within their respective boundaries. The assistant should determine whether the more specific source is an authorized exception or merely an informal interpretation.
If these conditions cannot be established, the answer should become less specific—not more confident.
A worked example: the outdated procedure and the new policy
Suppose an HR knowledge owner identifies this conflict:
- The leave policy, approved by the enterprise HR governance group, takes effect on July 1 and says unused leave may be carried over under defined conditions.
- An older manager procedure, last reviewed before July 1, says unused leave expires at year-end.
- Neither record clearly states whether the procedure was superseded.
A weak assistant might select the newer-looking text, combine both rules into a vague answer, or quote the procedure because it contains a simple instruction.
A governed assistant should instead establish:
- which source has higher authority;
- whether the new policy explicitly supersedes the procedure;
- which employees and jurisdictions are covered;
- whether the employee’s leave year falls before or after the effective date;
- whether a local exception or employment agreement applies; and
- which HR owner is responsible for resolving the unresolved relationship.
If those facts are confirmed, the assistant can answer with the governing rule, the effective date, the relevant scope, and links or references that let the employee verify it.
If they are not confirmed, the assistant should say that the approved sources conflict, avoid giving a definitive entitlement answer, identify the two records and their dates, and direct the employee to the designated HR channel. That is not a failed interaction. It is a controlled refusal to invent certainty.
Record the conflict as an operational issue
A conflict should not disappear after one answer is generated. The knowledge owner should preserve a review record that is understandable to an auditor, policy owner, or future maintainer.
At minimum, record:
- the source identifiers and exact versions;
- the relevant conflicting passages;
- each source’s owner and approval status;
- publication, effective, review, and expiry dates where available;
- the affected population, geography, process, or system;
- the authority decision and its rationale;
- the person or group responsible for resolving the conflict;
- the date of escalation and target review date; and
- the resulting action, such as clarification, supersession, correction, or continued hold.
This record is more useful than a generic label such as “low confidence.” It tells the organization what is uncertain and what must happen next.
Define stop conditions before deployment
The assistant should have explicit stop conditions for unresolved conflicts. These should be based on business impact, not only on model confidence.
A stop or escalation is appropriate when:
- the sources have equal or unclear authority;
- the effective date or scope cannot be established;
- the answer could affect pay, benefits, employment status, safety, privacy, legal rights, or disciplinary action;
- a local rule may override a general rule;
- a source is marked draft, expired, withdrawn, or under review; or
- the assistant cannot show the employee which approved material supports the answer.
The response should explain the limitation without exposing unnecessary internal details. For example: “The approved HR policy and procedure do not currently agree on this point. I cannot determine which rule applies to your situation. Please contact HR through the employee support channel and reference [policy name] and [procedure name].”
The employee should not have to guess whether the assistant’s answer is a final rule, a summary, or a best-effort interpretation.
Preserve the employee’s ability to verify
A useful answer is not just a conclusion. It gives the employee enough context to check the result without turning the interaction into a document hunt.
For a resolved question, show:
- the governing source name and version;
- the effective date;
- the scope or eligibility condition that matters;
- a concise explanation of why another source does not control; and
- the appropriate owner or channel for exceptions.
For an unresolved question, show the existence of the conflict, avoid selecting a winner, and provide the approved escalation route. Do not present a synthesized rule that no accountable owner has approved.
This preserves an important boundary: an assistant can make governed information easier to use, but it should not become the organization’s unacknowledged policy-making authority.
What HR, operations, and knowledge owners should do next
Start with a conflict register for the business areas where wrong answers would matter most. Review a representative set of policy, procedure, FAQ, and temporary-instruction records. For each conflict, assign authority, scope, effective date, owner, and disposition.
Then turn the decisions into publishing requirements. Every controlled source should have enough metadata to answer basic governance questions: Who owns it? Who approved it? When does it apply? What does it replace? When should it be reviewed? Which population and geography does it cover?
Finally, test the assistant with deliberately conflicting sources. Evaluate not only whether it selects the intended rule, but also whether it stops when the decision cannot be justified, preserves the relevant evidence, and gives the employee a usable verification or escalation path.
For more practical guidance on governed business knowledge and employee-facing systems, visit the SimplSolutions blog. Where an organization is evaluating connected business systems, the SimplSolutions ecosystem perspective may provide relevant context.
The practical takeaway
When approved sources conflict, the right answer is not “use the newest document.” It is “apply the organization’s authority and scope rules, verify effective dates and supersession, record the conflict, and stop when the governing decision is not established.”
That framework protects employees from confident contradictions and gives policy owners a concrete way to improve the knowledge environment over time. A trustworthy assistant is not one that always answers. It is one that can distinguish a supported rule from an unresolved governance problem.



