Overview
Why this matters: Getting contracts signed is one of the most important — and most delayed — steps in any project. When your team has to manually send each document for signature, things get slow and mistakes happen. With automated SubHub Signing, you can set up an automation that sends documents for signature the moment a trigger fires (like a project reaching a specific stage). No chasing, no forgetting — contracts go out on time, every time.
SubHub Sign is SubcontractorHub's built-in electronic signature feature. This automation is available for the Project module only.
Prerequisites
Admin or Manager role in SubcontractorHub
SubHub Sign enabled for your organization
At least one document template already created in SubHub Sign
Project module with job types configured
Step-by-Step Instructions
Part A — Start a New Automation
From the main menu, go to Manage Database → Database.
Click Additional → Automations.
Click Add to create a new automation.
Enter a clear Title (e.g., "Auto-Send Install Contract for Signature") and click Next.
Part B — Select Module and Job Type
Select Project from the available modules. Click Next.
Select your job type (e.g., Solar). Click Start Now!
Part C — Set the Trigger
Click Add Start Trigger(s).
Select a trigger from the list (e.g., When Stage Changes to "Contract Ready").
Part D — Add the Sign Via SCH Action
Click the + sign above "Automation Ends Here" to add an action.
Select Sign Via SCH from the action list.
Choose the document template you want to send for signing.
Click Save.
Part E — Launch
Review your automation flow, then click Launch to go live.
Real-World Example
Scenario: GreenGrid Solar has a stage called "Customer Approved" in their project workflow. Once a project hits that stage, the install contract needs to be signed.
They create an automation with a When Stage Changes to "Customer Approved" trigger and a Sign Via SCH action using their "Solar Install Agreement" template. Now, the moment a project reaches that stage, the contract is automatically sent to the customer's email for electronic signature.
Result: Contracts that used to take 2–3 days to send out now go within seconds. The team closed 15% more deals in the first month.
Pro Tips
💡 Create different templates for different job types. A roofing contract looks different from a solar contract. Set up separate automations with the right templates for each.
💡 Add a delay before signing. Use a Wait/Delay action before the Sign Via SCH step to give your team a review window (e.g., 1 hour) before the contract goes out.
💡 Chain with notifications. Add an email or SMS action after the signing step to notify the project manager that the contract was sent.
Key Terms
Term | What It Means |
SubHub Sign | SubcontractorHub's built-in electronic signature tool for sending and tracking document signatures. |
Document Template | A pre-built contract or form in SubHub Sign that gets populated with project data and sent for signature. |
Sign Via SCH | An automation action that sends a document for electronic signature through SubHub Sign. |
Troubleshooting / FAQ
Question | Answer |
I don't see "Sign Via SCH" in the action list. | Make sure SubHub Sign is enabled for your organization and you selected the Project module. |
The contract was sent but the customer didn't receive it. | Check the customer's email address in the project. Also check spam folders. |
Can I automate signing for Proposals too? | Currently, Sign Via SCH automation is available for the Project module only. |
Change Log Summary
What Changed | Details |
Title | Rewritten from "How to Automate SubHub Signing" to a benefit-focused title. |
Structure | Added Overview, Prerequisites, five-part instructions, Real-World Example, Pro Tips, Key Terms, Troubleshooting, and Change Log. |
Language | Explained SubHub Sign and document templates for non-technical users. |
Images | 11 screenshots integrated with descriptive alt text. |


