Describe your approval process. Makeform creates a structured employee intake with device, business need, licensing, manager, and IT review details.
Route software requests to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, tailor it to your IT policy, or send it to the editable builder.
Audience
Employees requesting approved desktop software
Format
Short request with manager approval
Prompt size
243 chars
Example form structure
Short request with manager approval
Employee, department, and manager
Software name, vendor, and version
Business reason and needed-by date
Device asset tag and operating system
Is a license already available?
Suggested routing tags
Manager review
Security review
Ready to install
Ask for the device asset tag and operating system version; a software name alone rarely gives IT enough information to assess compatibility.
Step 1
Request
software, user, device, and business need
Step 2
Review
manager, license, security, and compatibility
Step 3
Install
approved version deployed to the right device
Step 4
Close
requester notified and completion recorded
Why structured intake matters
A vague install message leaves IT chasing the device, version, license, owner, and deadline. The form collects them before review.
Require product, vendor, version, source, asset tag, operating system, and needed-by date for faster triage.
Separate approved tools from purchases, elevated utilities, and software that handles sensitive information.
Keep the need, decision, review notes, and outcome attached to one submission.
Fits common request paths
Choose the nearest workflow, then adapt its fields and routing to your IT policy.
Choose from a controlled list, identify the device, explain the need, and set a date.
Add quote, plan, seats, billing owner, cost center, alternatives, and budget approval.
Capture source, version, permissions, license, updates, network behavior, and project.
Request one version across a device group with scheduling, licensing, and testing details.
Request workflow
Give approvers and technicians useful context through one published employee request link.
Define requesters, required details, and answers that trigger manager, purchasing, security, or IT review.
Add your catalog and device conventions. Reveal cost or permission questions when relevant.
Share the form internally, then send submissions to the responsible inbox or connected workflow.
Capture review status, decision reason, technician, installed version, completion, and notification.
Form vs email vs generic ticket
Effective intake consistently captures device, ownership, cost, permission, and timing details before review.
Field guide
Six field groups cover ownership, software, device, need, review, and fulfillment.
Requester and ownership
Capture employee, department, manager, location, and contact so reviewers know the owner.
Software identity
Ask for vendor, exact version or plan, product page, installer source, and extensions.
Device and compatibility
Device context helps technicians package, schedule, and attach work to the correct computer.
Business need and timing
Explain the enabled work, why current tools fall short, and when it is required.
License, access, and review
Surface purchases, elevated permissions, network access, and company data for review.
Decision and fulfillment
Let the same record show decisions, assignment, installation, testing, and requester communication.
Related tools
Connect software intake with service, access, equipment, and purchasing requests.
Evaluate a new application, including purpose, ownership, cost, and review context.
Open toolCreate a broader intake point for internal technology services beyond application installs.
Open toolCollect justification, owner, duration, and reviewer context for elevated account access.
Open toolStructure API access requests around system, environment, purpose, scope, and ownership.
Open toolHandle devices and accessories when an employee needs hardware alongside software.
Open toolCollect user and role details when the application exists but the employee still needs access.
Open toolFAQ
Practical answers for IT administrators creating a consistent intake and approval path for employee software requests.
It is an internal form employees use to ask IT to install an application. It records the requester, product, version, business need, device, deadline, license, and required reviews.
Require requester, manager, software, vendor, version, source URL, justification, asset tag, operating system, and needed-by date. Add license, cost, permissions, data access, device count, and maintenance window as needed.
Ask whether a license exists or a purchase is needed. Reveal quote, plan, seats, billing, cost center, and budget fields only for paid requests.
Yes. Collect the manager and review triggers, then configure notifications or downstream workflows. Purchases can go to budget owners; elevated permissions or external transfers can go to designated reviewers.
Yes. Offer one device, named assets, or a managed group. For multi-device work, collect the group, device count, operating system, test contact, rollout window, and required date.
Yes. Makeform provides unlimited free forms and responses. The paid tier removes the Makeform badge.
Submissions appear in Makeform and can feed configured email or integration workflows, including Google Sheets, Slack, or Zapier. Keep decisions and fulfillment notes tied to one request identifier.
Record status, technician, approval notes, schedule, installed version, device, completion, test result, and notification. If changed or declined, record the reason for future reference.
Give software requests one clear front door.
