Product · free template

IT Change Request

Three-page request to change a live system: what changes and why, who is affected, timing, testing and rollback, communications and approval.

A ready-to-use technology, saas & dev form for engineering, IT and product teams: 32 questions, 3 pages, 4 conditional rules.

Questions
32
Pages
3
Layouts
classic
Time to complete
≈ 14 min
Conditional rules
4
Preview it in the gallery

Searches this template answers

Also filed under

Live preview and test console

This is the real form. Answer it to test the flow — nothing is sent or stored.

Page 1 of 3 — The change

What is changing, and why now?

What is driving it?

This template runs as a straight sequence — no branching rules.

Compliance checklist

Ready to publish
  • Payment items priced — passingEvery payment question charges a real amount, so a submission always records a payment.
  • Conditional logic resolves — passingEvery rule points at a question or page that exists in this template.
  • Legal text not required — passingThis template collects neither health nor regulated financial information.
  • Question labels unique — passingLogic and exports address questions by label, so duplicates are ambiguous.

What happens after submit: nothing is stored in this preview. On your own copy, every response triggers an instant email notification and lands in your response dashboard, ready to export or forward.

Happy with it? Take a copy into your workspace — every question, rule and setting comes with it.

Who this template is for

IT Change Request is built for engineering, IT and product teams who need to route technical requests with the context needed to triage them.

  • Engineering, IT and product teams working in technology, saas & dev.
  • Teams who need to route technical requests with the context needed to triage them without writing code or paying for a custom build.
  • Anyone replacing vague reports that can't be reproduced or prioritised with one structured record per enquiry.
  • Respondents are users, testers and internal stakeholders — the form asks them 32 questions across 3 screens.

Why this form is useful

It removes the cost of vague reports that can't be reproduced or prioritised and turns each submission into a record your team can act on immediately.

  • 24 questions are required, so submissions arrive complete instead of needing a follow-up email.
  • It accepts a document or photo upload as evidence.
  • It records a signature you can keep as proof of agreement.
  • It pins the request to a specific date.
  • It allows multiple selections without free text.
  • It captures a numeric value you can filter and sort on.
  • Conditional logic hides 4 questions until they are relevant — shorter forms convert better than long ones.
  • Splitting the form across 3 pages keeps each screen short and shows respondents how much is left.

How to use this template

From copy to live form is a few minutes of work, and every step is reversible.

  1. 1Press “Use this template” — a fresh copy of IT Change Request lands in your workspace, ready to edit.
  2. 2Rename or delete any question, and change what is required. Nothing here is fixed.
  3. 3Open Notifications and add the email addresses that should be alerted on each submission; add an auto-reply to the respondent if the form collects an email address.
  4. 4Check the upload limits on the file question so respondents can attach what you actually need.
  5. 5Publish it, then either share the link directly or paste the embed snippet into your site — the embedded form resizes to fit and loads no marketing or advertising trackers.
  6. 6Watch responses land in Submissions, where you can filter, label and export them to CSV or PDF.

Logic and conditions blueprint

Exactly how this form behaves as it is answered — 4 conditional rules ship with it.

  • Features conditional validation: if “Will anyone lose access while the work happens?” is Yes, “Who loses access, and for how long” becomes mandatory before the form can be sent.
  • Features conditional validation: if “Has this been tested somewhere other than live?” is No, “Why it cannot be tested first” becomes mandatory before the form can be sent.
  • Features conditional validation: if “Can the change be undone?” is No, “What the plan is if it goes wrong” becomes mandatory before the form can be sent.
  • Features conditional validation: if “Does it need to happen outside working hours?” is Yes, “Preferred window outside hours” becomes mandatory before the form can be sent.
  • All 4 rules are editable in the Logic tab, and the built-in checker warns about rules that contradict each other.

About this template

Changes to live systems go wrong in predictable ways: nobody knew who depended on the thing being changed, and there was no agreed way back. This three-page form asks about both before any work is scheduled, in language a service owner outside IT can still follow. The first page covers what is changing and why, the systems and services affected, who requested it, whether it fixes a current problem or prevents a future one, and what happens if it is not done. The second page covers risk and preparation: who is affected and how many people, whether anyone loses access during the work, what has been tested and where, how long the change takes, how long a return to the previous state takes, and what the specific signal would be that the change has failed. The third page covers timing and communication: proposed window, whether it must be outside working hours, who needs telling and when, who is on hand during the change, how success will be confirmed, and approval. No jargon appears in what a requester reads.

What this form asks

Every question is editable — rename it, make it optional, or delete it entirely.

Page 1 — The change

  • Requested byrequired
  • Teamrequired
  • Short title for the changerequired
  • What is changingrequired
  • Why it needs to happenrequired
  • Systems or services affectedrequired
  • What is driving it?required
  • What happens if this is not done
  • Wanted byrequired

Page 2 — Risk and preparation

  • People affectedrequired
  • Who is affected, and howrequired
  • Will anyone lose access while the work happens?required
  • Who loses access, and for how long
  • Has this been tested somewhere other than live?required
  • Why it cannot be tested first
  • Expected duration in minutesrequired
  • Can the change be undone?required
  • Minutes needed to put things back
  • What the plan is if it goes wrong
  • The signal that would tell you it has failedrequired
  • Risk if it goes wrongrequired

