Maya starts her new marketing role at a Bristol agency expecting a straightforward first day. She opens an email containing a contract, signs the PDF, and assumes that document contains everything that governs her employment. A few months later, her manager changes her working location, her bonus is discussed in a team message, and a revised handbook appears in SharePoint. Which document now represents the agreement?
That question gets to the heart of what are contracts of employment in UK law. A contract isn't a signed file. It's a legally binding relationship, supported by express terms, implied obligations, statutory rights, workplace practice, and later variations. For HR teams, the safest approach is to manage it as a living, version-controlled record connected to the employee's structured data.
Table of Contents
- What a Contract of Employment Actually Is
- How UK Contract Law Reaches This Point
- Required Clauses Every UK Contract Should Cover
- Implied Terms and the Hidden Rules That Bind You
- Permanent, Fixed-Term, and Zero-Hours Compared
- A Practical Sample Structure for a UK Contract
- Storing and Managing Contracts Centrally
- Putting It All Together and What to Do Next
What a Contract of Employment Actually Is
Maya's employment contract begins before she opens the PDF. In the UK, a contract of employment exists as soon as a job offer is accepted, even if the agreement hasn't been written down under GOV.UK employment contract guidance. If the agency offers Maya a role, she accepts it, and both sides intend to create an employment relationship, the agreement may already be legally binding weeks before her start date.
The contract is the whole agreement between employer and employee or worker. It can cover her job duties, pay, working hours, workplace, holiday, benefits, confidentiality, notice, and the way employment may end. Some terms might be set out in a formal agreement, while others appear in an offer letter, employee handbook, policy, email, or established workplace practice.
Practical rule: Treat acceptance of the offer as the point at which the employment record begins, not the point at which somebody eventually uploads a signed document.
The contract and the written statement are different
Maya's day-one document may be a written statement of employment particulars. That statement is a statutory summary of important terms, but it isn't the contract itself. GOV.UK explains that contractual terms can be written, verbal, contained in an offer letter or handbook, or required by law, while the written statement is a separate employer duty in its guidance on employment contracts and conditions.
That distinction matters when a manager changes Maya's role. The original contract, the written particulars, a handbook rule, and the later variation may all need to be reviewed together. A written statement can still provide evidence of the agreed terms, but it shouldn't be mistaken for the complete legal relationship.
The employer must give the principal statement on the first day of employment, with the wider statement due within two months of the start date under GOV.UK written statement guidance. The statement must include core information such as pay, hours, holiday entitlement, workplace, probation arrangements where applicable, and fixed-term end dates where relevant.
Why a signed PDF isn't enough
A one-off PDF can show what the parties agreed at a particular point. It won't, by itself, show whether Maya was later promoted, moved to a different workplace, given new hours, or issued revised terms. HR needs a record of the original version, each accepted amendment, the effective date, and the approval trail.
In practical terms, the contract should connect to fields such as:
- Employment start date: When the relationship began.
- Continuous employment date: The date used to track continuity.
- Role and department: The duties and organisational context.
- Pay and hours: The commercial terms being administered.
- Workplace and working pattern: Where and when the work is performed.
- Notice and termination terms: What happens when either party ends the relationship.
This is why contract management belongs in the same operating model as onboarding, employee records, approvals, and document control. The PDF is evidence. The version-controlled employment record is what helps HR understand the agreement as it exists today.
How UK Contract Law Reaches This Point
A manager hires Maya and sends her a contract. Later, her hours change, she moves department, and her salary is updated. The original PDF still records the starting agreement, but HR also needs a reliable history of what changed, when it took effect, and which version Maya accepted. UK employment law provides the framework for that record.
Historical legal scholarship traces employment relationships in England back to at least 1349, when work obligations followed master-and-servant rules rather than modern HR documents as discussed in the supplied legal history reference. The modern contract-based framework is rooted in the Employment Rights Act 1996, which consolidated employment-rights legislation and established the right to written particulars at the beginning of employment through GOV.UK's written statement guidance.
For a people manager, the history matters because it explains why contract administration is both a legal duty and a record-keeping process.
The statutory framework in plain English
The Employment Rights Act 1996 requires an employer to provide a written statement containing defined employment information. The statutory framework covers items such as the parties, start date, continuous employment date, pay, pay intervals, hours, holiday entitlement, and holiday pay under the relevant statutory wording.
The practical rule is to separate the record into two stages. The principal statement must be available on day one. Wider particulars may follow, but the employer must provide them no later than two months after employment begins.
A contract system can represent this like controlled fields in Microsoft 365 or Dynamics 365:
- Prepare the principal statement: Capture the core terms before or on the first day.
- Track outstanding particulars: Mark information that has not yet been issued.
- Complete the wider statement: Set a task and owner for the remaining statutory information.
- Record acceptance and versions: Retain the issued wording, effective date, approval trail, and employee response.
Why the timing matters
The written statement gives an employee usable information about the working relationship. A manager can use it to confirm what was agreed about pay, hours, location, holiday, probation, and relevant end dates. HR can use the same information as a controlled checklist rather than searching through messages and attachments.
ACAS confirms that employees and qualifying workers are entitled to written particulars, and that the employer's duty applies regardless of how long the person is employed for in its guidance on what must be written in an employment contract. A short engagement can therefore still require documented terms.
A missing statement may become a tribunal issue. Check current GOV.UK and ACAS guidance on the available remedy and procedure before taking action, because the outcome depends on the circumstances. Treat day-one document control as part of compliance, with each amendment stored as a new, traceable version rather than replacing the original.
Required Clauses Every UK Contract Should Cover
A useful contract checklist has two layers. The first contains the principal particulars for day one. The second contains wider information that must be supplied within the statutory timeframe. Section 1 of the Employment Rights Act 1996 defines the required particulars, including the parties, start dates, pay, hours, and holiday information in the legislation.
| Day-one terms | Two-month terms |
|---|---|
| Employer and employee names | Notice periods |
| Start date and continuous employment date | Holiday entitlement and holiday pay arrangements |
| Job title or a description of the work | Pension and pension scheme information |
| Place of work or relevant workplace details | Sick pay and sickness procedures |
| Hours, working days, and variation arrangements | Collective agreements |
| Pay or the method used to calculate variable pay | Training requirements and repayment clauses |
| Probation information where applicable | Other wider particulars required by the statutory framework |
Turn every clause into a controlled field
The names of the parties should link to the correct legal entities and employee record. A trading name in an offer letter may not be enough if a different group company employs the person. Store the employing entity as structured data, then retain the document that confirms the wording issued to the employee.
The start date and continuous employment date deserve separate fields. They may be the same, but they serve different administrative purposes. A manager who records only the date on which the employee first attends the workplace may miss the date on which the contract began.
Hours and workplace terms also need precision. “Standard office hours” or “Bristol and elsewhere as required” may leave room for disagreement. Record the agreed pattern, the primary workplace, any permitted locations, and the mechanism for changing them.
Pay, benefits, and conditions
Pay records should show the amount or calculation method, payment interval, effective date, and approval history. A variable bonus should identify whether it is discretionary, what performance conditions apply, who approves it, and whether the terms can change. Avoid relying on a manager's informal explanation that isn't reflected in the controlled record.
Holiday, sick pay, pension, notice, grievance, and disciplinary information should be linked to the relevant policy or scheme version. The employee needs to know where the practical rules sit, while HR needs to know which version applied at a particular time.
Common drafting gaps include:
- Vague mobility wording: State how far or in what circumstances the workplace may change.
- Unclear variation language: Explain how contractual amendments are proposed, accepted, and recorded.
- Ambiguous bonus triggers: Separate eligibility, calculation, discretion, and payment conditions.
- Disconnected documents: Link the offer, written statement, contract, handbook, and amendments.
- Missing effective dates: Record when a promotion, pay change, or location change takes effect.
A contract system should therefore hold both the clause text and the data behind it. For example, a notice clause may be stored as a document paragraph, but the notice period should also be a searchable employee field. That lets HR identify affected employees when a policy or contractual arrangement changes.
For managers handling onboarding, contract terms should sit alongside compliance evidence. The UK right to work checks for employers process is separate from the employment contract, but both need reliable ownership, dates, documents, and audit trails.
Implied Terms and the Hidden Rules That Bind You
A new manager tells an employee that the team receives a monthly bonus. The payment appears regularly, colleagues receive it, and the business processes it through the same approval route. The contract calls the bonus discretionary, yet the repeated practice and communications may support an argument about what both sides reasonably understood.
That example shows why an employment contract is a living, version-controlled record, not only a signed PDF. UK employment relationships can include terms implied by statute, necessity, or established custom and practice. An implied term must fit the agreement, cannot contradict an express term, and, where it is based on custom, must be sufficiently known, certain, and reasonably expected to apply.
Working patterns can create the same question. If an employer consistently allows early finishes on Fridays, treats the arrangement as normal, and never reserves a right to withdraw it, employees may argue that the practice has contractual force. The outcome depends on the evidence and wording, including records held in Microsoft 365 and Dynamics 365, rather than on whether the arrangement was printed in the contract.
Three routes to an implied term
Statute supplies rights and duties because legislation requires them. The written statement duty and minimum wage requirement are examples of obligations surrounding employment. In a contract system, the related statutory requirement should be linked to the employee record, applicable policy, and effective date.
Necessity or fact can fill a genuine gap where a term is needed to make the agreement work or is so obvious that both parties would have understood it. A manager cannot add any condition that seems sensible. The proposed term must suit the relationship and remain consistent with the express clauses.
Custom and practice develops through consistent, known workplace behaviour. A handbook may start as guidance, but repeated application can affect how employees understand it. For example, if managers approve a bonus through the same workflow over time, the workflow may become operationally significant. Store the handbook version, approval history, manager communications, and contract record together so HR can examine what happened.
Audit the trail, not just the template. Emails, side letters, Teams messages, handbook versions, approval records, and manager assurances can all affect how the employment relationship is interpreted.
Before changing a policy or HR system field, review informal commitments. If the business intends to retain discretion, the contract and handbook should state that clearly, managers should avoid promising guaranteed outcomes, and the organisation should apply the wording consistently. Version control helps show which clause and policy applied at a given time. It cannot correct an inconsistent practice that has already developed.
Permanent, Fixed-Term, and Zero-Hours Compared
The label on a contract doesn't answer every legal question. A permanent contract normally continues until either party ends it under the agreed terms. A fixed-term contract has an identified end point or event, while a zero-hours arrangement usually offers flexibility around whether and when work is offered and accepted.
The drafting risk changes with each shape.
| Contract Type | Notice and Termination | Continuous Service | Statutory Reform Risk | Exclusivity Test |
|---|---|---|---|---|
| Permanent | Usually ends through notice, dismissal, resignation, or another lawful route | Normally designed to continue without a planned end date | Review changes affecting employment rights and processes | Check any restriction on outside work |
| Fixed-term | Ends under the stated term or may require notice, depending on wording | Can build continuity during employment | Check end-date wording, renewal decisions, and fair treatment | Review restrictions carefully |
| Zero-hours | Work may be offered variably, but termination wording still needs care | Depends on the actual relationship and continuity facts | Particularly sensitive as reforms develop | Test exclusivity provisions and practical effect |
| Other atypical arrangement | Depends on the agreed structure and actual working relationship | Must be assessed from the facts | Review classification and changing statutory rights | Ensure restrictions match the arrangement |
Flexibility needs evidence
A zero-hours label doesn't remove the need for clear terms. The contract should explain how work is offered, whether the worker may accept or decline it, how pay is calculated, how cancellations are handled, and how either party ends the relationship. HR should then compare the written wording with actual scheduling and management behaviour.
The UK government published updated zero-hours employer guidance on 28 August 2026, and the Employment Rights Act 2025 is already in force in part, with further zero-hours changes still to come in the official zero-hours guidance. Because the framework is evolving, organisations should avoid treating an old flexible-working template as permanently safe.
Fixed-term arrangements also need active review. The end date should be recorded as structured data, alongside renewal decisions, communications, and any change to duties or pay. A manager who lets a fixed-term worker continue without updating the record can create uncertainty about the current arrangement.
Permanent employment isn't risk-free either. A promotion, new location, changed hours, or revised benefit can create a variation that needs consultation, acceptance, and version control. The working time guidance for UK workplaces can help managers check how contractual hours interact with wider working-time obligations.
A Practical Sample Structure for a UK Contract
A workable UK employment agreement should be easy for an employee to read and easy for HR to maintain. Store the document in a controlled Microsoft 365 SharePoint library, then reflect the important attributes on the worker record in Dynamics 365 Human Resources. That arrangement separates the authoritative wording from the searchable data used for payroll, reporting, approvals, and change management.
Put principal particulars where managers can find them
Start with the parties and employing entity. Add the job title, start date, continuous employment date, place or places of work, hours, working pattern, pay, pay interval, holiday, probation terms, and the routes for grievances and disciplinary matters. The exact statutory content should be checked against the current legislation and guidance, but the system record should hold each field separately rather than hiding everything inside a single attachment.
A sensible record might include:
- Party details: Legal employer, employee name, worker status, and employing entity.
- Employment dates: Start date, continuous service date, fixed-term end date where applicable.
- Role details: Job title, department, manager, duties, and organisational position.
- Working arrangements: Hours, days, workplace, remote-working terms, and variation mechanism.
- Reward: Pay basis, pay interval, bonus rules, benefits, and effective dates.
- Policy connections: Holiday, sickness, pension, grievance, disciplinary, and collective agreement references.
The wider structure can then add confidentiality, intellectual property, restrictive covenants, garden leave, pension detail, training obligations, and repayment terms where appropriate. Optional clauses still need careful drafting. A clause that appears in a standard template may not suit a junior employee, a fixed-term specialist, or a worker with several workplaces.
Here is the practical test for consistency. If the offer letter says one salary, the contract says another, and the Dynamics record contains neither effective date, the manager can't reliably explain which term is current. The same problem appears when a handbook changes a process without recording whether the change is contractual or merely guidance.
The video below provides another way to visualise how a structured employment agreement can be organised.
Before issuing the contract, compare the generated document with the structured employee fields. After acceptance, save the final version, acceptance evidence, effective date, approver, and any future review date. That turns the agreement into a controlled HR asset rather than an orphaned file.
Storing and Managing Contracts Centrally
A contract stored in an employee's personal folder may be difficult to locate, compare, or update. A connected Microsoft environment gives HR a more practical architecture: SharePoint for controlled documents, Dataverse and Dynamics 365 for structured records, and Power Automate for change workflows.
SharePoint can hold the signed contract, written statement, amendments, acceptance evidence, and relevant handbook versions. Version history helps HR distinguish the original agreement from later changes. A document library can also apply permissions, approval steps, naming conventions, retention labels, and review ownership.
Dynamics 365 Human Resources can hold the fields managers need to work with every day. Notice period, role, workplace, pay basis, hours, contract type, fixed-term end date, and benefits can be searchable attributes rather than information trapped in a PDF. The document remains important, but the structured record supports reporting and operational decisions.
Let changes trigger controlled actions
Suppose a manager changes an employee's location. A Power Automate workflow can route the proposed variation for approval, create the amendment document, notify the employee, capture acceptance, update the workplace field, and retain the previous version. A similar flow can support a promotion, salary change, revised hours, or move from a fixed-term to a permanent arrangement.
This approach also makes clause ownership clearer:
- Notice periods: Stored on the employment record and supported by the current contract.
- Flexible-working terms: Linked to the relevant contract and policy version.
- Benefits: Connected to eligibility rules and the effective date.
- Holiday and sickness: Referenced through controlled policy documents.
- Amendments: Stored with approval, acceptance, and effective-date evidence.
Employee self-service through Microsoft Teams, Outlook, browser, or mobile interfaces can give employees access to their current documents without requiring HR to answer every retrieval request. Managers can submit changes through controlled forms instead of sending informal instructions to a shared inbox.
A central HR document centre can support this model by bringing documents, ownership, approvals, and employee access into a more consistent process. HR Management 365 is one platform option that maintains employment, contract, document, organisation, and change information within a Microsoft-based HR environment.
Access control remains essential. Employment records contain personal information, so organisations should restrict access by role, apply appropriate retention rules, maintain audit logs, and align processing with UK GDPR requirements. Centralisation only reduces risk when governance is designed alongside the technology.
Putting It All Together and What to Do Next
A contract of employment is best understood as a living agreement with controlled versions. It begins when the offer is accepted, includes express and implied terms, and develops when the employee is promoted, moved, given different hours, or affected by a valid policy or contractual change.
The written statement has its own compliance timetable. The principal statement belongs on day one, while wider particulars must be supplied within the statutory period. The statement isn't the whole contract, but it provides a defined set of core information that HR must issue, maintain, and update when material terms change as explained by ACAS.
Different contract types create different management questions. Permanent roles require controlled variation. Fixed-term roles need reliable end-date and renewal records. Zero-hours and other atypical arrangements need particular care as UK reforms develop. Custom and practice also matter, because repeated promises and working methods can influence the rights employees reasonably expect.
A first-time people manager can take four practical steps:
- Audit current records: Compare every contract against the day-one and wider-particulars checklist.
- Confirm central ownership: Make one controlled location the source for current documents and amendments.
- Schedule regular review: Check templates, handbooks, variable-pay wording, and flexible-working terms as legal requirements change.
- Assign version control: Give a named HR owner responsibility for approvals, acceptance evidence, effective dates, and superseded versions.
Microsoft 365 and Dynamics 365 can make that process operational. SharePoint can manage document versions, Dynamics can hold searchable employment attributes, and Power Automate can route changes through approval and acceptance. The important decision isn't whether to keep a PDF. It's whether your organisation can prove which terms applied, when they changed, and who accepted them.
HR Management 365 helps UK organisations maintain employment, contract, document, organisation, and change information in a connected Microsoft environment. Visit HR Management 365 to explore a structured approach to contract control, or call +44 1522 508096 today and send us a message about your HR requirements.
