Document Lifecycle
Understand how documents move through draft, review, and published states.
Read time:5 minUpdated:2026-01-10
Document Lifecycle
Every document in TyneBase follows a structured lifecycle that ensures quality and accountability.
Document States
┌─────────┐ ┌───────────┐ ┌───────────┐
│ Draft │ ──▶ │ In Review │ ──▶ │ Published │
└─────────┘ └───────────┘ └───────────┘
│ │
│ ▼
│ ┌───────────┐
└─────────────────────────▶ │ Archived │
└───────────┘
Draft
- Initial creation state
- Only visible to author and admins
- Not indexed for AI search
- Can be freely edited
In Review
- Submitted for approval
- Assigned reviewer notified
- Comments and suggestions enabled
- Changes tracked
Published
- Visible based on permissions
- Indexed for AI/RAG search
- Version snapshot created
- Lineage tracking active
Archived
- Hidden from navigation
- Preserved for compliance
- Searchable by admins
- Can be restored
State Transitions
| From | To | Required |
|---|---|---|
| Draft | In Review | Submit action |
| In Review | Published | Reviewer approval |
| In Review | Draft | Rejection with feedback |
| Published | Archived | Archive action |
| Archived | Draft | Restore action |
Verification Cycles
Published documents can have verification schedules:
- 30 days: Rapidly changing content
- 90 days: Standard documentation
- 180 days: Stable reference material
- 365 days: Policies and procedures
When verification is due:
- Owner receives notification
- Document marked "Needs Review"
- Must verify or update to clear
Version History
Every save creates a version snapshot:
{
"version": 5,
"created_by": "John Doe",
"created_at": "2026-01-10T14:30:00Z",
"changes": "Updated API examples",
"word_count": 1250
}
Restore any previous version with one click.