Overview
Information collection in construction is often messy. A subcontractor sends a text. A project request comes in through email. A new employee's onboarding details are scattered across a conversation. None of it is structured, searchable, or consistent.
Structur's form builder, built into Standard Operating Procedures, lets you create custom forms for collecting any kind of structured information, from lead capture and employee onboarding to project requests, feedback, and safety data. Once published, team members or stakeholders can submit the form and the entries are saved directly in Structur.
Forms replace the informal, fragmented ways information gets collected with a single, structured process that works the same way every time.
Understanding Forms
What It Does
Structur's form builder allows you to:
Create custom forms inside your Standard Operating Procedures with any combination of field types
Use field types like Text Field, Text Area, Dropdown, Radio Buttons, Checkboxes, Date Picker, and File Upload, to collect exactly the information you need in the format you need it
Configure field settings - including labels, placeholder text, required fields, and field descriptions, so every field is clear and purposeful
Customize the submit button text and the success message shown after a form is submitted
Save and publish forms to make them immediately accessible to your team or stakeholders
Capture structured entries that are stored in Structur rather than lost in email chains or text threads
When to Use It
Forms deliver the most value when you need to collect structured, consistent information from multiple people or on a recurring basis:
Lead capture - gather information from potential clients with a structured intake form that collects every piece of information you need before a first conversation
Employee onboarding - streamline the onboarding process by collecting essential employee information in one structured form rather than through back-and-forth emails
Project requests - allow clients or team members to submit project requests with all necessary details already included, so nothing is missing when you review them
Feedback collection - gather structured feedback from clients, employees, or project stakeholders in a consistent format that makes responses easy to review and act on
Safety data - create digital safety forms for job sites that capture consistent information from every submission
Step-by-Step Instructions
1. Navigate to Standard Operating Procedures
From your Structur dashboard, click on the Company Operations menu
Navigate into the Standard Operating Procedures area
This is where all your company's SOPs, procedures, checklists, and operational tools, including forms, are stored.
2. Navigate to the Right Department
Within the SOPs area, select the department that the form belongs to
Examples:
An employee onboarding form → Human Resources / Onboarding department
A project request form → Project Management or Sales department
A safety incident form → Safety department
A client feedback form → Operations or Quality department
A lead intake form → Sales / Preconstruction department
Placing the form in the relevant department means your team finds it alongside the related procedures and workflows.
3. Add a New Page
Once you're in the correct department, click New Page
Insert the page name and set privacy settings
4. Create "Form" Content
From the new page created, click on New Element to add the Form content type
Select New Form
Give the new content type a title
5. Give Your Form a Clear Title
Enter a descriptive title that clearly reflects the form's purpose.
Examples:
"New Employee Onboarding Form"
"Project Request Form"
"Client Feedback Form"
"Job Site Safety Inspection Form"
"Subcontractor Lead Intake Form"
6. Add Form Fields
Click the Manage Field button
Choose the appropriate field type for the information you're collecting:
Text Field - for short text entries such as name, email address, or phone number
Text Area - for longer text entries such as a project description, special instructions, or open-ended comments
Dropdown - for selecting one option from a predefined list, such as a project type or department
Radio Buttons - for selecting one option from a visible list where all options should be shown at once
Checkboxes - for selecting multiple options from a list, such as applicable trades or required documents
Date Picker - for selecting a specific date, such as a start date or submission deadline
File Upload - for uploading files such as a signed document, a photo, or a certificate
7. Configure Each Field
For each field, set:
Field Label - the text displayed next to or above the field. Keep it clear and specific so there's no ambiguity about what information is being requested.
Placeholder Text - example text shown inside the field to guide the person filling it out (for example: "e.g., [email protected]" or "Describe the project scope")
Required Field - mark as required if the form can't be complete or useful without this information
Field Description - additional instructions or context that helps the person understand what to enter (useful for fields that need more explanation than the label provides)
8. Add All Fields
Repeat Steps 6 and 7 to add as many fields as the form requires
Only include fields for information you will actually use, every unnecessary field reduces completion rates
10. Save and Publish
Once you're satisfied with the form, save and publish it
The form is now accessible to your team from the Standard Operating Procedures
Best Practices
Only include fields you will actually use - every field you add is a field someone has to fill out. A form with 20 fields for information you rarely need will have lower completion rates and create more friction than a focused form with 8 essential fields.
Mark required fields deliberately - don't make every field required by default. Required fields should reflect the minimum information you genuinely need to act on the submission. Optional fields let people provide more context when relevant without blocking submissions.
Use placeholder text to clarify format expectations - if a field expects a specific format (a phone number, a date range, a particular type of file), put an example in the placeholder text. It reduces errors and back-and-forth.
Write a meaningful success message - a generic "form submitted" message misses an opportunity to set expectations. Tell the person what happens next: who reviews the submission, what the expected response time is, or what action they should take now.
Place the form in the department where your team will actually look for it - a project request form buried in the HR department won't get used. Put it where the relevant team members naturally navigate.
Keep form titles specific - "Form" is not a useful title. "New Subcontractor Onboarding Form" tells someone exactly what they're filling out before they open it.
Common Questions
Q: Where do forms live in Structur?
A: Forms are created and stored inside Standard Operating Procedures in Structur, within the department structure you've set up for your company's operations. They're accessible to team members from the SOPs navigation.
Q: What field types are available?
A: Seven types: Text Field (short text), Text Area (longer text), Dropdown (select one from a list), Radio Buttons (select one from a visible list), Checkboxes (select multiple from a list), Date Picker (select a date), and File Upload (attach a file). Use the type that best matches the information you're collecting.
Q: Can I make certain fields required?
A: Yes. Each field has a Required Field setting you can enable. Use it for fields where a submission without that information wouldn't be actionable.
Q: Can I add instructions to a field to explain what someone should enter?
A: Yes. Each field has a Field Description setting for additional instructions or context, and a Placeholder Text setting that shows example text inside the field itself. Use both to make your fields as clear as possible.
Q: Can I use forms for collecting client information or is it just for internal use?
A: The form builder is flexible and can be used for any kind of information collection, internal (employee onboarding, project requests, safety data) or external (lead capture, client feedback). Place and share the form appropriately based on who it's for.
Common Mistakes to Avoid
❌ Don't | ✅ Do |
Include every field you might ever need | Only include fields for information you will actually use, focused forms get completed; bloated forms get abandoned |
Make every field required | Mark only the fields that are genuinely necessary to act on the submission as required |
Use generic field labels like "Field 1" or "Information" | Write specific, clear labels that tell the person exactly what to enter |
Leave the success message as a default | Write a meaningful success message that confirms the submission and sets expectations about next steps |
Store forms in the wrong department | Place each form in the department where the relevant team members will naturally look for it |
Give forms vague titles like "Request Form" | Use specific titles: "New Project Request Form," "Job Site Safety Inspection Form" |