If you already use metadata in SharePoint, sooner or later you'll come across the concept of content types. It's one of those terms that sounds more complicated than it is — and once you understand it, it changes how you think about document organisation.
A trick to make the term click: reverse the word order. "Content type" = "document type". A contract is a document type. An invoice is a document type. An internal procedure is a document type. That's all it is.
The problem they solve
Imagine you start well: you create a document library and add two metadata columns — "Document Type" (Invoice, Contract, Procedure) and "Department". A good start.
But the problem quickly appears. Invoices need fields that contracts don't — supplier, amount, payment status. Contracts need fields that invoices don't — client, expiry date, signature status. Procedures need version and review date.
If you put all those columns in the same library, you end up with 15 columns of which only 4 or 5 are relevant for each document. The invoice has the "expiry date" field empty because it doesn't apply. The contract has the "amount" field empty because that doesn't apply either. The library becomes confusing and hard to maintain.
The obvious solution is to create a separate library for each document type — but that doesn't scale well either. You end up with dozens of libraries, each with its own structure.
Content types solve exactly this — multiple document types, each with their own metadata, coexisting in the same library.
What is a content type?
A content type is a template that defines:
- Which metadata columns that document type has
- Which form the user sees when filling in the information
- Optionally, a Word or Excel template that opens automatically when creating a new document of that type
In other words: a content type is a definition of "what this document is and what information it carries".
A practical example
Instead of having a generic "Documents" library with 20 columns of which only 5 are relevant to each file, you create content types:
Content Type: Contract
- Client
- Start date
- Expiry date
- Status (Draft / Under review / Signed / Expired)
- Owner
Content Type: Invoice
- Supplier
- Invoice number
- Amount
- Date
- Payment status (Pending / Paid / Overdue)
Content Type: Procedure
- Department
- Version
- Last review date
- Process owner
All three content types can coexist in the same library. Each document shows only the columns relevant to its type.
What are they used for in practice?
Precise filtering
You can view all contracts expiring this month, or all unpaid invoices from a specific supplier — directly from the library without opening a single file.
Automation
Content types are the foundation of Power Automate flows. "When a document of type Contract is created, send to the owner for review" — without content types, the automation doesn't know what a contract is.
Consistency
The whole team fills in the same fields for the same document type. Fewer decisions, fewer errors, more coherence across the organisation.
Reuse
Once a content type is defined, you can use it across multiple libraries and sites. The definition is made once and applied everywhere.
When do I need content types?
If your organisation handles different document types with different metadata, content types are the answer. If you have a library with only one document type (for example, only invoices), you may not need them — simple columns are sufficient.
The move to content types is worth it when:
- You have several document types in the same library
- You want to reuse the same metadata structure across multiple sites
- You're building automations with Power Automate
The next step
Content types are configured from the SharePoint Content Type Hub or directly from a library. If you want to start structuring your organisation's information more effectively, get in touch — it's one of the first steps in any well-designed document management project.