Marital Status Options In The UK: What Employers Need To Know

As a small business owner, you’re probably collecting more employee data than you realise - and a lot of it sits quietly in your HR files until something goes wrong.

One of the most common examples is an employee’s marital status. It’s easy to treat this as harmless “admin info”, but in practice it can raise questions about discrimination risk, payroll/benefits setup, right-to-work checks, emergency contacts, and data protection.

In this guide, we’ll break down the key marital status options in the UK, when (and whether) you should ask about them, and how to stay compliant with the Equality Act 2010 and UK GDPR.

What Are The Marital Status Options In The UK (And Why It Matters In HR)?

In the UK, “marital status” usually refers to whether someone is:

• Single
• Married
• In a civil partnership
• Divorced
• Widowed
• Separated (not always treated as a formal legal status, but often used administratively)

You’ll sometimes see “cohabiting” or “living with a partner” as an option on forms too. That can be relevant for benefits or emergency contact context, but it’s not the same as being married or in a civil partnership (and it doesn’t carry the same legal status in many situations).

Why Marital Status Options Can Be A Legal Topic (Not Just An Admin Topic)

From an HR and compliance perspective, marital status becomes important because:

• It links directly to a protected characteristic (marriage and civil partnership) under discrimination law.
• It’s personal data, meaning you need a lawful basis to collect it and a good reason to keep it.
• It can influence workplace decisions (for example, relocations, travel expectations, or assumptions about availability) - and those assumptions are where disputes often start.

So while it’s useful to understand the UK’s marital status options, the bigger compliance question is: should you be asking at all - and if you do, what are you doing with the information?

Do You Actually Need To Collect Marital Status From Employees?

For most small businesses, the honest answer is: not usually.

There’s no general legal requirement for an employer to record an employee’s marital status. And if you don’t need it, collecting it “just in case” can create unnecessary risk under UK GDPR (because you’re holding more personal data than you need).

Situations Where Marital Status Might Be Relevant

There are scenarios where collecting marital status (or something closely related) can be legitimate, such as:

• Workplace benefits where eligibility depends on marital/civil partnership status (for example, spouse/civil partner cover in an insured benefit scheme).
• Pensions and death-in-service benefits where nomination forms may reference spouse/civil partner.
• Emergency contact details (although you usually only need a name/number/relationship, not marital status as a category).
• Conflict of interest declarations where a spouse/civil partner is a supplier, customer, or competitor.
• Relocation packages or overseas assignments where family circumstances affect immigration or allowances (more common in larger businesses, but it can happen).

Even in these cases, it’s good practice to ask for the minimum information needed and explain why you’re collecting it.

Situations Where Asking Can Create Risk

You should be especially cautious about asking for marital status in:

• Recruitment and hiring (where it may look like you’re assessing “commitment”, pregnancy likelihood, childcare responsibilities, or flexibility).
• Performance management (where it can creep into reasoning about availability and “attitude”).
• Redundancy selection (where assumptions like “they have a partner, they’ll be fine” can be discriminatory).

If you’re reviewing your recruitment process, it’s worth checking your application forms and interview scripts to remove risky questions - issues like this often overlap with illegal interview questions.

Marriage And Civil Partnership: Your Equality Act 2010 Duties

Under the Equality Act 2010, marriage and civil partnership is a protected characteristic. That means you must not treat an employee (or job applicant) unfairly because they are:

• married; or
• in a civil partnership.

It’s important to be clear on what the law covers here. The protected characteristic is not “being single”, “being divorced” or “being in a relationship”. It specifically protects people who are married or in a civil partnership.

What Discrimination Can Look Like In Real HR Decisions

In small businesses, discrimination claims often don’t come from obviously bad behaviour. They come from patterns and assumptions, such as:

• Scheduling and flexibility assumptions (for example, assuming a married employee can’t travel, or assuming a single employee can work every weekend).
• Client-facing opportunities being given to one group over another due to “image” or “stability” assumptions.
• Work social events or benefits that subtly exclude civil partners, or treat marriage as the “default”.
• Pay and progression decisions influenced by personal circumstances rather than performance.

Even if your intentions are good, the risk is the same: you’re making decisions using personal status rather than objective business criteria.

Practical Steps To Reduce Discrimination Risk

Here’s what tends to help most SMEs in practice:

• Keep recruitment forms lean: remove marital status options entirely unless you have a specific, lawful reason.
• Train managers: especially first-time managers, who may not realise “helpful” assumptions can create legal risk.
• Use objective criteria in performance, promotion and redundancy processes (and document them).
• Check your benefits language: use “spouse or civil partner” where relevant, rather than “husband/wife”.

Also, make sure the basics are solid - including a properly drafted Employment Contract and clear workplace policies (usually pulled together in a Staff Handbook), so your managers aren’t improvising.

UK GDPR And HR Records: How To Handle Marital Status Data Properly

Even if marital status isn’t “special category data” by default, it’s still personal data. That means UK GDPR and the Data Protection Act 2018 apply.

So if you collect marital status options on a form, you should be able to answer (confidently):

• Why are we collecting this?
• What lawful basis are we relying on?
• Who can access it internally?
• How long will we keep it?
• How will we keep it secure?

Lawful Basis: What Usually Works For Employers?

Most employers won’t rely on consent in an employment context (because consent can be tricky if there’s an imbalance of power).

Instead, you may rely on lawful bases like:

