Create a New Metadata Column in SharePoint

What it is

A metadata column is a piece of structured information you attach to every file in a library — Department, Document Type, Status, Owner, Project. Instead of relying on folder paths or filenames to tell you what a file is, you tell SharePoint directly. Once columns exist, you can filter by them, sort by them, group by them, build views around them, and trigger workflows from them. Copilot can read them too.

Most SharePoint libraries are still set up the way shared drives were: a single ‘Documents’ library with no metadata, just nested folders. This works at small scale (under maybe 200 files) and falls apart fast above that. Without metadata, finding files means clicking through folder trees and hoping. With metadata, finding files means filtering — and that scales to thousands of files without breaking.

Adding a column is a small action with big downstream effects. Every column you add becomes a question SharePoint can answer about your content. Three good columns are usually enough to transform a chaotic library into a navigable one. The hard part isn’t creating the columns — it’s choosing which ones matter most for the way your team actually works.

Why it matters

Metadata columns aren’t just nice-to-have organisation. They’re the structural layer that makes SharePoint scale, supports Copilot, and keeps your team finding what they need:

• Columns make filtering possible. ‘Show me all approved policies for Finance’ is a one-click filter when you have Status, Document Type, and Department columns. Without them, it’s an hour of scrolling.
• Columns make Copilot accurate. Copilot reads metadata to understand context. A file tagged ‘Document Type: Policy, Status: Approved, Department: HR’ is far more findable than a file with no tags.
• Columns force clarity. Adding a ‘Document Type’ column means deciding what types you actually have. That conversation alone is often more valuable than the column.

When to use this

• When you’re setting up a new library and want it to work properly from day one.
• When an existing library has grown beyond what folders can manage.
• When you can’t find files easily and you’re tempted to create more folders to fix it.
• When you’re preparing a library for Copilot and need structured tags it can read.

How to do it

1. Open the SharePoint library where you want to add metadata.
2. Click + Add column in the column header row.
3. Choose the column type (see M-02 for how to pick the right type).
4. Name your column clearly — use plain English (e.g. ‘Department’, not ‘Dept’ or ‘D’).
5. Add a description explaining what the column is for and how to fill it in.
6. Decide if it should be required — if a file can’t function without this tag, make it required.
7. Save. The column appears in your default view immediately.
8. Tag existing files in bulk using Quick Edit / Grid View (M-44).

Best practices

• Start with three columns: Document Type, Status, Owner. Add more only when the team agrees they’re needed.
• Use plain English names. ‘Department’ beats ‘Dept’. ‘Document Type’ beats ‘DocType’. Search engines (and humans) prefer real words.
• Always fill in the Description field. What does this column mean? When should it be filled in? A 1-line description prevents 100 misuses.
• Make critical columns required. If you can’t function without it, the system shouldn’t let people skip it.

Common mistakes

• Adding 15 columns at once. Users won’t tag any of them properly. Start with 3, prove they work, add more later.
• Naming columns with abbreviations. ‘Dept’ is faster to type but harder to search and harder to understand. Plain English wins.
• Skipping descriptions. Six months later, nobody remembers what the column was for. Two minutes of writing prevents months of confusion.

FAQ