Skip to main content

Yes/No Column

A Yes/No column stores a true/false value rendered as a checkbox in SharePoint lists, defaulting to either checked (Yes) or unchecked (No) and is commonly used for flags, and toggles within SharePoint lists and libraries.

Common Use Cases

  • Task completion flags: add an Is Complete checkbox to a task list so users can check off items without changing a Status choice column, driving view filters for open vs. completed tasks
  • Approval decision recording: capture a simple Approved yes/no decision in a list item alongside comments and approver fields for straightforward approval tracking
  • Active/inactive record management: use an Is Active column to flag records as current or archived, then filter the default view to show only active records

Benefits

  • Simplest boolean data type: a checkbox is the most intuitive UI for binary flags, users understand it instantly with no training required
  • Editable in Grid View: Yes/No columns render as checkboxes in Edit in Grid View, making bulk toggling of many items fast and efficient
  • View filtering on boolean values: filtering a view to show only items where the checkbox is checked (Is Equal To: Yes) is one of the most common and useful view filter patterns
  • Calculated column support: Yes/No column values can be used in Calculated Column IF formulas as TRUE/FALSE conditions for conditional text or numeric output

Key Considerations

  • Only two states: Yes/No is binary. If your workflow needs more than two states (e.g., Pending, Approved, Rejected), use a Choice column instead
  • Default value is a governance decision: a default of Yes means every new item is opted in unless unchecked, for flags like marketing consent or subscription, a default of No is usually the safer governance choice
  • Cannot store a “not set” state: unlike some database boolean fields, SharePoint Yes/No columns always default to Yes or No; there is no null/unset state