How to Choose the Right SharePoint Column Type
Picking the wrong column type means your data won’t filter, sort, or report properly. Picking the right type makes every other thing work.
What it is
When you create a column, SharePoint asks what type of data it holds: text, choice, date, person, number, yes/no, hyperlink, lookup, managed metadata, calculated. Each type behaves differently — different inputs, different validation, different sort/filter behaviour, different storage. Choose the wrong type and your column is harder to use, less reliable, and less useful in views and workflows.
The most common mistake is using Single Line of Text for everything. It works in the short term — users can type whatever they want — but the cost shows up later. Filters break because half the team typed ‘HR’ and half typed ‘Human Resources’. Sorting is alphabetical instead of meaningful. There’s no validation, so typos accumulate. And reports built on top of text columns are unreliable forever.
The better approach is to ask: what is this data, really? If it’s a fixed list of options, use Choice or Managed Metadata. If it’s a person, use Person. If it’s a date, use Date. If it’s a yes/no, use Yes/No. Match the type to the data, and SharePoint does the heavy lifting for you.
Why it matters
Column type isn’t just a technical setting — it’s the difference between data you can trust and data that’s forever a bit off:
- Structured columns enforce consistency. A Choice column with 5 options means everyone tags from the same list. A text column means everyone types something slightly different.
- Structured columns power filtering and views. ‘Show me everything where Status = Approved’ is a clean filter on a Choice column. On a text column, it’s ‘where Status contains approved or Approved or APPROVED or aproved…’
- Copilot understands structure. A Person column tells Copilot ‘this is a real human in your tenant’. A text column with someone’s name is just a string of characters.
When to use this
- When you’re about to create a column and choosing what type to use.
- When an existing column isn’t behaving the way you expected.
- When filters and views aren’t returning what they should.
- When you’re auditing a library and finding inconsistent data.
How to do it
- Identify the data: is it finite (list of options) or open-ended?
- If finite and local to one library: use Choice.
- If finite and used across multiple sites: use Managed Metadata (see M-13).
- If it’s a person: use Person.
- If it’s a date: use Date and time (Date only if time doesn’t matter).
- If it’s a yes/no: use Yes/No.
- If it’s a number with units: use Number or Currency.
- If you genuinely need free text (like a description): use Single Line or Multiple Lines of Text — but accept that you can’t filter cleanly on it.
Best practices
- Default to structured types. Choice, Date, Person, Yes/No before Text. Always.
- Use Person for ownership and assignment. ‘Owner’ as a Person column gives you ‘Me’ filters and automated notifications for free.
- Reserve Text for genuinely unstructured content. Notes, descriptions, summaries — not categories.
- Don’t change types after the fact. Changing a column type usually loses data. Plan once, build once.
Common mistakes
- Using Text for everything. Easy now, painful forever. Half your team will type slightly differently and your filters will be unreliable.
- Using Lookup when Managed Metadata is the right answer. Lookup only works within a single site. Managed Metadata works across the whole tenant.
- Building calculated columns on text. Fragile, error-prone, hard to maintain.
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 are the column types in SharePoint?
SharePoint offers around a dozen column types: Single Line of Text, Multiple Lines of Text, Choice, Person or Group, Date and Time, Yes/No, Number, Currency, Hyperlink or Picture, Lookup, Managed Metadata, Calculated, and Location. Each is built for a different kind of data — match the type to the data and SharePoint does the heavy lifting in views, filters, and Copilot.
Can I change a SharePoint column type after creating it?
Mostly no. SharePoint allows a small number of conversions (Single Line of Text to Multiple Lines, for example) but most type changes are blocked — and the few that are allowed often lose data. The practical answer: don’t plan on changing types. Decide once, build once. If you’ve already created the wrong type, the safest fix is to add a new column of the right type, migrate the data manually using Grid View, then delete the old column.
What’s the difference between Choice and Managed Metadata columns?
A Choice column stores a list of options inside one library — fast to set up, no admin needed, but the list is local to that library. A Managed Metadata column pulls from the central Term Store and works across the whole tenant — every library that references it stays in sync. Use Choice for library-specific lists (Status, Phase, Priority). Use Managed Metadata when the same vocabulary needs to apply everywhere (Department, Document Type, Location).
Should I use Text or Choice for categories in SharePoint?
Always Choice (or Managed Metadata) for categories. Text columns let people type slightly different versions of the same thing — ‘HR’ / ‘Human Resources’ / ‘hr’ all become separate values, and your filters break. Choice forces consistency: everyone picks from the same fixed list. Reserve Text columns for genuinely unstructured content (a description, a note) — never for anything you’d want to filter, sort, or group by.