• Legal obligation (where a law requires you to process certain data - not common for marital status specifically, but common for payroll/tax records generally).
• Contract (where processing is necessary to perform the employment contract - marital status is rarely necessary for this in most roles).
• Legitimate interests (for example, administering a benefit scheme, preventing conflicts of interest, or maintaining accurate personnel records - but only where it’s genuinely justified and balanced against privacy impact).

If you’re not sure which basis applies, it’s often a sign you should stop collecting the data (or narrow what you collect) until you can justify it properly.

Data Minimisation: Don’t Collect It Unless You Need It

One of the most overlooked GDPR principles in HR is data minimisation: collect only what you need.

In other words:

• If the purpose is emergency contact, ask for emergency contact details - not marital status options.
• If the purpose is benefits eligibility, ask only what the provider needs, at the point you’re enrolling them.
• If the purpose is conflict declarations, ask for relationships that create conflicts (spouse/civil partner working at a supplier), not general relationship status.

Retention: How Long Should You Keep It?

Keeping HR information forever “because it might be useful” is a common trap. Instead, set retention periods that match your business needs and legal obligations.

As a rule, you should be able to justify how long you keep each category of HR data - and then delete it when it’s no longer needed. This is particularly important for ex-employee records, which often contain old personal details that can be inaccurate and risky to hold.

If you’re tightening up your data practices, it can help to align HR retention with a wider approach to data retention across your business (including marketing/customer information) - the same thinking applies as in data retention periods.

Be Careful: Marital Status Can Reveal Other Sensitive Information

While “married” alone isn’t special category data, HR records about family relationships and personal circumstances can sometimes reveal (or be closely connected to) more sensitive information. For example:

• Some benefits or next-of-kin details may indirectly suggest information an employee would consider private.
• Benefit nominations can reveal family circumstances.
• Requests for changes can be linked to separation, domestic abuse, or health issues.

This doesn’t mean you can never hold the information - it just means you should treat it with care, keep access limited, and avoid sharing it internally unless there’s a genuine need.

Updating Your HR Process: Best Practice For Forms, Policies, And Payroll

If you want to handle marital status information properly, the most effective approach is usually a quick HR workflow audit.

In practical terms, that means looking at:

• job application forms and ATS fields
• new starter forms
• HRIS/employee profile fields
• benefits enrolment forms
• equal opportunities monitoring forms
• privacy notices and retention schedules

1) Recruitment: Keep It Out Of The Hiring Decision

If you collect marital status data at application stage, it creates an obvious question: why?

Even if you never use it, collecting it can still raise concerns if you later need to defend your hiring decision. A safer approach is:

• Don’t ask for marital status on application forms.
• If you do monitoring, separate it from hiring decision-makers and keep it optional.
• Ensure interviewers and managers aren’t asking “casual” personal questions that drift into protected areas.

2) New Starter Onboarding: Ask Only What You Need

Your onboarding checklist should focus on information you genuinely need to employ someone safely and lawfully, such as identity/right to work, payroll details, emergency contact info, and role requirements.

If you’re using a starter form template that includes marital status options by default, consider removing that field unless you can justify it.

Also, ensure you have the contractual basics in place early. For example, a properly tailored Employment Contract can set expectations around policies, confidentiality, and acceptable conduct from day one.

3) Workplace Policies: Reduce “Assumption-Based” Management

A lot of marital status-related risk isn’t about forms - it’s about how managers behave when they think they’re being flexible or fair.

This is where strong policies help, because they create consistent decision-making. A good Staff Handbook can cover (among other things):

• equal opportunities and anti-discrimination expectations
• absence, flexible working and leave processes
• conflict of interest declarations
• data handling expectations

And if your team uses work devices and systems, clear rules around personal data access and handling are important too - many businesses build this into an Acceptable Use Policy.

4) Privacy Information: Tell Staff What You Collect And Why

Transparency is a core GDPR principle. Employees should understand what HR data you hold and what you do with it.

That usually means having a clear employee privacy notice (or privacy wording within onboarding documentation) that covers:

• what HR data categories you collect (and whether marital status is one of them)
• your lawful bases for processing
• who you share data with (payroll providers, benefit providers, accountants)
• retention periods
• employee rights

If your business is tightening its privacy approach overall, it may make sense to align HR privacy and business privacy in one consistent compliance setup - many SMEs do this through a broader GDPR package rather than patching documents together over time.

5) Be Consistent With “Written” HR Decisions

Whenever marital status comes up (directly or indirectly), consistency matters.

For example, if you agree to a flexible pattern for one employee and refuse it for another, your notes and communications need to clearly show the business reason - not personal circumstance assumptions.

Remember: lots of HR communication happens over email or messaging. If you’re relying on written notices or agreements, it helps to understand when emails are legally binding, because an informal “sure, that’s fine” can accidentally become something you’re expected to honour.

Key Takeaways

• The most common marital status options in the UK include single, married, civil partnership, divorced, widowed, and sometimes separated - but you don’t automatically need to collect this data as an employer.
• Marriage and civil partnership is a protected characteristic under the Equality Act 2010, so HR decisions influenced by marital/civil partnership status can create discrimination risk.
• Be cautious in recruitment: asking about marital status at application or interview stage is rarely necessary and can look discriminatory.
• Marital status is personal data, so UK GDPR applies - only collect it if you have a clear purpose, a lawful basis, and appropriate security/access controls.
• Data minimisation and retention matter: collect only what you need, keep it only as long as you need it, and delete it when it’s no longer required.
• Strong contracts and policies help reduce “assumption-based” management and keep HR decisions consistent, especially as your team grows.

If you’d like help reviewing your HR processes, updating your workplace policies, or making sure your employment documentation is compliant, you can reach us at 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.