1
Prepare and review
Determine whether the content belongs, where it should live and what must be true before it can be trusted.
Proposed · Working · In review
The NAVI AI Enablement Journey · Guide 04
Knowledge Content Lifecycle SOP
A practical system for moving knowledge from an initial idea to trusted use—and retiring it safely when it is no longer current.
Core idea
A healthy Knowledgebase establishes which information people and AI may rely on, who is responsible for it, and what happens when it changes.
Where this guide fits: Guide 03 establishes the Knowledgebase structure. Guide 04 governs how trusted knowledge is prepared, approved, published, maintained, and retired before later guides rely on it in permissions, connections, and workflows.
The lifecycle in one view
Knowledge is continuously created, approved, shared, used, updated and eventually retired. Ongoing maintenance keeps it dependable for both people and AI agents.
Continuous lifecycleTrusted knowledgeAuthority · Access · Evidence
1 · PrepareAssess, classify and approve
2 · PublishConnect, control and validate
3 · MaintainMonitor, revise and improve
4 · RetireSupersede, archive or remove
2
Publish and validate
Make approved content available to the intended audience and confirm that retrieval behaves correctly.
Approved · Restricted
3
Maintain and improve
Use change signals, feedback and retrieval evidence to keep active knowledge dependable.
Active approved knowledge
4
Retire or contain
Stop obsolete or inappropriate material from controlling current answers while preserving what must be retained.
Superseded · Archived · Removed · On hold
Universal operating principles
The controls that matter across every phase.
1Preserve authorityConnect maintained sources instead of creating unmanaged copies.
2Separate working materialDrafts and generated outputs stay outside governed retrieval until approved.
3Match review to riskHigher-consequence use requires stronger review and test evidence.
4Let change trigger reviewKnown business changes matter more than arbitrary calendar dates.
5Retire deliberatelyPrevent outdated answers without destroying information that must be preserved.
Lifecycle stages
Each stage has a purpose, a small set of decisions and a clear output.
1
Prepare and review
Decide what qualifies, where the approved version should live and how it will enter the Knowledgebase.
Proposed · Working · In review
As teams adopt AI, they will create new workflows, SOPs, frameworks, policies, agent instructions and operating practices. Documents like these may begin in Workspace while they are being drafted or tested. Before approval, decide whether the information qualifies as trusted organizational knowledge, where its official version should be maintained and how NAVI should access it.
Walk through the decision
QualificationIs this dependable, reusable knowledge that people or AI should be able to rely on?
Official homeWhere should the approved version be maintained after development is complete?
Knowledgebase entryShould NAVI connect to the maintained source, or should the approved content be published directly into a governed Knowledgebase area?
AuthorityIs there an approved version, and which source controls if information conflicts?
AccountabilityWho owns, reviews and approves it?
Access and applicabilityWho may use it, and where or when does it apply?
MaintenanceWhat change or event should trigger another review?
Match review to consequence
| Tier | Typical use | Minimum review |
|---|---|---|
| 1 · High consequence | Regulated, safety-critical, confidential, legally significant or autonomous-action content | Owner, qualified reviewer, required specialist approval and test evidence |
| 2 · Material operational | Procedures, customer guidance, shared workflows and decision support | Owner or steward, qualified review and representative testing |
| 3 · General reference | Stable training, glossary and low-consequence guidance | Owner or steward review and basic validation |
Outcome: approve, restrict, revise, connect the maintained source, publish into a governed Knowledgebase area, keep in Workspace or reject.
2
Publish and validate
Carry the review decision into the Knowledgebase and prove that it works as intended.
Approved · Restricted
The decisions from the previous stage travel with the content: owner, authoritative source, audience, access, applicability, risk tier and review trigger. Publication is the implementation of those decisions—not a separate administrative exercise.
Publish or connect
- Apply the approved location, audience and access controls.
- Preserve the authoritative upstream source.
- Carry forward applicability, restrictions and review expectations.
- Exclude drafts, obsolete versions and unauthorized content.
- Identify prompts, workflows and agents that depend on it.
Validate before relying on it
- Known questions retrieve the intended source.
- The source and applicability are understandable.
- Permissions produce appropriately different results.
- Conflicting sources trigger qualification or escalation.
- Missing knowledge is reported rather than invented.
- Dependent workflows continue to behave as intended.
Outcome: activate, activate with limitations, correct and retest, restrict or escalate.
3
Maintain and improve
Manage knowledge, agents and workflows as a connected operating system.
Active use and revision
This is the operating core of an AI-forward organization. Agents and workflows depend on organizational knowledge, while changes to those agents and workflows can also change what knowledge is needed and how it should be structured, tested and maintained. This work belongs inside normal operations—not in a separate annual cleanup.
Review when something changes
- Policy, product, price, regulation or process
- Version, owner, audience, access or organizational structure
- User-reported error, conflict or stale answer
- Repeated failed search or no-answer result
- Dependent workflow, connector, model or agent
- Agent behavior or outputs indicate incomplete or unclear supporting knowledge
- Security, privacy, legal or compliance concern
Revise responsibly
- Update the authoritative source whenever possible.
- Reapprove changes that affect meaning, authority, access or risk.
- Preserve effective dates and applicability.
- Supersede the prior version when it should no longer control.
- Republish and rerun affected retrieval and workflow tests.
Calendar backstop
Tier 1: at least quarterly. Tier 2: quarterly or semiannually. Tier 3: annually. Known change triggers always override the calendar.
4
Retire or contain
Choose the least destructive action that protects current answers and meets governing obligations.
Superseded · Archived · Removed · On hold
| Action | Use when | Retrieval treatment |
|---|---|---|
| Supersede | A newer approved version controls | Exclude the old version and identify the replacement |
| Archive | Historical, audit, recovery or research value remains | Preserve outside current-answer retrieval |
| Restrict | The content remains valid but its audience changed | Narrow access and retest permissions |
| Remove | No continuing value or authorization exists and retention permits removal | Remove from retrieval and retain required evidence |
| Hold | Legal, audit, incident or investigation requirements apply | Preserve under the controlling hold process |
Emergency correction
- Restrict risky retrieval quickly.
- Notify the owner, administrator and required specialists.
- Identify dependent workflows and distributed outputs.
- Provide an approved interim source when possible.
- Correct, republish and perform focused validation.
- Record the incident and prevention lesson.
Favor containment and reversibility until the facts are established.
Controls that support the lifecycle
Keep accountability and quality visible without creating unnecessary bureaucracy.
Roles and accountability
One person may perform several roles, but ownership and approval should remain explicit.
Content ownerAccuracy, purpose, authority and continued value
Domain stewardStandards, routing and lifecycle consistency
Reviewer or approverApplicability and authorization for use
Platform administratorConnections, publication and access controls
Workflow ownerDependent prompts, automations and outputs
GrowthIQ advisorFacilitation, validation and improvement
Minimum quality checklist
Clear title and purpose
Named content owner
Authority and provenance are clear
Audience and access are defined
Currency and applicability are clear
Conflicts and limitations documented
Working and historical material separated
Review trigger established
Retrieval test completed
Permission test completed
Measure system health—not content volume
OwnershipMaterial knowledge with an owner and review trigger
High-risk controlConsequence-sensitive content with approval and evidence
Retrieval qualitySuccess on representative questions
Conflict resolutionUnresolved conflicts and time to correction
Lifecycle healthStale, duplicate and superseded items corrected
Access healthPermission issues discovered and resolved
Knowledge gapsNo-answer patterns converted into approved knowledge
Business valueUse and outcomes of dependent workflows
Record material lifecycle decisions
For a significant publication, revision or retirement, retain enough evidence to explain what changed and why.
Content or sourcePrior and new stateReasonOwner and approverEffective dateAccess changeReplacement or archiveAffected workflowsValidation resultNext review trigger
This SOP is a starter operating framework, not a legal retention schedule or compliance program. Adapt approval roles, review periods, records treatment and security controls to the organization's obligations. Governing legal, security, privacy, compliance, records-management and source-system requirements take precedence.