![Samantha V.](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Samantha V.") SV Samantha V. Project Manager Marketing and Advertising Mid-Market (51-1000 emp.) 8/18/2026 "Workflows significantly reduced manual approval tracking across teams" 5/5 What do you like best about Jotform? We use Jotform Forms as the front door for requests that used to come in through email, or whatever template someone happened to remember. Conditional Logic lets us collect different information depending on the type of request. For example, a technical change might require impact and a target date, while a marketing request can ask for format, market, and approver. That alone has cut down a lot of back-and-forth, because fewer requests arrive half-complete. From there, Jotform Workflows handles the routing. We assign reviews, approvals, and next steps based on amount, department, or project type, and the process keeps its own history instead of turning into another email chain nobody wants to reconstruct later. For recurring workflows like purchases, scope changes, and content approvals, the biggest win is simply that the next person gets the task when they’re supposed to. Jotform Tables then gives us an operational layer on top of the submissions, so we can add status, owners, filters, and internal fields without changing the original request. We eventually stopped maintaining a separate spreadsheet just to track what was Pending, Approved, In Progress, or Closed. Review collected by and hosted on G2.com. What do you dislike about Jotform? Forms, Tables, and Workflows are strong for intake, approvals, and other relatively structured processes, but I wouldn’t keep trying to stretch them into work that really needs deeper project management. As soon as the conversation shifts to complex dependencies, capacity planning, estimates, sprints, or resource allocation, I’d rather hand the approved work off to a system that’s built for execution. For us, Jotform works best as the gate that produces clean, decided work, not as the place where the entire project has to live. Review collected by and hosted on G2.com. What problems is Jotform solving and how is that benefiting you? We saw this clearly on an implementation project where change requests started coming in after delivery was already underway. Every stakeholder described the request differently, and several arrived without any impact assessment, urgency, or even a clear owner. To bring order to it, we built a Jotform intake using Conditional Logic to separate bugs, scope changes, and content requests, and then used Prefill and URL parameters to automatically carry the project ID and client details into the form. Each submission landed in Jotform Tables with an initial status, and Workflows routed low-impact changes to the Project Manager, while anything that could affect budget or deadline went through delivery and then to the client. Our first version asked for too much. Stakeholders were abandoning the form because we made several fields mandatory even when that information already existed elsewhere. We removed the duplicate questions and kept only what was necessary to make a decision. Review collected by and hosted on G2.com. Show More Current UserValidated ReviewerIncentivizedSource: G2 invite See what 5162 reviewers think of Jotform 4.7 out of 5 · Verified reviews from real users [ Read all reviews ](https://www.g2.com/products/jotform/reviews)