The signing sequence
To sign a subcontractor agreement electronically, confirm the approved agreement and exhibits, identify the authorized people signing for each business, place and assign the fields, send the request, then have each signer review and submit. After every required party finishes, retrieve the completed agreement and available signing history. Check both before recording the handoff.
Use the two CSV registers below to keep preparation and evidence review visible. They are operational worksheets with fictional examples; they do not supply a subcontract or decide whether an agreement is enforceable.
1. Establish exactly what is being signed
Give the agreement a project reference and version identifier before uploading it. List every included exhibit by name and revision: scope, price schedule, drawings, insurance requirements and any other incorporated material. Check that referenced attachments are present and readable. An email thread saying “latest version” is a poor handoff instruction when several drafts exist.
Ask the contract owner to resolve missing terms and review questions before sending. Record their approval against the version being issued. If your arrangement uses a master agreement plus a project work order, identify both records and the relationship between them. Do not assume that signing one completes the other.
Keep the contract review separate from choosing the signing tool. Counsel should address disputed terms, applicable state law, required formalities and whether the particular document is appropriate for electronic execution.
2. Confirm people, authority and order
Record each business name, signer name, title, confirmed email address and the person who checked signing authority. A project contact who receives scheduling messages may need to route the agreement to an officer or another authorized representative. Verify the intended recipient through a known contact before changing an address.
Choose the signing order to match your approved process. Fill project details before requesting signatures; do not depend on an early signer to discover blank commercial terms. If an internal signature must precede the subcontractor signature, make that sequence explicit. If the subcontractor signs first, record that instruction instead of adopting a universal “GC first” rule.
Confirm that both sides are willing and able to use the electronic workflow. Under ESIGN, electronic form alone is not a reason to deny legal effect to a covered transaction, but the statute preserves other obligations and generally does not force someone to accept electronic records. See 15 U.S.C. § 7001(a)–(b).
3. Place fields and check the whole packet
Assign each signature, initial and completion field to the correct role. Preview every page, including exhibit signature blocks. Check field placement against long company names and the actual space on the PDF. Separate information entered by the sender from information the recipient must supply.
In SubDoc, an administrator can upload a PDF template, place fields and configure signer roles. The send flow lets the team select templates or a saved packet, choose the vendor and optional project, confirm signers, and complete sender fields. Reference attachments are distinct from documents containing signing fields. These steps are described in the SubDoc Help Center.
Use a packet manifest even when the software groups the files into one request. Mark which items require execution and which are reference material. Keep sensitive tax information out of a general project handoff register; record a restricted document reference where needed.
4. Review, sign and finish the request
Tell the recipient the project, agreement version, expected documents and contact for questions. The signer should inspect the complete agreement, confirm the displayed business and personal details, complete their assigned fields, and review the electronic signing disclosure before submitting.
SubDoc supports drawing or typing a signature and provides a Finish signing action. Completing one signature box is different from submitting the request; completing one person’s turn is also different from every party finishing. Check the overall request status before treating the agreement as fully executed.
The federal definition of an electronic signature concerns a sound, symbol or process associated with a record and adopted with intent to sign. A particular cursive font is not specified by that definition. See 15 U.S.C. § 7006(5).
5. Resolve exceptions with a named owner
- Wrong signer: pause the request and have the contract owner confirm the replacement. Avoid forwarding a personal signing link as an informal reassignment.
- Expired link: verify the recipient, then use the tool’s resend or reminder process. SubDoc’s manual reminder issues a fresh link and invalidates that signer’s earlier emailed links.
- Changed scope or price: record the correction and obtain approval for the replacement version before issuing it. Keep the prior request’s disposition and replacement reference together.
- Declined or waiting: record the reason, next action and responsible person. A request waiting on another signer has an unresolved step even if one signature is already visible.
Use a review date for every open item. Avoid converting a due date into permission to sign on someone else’s behalf or to change a completed record.
6. Retrieve and verify the evidence handoff
Open the completed download and confirm the parties, version, exhibits, signature blocks and legibility. Save the available audit certificate or transaction history with the same request reference. Record the final status and relevant timestamps with their time zone. Preserve the original export; create a separate working copy if annotation is needed.
Evidence formats vary. Docusign distinguishes transaction metadata from document content and provides a Certificate of Completion. Adobe distinguishes interim and final audit reports; a terminal status still needs checking because “final” alone does not tell your team that the agreement was successfully signed.
ESIGN’s retention provision addresses accuracy, accessibility and later reproduction where retention is required by law. Set the retention period and access permissions under your applicable requirements rather than copying a generic number of years. A hash or activity log can support review, but your handoff should also record how signer authority was checked and who accepted the file.
Free signing-readiness and evidence-handoff registers
The readiness CSV tracks the approved version, packet contents, authority check, signing order, open issue and send decision. The evidence CSV tracks the completed export, history reference, final-status review, storage location, recipient access and handoff acceptance.
Fictional example: Cedar Field Builders prepares agreement CF-014-v3 for Orchard Electric. The readiness row stays on hold because the exhibit revision is unconfirmed. After that issue closes, the coordinator records the authorized signers and sends the approved packet. Following completion, the evidence row remains pending until the reviewer opens the final export, checks the request status and confirms the project lead can access the stored files. Each file includes a fictional example and a blank starting row.
Keep signing and onboarding decisions connected
Record contract completion alongside the remaining items in your subcontractor onboarding checklist. Keep insurance review, tax-document collection and authorization to start work as separate decisions with their own owners. If selection questions remain unresolved, use the prequalification reviewer log before proceeding.
SubDoc’s subcontractor compliance workflow connects signed agreements with vendor records. Confirm the filing destination and the actual stored copy during your handoff. Use the signing guides for current product instructions.