What’s New in Forms - May '26
Forms in Hive have become more powerful and flexible, helping teams turn requests, submissions, and intake processes into organized, automated workflows.
Below is a breakdown of the latest Forms improvements and how they may impact your team’s experience.
Project Status Mapping from Forms
Forms can now map directly to a project’s status during submission.
What this means
When someone submits a form, their response can automatically update the associated project’s status.
For example:
A “New Request” form could automatically place a project into “Planning”
A “Ready for Review” submission could move work into “Approval Needed”
Why this matters
Reduces manual project updates
Keeps workflows more organized
Helps teams move work into the correct stage faster
Best practices
Only expose statuses that make sense for submitters
Use clear status names for external-facing forms
Workflow Automations Based on Form Responses
Workflow automations can now use submitted form fields as conditions.
What this means
Different answers in a form can trigger different actions automatically.
Examples:
Route requests to different teams based on request type
Apply priority labels for urgent submissions
Notify stakeholders based on department or region selections
Why this matters
Forms can now support smarter routing and more advanced intake processes without requiring manual triage.
Best practices
Keep dropdown values standardized
Avoid frequently renaming fields used in automations
Review workflows when updating form structures
Rich Text Formatting in Forms
Forms now support richer formatting options in text responses.
What this means
Formatting (such as bolding text) can carry into the action cards or projects created from a form submission.
Why this matters
Improves readability of submitted information
Makes longer responses easier to scan
Helps important details stand out
Best practices
Use formatting intentionally for instructions or key information
Structure long-form responses clearly for downstream teams
Improved Forms Builder Experience (Forms 2.0)
Forms have received major usability and presentation improvements.
What’s included
Updated Forms builder interface
More advanced form controls
Device preview capabilities
Why this matters
Teams can better understand how forms will appear to submitters, especially on mobile devices.
Best practices
Preview forms before sharing externally
Revisit older forms to ensure layouts and instructions still feel clear and modern
Due Date Range Controls
Forms can now limit available due date selections.
What this means
Teams can restrict submitters from selecting unrealistic or unsupported timelines.
Why this matters
Helps improve planning accuracy
Reduces scheduling conflicts
Creates more realistic intake expectations
Best practices
Add helper text explaining date limitations
Use date restrictions for request-heavy workflows like marketing, operations, or IT intake
Why These Changes Matter
Forms are now more than simple intake questionnaires — they can directly power workflows, routing, project updates, and automation across your workspace.
Because of this, form structure plays a larger role in how work moves through your organization.
Well-structured forms help create cleaner intake, better automation, and more consistent execution across teams.