Describe your submittal workflow. Makeform creates a structured form for drawing identification, reviewer comments, disposition, revisions, and return dates.
Send review records to Google Sheets, Slack, and Zapier.
Sample prompts for the review form builder
Choose a scenario, revise it, or send it to the builder. Match the status language to your document-control procedure.
Audience
Architects reviewing cabinet and millwork shop drawings
Format
Drawing review form with sheet-level comments
Prompt size
379 chars
Example review form structure
Drawing review form with sheet-level comments
Project, spec section, and submittal number
Drawing number, title, and revision
Sheet or detail reference
Review comment and required action
Overall review status
Suggested routing tags
Approved as noted
Revise and resubmit
Coordination required
Use separate fields for the contractor's submittal number, drawing number, and revision; they answer different document-control questions.
Step 1
Identify
project, package, drawing, revision, and submitter
Step 2
Review
references, comments, markups, and coordination
Step 3
Decide
disposition, conditions, and required action
Step 4
Return
files, dates, owners, and resubmittal trail
Controlled reviews
Keep each comment, markup, and status with the exact package reviewed.
Require the submittal number, specification section, drawing number, and revision before disposition.
Pair each note with a precise drawing location and expected action.
Record disposition, open items, owner, return date, and resubmittal deadline together.
Different packages, one pattern
Change checks, reviewers, comment categories, and dispositions while keeping document control consistent.
Review finishes, dimensions, interfaces, details, and markups.
Organize member, connection, opening, embed, and coordination notes.
Route discipline comments on clashes, access, penetrations, and interfaces.
Compare previous comments with responses and new items.
Review workflow
Describe your identifiers and review rules, test the status paths, then share the form with the project team.
Name drawing types, identifiers, disciplines, dispositions, and dates.
Show resubmittal details and discipline checks when relevant.
Confirm references, statuses, attachments, and owners are clear.
Share the form and route completed reviews to document control.
Choose a review record
Choose between informal discussion and a repeatable document-control record.
Field guide
Separate document identity, comments, coordination, disposition, and closeout using your project's review terminology.
Project and package
Start with the submittal-register information needed to retrieve the correct package later.
Drawing identity
Bind every status to drawing numbers, titles, revisions, issue dates, and the documents reviewed.
Review responsibility
Record key dates, the lead, and contributing disciplines. Identify each comment's source and the final consolidator.
Itemized comments
Give each comment an ID, drawing location, category, requirement reference, action, owner, status, and matching markup.
Coordination and scope
Use focused checks for trade interfaces, dimensions, clearances, penetrations, access, supports, embeds, and adjacent systems.
Disposition and closeout
End with one project-defined disposition, conditions, returned files, and next action. Retain prior comment IDs on resubmittals.
Related tools
Build companion forms for submittals, drawing registers, changes, field work, and closeout.
Collect package identifiers, specification references, files, and response dates.
Open toolRegister drawing titles, disciplines, revisions, dates, and files.
Open toolRecord work, constraints, site conditions, photos, and upcoming activities.
Open toolDocument proposed changes, reasons, references, effects, estimates, and status.
Open toolAssign work with scope, location, dates, attachments, and status.
Open toolTrack closeout items by location, owner, due date, evidence, and status.
Open toolFAQ
Answers for project teams creating a consistent review record.
Include project and package IDs, specification section, submitting trade, drawing revisions, dates, reviewers, itemized comments, markups, coordination items, disposition, required actions, owners, and return date. Use the project's submittal terminology.
Common choices are Approved, Approved as Noted, Revise and Resubmit, and Rejected. Define each option and its next action using the project's document-control rules.
Give each comment a stable ID, drawing location, discipline, category, requirement reference, requested action, responder, markup, and status. A resubmittal can then address prior items individually.
Yes. List the assigned disciplines and tag each comment by discipline. Add a consolidation field for duplicate or conflicting notes and identify the lead reviewer for the overall disposition.
Capture prior and current revision IDs. Carry each previous comment forward with the contractor response, change location, and Addressed, Open, or Needs Clarification status. Record new comments separately.
No. It organizes identifiers, comments, attachments, status, and routing; it does not define review scope, transfer responsibility, or authorize fabrication. Configure it for the project's contracts, specifications, procedures, and reviewers.
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and reuse the form. The paid tier removes the Makeform badge.
Separate the received, due, completed, and returned dates. Assign a lead reviewer, document controller, and responder. Give every open comment an owner and next due date.
Replace scattered review emails with one structured record.
