How to Add a Document Status Column in SharePoint
Status tells you where a document is in its lifecycle: Draft, Review, Approved, Published, Archived. Done well, it makes the lifecycle visible.
What it is
A Status column tracks where a document is in its lifecycle — typically values like Draft, In Review, Approved, Published, Superseded, Archived. It’s a simple Choice column most of the time, but its impact is significant: it makes the document’s lifecycle visible at a glance, lets you filter views (‘show me all drafts’), and powers Power Automate flows that act when status changes.
Status is also the column that turns a flat library into a managed lifecycle. With status colour-coded (‘Draft’ in red, ‘Approved’ in green, ‘Archived’ in grey), a library view becomes a dashboard. With status driving Power Automate flows, status changes can trigger notifications, file moves, retention rules, or approval workflows. Without status, the lifecycle is invisible and unmanaged.
The choice of status values depends on your process. Simpler libraries might have just three: Draft, Approved, Archived. More controlled libraries might have six or seven, mapped to a formal review and approval workflow. Match the values to your actual process — don’t invent statuses you’ll never use, and don’t omit statuses your team relies on.
When to use this
- On any library where documents move through stages (drafts, reviews, approvals).
- When you want lifecycle visibility at a glance.
- When Power Automate flows should trigger on status changes.
- When auditors want to see the journey from draft to approval.
How to do it
- Decide your status values to match your process (typically 4-6 values).
- Add as a Choice column.
- Set ‘Draft’ as the default for new files.
- Apply colour formatting in views — red for Draft, green for Approved, etc.
- Build views filtered by status (e.g. ‘My drafts’, ‘Pending review’, ‘Approved this month’).
- Use Power Automate to react to status changes (notify, move, archive).
Best practices
- Apply colour formatting. Visual scanning beats reading. Red drafts and green approvals make views instantly readable.
- Default to ‘Draft’. Approved-by-default is dangerous. Always start as Draft.
- Match values to your actual process. Don’t invent statuses you won’t use.
- Trigger automation from status changes. Status moving to Approved can trigger notifications, file moves, retention.
Common mistakes
- Too many statuses. ‘Initial Draft’, ‘Working Draft’, ‘Refined Draft’ is one status (Draft) overcomplicated.
- No default value. Files appear with blank status, which breaks filters.
- Status that doesn’t match the process. If you have ‘Published’ but no one publishes, the value is dead weight.
The File Sanity Kit gives you the Container Method™ — audit, restructure, and future-proof SharePoint without IT admin. The complete methodology, full workbook, and 8-tab Excel planner.
Get the File Sanity Kit — $27 →FAQ
What is a Document Status column in SharePoint?
A Document Status column tracks where a file is in its lifecycle: Draft, In Review, Approved, Published, Archived. It’s the third critical axis of metadata alongside Document Type (what is it) and Department (whose is it). Without a Status column, every file looks the same — current — even drafts and archived content. With it, the lifecycle is visible at a glance.
What status values should a SharePoint library have?
Keep it to 4-6 values. A good default set: Draft, In Review, Approved, Archived. Add Published if your team distinguishes ‘approved internally’ from ‘published externally’. Resist the urge to add Pending, Submitted, Under Review, Awaiting Approval — they overlap, confuse users, and create paralysis at tagging time. The simpler the list, the more reliable the tagging.
Can I trigger automation when Document Status changes?
Yes — Status is one of the best triggers for Power Automate. Common patterns: ‘when Status changes to Approved, move file to Published library and notify the author’; ‘when Status changes to Archived, restrict permissions and apply retention’. The clean discrete values make the automation logic simple and reliable.
Should Document Status be required in SharePoint?
Yes, with a default value of ‘Draft’. Making it required ensures every file has a lifecycle stage; defaulting to Draft means users don’t have to think about it on upload — the file starts in Draft and graduates from there. Files without a Status often slip through review entirely, which is the worst failure mode.