Draft, negotiate and sign a subcontract from Procore, then mark it executed

Two workflows share one Agreement Desk request type: the first reads the commitment and the subcontractor from Procore, drafts the subcontract, emails it for review and moves the request to Negotiation. When legal moves the request to Waiting for Signature, the second sends the negotiated subcontract for signature, marks the commitment executed with the agreed retainage, attaches the signed PDF and closes the request.

Your construction platform
Free download: the workflow file to import, the subcontract agreement template and the document
› Read the transcript

Summit Ridge Builders has awarded the electrical work on a project to Meridian Electrical. In Procore, subcontract SC-002 is approved, but nobody has signed it: it isn't marked executed, and there's no agreement attached.

So the project manager asks legal for the subcontract with a Docusign Agreement Desk request. The subcontractor field searches Procore's companies as you type.

Then the subcontract's number in Procore, and the scope of work.

A minute later, the request has its draft. The workflow read the subcontract and Meridian's company from Procore, filled the firm's subcontract template, emailed it to Meridian for review, moved the request to Negotiation, and made the requester its owner.

This is that workflow in Docusign Workflow Builder. It starts when a subcontract request is submitted, reads Procore through the Fluidlabs Procore app, and drafts from the template.

Meridian replies with its comments, and legal negotiates the draft inside the request. Once the terms are agreed, legal records the agreed retainage on the request.

Then it moves the request to Waiting for Signature. That status starts the second workflow.

It takes the negotiated subcontract from the request, reads Meridian's contact from Procore, and sends the agreement for signature: Meridian first, then the request owner. When both have signed, it marks the subcontract executed in Procore, files the signed PDF on it, and closes the request.

Meridian gets the subcontract by email, ready to sign.

It's the subcontract legal negotiated: SC-002, the scope from the request, and the agreed retainage. Meridian signs and finishes.

Next, Summit Ridge countersigns.

At Summit Ridge, the request owner finds the subcontract waiting in Docusign.

Meridian has signed. The owner countersigns, and the subcontract is complete.

From here, the workflow takes over again.

The request is closed, and its owner has a note: the subcontract is executed and filed in Procore.

And in Procore, SC-002 is now marked executed, with the retainage legal agreed, and the signed subcontract attached, named for its number and the request.

Request it in Agreement Desk, negotiate, sign, and Procore updates itself. That's subcontracting with Docusign and Procore.

Starts
From an Agreement Desk request
Steps
15
Document
Subcontract agreement, 2 pages
Signers
The subcontractor's company contact, then the request owner
Last test run
22 November 2026
Subcontract agreement from Procore
  1. Workflow 1 starts
  2. 1Read Subcontract from Procore
  3. 2Read Subcontractor Contact from Procore
  4. 3Draft Subcontract from Procore Data
  5. 4Set Status to Negotiation
  6. 5Email Draft to Subcontractor
  7. 6Make Submitter the Request Owner
  8. 7Workflow 2 starts
  9. 8Get Final Subcontract from Request
  10. 9Read Subcontract from Procore
  11. 10Read Subcontractor Contact from Procore
  12. 11Sign Subcontract
  13. 12Mark Subcontract Executed in Procore
  14. 13File Executed Subcontract in Procore
  15. 14Close the Request
  16. 15Tell the Owner It Is Executed
  17. Path End
The steps of this workflow in Docusign Workflow Builder.

