Draft policies should not silently become company rules because they are searchable. Preserve publication status and approved authority so the assistant distinguishes proposed guidance from the policy users may rely on.
Draft status is a governance boundary
A draft document contains content not yet approved for its intended audience or purpose. It may still be useful to authorised reviewers, but it should not automatically support definitive operational answers.
For a proposed ingestion contract, include trusted publication status, owner, effective version, audience, and supersession relationship. Keep filename wording separate from that state. A title containing final or approved is not sufficient evidence of publication.
The content owner decides meaning and release authority. The technical pipeline enforces the resulting eligibility rules and records the version supplied to each answer.
Test a fictional benefits-policy draft
An employee asks whether a new benefit is available. The index contains an approved current policy and a draft proposing expansion. The assistant should answer from the approved applicable source and not present the proposal as an existing entitlement.
An authorised reviewer may ask to compare the draft with the current policy. That is a different task and audience. The output should clearly label proposed versus approved differences rather than hide the draft entirely from every user.
| Document state | Retrieval and answer behaviour |
|---|---|
| Current approved policy | Eligible under audience and scope |
| Draft for review | Restricted to the approved review task |
| Superseded policy | Historical use only under defined rules |
| Status missing | Explicit safe disposition |
| Draft renamed final | No inferred publication transition |
Replay a publication event, withdrawal, and delayed old draft import. The active answer path should follow trusted current status, not arrival order or filename.
Handle approval transitions deliberately
Publishing can require metadata, content, and permission changes to reach the index together. Test the activation boundary and any stale caches. A new approved version should not coexist with an unlabeled earlier draft as equally authoritative evidence.
Status management adds governance work, but it prevents search relevance from deciding company policy. Start with consequential collections and a clear owner. Preserve access for legitimate drafting work without broadening the customer or employee answer scope accidentally.
This publication design is proposed. The voice integration case study describes related knowledge work without claiming this policy lifecycle. Pair it with cross-system version conflicts.
Draft-policy FAQ
Does a filename saying final establish approval?
No. Use the trusted publication and authority record.
Should all drafts be deleted from search?
Not necessarily. Authorised review can be a supported separate scope.
What should be tested after publication?
Verify status, audience, current version, superseded copies, context assembly, previews, and cached answers.