Sign a Procore change order as Procore prints it, then mark it executed

The workflow reads the change order, its subcontract and the subcontractor's contact from Procore, then pulls the change order PDF from Procore with File Input from Procore. It sends that PDF for signature to the subcontractor and the general contractor, marks the change order approved and executed, and files the signed copy on it.

Your construction platform
Free download: the workflow file to import and a sample commitment change order
› Read the transcript

Summit Ridge Builders needs a change on Meridian Electrical's subcontract: a bigger electrical panel and a standby generator, fifty-eight thousand dollars. In Procore, the commitment change order is pending review, not executed, with nothing signed attached.

This Docusign workflow handles the signature. It reads the change order, its subcontract and Meridian's contact from Procore. Then it pulls the change order PDF straight out of Procore, exactly as Procore prints it, and sends it for signature.

When both sides have signed, it marks the change order approved and executed, and files the signed copy back on it.

In production, a call from your system starts it with the change order's id. Here, we start it by hand: the record id, and the change order as File Input finds it in Procore.

Meridian gets the change order by email.

It's Procore's own change order document: the three line items, fifty-eight thousand dollars, and the new contract sum. Meridian drags a signature under its name, and finishes.

Meridian has signed. At Summit Ridge, the change order is waiting in Docusign for the countersignature.

The owner signs under Summit Ridge's name, and the change order is complete.

From here, the workflow writes back to Procore.

Back in Procore, nobody touched the change order, and it's done: approved, executed, and the signed copy, with its certificate of completion, attached and named for the change order and the subcontractor.

The document Procore produced, signed in Docusign, and back in Procore, with no downloads and no uploads. That's change orders with Docusign and Procore.

Starts
From an API call or by hand
Steps
7
Document
Commitment change order, 1 page
Signers
The subcontractor's company contact and the general contractor
Last test run
22 November 2026
Commitment change order from Procore
  1. Start WorkflowFrom an API call
  2. 1Read Change Order from Procore
  3. 2Read Subcontract from Procore
  4. 3Read Subcontractor Contact from Procore
  5. 4Get Change Order PDF from Procore
  6. 5Send Change Order for Signature
  7. 6Mark Change Order Approved and Executed in Procore
  8. 7File Signed Change Order in Procore
  9. Path End
The steps of this workflow in Docusign Workflow Builder.

What it does

  1. Start: Start WorkflowFrom an API call, or Run Workflow by hand. Inputs: Change_Order_ID (the record id) and Change_Order_Record (commitmentCOs/ followed by the same id, the record File Input reads).
  2. 1
    Read Change Order from ProcoreCommitment Change Orders where Record ID equals Change_Order_ID: Number, Title, Status, Contract ID, Grand Total.
  3. 2
    Read Subcontract from ProcoreCommitment Subcontracts where Record ID equals the change order's Contract ID: Number, Title, Contract Company Name and Id.
  4. 3
    Read Subcontractor Contact from ProcoreProject Companies where Record ID equals the subcontract's Contract Company Id: Name and Email Address.
  5. 4
    Get Change Order PDF from ProcoreFile Input from Procore on Change_Order_Record, Latest Document Only: the change order PDF as Procore prints it.
  6. 5
    Send Change Order for SignatureThe PDF to the subcontractor's contact and to the user who published the workflow. Each signer places a signature on the page.
  7. 6
    Mark Change Order Approved and Executed in ProcoreCommitment Change Orders where Record ID equals the change order read in step 1: Status Approved, Executed.
  8. 7
    File Signed Change Order in ProcoreFile Upload to Procore: the signed PDF with its certificate of completion, attached to the change order.

What it writes back

Written back: Status = Approved; Executed = Yes

Filed to: Change order attachments / Signed Change Order {Number} - {Contract Company Name}.pdf

Page preview of the sample commitment change order, as the system of record prints it.
Summit Ridge Builders and Meridian Electrical are fictional companies. This is a demonstration document. Sample document for workflow testing. Have counsel review before use.
The document

A commitment change order, signed as printed

The workflow does not generate this commitment change order: Procore prints it, and the workflow pulls the PDF from Procore and sends it for signature as it is. It carries no signature fields, so each signer places a signature where the page asks for one. This sample is the PDF Procore printed for the demo record.

Set it up

  1. Install and connect the app

    Install Procore for Docusign IAM from the Docusign App Center and connect it to your Procore account. An account admin does this once.

  2. Import the workflow

    In Docusign, go to Agreements, Workflows, Create Workflow, then Import Workflow, and pick the .zip. When it asks, pick your Procore connection.

  3. Check the signers

    The second signer is the user who last published the workflow. Change it on Send Change Order for Signature if someone else countersigns for your company.

  4. Publish and test

    Publish, then run it on a test change order whose subcontractor email is your own inbox. Give it the change order id and commitmentCOs/ followed by the same id.

Make it yours

  • Countersign as someone else: change the second signer on Send Change Order for Signature from the workflow publisher to your project executive.
  • Sign other Procore documents: point File Input at a prime contract change order with potentialCOs/ and the record id, and swap the reads and the write-back to that object.
  • Refuse large changes: add a branch after Read Change Order from Procore that stops change orders above an amount and routes them to a manager first.
  • Record the signing date: add Signed Change Order Received Date to the write-back step.

Questions

Why does the workflow need two start inputs?

Read steps take the change order's record id. File Input from Procore takes the record as type and id, commitmentCOs/ followed by the id. A system that starts the workflow sends both.

Why are there no signature fields on the PDF?

Procore prints the change order without Docusign fields, and the workflow sends it unchanged. Each signer drags a signature onto the signature line.

The import says an app linked to a workflow step is missing.

Install Procore for Docusign IAM from the Docusign App Center and connect it, then import again. The import asks for your Procore connection and fills it into every Procore step.

Are Summit Ridge Builders and Meridian Electrical real companies?

No. Both are fictional and every sample value is invented. The change order PDF is what the Procore sandbox printed for the demo record.

Need it to match your project process?

We adapt library workflows to your stages, approvals and documents, and build private apps when a system has no app yet.

Video, 2:23
Finance and procurement

Onboard a supplier from a NetSuite vendor record

Fills a supplier agreement from the vendor, collects the legal name, tax ID and both signatures, and updates the vendor.

Starts: API or by handTested 10 Nov 2026

Docusign is a trademark of Docusign, Inc. Procore for Docusign IAM is published by Fluidlabs. To ask us to remove a mark, email hello@fluidlabs.com.