Describe your infrastructure standards. Makeform builds a server request form for workload, environment, resource, network, ownership, cost, justification, and timing details.
Route server requests to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a request pattern, edit it, or send it to the Makeform builder. The structure is an example.
Audience
Application teams requesting a VM
Format
Provisioning intake with conditional specifications
Prompt size
354 chars
Example form structure
Provisioning intake with conditional specifications
Requester, technical owner, and cost center
Environment and server role
vCPU, RAM, and storage required
Network zone, ports, and dependencies
Business justification and target date
Suggested routing tags
New provision
Capacity change
Decommission
Ask for peak demand and growth alongside the requested size so reviewers understand the sizing reason.
Step 1
Specify
workload, environment, compute, storage, and network
Step 2
Justify
business need, sizing evidence, cost center, and date
Step 3
Review
ownership, architecture, security, and budget checks
Step 4
Provision
request enters provisioning
Why structured intake matters
Structured intake gives infrastructure teams workload, sizing, connectivity, ownership, and timing facts in one submission.
Capture resources, platform, and network requirements beside the workload assumptions that explain them.
Reveal database, production, urgent-change, or temporary-resource questions only when needed.
Give every reviewer the same identifiable request instead of scattered chat details.
One front door
Start with the request type, then display the fields and review path that match the work.
Collect server role, environment, operating system, sizing, connectivity, backups, monitoring, ownership, and desired delivery date.
Record current and requested values, utilization evidence, impact, maintenance window, and why the change is needed now.
Request related web, application, and database tiers with shared architecture, traffic assumptions, dependencies, and expiration dates.
Identify dependencies, shutdown timing, backup instructions, validation owners, and DNS, monitoring, and license cleanup tasks.
Build the intake
Begin with your usual request pattern, refine the technical questions, and publish one route into the provisioning queue.
List accepted request types, required specifications, and technical and budget reviewers.
Add platform choices, cost allocation, and follow-up questions by environment or role.
Notify reviewers with the ID, owner, date, justification, and technical details.
Tag requests as awaiting details, under review, approved, scheduled, or completed.
Form vs email vs ticket
A dedicated form can feed complete provisioning details into the workflow that tracks the work.
Field guide
Collect the details needed to size, connect, own, fund, schedule, and retire the resource.
Ownership
Identify the requester, technical owner, business owner, support team, and approver so reviewers and operations know whom to contact.
Workload
Ask about server role, expected users, activity schedule, peaks, growth, dependencies, and downtime tolerance.
Compute & storage
Record vCPU, memory, disk, performance tier, and growth. For changes, capture current values and utilization.
Platform & network
Capture platform, network zone, DNS, connections, ports, certificates, and dependencies. Use conditional fields for detail.
Operations
Ask for data classification, backups, monitoring, maintenance, recovery expectations, and patching ownership.
Timing & lifecycle
Separate target date from urgency and impact. Record expiration, shutdown, validation, and rollback dates when relevant.
Related tools
Connect server intake with service, software, access, change, support, and asset workflows.
Create a broader intake for IT services beyond provisioning.
Open toolCollect need, users, compatibility, ownership, and purchase inputs.
Open toolStructure API access by identity, environment, scope, owner, and need.
Open toolCapture implementation, impact, schedule, validation, and rollback details.
Open toolRecord infrastructure assets, owners, locations, status, and lifecycle.
Open toolFAQ
Practical answers for IT teams standardizing provisioning and resource-change intake.
It is structured intake for a new server, resource change, project environment, or decommission. It records requester, workload, environment, specifications, connections, ownership, cost, justification, timing, and review inputs.
Include requester, owners, service, role, environment, operating system, CPU, memory, storage, network, connections, backup, monitoring, data classification, cost center, justification, target date, lifespan, and approvers. Add current values and utilization for capacity changes.
Use an environment dropdown and conditional logic. Development may ask for ownership, sizing, access, and expiration. Production can reveal availability, recovery, monitoring, backup, maintenance, dependency, data, launch, and operational-ownership questions.
Yes. Start with request type, keep shared identity, ownership, justification, cost, and timing fields together, then reveal technical fields for provisioning, capacity change, project environment, or retirement.
Ask about workload first, offer approved choices, and reveal deeper fields only when needed. Explain terms such as network zone or recovery expectation, while leaving final sizing to review.
Yes. Collect reviewer and routing fields, label submissions by request type and environment, and send the complete response to an inbox, sheet, Slack channel, or connected workflow.
Yes. Makeform provides unlimited free forms and responses. Generate, edit, publish, and use the form without a response cap; the paid tier removes the Makeform badge.
Not necessarily. The form gathers server-specific details before review. Your service management system can track assignment, approval, implementation, and status. A connected workflow or request ID can align both records.
Replace vague server requests with review-ready intake.
