Free HTML Change Request Form Generator

IT and web teams can take change requests from the business on an intranet page. The form captures type, target date, and details so CAB is not reading forwarded Outlook chains.

Form Builder

#3b82f6

How to Use This Form Generator

1

Create a Form ID

Notify the change manager or web editor.

2

Map types to your policy

Normal vs emergency in the copied select.

3

Prompt for URL and rollback

Edit the details placeholder.

4

Implement in your usual tool

Paste a ticket ID back to the requester by email.

What is a change request form?

A change request (CR) is a stakeholder asking to alter a live system: copy on a page, a firewall rule, a pricing table, a feature flag. US ITIL shops and UK public-sector IT both recognise the pattern. This HTML form is the front door for teams that do not yet have ServiceNow change management, or for marketing sites that will never live in the ITSM.

It is not an RFC 2119 spec and not a git pull request. Engineering still implements in the usual repo. The form creates a numbered-enough record of who asked and by when.

Enough for a CAB or a web editor

You need the outcome, the urgency, and a rollback hint. You do not need them to write the implementation plan.

  • Name and work email of the requester, not an intern’s personal Gmail.
  • Request type as standard, urgent, follow-up, other—or relabel to normal/emergency/standard.
  • Preferred date as the business go-live wish.
  • Details for URL/system, current vs desired, and who already approved commercially.

Emergency production incidents belong on the incident path, not this form. Say that on the page.

How changes are requested

Jira, ServiceNow, and Slack :change: emoji all exist. HTML is for business users who will never open Jira.

1. HTML on the intranet

The comms team can submit without an Atlassian licence.

2. ITSM change modules

Use when you need CAB calendars, CI linkage, and audit. Feed this form into that later.

3. Email the webmaster

No audit trail of who asked for the pricing typo.

4. Direct Slack to engineering

Fine for tiny teams; unsearchable after six months.

Static intranet and marketing-ops pages

A Confluence HTML macro or an internal GitHub Pages site can host the form.

Export CSV for CAB. Retention should match your change policy, which may be years in regulated US and UK environments.

Frequently Asked Questions

Is this ITIL compliant?

It is intake only. Compliance lives in how you assess, approve, and record the change afterwards.

Code changes?

Still use pull requests. This form is for the business ask that triggers the PR.

Urgent vs incident?

Incidents restore service. Changes alter it. Keep two paths.

Can we attach screenshots?

URL in details, or a file-upload form for the web team.

Similar Form Generators

Bug Report Form Generator

Capture repro steps, severity, and environment from users on your site.

Feature Request Form Generator

Let customers pitch product ideas with context, not a one-line tweet.

Suggestion Box Form Generator

A lighter intake than a feature request for culture, process, or UX niggles.