Page 3 — Timing and approval

  • Proposed daterequired
  • Proposed start timerequired
  • Does it need to happen outside working hours?required
  • Preferred window outside hours
  • Who needs tellingrequired
  • Hours of notice to give
  • Who is available during the changerequired
  • How success will be confirmedrequired
  • Service ownerrequired
  • Attach plan, test results or supplier notes
  • Approved byrequired

32 questions in total.

Example of a completed IT change request form

Shows how a change might be described, including its risk, rollback plan and who needs telling.

Requested by
Naomi Fischer
Short title for the change
Upgrade email filtering rules
What is changing
Spam filter thresholds will be tightened for all inboxes
Systems or services affected
Company email
Wanted by
2026-03-15
People affected
120
Can the change be undone?
Yes
Who needs telling
All staff, IT support desk

Sample data — no real people, addresses or records are shown.

How the form changes as it's filled in

This template ships with 4 conditional rules, grouped into 4 behaviours driven by 4 questions. Everything below is already set up — edit or delete any rule once the template is in your workspace.

Driven by “Will anyone lose access while the work happens?”

  • Makes answers required

    If “Will anyone lose access while the work happens?” is Yes, “Who loses access, and for how long” becomes required before the form can be submitted.

Driven by “Has this been tested somewhere other than live?”

  • Makes answers required

    If “Has this been tested somewhere other than live?” is No, “Why it cannot be tested first” becomes required before the form can be submitted.

Driven by “Can the change be undone?”

  • Makes answers required

    If “Can the change be undone?” is No, “What the plan is if it goes wrong” becomes required before the form can be submitted.

Driven by “Does it need to happen outside working hours?”

  • Makes answers required

    If “Does it need to happen outside working hours?” is Yes, “Preferred window outside hours” becomes required before the form can be submitted.

Set it up step by step

  1. 1

    Ask for the failure signal

    The most useful field is the one naming how you would know it failed, because it forces a check rather than a hopeful look.

  2. 2

    Pair it with the maintenance notice

    Once approved, use the maintenance window notice to tell everyone; keep the technical plan and the announcement separate.

  3. 3

    Refuse untested high-risk changes

    The form makes 'not tested' an explicit answer with a reason, so the decision to proceed anyway is a recorded one.

  4. 4

    Keep the language plain

    Service owners outside IT approve these, so no acronyms in anything they read; put detail in the attachment instead.

Mistakes to avoid

  • Planning a change with no way back, discovered only when the change fails at midnight.
  • Counting affected people as 'some users', so nobody can judge whether the risk is acceptable.
  • Announcing to everyone every time, which trains people to ignore the announcements that matter.

What it pairs with

Most teams don't run this form on its own. These are the forms and systems it sits next to.

What to do with the responses

Approve or send back with questions, schedule the window, announce it through the maintenance notice, and record afterwards whether the success check passed.

Works in this layout

Browse classic templates

Forms that overlap this one

These pages cover the same subject ground as the it change request, matched on the words people actually search for.

Frequently asked questions

How is this different from an incident postmortem?

A postmortem looks back at something that already broke. This looks forward at a planned change, and asks how you would undo it.

Do small changes need one?

Set a threshold: anything affecting other people's access or customer-facing systems needs one; routine work should not be slowed down.

Who approves it?

The service owner for the affected system, not just the person doing the work. That separation is the point of the form.

What if a change is urgent?

Fill the same form afterwards with the same honesty, especially the risk and rollback answers, so emergency changes are still visible.

Is the IT Change Request template free to use?

Yes. You can preview and test IT Change Request on this page without an account, and take a copy into your own HelloForms workspace on the free plan. There is nothing to install and no card required to publish it.

What does the IT Change Request template ask for?

It asks 32 questions across 3 pages, 24 of which are required. Every question is listed in full further down this page, and each one can be renamed, reordered, made optional or deleted after you copy the template.

Can I edit the IT Change Request form after copying it?

Yes — the copy is entirely yours. Change wording, add or remove questions, switch between the classic layout, restyle it to match your brand, and set who gets notified on each submission.

How does the conditional logic in this technology, saas & dev form work?

4 conditional rules ship with the template: Features conditional validation: if “Will anyone lose access while the work happens?” is Yes, “Who loses access, and for how long” becomes mandatory before the form can be sent. Features conditional validation: if “Has this been tested somewhere other than live?” is No, “Why it cannot be tested first” becomes mandatory before the form can be sent. Features conditional validation: if “Can the change be undone?” is No, “What the plan is if it goes wrong” becomes mandatory before the form can be sent. All rules are editable in the Logic tab.

Where do responses to the IT Change Request form go?

Submissions land in your workspace under Submissions, where you can search, filter, label and export them to CSV or PDF. You can also email a notification to your team on every submission and send the respondent an auto-reply.

Can I embed the IT Change Request form on my own website?

Yes. Publish the form and paste the embed snippet into any page or share the direct link. The embedded form resizes to fit its container and loads no advertising or marketing trackers inside the iframe.

Can respondents upload files?

Yes. This template includes a file upload question, so respondents can attach documents or photos with their answers. You can adjust the accepted file types and size limits on that question.

Is the signature on this form legally usable?

The template captures a drawn signature and stores it with the submission, along with the timestamp, so you keep evidence of who agreed and when. Whether that is sufficient depends on your jurisdiction and the agreement itself.

Related templates

More forms teams pair with the it change request.

Related categories

All Technology, SaaS & Dev templates