IT Services Agreement Template
Updated on November 21, 2026
IT Services Agreement is a working document, not a decorative PDF. It should let a later reader identify the parties, purpose, scope, evidence, money, timing, approvals and limits without reconstructing the matter from email or memory. This US master is built around those control points.
The Jotform source is a demand signal, but its drafting is incomplete: The source hard-codes 24/7 support and vague priority language, and omits service credits, change control, subcontractors, data-processing roles, backup/recovery, IP, acceptance, liability, insurance and exit assistance. This version adds explicit decisions, assumptions, response paths, records and a jurisdiction prompt without claiming that a template is approved or sufficient everywhere.
This master turns an IT service description into an operational agreement. It makes service levels, responsibilities, data roles, security, changes and exit visible without claiming a particular security certification.
Tap any highlighted blank in the document below and type straight into it.Free — no sign-up, no watermark
IT Services Agreement
- Primary party:
- Other party / recipient:
- Effective or issue date:
- Jurisdiction:
1. Purpose and background
2. Services, service levels and responsibilities
3. Money, timing and evidence
4. Safeguards and limitations
5. Response or approval
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:
What this document is for
Use it after defining the systems, data, support boundaries, priority levels, maintenance, client responsibilities and handoff to any data-processing addendum.
Use it when the parties need a dated record that separates facts from assumptions and shows what still requires an official form, permit, inspection, disclosure, licence or professional review. Label the signature accurately as approval, acknowledgement, consent or agreement.
For a continuing relationship, attach the schedule, policy, inventory, evidence and amendments that make the document intelligible at the next review.
What the source leaves out
The source is product-led and leaves important operational choices in unlabelled blanks. That creates risk when a user assumes that a generic clause allocates a permit, deposit, safety, privacy, title, acceptance, tax or cancellation obligation.
The source hard-codes 24/7 support and vague priority language, and omits service credits, change control, subcontractors, data-processing roles, backup/recovery, IP, acceptance, liability, insurance and exit assistance.
Do not use it to promise cybersecurity compliance, uptime, privacy or data recovery without matching controls, evidence, service scope and applicable law.
How the improved document is structured
The agreement separates scope, service levels, client inputs, fees, changes, security, data, incident response, subcontractors, IP, warranties, liability, termination and transition.
The fillable version uses named clauses rather than numbered cross-references. Optional blocks can be switched off without leaving broken references. Keep attachments named and dated; a blank field should trigger a decision, not silently mean “not applicable.”
The page guide explains the document-specific choices, common failure modes and handoff points so the user can decide whether the document is the right instrument before completing it.
US legal and compliance boundaries
NIST SP 800-171 Rev. 3 describes requirements for systems handling CUI and external service-provider responsibilities, but it is not a universal IT contract requirement or certification. Match the agreement to the actual environment and obligations.
Federal guidance is only one layer. State, county, city, tribal, industry, contract and professional rules may change the result. This master therefore uses a jurisdiction field, identifies the limits of the cited source and avoids statements such as “compliant,” “approved,” “enforceable” or “attorney reviewed.”
If the matter involves a minor, consumer credit, employment restrictions, hazardous materials, a public accommodation, a regulated food operation, a real-estate closing, a lien, a franchise disclosure or a disputed claim, obtain the applicable local review before relying on the document.
Recordkeeping, privacy and evidence
IT services may process credentials, logs, customer records and sensitive data. Define access, roles, minimisation, incident notice, return/deletion and evidence without putting secrets in the form.
Collect only information needed for the stated purpose. Keep contact, payment, health, identity, employee, customer and security details in the appropriate controlled workflow. Record who approved the document, which attachments were reviewed, how it was delivered and when it should be refreshed.
Do not use the form to store passwords, payment-card data, diagnoses, unsupported accusations, copied third-party content or a blanket release of rights.
When not to use it
Do not use it as a data-processing agreement, security plan, incident report, software licence, cloud terms or government contract clause without adapting it.
Do not use this template in place of a government form, official disclosure, permit, inspection certificate, title document, tax filing, insurance policy, court filing or professional opinion. Where facts are high-value, contested, safety-critical or regulated, pause and obtain appropriate advice.
The disclaimer is deliberately conservative: it tells the user what the template cannot prove rather than adding credentials or a promise of outcome.
Clause-by-clause guide
- Services and exclusions
- Services and exclusions: identify the responsible party, source evidence, timing, approval and follow-up. Keep the field narrow enough to avoid collecting unrelated sensitive information. This clause is a decision point in the it services agreement, not boilerplate that can be copied into a different document.
- SLA, priority and maintenance
- SLA, priority and maintenance: identify the responsible party, source evidence, timing, approval and follow-up. Keep the field narrow enough to avoid collecting unrelated sensitive information. This clause is a decision point in the it services agreement, not boilerplate that can be copied into a different document.
- Fees and change control
- Fees and change control: identify the responsible party, source evidence, timing, approval and follow-up. Keep the field narrow enough to avoid collecting unrelated sensitive information. This clause is a decision point in the it services agreement, not boilerplate that can be copied into a different document.
- Data roles and security
- Data roles and security: identify the responsible party, source evidence, timing, approval and follow-up. Keep the field narrow enough to avoid collecting unrelated sensitive information. This clause is a decision point in the it services agreement, not boilerplate that can be copied into a different document.
- IP, subcontractors and insurance
- IP, subcontractors and insurance: identify the responsible party, source evidence, timing, approval and follow-up. Keep the field narrow enough to avoid collecting unrelated sensitive information. This clause is a decision point in the it services agreement, not boilerplate that can be copied into a different document.
- Termination, transition and deletion
- Termination, transition and deletion: identify the responsible party, source evidence, timing, approval and follow-up. Keep the field narrow enough to avoid collecting unrelated sensitive information. This clause is a decision point in the it services agreement, not boilerplate that can be copied into a different document.
US compliance checklist
Use this checklist before sending or signing the it services agreement. It is a research and handoff checklist, not a certification.
Define systems, data and service boundaries
Before using this it services agreement, verify the facts, owner, evidence, jurisdiction, timing and storage path. If the item depends on a permit, official form, professional inspection, consumer disclosure, safety rule or local practice, record the source and use the required process instead of treating this template as proof.
NIST SP 800-171 Rev. 3Set measurable service levels
Before using this it services agreement, verify the facts, owner, evidence, jurisdiction, timing and storage path. If the item depends on a permit, official form, professional inspection, consumer disclosure, safety rule or local practice, record the source and use the required process instead of treating this template as proof.
Allocate client and provider responsibilities
Before using this it services agreement, verify the facts, owner, evidence, jurisdiction, timing and storage path. If the item depends on a permit, official form, professional inspection, consumer disclosure, safety rule or local practice, record the source and use the required process instead of treating this template as proof.
Check data-processing and incident duties
Before using this it services agreement, verify the facts, owner, evidence, jurisdiction, timing and storage path. If the item depends on a permit, official form, professional inspection, consumer disclosure, safety rule or local practice, record the source and use the required process instead of treating this template as proof.
Document subcontractor and recovery controls
Before using this it services agreement, verify the facts, owner, evidence, jurisdiction, timing and storage path. If the item depends on a permit, official form, professional inspection, consumer disclosure, safety rule or local practice, record the source and use the required process instead of treating this template as proof.
Plan exit, return and deletion
Before using this it services agreement, verify the facts, owner, evidence, jurisdiction, timing and storage path. If the item depends on a permit, official form, professional inspection, consumer disclosure, safety rule or local practice, record the source and use the required process instead of treating this template as proof.
How to complete this template
- Confirm the instrument. Check that a it services agreement is the right document and that no official form or mandatory process applies.
- Gather the facts. Enter parties, purpose, scope, money, timing, jurisdiction, evidence and attachments. Keep assumptions visibly labelled.
- Check the rules. Review the cited source, then verify state and local rules, contracts, policies, permits, licences, disclosures and professional requirements.
- Review and approve. Give the affected party or counterparty a chance to correct facts. Label the signature and record the approver.
- Store and review. Store the final document with attachments, restrict access and set a review date for changes in facts, policy, product or law.
Frequently asked questions
Is this a legally approved form?
No. It is a structured starting point. Its usefulness depends on accurate facts, the actual relationship, the applicable jurisdiction and any required official form or professional review.
What should I attach?
Attach the schedules, specifications, inventory, plans, disclosures, approvals, policies, permits, evidence or payment records that the document refers to. Name each attachment and record its date or version.
Can I use it in every state?
No. State and local rules can change the required wording, process, notice, deposit, licence, disclosure or enforceability. Use the jurisdiction field as a prompt for current research.
Does signing guarantee compliance or enforcement?
No. A signature records assent or acknowledgement only to the extent the wording and law give it that effect. It does not cure an unlawful term, missing permit, inaccurate fact or required official process.
How should sensitive information be handled?
Use the minimum necessary information, restrict access, separate health, payment and security data where appropriate, and retain the request, approval, delivery and final version in the correct system.
What if the other party disputes the facts?
Pause the document, identify the disputed item, preserve supporting evidence, give the affected person or counterparty a fair correction or response route, and obtain appropriate review before relying on the disputed statement.
Related templates
Disclaimer
This template and guide are general information and drafting assistance only, not legal, tax, employment, privacy, accounting, safety, licensing or professional advice. No attorney, agency or other professional has reviewed your facts or approved this document. Rules differ by jurisdiction and change over time; verify current federal, state and local requirements before relying on it.


