When to Use a Global Form vs. a Project-Specific Form

📄 When to Use a Global Form vs. a Project-Specific Form
 

Choosing between a global form and a project-specific form depends on how you want the form to be used, managed, and reused. Here’s a quick breakdown to help you decide.


✅ Use a Global Form When…

  • You want to standardize forms across your entire company or multiple teams
  • The form is part of a repeatable workflow (e.g., Daily Logs, Toolbox Talks)
  • You want to be able to import the same form into multiple projects
  • You're building a form that might be adjusted over time, and you want to keep a clean master template

✅ Use a Project-Specific Form When…

  • The form will only be used in one specific project
  • You want the form to be managed within the project only
  • You’ve imported a global form and want to customize it for that job
  • You want to modify form workflows for that specific project without affecting other projects/uses for the form

🔁 Common Use Cases

Use CaseBest Form Type
Company-wide FLHA formGlobal Form
Site-specific Deficiency LogProject-Specific Form
One-off inspection for a high-risk jobProject-Specific Form
Change Order request used on all jobsGlobal Form
Client quote with reusable structureGlobal Form
Special form for a unique subcontractor workflowProject-Specific Form

🧠 Pro Tips

  • Start with a global form to maintain consistency, then import it into a project if you need to make unique, project-specific changes.
  • Edits made to the project-specific version won’t affect the global template.
  • You can achieve most of the benefits of project-specific forms by using a global form with conditional logic configured for the form’s fields and workflow steps.

Was this article helpful?