IT request form templates

An IT request form records what someone needs from IT — a laptop, an account, a VPN connection, a change to a system that is already running — with enough context that whoever picks it up does not have to ask twice. This collection gathers the formformform templates built for that task, from a hardware request that tells a replacement apart from a new issue to a disposal request that asks whether the device still holds data.

7 templates3 categoriesLast updated

An IT request is a request for something someone does not have yet: a machine, an account, a connection, or a change to a system that is already running. Most of these templates sit in formformform's IT & Technology forms, but not all of them, because the task crosses shelves — retiring a device lives in operations forms, where finance and facilities care about a disposal as much as IT does, and a seat on a learning platform lives in education forms, because the person filling that one in may be a student rather than an employee. Membership here follows the task rather than the category: if a form's job is to tell an IT team what someone needs and why, it belongs on this page.

All of them open the same way — a name, an email address, and the department or programme the request comes out of — so read past the third question before you compare them. What separates these forms is the single field that decides the answer. On the asset request it is Request Type, New Asset or Replacement for Existing Asset, with Current Asset Tag hanging off the second one. On the software access request it is Access Level Needed, a ladder whose two ends — View / Read-Only and API / Integration Access — are a two-minute grant and a conversation with whoever owns security. On the remote access request it is Device Type for Remote Access, Company-Issued Device or Personal Device, the answer that decides whether the traffic ever touches an unmanaged machine. On the change request there is no approver named anywhere; the gate is technical instead. Work out which field carries that weight on your form and the rest of it more or less writes itself.

Look closely at the labels above and you can see the constraint that bites this form type hardest. Current Asset Tag (if replacement). Device Description (if personal device). Office Location (if in-office or hybrid). If 'Other', specify software or system name. Those parentheses are doing work that branching logic should be doing: formformform's template generator writes every field flat and always visible, so a condition that ought to hide a question until it is relevant has been written into the question's label instead. The product itself is not missing the feature — clone any of these templates, open the editor, and reveal Current Asset Tag only once someone picks Replacement for Existing Asset, or the personal-device description only once someone picks Personal Device. That is a few minutes of work, and it is the difference between a ten-question form and one that feels like five.

7 templates, and when to use each

Every one is free to open, edit and publish. The line under each name is what separates it from the others here.

  • IT Asset Request Form

    Reach for this when the thing being asked for is physical — its Asset Type dropdown runs from Laptop and Monitor through Headset, Webcam and Docking Station — and it is the one member that treats a replacement differently from a first issue: Request Type splits New Asset from Replacement for Existing Asset, and Current Asset Tag records the machine coming back the other way.

    Streamline equipment requests with a structured IT asset request form.

  • Software Access Request Form

    Use it when the request is a seat in a named system rather than a device, and the argument is about how much power that seat carries: Access Level Needed runs View / Read-Only, Standard User, Editor / Contributor, Admin / Full Access, API / Integration Access, and it is the only member that asks for a Manager Approval Code — a reference someone was given before they opened the form, not a name typed into a box.

    Manage software access provisioning with a structured request and approval form.

  • Remote Access Request Form

    Pick this when the question is not whether someone gets in but from where and for how long — it is the only member that asks what machine the connection comes from (Company-Issued Device or Personal Device, with a Device Description for the personal case) and the only one that asks whether the access should ever end, setting Permanent / Ongoing against a Temporary option that asks for the end date in the justification box, with the connection itself pinned down by a Remote Access Type Required dropdown running VPN (full network access), VPN (split tunnel), Remote Desktop Protocol (RDP), Cloud Application Access (SSO), SSH / Server Access and Other.

    Manage VPN and remote desktop access requests with security review built in.

  • New Employee IT Setup Request

    Use it when the request is filed about someone rather than by them — it is the only member whose email field is optional, because the label reads New Employee Work Email (once created) and the account does not exist yet — and the only one that bundles the whole day-one order into two checkbox lists, Equipment Needed and Software Access Needed on Day One, keyed off a required Start Date and a Role Type.

    Ensure new hires have everything they need on day one with a structured IT setup request.

  • LMS Access Request Form

    Use this one when the requester may not be on the payroll: it is the only member that accepts a student address (Work or Student Email Address) against a Department or Program, and the only one where what you are granting is content rather than a system — Courses or Content to Access is a required free-text list, and at eight questions it is the shortest form here.

    Manage employee or student access requests to your Learning Management System.

    8 questionsEducation Forms
  • Software Change Request Form

    Choose it when the system already exists and the ask is that it behave differently — Change Type runs from New Feature and Bug Fix through Upgrade / Version Update, Deprecation / Removal and Security Patch — and note it is the only member with no approver field at all: the gate it imposes is technical instead, asking whether the change has been tested in a development or staging environment, and it inverts the usual justification into Business Impact if Not Completed.

    Manage software changes with a structured request, prioritization, and impact assessment.

  • Asset Disposal Request

    Use it for the other end of the lifecycle, when a device is leaving rather than arriving — it is the only member that requires an Asset Tag or Serial Number outright, and the only one that asks a data question, Does this asset contain data that requires secure wiping?, which is what decides whether the machine goes straight to a recycler or through a wipe first.

    Request asset disposal with reason, data-wiping needs, and manager authorization tracking.

    9 questionsOperations Forms

