Technology, SaaS & Dev · community shared

Hardware Request — shared by the community

Clara D. shared this 13-question build with 3 conditional rules already wired up. Test it below, then take a copy.

A ready-to-use technology, saas & dev form for engineering, IT and product teams: 13 questions, 1 page, 3 conditional rules.

Shared by
Clara D. · Non-profit programme lead
Questions
13
Replies
18
Copies taken
159
See the library version

hardware request form, it equipment request form online, laptop request form for employees, computer equipment order form, staff device request form, hardware request, hardware request forms, hardware request template, online hardware request, hardware, hardwares, request, requests, screen, equipment, person, needs, where, support form, bug report, ticket form, issue report, helpdesk, it request, feature request, saas form, technical intake, service desk, hardware request example, shared hardware request

Live preview and test console

This is the real form. Answer it to test the 3 conditional rules — nothing is sent or stored.

What do you need, and when?

What is needed
Is this a replacement or an extra item?
Is anything about the request non-standard?
Do you need it delivered or will you collect it?

Draw your signature with a mouse or finger.

3 questions are hidden by conditional logic right now — change an answer above to reveal them.

Works for you? Take Clara D.'s copy into your own workspace — questions, rules and settings included.

Who this template is for

Hardware 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 13 questions across 1 screen.
  • Mobile-heavy audiences, thanks to the one-question-per-screen card layout.

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.

  • 10 questions are required, so submissions arrive complete instead of needing a follow-up email.
  • It records a signature you can keep as proof of agreement.
  • It pins the request to a specific date.
  • It captures a full postal address.
  • It allows multiple selections without free text.
  • Conditional logic hides 3 questions until they are relevant — shorter forms convert better than long ones.
  • Every response is stored, searchable and exportable, so nothing depends on one person's inbox.

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 Hardware 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. 4Publish 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.
  5. 5Watch 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 — 3 conditional rules ship with it.

  • Features advanced show logic: if “Is this a replacement or an extra item?” is Replacing something faulty, the form dynamically exposes “Asset tag and what is wrong with it”. Otherwise that question never appears.
  • Features advanced show logic: if “Do you need it delivered or will you collect it?” is Delivered, the form dynamically exposes “Delivery address”. Otherwise that question never appears.
  • Features advanced show logic: if “Is anything about the request non-standard?” is Yes, the form dynamically exposes “What is non-standard, and why it is needed”. Otherwise that question never appears.
  • All 3 rules are editable in the Logic tab, and the built-in checker warns about rules that contradict each other.

What this form asks

Equipment request

  • Who is it forrequired
  • Team or departmentrequired
  • What is neededrequired
  • What they need it forrequired
  • Is this a replacement or an extra item?required
  • Asset tag and what is wrong with it
  • Is anything about the request non-standard?required
  • What is non-standard, and why it is needed
  • Do you need it delivered or will you collect it?required
  • Delivery address
  • Needed byrequired
  • Managerrequired
  • Manager approvalrequired

Conditional logic in this build

  • WhenIs this a replacement or an extra item?is Replacing something faulty, showAsset tag and what is wrong with it”.
  • WhenDo you need it delivered or will you collect it?is Delivered, showDelivery address”.
  • WhenIs anything about the request non-standard?is Yes, showWhat is non-standard, and why it is needed”.

Questions about this shared form

How is this different from a helpdesk ticket?

A ticket fixes a problem with equipment someone has. This asks for equipment they do not have, so it needs approval, delivery and a stock check.

Should it ask for a specification?

No. Ask what the work is; IT chooses the specification. Requesters guessing at specifications either over-order or under-order.

Does it work for a new starter?

It can, but the new user account request covers a starter's whole setup, including access, so use that as the primary request.

Who approves a personal-preference upgrade?

The manager signs, and the non-standard field makes the reason visible so the decision is not made silently by IT.

Is the Hardware Request template free to use?

Yes. You can preview and test Hardware 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 Hardware Request template ask for?

It asks 13 questions across 1 page, 10 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 Hardware Request form after copying it?

Yes — the copy is entirely yours. Change wording, add or remove questions, switch between the card and classic layouts, 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?

3 conditional rules ship with the template: Features advanced show logic: if “Is this a replacement or an extra item?” is Replacing something faulty, the form dynamically exposes “Asset tag and what is wrong with it”. Otherwise that question never appears. Features advanced show logic: if “Do you need it delivered or will you collect it?” is Delivered, the form dynamically exposes “Delivery address”. Otherwise that question never appears. Features advanced show logic: if “Is anything about the request non-standard?” is Yes, the form dynamically exposes “What is non-standard, and why it is needed”. Otherwise that question never appears. All rules are editable in the Logic tab.

Where do responses to the Hardware 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 Hardware 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.

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.