What it does

  1. Start: Workflow 1 startsA Subcontract Request is submitted in Agreement Desk. Its form picks the subcontractor from Procore's project companies and asks for the Procore subcontract number and the scope of work.
  2. 1
    Read Subcontract from ProcoreCommitment Subcontracts where Contract Company Name equals the request's subcontractor and Number equals the Procore subcontract number: Id, Number, Title, Contract Company Name and Id, Default Retainage, Grand Total.
  3. 2
    Read Subcontractor Contact from ProcoreProject Companies where Record ID equals the subcontract's Contract Company Id: Name and Email Address.
  4. 3
    Draft Subcontract from Procore DataDocument generation from the subcontract template with its seven fields mapped. The draft is attached to the request.
  5. 4
    Set Status to NegotiationThe request moves to Negotiation.
  6. 5
    Email Draft to SubcontractorTo the company's email in Procore, with the draft attached from the request, asking for comments or a redlined Word version.
  7. 6
    Make Submitter the Request OwnerThe project manager who submitted the request becomes its owner and countersigns later.
  8. 7
    Workflow 2 startsThe request's status changes to Waiting for Signature, on a Subcontract Request. Legal moves it there once the terms are agreed and the Agreed Retainage (%) field is filled.
  9. 8
    Get Final Subcontract from RequestThe latest version of the document generated from the subcontract template, including any redlines legal saved to the request.
  10. 9
    Read Subcontract from ProcoreThe same rule as in workflow 1, plus Record ID, for the write-back and the file.
  11. 10
    Read Subcontractor Contact from ProcoreProject Companies where Record ID equals the subcontract's Contract Company Id: Name and Email Address of the signer.
  12. 11
    Sign SubcontractThe final subcontract to the subcontractor first, then to the request owner, with a signing order.
  13. 12
    Mark Subcontract Executed in ProcoreCommitment Subcontracts where Id equals the subcontract read in step 2: Status Approved, Executed, and Default Retainage from the request's Agreed Retainage (%).
  14. 13
    File Executed Subcontract in ProcoreFile Upload to Procore: the signed subcontract, attached to the commitment.
  15. 14
    Close the RequestThe request moves to Closed.
  16. 15
    Tell the Owner It Is ExecutedAn email to the request owner: both parties signed, the commitment is executed and the signed PDF is on it.

Field map

Where each data label on the subcontract agreement is filled from in Procore
Data label on the subcontract agreementProcore fieldStep
SubcontractNumberCommitment Subcontracts / Number1
RequestIdAgreement Desk request / Request IDStart
SubcontractorNameCommitment Subcontracts / Contract Company Name1
SubcontractTitleCommitment Subcontracts / Title1
ScopeNotesAgreement Desk request / Scope of WorkStart
ContractSumCommitment Subcontracts / Grand Total1
RetainagePercentCommitment Subcontracts / Default Retainage1

Written back: Status = Approved; Executed = Yes; Default Retainage = Agreed Retainage (%), as legal entered it on the request

Filed to: Commitment attachments / Executed Subcontract Agreement {Number} {Request ID}.pdf

Page preview of the sample subcontract agreement, with its data label fields highlighted and filled with sample values.
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 subcontract agreement that fills itself

The highlighted fields are the subcontract agreement's data labels, shown here with sample values. The field map lists where each one comes from in Procore or the start inputs. Each field sits on a hidden anchor tag, so you can use your own subcontract agreement: keep the seven data labels and the workflow keeps working.

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 workflow 1

    In Docusign, go to Agreements, Workflows, Create Workflow, then Import Workflow, and pick the first .zip. It brings the Subcontract Request type with its statuses, form and custom fields, and the subcontract template. When it asks, pick your Procore connection.

  3. Import workflow 2 and point its start

    Import the second .zip the same way. It brings a second copy of the request type, named Subcontract Request (1). Open workflow 2's start, set Request Type to Subcontract Request, and set the copy to inactive in Agreement Desk settings.

  4. Publish and test

    Give the people who run requests the Manage all requests in the account permission for Agreement Desk, which status changes need. Publish both workflows, then submit one request for a sample subcontract addressed to your own inbox.

Make it yours

  • Put your own subcontract in place: upload it as a Docusign document template with the seven fields, and choose it in Draft Subcontract from Procore Data and Get Final Subcontract from Request.
  • Format the money: the template prints Grand Total as Procore returns it, such as 507000.0. Type the field as a number in your template, or add a formatted amount to the request form.
  • Keep the agreed retainage on the document as well as in Procore: legal changes it in the draft during negotiation, and workflow 2 writes the Agreed Retainage (%) field to the commitment.
  • Let your account run status changes: the user who publishes the workflows needs the Agreement Desk permission Manage all requests in the account, or the status steps fail with a 403 error.

Questions

Why two workflows?

Negotiation takes days and happens in the request, between people. The first workflow ends when the draft is out for review, and the second starts when legal moves the request to Waiting for Signature, so nothing waits inside a running workflow.

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.

Why is there a second Subcontract Request type after the second import?

Each .zip carries the request type, so the second import adds a copy named Subcontract Request (1). Point workflow 2's start at Subcontract Request and set the copy to inactive. Both workflows then run on the same requests.

Can another system start it through the API?

No. An Agreement Desk request starts both workflows, so Baton Launcher and the API cannot. People start it from the Subcontract Request form in Agreement Desk.

Are Summit Ridge Builders and Meridian Electrical real companies?

No. Both are fictional and every sample value is invented. Put your own company, terms and template in place before you use the workflows.

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.