What these forms ask for

Question labels shared by more than one of the 7 templates above, counted once per template.

  • Department6 of 7 templates
  • Manager Name4 of 7 templates
  • Requester Name4 of 7 templates
  • Work Email4 of 7 templates
  • Access Needed By3 of 7 templates
  • Business Justification3 of 7 templates

What these forms are made of

These forms ask between 8 and 11 questions each, and 58 of the 68 questions across the set are required. Field types, counted once per template:

  • Date7 of 7 templates
  • Dropdown7 of 7 templates
  • Email7 of 7 templates
  • Short Text7 of 7 templates
  • Long Text6 of 7 templates
  • Radio6 of 7 templates
  • Checkbox1 of 7 templates

How to build an IT request form

  1. Decide first whether you are building a request or a report, because the two need different fields and should not share a queue: someone who wants a laptop is telling you about the future, someone whose laptop has died is telling you about the present.

  2. Identify the requester the way your directory does — a work email rather than a personal one, plus a department — and add the manager's name unless the request genuinely needs no second person, the way a change to a system you already own does not.

  3. Name the thing being asked for from a fixed list wherever one exists: an Asset Type dropdown, a list of the systems you actually license, a set of connection types. Free text gets you "the thing on my desk" and a follow-up email.

  4. Ask what level, not just what — read-only against admin, split tunnel against full VPN, temporary against permanent. That one field is usually what decides whether the request can be handled in a minute or needs a review first.

  5. Pair a justification field with a date field and require both. A needed-by date without a reason gives you a queue sorted by optimism, and a reason without a date gives you no queue at all.

  6. Add the branching in the editor after you clone, then send submissions to whatever tracker your team already works out of — a webhook drops the request into the queue you triage instead of an inbox you forget.

Who uses these forms

One audience per template, in the order the templates are listed above, taken from what each template names for itself.

IT departmentsIT administratorsIT security teamsHR teams coordinating onboardingCorporate L&D and HR departments managing LMS accessSoftware development teamsOperations managers

Frequently asked questions

Does submitting one of these forms actually grant the access or order the device?

No. A form records a request; it does not provision an account, raise a purchase order or open a ticket by itself. formformform stores the submission, emails you about it, and can post it to a webhook — from there whatever you already run picks it up, whether that is a ticket queue, a spreadsheet a coordinator works through, or someone reading their notifications. Treat every field on these templates as a fact you are capturing, not a switch you are throwing.

Should IT requests and IT problems go through the same form?

Keep them apart. A request is about something you do not have yet and can be scheduled; a broken laptop or a suspicious email is an incident and needs to jump the queue, so mixing them gives you one list you cannot triage. formformform has separate templates for the other half: the IT Help Desk Ticket, with an Issue Type list and a four-level Priority that runs up to "Critical — full outage or security incident", and the Security Incident Report Form, which asks what was affected and whether the incident is still ongoing. That second one sits in the incident report collection linked below.

Why do so many of these labels say "if replacement" or "if personal device"?

Because the templates ship without conditional logic. formformform's template generator writes every field flat and always visible, so a question that should only appear after a particular answer carries its condition in the label instead. The editor does support branching — clone the template, then hide Current Asset Tag until someone picks Replacement for Existing Asset, or the Device Description until someone picks Personal Device, and rewrite the label plainly once the logic is doing the work.

Can a requester attach a quote, a screenshot or a photo of the asset tag?

Not in the template as generated, but yes in the product. formformform's editor has an Upload field — up to 2 MB per file, and encrypted along with everything else on an encrypted form — it is simply not one of the field types the template generator can seed, so nothing on this page arrives with one. Clone the template and drag Upload in from the palette, or if you would rather have a link than a file, add a short text field and ask for the URL of the quote.

Does a manager approval field mean the request has been approved?

No, and it is worth being blunt about it internally. The asset disposal template asks for a Manager Approval Name and the software access template asks for a Manager Approval Code, but both are text the requester types in; the form does not check either one, cannot route the submission to that manager for a decision, and there is no signature field of any kind in formformform. If approval has to be real, get it before the form is filled in — the code field exists for exactly that pattern — or send the submission on to your approver by webhook and let the tool that already owns approvals record the decision.

Keep browsing

All IT & Technology form templates8 templates

Build yours in a few minutes

Open any template above, change what you need, and publish. Free during early access — no credit card, and no cap on how many responses a form can take.

Start free