IT service request — United Kingdom

Updated on 21 November 2026

This local template is a practical starting point. Confirm the facts, the parties’ status, any applicable collective instrument or award, and the governing law before signing or relying on it. IT service request is designed for United Kingdom; it is not a translation of the US version and it does not replace a mandatory form, collective agreement, award, regulator process or professional advice.

IT service request should let a later reader identify the parties, purpose, scope, evidence, timing, approvals and limits without reconstructing the matter from email or memory. Record the local source and the owner of each follow-up.

This local equivalent separates the operational decisions from the legal assumptions. Re-check it when the facts, sector, technology, workplace, transaction or governing law changes.

0 of 11 blanks filled

Tap any highlighted blank in the document below and type straight into it.Free — no sign-up, no watermark

IT Service Request

Primary party:
Other party / recipient:
Effective or issue date:
Jurisdiction:

1. Purpose and background

2. Issue, impact and requested service

3. Money, timing and evidence

OptionalInclude safeguards and limitations

4. Safeguards and limitations

OptionalInclude response or approval block

5. Response or approval

OptionalInclude review and next steps

6. Review, attachments and closeout

7. No unsupported waiver or guarantee

Nothing in this document waives non-waivable rights or guarantees legal compliance, payment, safety, privacy, accessibility, licensing, approval, performance or a particular outcome. Required official forms and attachments control where applicable.

8. Storage and signatures

Store the completed document with its evidence, limit access to people who need it, and use the appropriate controlled system for sensitive personal, payment, health or security information.

Primary party

Date signed:

Other party / recipient

Date signed:

Purpose and scope

Purpose and scope: IT service request should identify the real people, entity, system, transaction or workplace involved, the decision date, the evidence used and the person responsible for the next action. Avoid placeholders in a signed copy. If the facts change, preserve the prior version and record why the new version was issued.

United Kingdom context: check this part against GOV.UK written statement of employment particulars, the Health and Safety at Work etc. Act 1974, UK GDPR and Data Protection Act 2018, the Copyright, Designs and Patents Act 1988, and UK IPO guidance. The correct result can depend on sector, employee or contractor status, an award or collective instrument, the sensitivity of the information, and whether a public authority or regulated activity is involved. Keep a source note with the file and obtain any required consultation, notice or approval before implementation.

Parties, authority and records

Parties, authority and records: IT service request should identify the real people, entity, system, transaction or workplace involved, the decision date, the evidence used and the person responsible for the next action. Avoid placeholders in a signed copy. If the facts change, preserve the prior version and record why the new version was issued.

United Kingdom context: check this part against GOV.UK written statement of employment particulars, the Health and Safety at Work etc. Act 1974, UK GDPR and Data Protection Act 2018, the Copyright, Designs and Patents Act 1988, and UK IPO guidance. The correct result can depend on sector, employee or contractor status, an award or collective instrument, the sensitivity of the information, and whether a public authority or regulated activity is involved. Keep a source note with the file and obtain any required consultation, notice or approval before implementation.

Operational requirements

Operational requirements: IT service request should identify the real people, entity, system, transaction or workplace involved, the decision date, the evidence used and the person responsible for the next action. Avoid placeholders in a signed copy. If the facts change, preserve the prior version and record why the new version was issued.

United Kingdom context: check this part against GOV.UK written statement of employment particulars, the Health and Safety at Work etc. Act 1974, UK GDPR and Data Protection Act 2018, the Copyright, Designs and Patents Act 1988, and UK IPO guidance. The correct result can depend on sector, employee or contractor status, an award or collective instrument, the sensitivity of the information, and whether a public authority or regulated activity is involved. Keep a source note with the file and obtain any required consultation, notice or approval before implementation.

Privacy, confidentiality and security

Privacy, confidentiality and security: IT service request should identify the real people, entity, system, transaction or workplace involved, the decision date, the evidence used and the person responsible for the next action. Avoid placeholders in a signed copy. If the facts change, preserve the prior version and record why the new version was issued.

United Kingdom context: check this part against GOV.UK written statement of employment particulars, the Health and Safety at Work etc. Act 1974, UK GDPR and Data Protection Act 2018, the Copyright, Designs and Patents Act 1988, and UK IPO guidance. The correct result can depend on sector, employee or contractor status, an award or collective instrument, the sensitivity of the information, and whether a public authority or regulated activity is involved. Keep a source note with the file and obtain any required consultation, notice or approval before implementation.

Review, incidents and changes

Review, incidents and changes: IT service request should identify the real people, entity, system, transaction or workplace involved, the decision date, the evidence used and the person responsible for the next action. Avoid placeholders in a signed copy. If the facts change, preserve the prior version and record why the new version was issued.

United Kingdom context: check this part against GOV.UK written statement of employment particulars, the Health and Safety at Work etc. Act 1974, UK GDPR and Data Protection Act 2018, the Copyright, Designs and Patents Act 1988, and UK IPO guidance. The correct result can depend on sector, employee or contractor status, an award or collective instrument, the sensitivity of the information, and whether a public authority or regulated activity is involved. Keep a source note with the file and obtain any required consultation, notice or approval before implementation.

