Published Updated

Reception asks an AI assistant how to admit a visitor. A revised visitor-access policy has been approved, but it takes effect next month. The earlier policy still applies today, and both documents are available to the policy team. Which one should support the answer?
The answer needs the policy that applies to the person's work and the date of the question. An approved future revision can support preparation for a change. An earlier revision can explain a past decision. Neither should quietly become today's instruction because the assistant found relevant wording in it.
| Staff question | Source to use | What the answer should make clear |
|---|---|---|
| What should I do today? | The published release currently applicable to the reader's role and location. | The current instruction, source revision and effective date. |
| What changes next month? | The approved future release, where it is available to that audience. | What is upcoming and when it takes effect, separately from today's rule. |
| What applied to an earlier visit? | The retained release applicable on the date being examined. | The historical date and revision, without presenting them as current guidance. |
| Why did the policy change? | The permitted change record and reviewed decision. | The recorded reason and its supporting source; restricted review notes stay protected. |
If the question leaves the relevant date or location unclear, ask for that context before presenting an operational instruction. A policy owner may need access to future and historical releases that ordinary staff do not need in their day-to-day answers.
The owner records the reviewed revision, audience, effective date and treatment of the earlier release.
The configured integration makes the appropriate releases available for current, upcoming or historical questions.
Review representative questions and source references before treating the changed answer experience as ready.
These are operating responsibilities to configure with the selected module. FormKiQ's KnowledgeBase documentation describes collection setup, ingestion, source references and access verification. It does not establish an automatic policy-release switch for every connected assistant.
AWS documents synchronisation after source changes, including a possible delay before newly synced information is available for questions. Agree how staff are directed to the governed policy or its owner while the assistant's update is still being verified. The unanswered-question guide follows that handoff through clarification, an assigned investigation and a verified result.
This illustrative extension of POL-1042 gives version 3 a December 1 effective date after approval on November 19. Version 2 remains the applicable release until the end of November. The dates and assistant rollout are example configuration choices.
Facilities confirms version 3's approved wording, effective date and reception/security audience. The policy file retains version 2 and the review that led to the replacement.
Authorised staff can ask what will change on December 1. The upcoming-policy experience identifies version 3 as future guidance, while questions about a visitor arriving today still use version 2.
The policy owner tests the same visitor question in current and upcoming contexts. Each answer identifies its source revision and when it applies. The owner opens the actual policy and checks whether the answer captures the relevant instruction and exceptions.
The operator checks that current questions use version 3 and that version 2 is excluded from that answer path. If the source update is incomplete, the application gives a clear unavailable result and directs staff to the approved policy or owner. It does not present an unverified earlier answer as current.
A later review asks what applied to a November visit. Permitted historical retrieval can still refer to version 2, with the visit date and superseded status clear. Its retained acknowledgement and decision history remain attached to that release.
Departments, business use cases and customer tenants may have different policy collections. Some documents within a site can also have narrower access. Agree which material each audience may use before it is supplied to the assistant. FormKiQ permissions do not automatically become the permissions of a separate retrieval service.
Show the source title, revision, effective date and an authorised route to inspect it. A source reference helps review; it does not prove the generated explanation is correct. A blocked source link also cannot undo information already disclosed in an answer.
When a policy is withdrawn or corrected, include the assistant's retained conversations and saved answers in the operating plan. Staff should be able to recognise a dated earlier answer and reach current guidance. The deletion and downstream-copy guide covers the separate task of removing material from connected systems.
Keep policy decisions and assistant source selection connected. Staff need to know what applies to their work now, what changes later and which earlier release explains the past. Verify those answers through the actual collection and retain a clear route to the governed source.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.