Build a Change Order Approval Workflow in Cognito Forms
A foreman finds rock where the drawings said clay. He calls the PM, the PM says go ahead, and the crew works the rest of the day on a verbal. Three weeks later the office is trying to bill for it, the client says nobody told them, and the only record anyone can produce is a text message with no dollar figure in it. The approval happened somewhere that writes nothing down. This post builds the thing that does: a change order form where the field submits, the PM approves or rejects against their own name, and an approved order reaches the office and the client for signature with nobody retyping it.
Every step below was checked against Cognito Forms’ official documentation in September 2026. Where a feature needs a particular plan, it says so.
Who this is for, and who it isn’t
Build this if your field crews and your office staff are not the same people, change orders get approved verbally more often than not, and a client signs something at the end. It helps most when the approver is one person who is rarely at a desk. Workflow Link Sharing — what lets that person approve from a phone without a login — requires a Team or Enterprise plan.
Don’t build this if change orders already live inside an estimating or project management package your team actually uses; you would be creating a second home for the same record, and two records that disagree are worse than one that is late. Skip it too if the approval is a judgment call made fresh with the client each time, with no rule behind it. Cognito Forms routes a decision well. It does not make one.
Change orders are usually where we start in our workflow automation work for construction and field service companies, because getting them wrong shows up on the next invoice.
The three lists the whole thing is made of
- Statuses are where an entry is. New forms come with Incomplete and Submitted; Incomplete cannot be deleted or renamed. Limit of 20.
- Roles are who is looking. Two are built in: Public, the default role for new form submissions, and Internal, the default role for new entry views. Limit of 20, so 18 of your own.
- Actions are the buttons. Each can change status, send emails, auto-create entries on another form, and clear fields. Forms start with Submit and Update. Limit of 20.
All three live under Workflow on the form’s Build page. Those caps are not generous once a workflow grows a rejection path and a revision path — design against them now rather than finding the ceiling at step nine.
The build, step by step
1. Write the statuses before you write a single field
Click + Add Status. Each takes a Status Name, a Color, and Automatically Assign Status set to When or Never. For a change order: Pending PM Review, Approved, Rejected, Sent for Signature, Signed.
Why first: a new entry moves from Incomplete to the second status listed unless conditional logic says otherwise, so the order of this list decides where a field submission lands. Put Pending PM Review straight after Incomplete and the routing is done before you write any logic. Signed is the terminal status — Cognito’s prelaunch checklist asks whether you have included one that signifies the end of the workflow, because a workflow with no end is one where nobody can tell what is finished.
2. Add the roles, one per human
Workflow > Roles > + Add Role. The foreman submitting from site is Public. The office is Internal. Add Project Manager and Client as Other roles.
Keep the PM and the office separate even when one person does both. Collapse them and the approval view and the accounting view of the same record become one view — which you will regret the first time a PM’s assistant starts approving on their behalf.
3. Build the field’s half of the form
This is the part people over-build. A foreman with wet hands and one bar of signal finishes a short form and abandons a long one. So: the job as a Dropdown, never free text — free text is how you get four spellings of the same job number; what changed and why; a File Upload for photos; a Number for estimated cost; a Date.
Everything the PM and the office need — approved amount, cost code, comments, signature — sits on the same form but hidden from the field. On each, open Field Settings, find Show This Field, choose For Roles, and pick the roles that should see it. One form that looks like four, depending on who opened it.
4. Make the field’s answers uneditable after submission
Same Field Settings panel, the Read-Only setting, again For Roles: set the description, photos and estimated cost read-only for Project Manager and Client. The entire commercial value of this record is that it says what was requested at the time it was requested. If the approver can quietly edit the cost before approving it, you have built a document that proves nothing — the situation you started in, now with a login screen.
5. Add the Approve and Reject actions
Workflow > Actions > + Add Action. Each has an Action Name (internal, 40 characters), Button Text, and Allow Action offering Always, When, For Roles or Never. Create Approve Change Order with Button Text “Approve”, Allow Action > For Roles > Project Manager, and Change Status To set to Approved. Build Reject the same way against Rejected.
Then add a When condition so each action is only available while the entry sits in Pending PM Review. Without it, an approved entry reopened later still shows a live Approve button, and someone presses it — the most common reason an approval workflow ends up with a status history that contradicts the emails people received.
6. Get the PM the link
Open the Submit action’s settings and create a notification under Send Emails. The fields are To, From, Subject, Message, Include, Attach and Send. To the right of To is a Share Workflow Link button: click it and choose the Project Manager role. The link carries the role, the role carries the permissions, and the PM lands on a page showing their fields and their two buttons.
Workflow Link Sharing is toggled on in the Workflow menu, on Team and Enterprise plans. Its Require Authentication setting offers Always (organization members only), For Roles, or Never. Require it for the Project Manager role. The client has no account and will not make one, so their role relies on the link alone — a tradeoff to make deliberately, and to revisit when contract values get large.
Put the job number and the dollar figure in the Subject. A PM with forty unread emails decides what to open from the subject line.
7. Route approvals forward and rejections back
Inside the Approve action, add a second email to the office carrying a workflow link scoped to Internal. Inside Reject, add one back to the foreman’s email field with the PM’s comment included. A rejection nobody sees is indistinguishable from an approval that never came.
Each email has its own Send setting of Always, When or Never, plus an Only send when conditions become true? checkbox that fires on the transition rather than on every save. Use it, or every later edit to an approved entry re-sends the approval email and people stop reading the ones that matter.
8. Send it to the client for signature
Add a Send to Client action, allowed for Internal only, changing status to Sent for Signature and emailing a workflow link scoped to the Client role. On the client’s view, show the approved scope and amount read-only and expose one field they can touch: a Signature field, which collects a typed or handwritten signature in Draw, Type or Draw & Type mode and requires Pro, Team or Enterprise.
Finish with an Accept Change Order action, allowed for the Client role and conditioned on Sent for Signature, moving the entry to Signed. Attach a generated document so the client keeps a copy: templates live in the Manage Document Templates dialog, Standard or Custom, output as PDF or Word, and a generated document can be attached to an email notification.
9. Lock the record when it’s done
Under Workflow, Form Read-Only takes Always, When, For Roles or Never. Set When, conditioned on status equals Signed. Cognito’s documentation notes this is what stops further changes arriving through workflow links sent earlier — the actual risk, because those links stay live in inboxes long after the job closes.
10. Give the PM a queue, not an inbox
On the Entries page, click the plus icon and choose New Task View. Set the workflow Role tasks are assigned to, leave Assign As Tasks enabled, optionally set Priority and Due Date, and filter to Pending PM Review. Users who log in see outstanding items under Tasks in the sidebar. Team and Enterprise only.
Do this even though the emails work. Email is a notification, not a queue — it has no concept of “still outstanding”, and the change order that costs money is always the one buried on a Friday. Then run Cognito’s Workflow Prelaunch Checklist before you turn it on. The item that catches the most: “Double check that any workflow links you’ve included in emails contains the correct role.”
Where this breaks
A status nobody advances. Pending PM Review becomes a graveyard. The PM was on a roof, then it was Friday, then it was three weeks. Nothing is broken — the form is doing exactly what it was told, which is what makes it hard to see. The fix is the task view from step 10 plus a due date, so an untouched entry is visibly overdue to somebody rather than invisibly parked.
Notifications to a shared inbox. Send approvals to office@ and the approval belongs to nobody. “Approved by office@” is worth very little in a dispute. Use a named person’s address. If there really are two approvers, the honest design is two roles and two actions, not one address four people can reach.
Permissions that leak a record. The dangerous combination is a field you forgot to scope plus an entry view with no role set. Fields default to visible, and Internal is the default role for new entry views. Nothing warns you when a client-facing link inherits a view showing your margin. Check by opening the real emailed link in a private browser window — not by reviewing the settings screen, which tells you what you intended rather than what you built.
Questions we actually get asked
Does the PM need a Cognito Forms login to approve?
No, provided you use Workflow Link Sharing, which emails a role-scoped link to a single entry and is available on Team and Enterprise plans. The recipient opens the link and sees only the fields and actions their role allows. To tie the approval to a verified identity, set Require Authentication to Always, restricting access to organization members, or to For Roles for the approver role only. Approvers who want the Tasks dashboard do need inviting as users.
Can two people approve the same change order?
Yes — Cognito Forms documents a parallel approval pattern among its workflow scenarios, where multiple approvers each act before the entry progresses. In practice that means one role and one action per approver, a status for the partially-approved state, and the final status assigned conditionally once both approvals exist. Budget the 20-status and 20-action caps accordingly.
Is a signature collected this way legally binding?
The Signature field collects a typed or handwritten electronic signature, stores it with the entry, and renders it as an image in PDF exports. Whether that satisfies your contract terms, your state’s requirements or your insurer is a question for your counsel, not for a form builder. What we can tell you is what the record contains: the signature, the entry’s field values, and the status history showing who moved it and when.
What happens to the record if we stop using Cognito Forms?
Entries are exportable and generated documents are PDF or Word files you already hold. If a signed change order is something you might need in a dispute years from now, attach the generated PDF to the job folder in whatever system holds your contract documents. A form platform should not be its only home.
How long does this take to build?
A day’s work for someone who has built one before. What takes longer is the part before the clicking: deciding who has authority to approve what, at what dollar threshold. Almost every engagement finds that the rule the office believes is in force and the rule the field operates under are different rules. That conversation is the project. The form is the easy part — true of most of the systems on our portfolio of built systems.
If you’d rather not build it yourself
All of the above is buildable by a competent person inside your own organization, and if that person exists you should let them. We come in when nobody has the day, or when this workflow is one of six that have to connect to each other and to the accounting package — that wider piece is our workflow automation service.
Tell us what your change order process looks like now, including the part that happens verbally, and we will map what a system would need to do. No obligation, and you keep the map either way. Request a system review.
Interface labels and feature behavior verified against Cognito Forms’ official documentation, September 2026. Labels and plan availability change; check current documentation before relying on any detail here.