Signatures and handover

Signatures and handover: IT service request should identify the real people, entity, system, transaction or workplace involved, the decision date, the evidence used and the person responsible for the next action. Avoid placeholders in a signed copy. If the facts change, preserve the prior version and record why the new version was issued.

United Kingdom context: check this part against GOV.UK written statement of employment particulars, the Health and Safety at Work etc. Act 1974, UK GDPR and Data Protection Act 2018, the Copyright, Designs and Patents Act 1988, and UK IPO guidance. The correct result can depend on sector, employee or contractor status, an award or collective instrument, the sensitivity of the information, and whether a public authority or regulated activity is involved. Keep a source note with the file and obtain any required consultation, notice or approval before implementation.

Clause-by-clause guide

Purpose and scope
State what the document governs, what it excludes and which facts trigger an update. In United Kingdom, document the source and any local approval or consultation step instead of relying on a generic US clause.
Roles and authority
Name the parties, decision owner, delegate and escalation contact; verify signing authority. In United Kingdom, document the source and any local approval or consultation step instead of relying on a generic US clause.
Performance or controls
Describe the required service, evidence, acceptance test, safety control or record without promising a result the law does not guarantee. In United Kingdom, document the source and any local approval or consultation step instead of relying on a generic US clause.
Information handling
Limit collection and access to what is necessary; describe confidentiality, retention, security and return or deletion. In United Kingdom, document the source and any local approval or consultation step instead of relying on a generic US clause.
Change and termination
Set a review trigger, notice route, handover steps and treatment of open work, materials, access and records. In United Kingdom, document the source and any local approval or consultation step instead of relying on a generic US clause.
Disputes and signatures
Identify the governing-law choice only after checking mandatory rules, then capture dates, names, capacity and signed copies. In United Kingdom, document the source and any local approval or consultation step instead of relying on a generic US clause.

Local compliance checklist

Use this research checklist before sending or signing the IT service request. It is not a certification.

  • Confirm the parties and legal status

    Check whether the relationship is employment, internship, contractor, customer, supplier, investor, applicant or another status under United Kingdom law.

  • Check mandatory terms and process

    Compare the draft with GOV.UK written statement of employment particulars, the Health and Safety at Work etc. Act 1974, UK GDPR and Data Protection Act 2018, the Copyright, Designs and Patents Act 1988, and UK IPO guidance; identify any written-statement, award, collective, regulator, filing, notice or consultation requirement.

  • Minimise personal and confidential data

    Collect only what is needed, tell people what happens to it, restrict access and set a defensible retention and deletion rule.

  • Check safety and operational controls

    For a workplace, system, site or service, record hazards, controls, training, incident escalation and evidence of completion.

  • Check IP, ownership and permissions

    Identify pre-existing material, new outputs, licences, assignments and moral-rights or creator-consent issues relevant in United Kingdom.

  • Record review and approval

    Keep the source links, review date, approver, version, signed copy and follow-up owner. The primary research anchor is https://www.gov.uk/employment-contracts-and-conditions/written-statement-of-employment-particulars.

How to use this template

  1. Confirm the instrument. Check that the IT service request is the right document and that no official or mandatory local form is required.
  2. Gather verified facts. Collect names, dates, scope, evidence, amounts, systems, risks and attachments; leave unknowns as explicit follow-ups.
  3. Adapt local terms. Use the vocabulary of United Kingdom, the applicable sector instrument, currency, dates and responsible authority.
  4. Review and sign. Run the checklist, obtain any consultation or approval, then capture signatures and capacity on the same version.
  5. Store and review. Give authorised people access, retain the evidence, and set a date or event for review, renewal, incident response or closure.

Frequently asked questions

Is this legally approved?

Use the IT service request as a structured starting point, not as legal approval. Confirm the facts and the applicable United Kingdom requirements with the responsible adviser before relying on it.

Which law applies?

Use the IT service request as a structured starting point, not as legal approval. Confirm the facts and the applicable United Kingdom requirements with the responsible adviser before relying on it.

What should be attached?

Use the IT service request as a structured starting point, not as legal approval. Confirm the facts and the applicable United Kingdom requirements with the responsible adviser before relying on it.

Who should sign?

Use the IT service request as a structured starting point, not as legal approval. Confirm the facts and the applicable United Kingdom requirements with the responsible adviser before relying on it.

How should records be kept?

Use the IT service request as a structured starting point, not as legal approval. Confirm the facts and the applicable United Kingdom requirements with the responsible adviser before relying on it.

When should it be reviewed?

Use the IT service request as a structured starting point, not as legal approval. Confirm the facts and the applicable United Kingdom requirements with the responsible adviser before relying on it.

Related templates

Disclaimer

This template is not legal advice and has not been attorney-reviewed or compliance-approved for United Kingdom.