Describe your project and review path. Makeform creates a construction submittal form for materials, shop drawings, product data, attachments, revisions, and reviewer decisions.
Route submittal records to email, Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a prompt, tailor the project details, or send it to the Makeform builder.
Audience
Trade contractors submitting proposed materials
Format
Cover sheet with specification and attachment fields
Prompt size
297 chars
Example form structure
Cover sheet with specification and attachment fields
Project, contractor, and subcontractor
Submittal number and specification section
Material, manufacturer, and supplier
Product data and sample photos
Reviewer status and comments
Suggested routing tags
Submitted
Revise and resubmit
Reviewed
Keep the submittal number and revision separate. The identifier follows the item; the revision distinguishes each review cycle.
Step 1
Prepare
identify the item, spec section, and revision
Step 2
Submit
attach coordinated drawings, data, and samples
Step 3
Review
record disposition, comments, and marked-up files
Step 4
Close
resubmit when needed and preserve the final record
Why structured submittals
Email attachments separate the package from its project identifiers, due dates, and decision. A structured intake keeps those details together from first submission through final revision.
Required project, submittal, revision, discipline, and specification fields make each package recognizable before anyone opens an attachment.
Collect drawings, product sheets, samples, warranties, and deviation notes in the same submission, with instructions tailored to the submittal type.
Give reviewers standard outcomes and space for comments and markups, then keep the decision beside the submitted files and review date.
Common packages
The cover data stays consistent while conditional questions capture what matters for materials, drawings, products, and revisions.
Record manufacturer, supplier, finish, sample details, availability, and the specification requirement being addressed.
Capture drawing titles, related sheets, coordination confirmations, fabrication lead time, revision, and drawing uploads.
Package model selections, technical sheets, warranties, maintenance information, and highlighted options for review.
Show prior comments beside responses, and disclose proposed deviations with their cost and schedule effects.
Submittal workflow
Start with register fields, then shape questions and routing around submitters and reviewers.
Name the trades, package types, identifiers, reviewers, and disposition choices.
Require specification and revision fields; reveal deviation questions only when applicable.
Publish a link with upload instructions and a requested response date.
Send records to reviewers and track open, returned, and completed cycles.
Form vs email vs spreadsheet
A register can summarize status, but the intake form is where complete, consistently labeled review records begin.
Field guide
Six field groups make the submission identifiable, reviewable, and easier to reconcile with a submittal register.
Project identity
Capture the project, location, companies, contacts, and dates so packages cannot drift between jobs.
Document control
Pair a stable submittal number with revision, discipline, title, specification, and related-document references.
Technical scope
Identify the material, product, manufacturer, model, finish, and applicable requirement.
Contractor review
Confirm that dimensions, quantities, field conditions, and connected work were checked; disclose exceptions clearly.
Impact and attachments
Collect technical files, lead time, required-on-site date, and stated cost or schedule effects.
Reviewer response
Record disposition, comments, markup, reviewer, and date; link resubmittals to the prior revision.
Related tools
Pair the review intake with tools for progress reporting, material ordering, changes, safety, bids, and field work.
Summarize completed work, constraints, photos, workforce, and upcoming activities.
Open toolIssue defined field tasks with location, scope, priority, assignee, and completion notes.
Open toolCollect comparable pricing, scope inclusions, exclusions, schedule, and bidder details.
Open toolRequest approved products with quantities, delivery dates, locations, and purchasing details.
Open toolDocument proposed scope changes and the cost, schedule, and approval information around them.
Open toolRun repeatable site observations with findings, photos, corrective actions, and follow-up ownership.
Open toolFAQ
Practical answers for contractors, project engineers, architects, and consultants organizing review packages.
It is the intake record used to send materials, shop drawings, product data, samples, and related documents for design-team review. It identifies the project, specification, revision, attachments, due date, and disposition.
Include project, contractor, contact, submittal number, revision, title, discipline, specification, dates, item description, attachments, deviations, contractor review confirmation, disposition, comments, reviewer, and review date. Add lead time when procurement timing matters.
Use labeled uploads for the current package, calculations, comparisons, and sample photos. Put the submittal number and revision in file names. Keep reviewer markups separate from submitted files.
Keep the submittal number stable and increment the revision. Cite the prior disposition, repeat open comments, explain responses, identify changed locations, and attach replacement files.
Yes. Use shared project and document-control fields, then conditional sections for materials, drawings, product data, samples, substitutions, or closeout documents.
Disposition meanings depend on the project documents and review procedure. Define labels with the project team. The form records the selection, comments, reviewer, and date; participants should follow the established process before procurement or installation.
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and collect construction submittals without a response cap. The paid tier removes the Makeform badge.
Use consistent project, number, revision, type, specification, reviewer, date, and disposition fields. Send them to your tracking destination and keep uploads linked to each submission.
Turn every review package into a traceable record.
