Request ownership
Identify responsible people.
Capture requester, work owner, supervisor, contractor, crew contacts, and an emergency contact where relevant.
- Requester and work owner
- Supervisor and crew contacts
- Area or asset owner
Describe the job, site, risks, and reviewers. Makeform creates a work approval form for scope, controls, files, decisions, and pre-start conditions.
Route work requests to email, Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, tailor it, or send it to the Makeform builder. Edit every example before publishing.
Audience
Employees and vendors requesting building work
Format
Request with manager and facilities review
Prompt size
248 chars
Example form structure
Request with manager and facilities review
Requester, building, and exact location
Scope, asset ID, and operational impact
Requested work window
Plans, photos, or supporting documents
Decision, conditions, and approved window
Suggested routing tags
Awaiting review
Approved with conditions
Returned for changes
Separate the requested start time from the approved start window. Reviewers may allow the job only after an isolation, inspection, or site handover is complete.
Step 1
Request
scope, site, people, timing, and attachments
Step 2
Assess
impacts, hazards, dependencies, and controls
Step 3
Decide
reviewers record status, conditions, and window
Step 4
Close
crew reports completion, issues, and follow-up
Control work before it begins
Scattered emails hide missing details and unclear decisions. A structured work approval form keeps scope, controls, reviewers, conditions, and timing together from request through closeout.
Required fields capture the exact area, asset, task, crew, and schedule before a reviewer spends time chasing basics.
Conditional questions can reveal isolation, access, shutdown, fire-watch, or equipment checks only when that work needs them.
Decision, reviewer, date, conditions, and approved window stay attached to the original submission and supporting files.
Designed for real jobs
Start with the workflow closest to your team, then replace generic questions with your sites, assets, reviewers, and internal control language.
Location, asset ID, access needs, occupant impact, vendor files, facilities decision, and approved schedule.
Task-specific hazard prompts, control confirmations, supervisor review, conditions, and post-work inspection.
Company contacts, worker list, method, equipment, supporting documents, access coordination, and site review.
Affected services, dependencies, communications, test plan, rollback steps, authorized window, and outcome.
Approval workflow
Build around what reviewers check, then connect the decision and closeout to the request.
Name work types, sites, required information, reviewers, outcomes, and closeout checks.
Require the scope, then reveal controls for hot work, shutdowns, roof access, or contractors.
Use notifications and tags so the correct manager or site representative sees each request.
Keep status, conditions, authorized timing, completion notes, issues, and follow-up together.
Email vs document vs online form
Approval is more useful when every reviewer sees the same scope and the crew can find the conditions attached to the final decision.
Field guide
The form should help a reviewer understand the proposed job, test readiness, set clear conditions, and hand the decision back to the people doing the work.
Request ownership
Capture requester, work owner, supervisor, contractor, crew contacts, and an emergency contact where relevant.
Scope and location
Ask for task, reason, exact area, asset ID, equipment, and boundaries. Attach plans or photos when needed.
Hazards and controls
Screen for energy, heat, height, excavation, confined areas, traffic, chemicals, dust, and public access.
Impact and coordination
Ask which services, occupants, utilities, alarms, or routes are affected and who must coordinate.
Review and decision
Capture outcome, reviewer, date, comments, conditions, and the exact authorized work window.
Closeout
Record finish time, testing, restored services, area checks, issues, photos, and follow-up work.
Related tools
Build companion forms for work intake, inspections, changes, equipment, incidents, and maintenance without forcing every task into one oversized form.
Collect the initial problem, location, priority, requester, and requested service before approval review.
Open toolTurn approved construction tasks into assigned scope, scheduling, materials, and completion records.
Open toolDocument requested scope, cost, schedule, and reason when planned work needs to change.
Open toolRun structured site or area checks before work starts and record items needing attention.
Open toolCapture equipment condition, defects, photos, and follow-up before tools or machines are used.
Open toolGive occupants and staff a simple way to report faults that may become planned work.
Open toolFAQ
Practical answers for managers, facilities teams, site coordinators, and contractors designing a pre-start review.
It is a structured pre-start request covering scope, location, timing, people, impacts, controls, files, reviewer decisions, and conditions. It supports internal authorization; teams must still follow separate site or authority requirements.
Include requester, owner, location, asset, scope, reason, crew, dates, impact, controls, access or shutdown needs, and files. Add decision, reviewer, conditions, approved window, and closeout.
Do not assume so. Use it for internal requests and permit references. Confirm site, work-type, and jurisdictional requirements with the responsible people before starting.
Yes. Conditional logic can reveal matching controls for hot work, excavation, height, shutdowns, contractors, or after-hours work while keeping shared scope fields.
Let reviewers select approved with conditions, list each condition, assign an owner and due point, then require pre-start confirmation.
Yes. Add review blocks for the area owner, facilities lead, manager, or site representative, each with decision, conditions, name, and date.
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and collect work requests without a form or response cap. The paid tier removes the Makeform badge.
Capture finish time, outcome, testing, restored services, area checks, photos, unresolved issues, and the follow-up owner.
Make the start decision clear.