How to Create a Yes/No Column in SharePoint
When the question has only two answers, Yes/No is the column. Fast to fill in, easy to filter, perfect for triggers and checklists.
What it is
A Yes/No column is a single checkbox: true or false, yes or no. It’s the simplest column type, and that’s its strength — fast for users to fill in, perfectly clean to filter on, and trivial for automation to react to.
Yes/No columns are everywhere in well-designed libraries. Confidential? Approved? Reviewed? Audit complete? External access allowed? Personal data? GDPR review needed? Each is a yes/no question that, in aggregate, gives you a clean structural picture of your content. Multiple Yes/No columns combined make excellent simple checklists.
The unsung use of Yes/No columns is in Power Automate triggers. ‘When Confidential changes from No to Yes, move the file to a secured library and notify Compliance.’ That’s a clean automation that wouldn’t work nearly as well with a Choice column or a text field. Yes/No is unambiguous for both humans and code.
When to use this
- For Confidential, Approved, Reviewed, Audit Complete, Compliance Reviewed.
- For external sharing flags, GDPR markers, sensitive content indicators.
- For checklists where each step is a separate Yes/No.
- Whenever the answer is genuinely binary.
How to do it
- Click + Add column → Yes/No.
- Set a default value (usually No — Yes makes everything look approved by default).
- Add a clear description explaining what the question is.
- Add to default view if you want it visible.
- Use in filters: ‘where Confidential is Yes’.
- Use in Power Automate to trigger actions when value changes.
Best practices
- Use Yes/No for genuinely binary states. If there’s a third option (Maybe, In Progress), use Choice instead.
- Default to No. Approved-by-default is dangerous. Confidential-by-default is paranoid. Pick the safe default.
- Make labels clear. ‘Confidential’ is clear. ‘Status’ as a Yes/No is not.
- Combine multiple for simple checklists. Five Yes/No columns can replace a complex form.
Common mistakes
- Using Yes/No for three-state data. If your column needs Yes, No, and Pending, you need a Choice column.
- Approved-by-default. Confused users tick a box without thinking, and content is suddenly ‘approved’. Default to No.
- Vague labels. ‘Reviewed’ — by whom? When? For what? Be specific in the description.
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 Yes/No column in SharePoint?
A Yes/No column is a checkbox — ticked or not. Despite its simplicity (or because of it), it’s one of the most useful column types for binary states: Confidential, Reviewed, Approved, External Access, Audit Complete. Fast to fill in, easy to filter, perfect for compliance checklists and Power Automate triggers.
What’s the default value for a Yes/No column?
You can set it to Yes or No (or leave it unset). For safety, default to No on anything that grants access or signals approval — items shouldn’t be flagged ‘Confidential’ or ‘Approved’ until someone actively says so. For things like ‘Reviewed’, No-by-default makes sense too: it forces the explicit action.
Can I trigger a Power Automate flow when a Yes/No column changes?
Yes. Yes/No columns are excellent automation triggers because they’re unambiguous. Build a flow with the trigger ‘When an item is modified’, then add a condition: ‘if Confidential equals Yes, move file to secure library and notify the compliance team’. The clean binary state makes the logic simple and reliable.
When should I use Yes/No instead of Choice in SharePoint?
Use Yes/No when there are exactly two states and they’re truly binary (yes or no, on or off, approved or not). The moment you need a third state — Pending, Rejected, In Review — switch to Choice. Don’t try to model multiple states with multiple Yes/No columns; it gets confusing fast.