Signing the Agreement

The signature is the moment a sale becomes a customer, and it's the record every later argument goes back to. Months after a rep's driveway pitch, a customer disputes a charge, an inspector asks for the contract, a rep claims commission on an account that cancelled, or a regulator asks whether the buyer was told they could cancel. Each question is answered by what the system captured in the few minutes around the signature: which document and version, who signed, on whose device, what they were shown, and what happened next. Signing is also where the hardest consumer rules bite. A pest or lawn plan sold at the door, a furnace replacement signed at the kitchen table and a solar contract closed in the living room are all sold away from the seller's place of business, which brings the federal Cooling-Off Rule and its state cousins into the sale.

What Gets Signed#

A signed agreement is a signing packet: several documents executed together, each with its own legal job.

• The service agreement: the services, the initial and recurring price, the billing frequency, the term, renewal, and termination terms (Service Agreements & Plans covers the agreement as data).
• The right-to-cancel disclosures: for a door-to-door sale, the receipt, cancellation statement and duplicate Notice of Cancellation the Cooling-Off Rule requires (Consumer Protection lists them).
• Consent to electronic records: a notice the law requires in writing (like the cancellation notice) counts electronically only after ESIGN consent, below.
• The payment authorization: consent to store a card or bank account and charge it on a schedule (Stored Cards & Recurring Billing).
• State, trade and product addenda: termite warranty terms, chemical notices, an equipment registration for an HVAC manufacturer's warranty, financing disclosures, a state-required clause.

The packet is a unit. A service agreement signed without its cancellation notice is a defective sale, and a system that lets a rep send one without the other has built the defect in.

Commercial contracts sign differently. A service contract with a business (a restaurant's pest plan, a property manager's landscaping, a hospital's HVAC maintenance) isn't a consumer sale, so the Cooling-Off Rule, which covers goods and services bought "primarily for personal, family, or household purposes," doesn't apply and the packet has no cancellation notice. The paperwork comes from the buyer as often as from the seller: a master services agreement sets the terms once, and each site or job is a work order or statement of work under it, often released against the customer's purchase order, whose number the customer's accounts payable expects on every invoice. The question that replaces "was the buyer told they could cancel" is "could this person bind the company": record the signer's name, title and email domain, and for large or multi-site contracts ask for a signature from someone the customer's procurement office names. Repair, Install & Commercial Work covers the contract terms that follow (SLAs, not-to-exceed amounts).

The Law, Applied at the Door#

ESIGN and UETA, consumer consent, attribution and signing evidence are in Electronic Signatures & Records. The part that bites field sales is Consumer Consent Comes First: the cancellation notice is a disclosure the law requires in writing, so an electronic copy counts only if the customer's consent shows they can open it where it will be delivered. Consent tapped on the rep's tablet for a notice that arrives by email is the weak case, and it surfaces later as "the customer was never validly told they could cancel." Store the rendered PDF exactly as signed, with its hash and the provider's certificate.

How the Platforms Do It#

Field-service platforms split into those that own the signing experience and those that hand it to an e-signature provider.

Platform	Where the customer signs	What the public docs say
FieldRoutes	Rep's device, in the field	"You can sign an agreement offline," but only one opened while online can be viewed, and "creating a new contract requires a connection"
ServiceTitan	Customer's own device, by link	Forms are sent by email or text, customers "review and sign on their own devices," signed documents go to the job audit trail, and sending requires a connection
Jobber	Client hub, on the customer's device	The client approves a quote and signs by drawing or typing a name; a required deposit turns the button into "Approve and Pay Deposit"; editing an approved quote removes the signature and saves the signed version as a PDF note
SalesRabbit	Rep's device	"Digital Contracts" builds contracts, and "Mobile eSignature" is a paid add-on
Enerflo	Email or in person	"Docflo" compiles a solar sale's documents into one signing packet

ServiceTitan's offline guide saves form signatures locally but needs a connection for contracts, proposals and financing. That split is common: a signature image is easy offline; a complete packet with a delivered copy isn't. Platforms that want a portable, independently verifiable record embed an e-signature provider (DocuSign, Dropbox Sign, Acrobat Sign), and all of them put the same thing on you in embedded mode: identifying the signer. In remote signing the provider's link is evidence that the signer controls that inbox or phone; in embedded signing the provider records that your application said it checked, and nothing more.

Embedded or Remote: Whose Device#

The field industry's signature problem is a tablet. A rep finishes the pitch, turns the tablet around, scrolls to the signature box and hands over a stylus. It's fast and it works without the customer's email. The law doesn't ban signing on a seller's device, but a complaint that the customer never saw the terms or the price (Consumer Protection covers what regulators look for) is easier to make, and harder to rebut, when the customer never held a copy.

Pattern	Evidence of identity	Customer keeps a copy	Works offline	Risk
Signature on the rep's tablet, copy emailed later	Rep's word, GPS, photo	Only if the email arrives	Yes	Customer can say they never saw the terms
Embedded provider session on the rep's tablet	Provider certificate plus your declared auth method	At completion, if delivered	Rarely	Same, with better tamper evidence
Link to the customer's own phone	Control of the phone or inbox	Yes, before and after signing	No	Needs signal and a working contact

My default is the last row: send the packet to the customer's phone, let them read it on their own screen, and sign there, as ServiceTitan and Jobber do. Keep the tablet for when there's no signal, and then require delivery of the copy and cancellation notice to a verified contact before the sale counts as complete. An undelivered copy belongs in a visible exception queue, not a quiet new customer. The cost is real: some door sales are lost to a dead phone or a customer who won't share a number, and a business that weighs that higher can sign on the tablet with more evidence (a photo, GPS, the provider certificate) and accept the weaker position in a dispute.

Templates by State#

Contract terms vary by state, trade and product, so the agreement is assembled from a template chosen by rules, not picked by a rep. State home-solicitation laws differ in the length of the window, who gets a longer one, the wording of the notice and what counts as a business day (Consumer Protection has the federal baseline and California's example). Accreditation adds its own layer: a QualityPro pest company certifies that it "has a termite warranty/service agreement that meets requirements" of the program's current US V6.1 standards. Check current state law with counsel; don't ship a fifty-state table you haven't verified.

The model that survives this has three parts: a clause library (each clause versioned, with the jurisdictions, trades and products it applies to), templates that compose clauses and are versioned as a whole, and a resolution rule that picks the template from the service address's state, the product, the sale channel (sold_via: door, phone, web, store or technician) and buyer attributes like age where a state makes them matter (Rules as Data). The resolved template version is pinned on the agreement at the moment it's generated. Never re-resolve a signed agreement against today's templates. The one table this chapter adds hangs signing documents off the canonical agreements table from The Field Operations Business:

CREATE TABLE agreement_documents (
  id               UUID PRIMARY KEY DEFAULT uuidv7(),
  tenant_id        UUID NOT NULL,
  agreement_id     UUID NOT NULL REFERENCES agreements (id),
  template_id      UUID NOT NULL,
  template_version INTEGER NOT NULL,       -- pinned at generation
  jurisdiction     TEXT NOT NULL,          -- e.g. 'US-CA'
  rendered_sha256  TEXT NOT NULL,          -- hash of the exact bytes shown
  provider         TEXT,                   -- 'docusign', 'dropbox_sign', 'in_house'
  provider_ref     TEXT,                   -- envelope or signature request id
  status           TEXT NOT NULL,          -- draft, sent, signed, declined, expired, voided
  signed_at        TIMESTAMPTZ,
  certificate_uri  TEXT                    -- provider's audit certificate
);

Computing the Cooling-Off Deadline#

The deadline is a computation, and the system should own it rather than leave it to the rep's pen. Under the federal rule a business day is "any calendar day except Sunday or any federal holiday," so Saturdays count, and the buyer may cancel until midnight at the end of the third business day after the day of the transaction. The FTC's consumer page works four examples:

deadline(sale_date, rules):
  day = sale_date
  counted = 0
  while counted < rules.days:            # 3 federally; longer under some state laws
    day = day + 1
    if day is Sunday or day in rules.holidays(jurisdiction, year): continue
    counted += 1
  return end_of_day(day, service_address_timezone)

The traps are all in the inputs. Holidays come from a calendar table per jurisdiction and year, maintained ahead of time, because a state rule may use state holidays rather than federal ones, and this business day isn't the banking one (Time). "Midnight" is local to the buyer, so the time zone comes from the service address, not the server or the rep. And the deadline must be printed on both copies of the notice (the federal rule requires the seller to fill in the date of the transaction and the last day to cancel), so it's computed before signing and stored with its inputs and the rule version, not derived later (Rules as Data).

The deadline is stored as cancellation_deadline_at with cancellation_deadline_time_zone, the zone its midnight is in. A mailed cancellation is checked against it by its postmarked_on date, not the day it arrived (Consumer Protection has the channels and the postmark rule).

Taking Payment at Signing#

Most recurring-service sales collect something at signing: the initial service fee, a deposit, or just a payment method for autopay. Where the card is typed decides your PCI DSS scope (PCI DSS).

• The customer types on their own device into a provider-hosted page. SAQ A, the lightest questionnaire, requires that "the entirety of all payment pages delivered to the consumer's browser" come from a PCI DSS-validated third party, by redirect or iframe. If your page embeds the provider's fields in an iframe, you also need to confirm your page isn't susceptible to script attacks, with techniques like those in requirements 6.4.3 and 11.6.1 or with the provider's assurance.
• The rep keys the card into a web virtual terminal. SAQ C-VT is meant for merchants who manually enter one transaction at a time by keyboard into a third-party-hosted virtual terminal, on an isolated device. A shared sales tablet running other apps fits that poorly.
• The rep taps or dips the card on a reader or the phone. That's card-present acceptance, with its own validated-solution path (Card-Present Payments).

The pattern that keeps reps out of scope and customers in control is the same one as for signing: the payment step is a hosted page on the customer's phone, opened from the same link as the packet, and the app never sees a card number. Store only the provider's token, brand, last four and expiry (Sensitive Data).

Timing matters as much as scope: signing stores the payment method, and whether anything is charged before the agreement is active follows the rule and its two refundable exceptions in Billing Recurring Service, with the law in Consumer Protection.

Financing follows the same principle with higher stakes, because the application includes a Social Security number and income. Wisetack's flow sends the customer a text link, the customer sees and locks in options on their own phone, and the contractor is paid after "your customer confirms the work has been completed and releases the funds." Hearth's pitch is the same separation: "Homeowners apply for financing directly, not you." The rep's app should record that an application was sent, its status and the approved terms, never the credit data. Consumer credit brings its own disclosures, presented as Pricing & Sales Rules describes, and its own sequencing (when the note may be transferred, and when a loan secured by the home may fund), which Consumer Protection covers.

Verification Calls#

Door-to-door operators often add a step the law doesn't require: someone other than the rep confirms the sale with the customer. A 2023 Pest Control Technology article on door-to-door selling describes one company that requires every door-to-door sale to pass both a phone verification and a technician verification, "a checks-and-balance [procedure] in place to ensure the customer is onboarding with correct information." Treat it as an operating practice, not a legal requirement.

A verification is a short structured interview, not a sales call: it confirms the key terms of the deal and that the customer received the agreement and the cancellation notice. Build it as a form with a versioned script, an answer per question, and an outcome: verified (proceed), corrected (a new agreement version for the customer to accept, never an edit to the signed one), disputed (the customer describes a different deal; hold the commission and route to a manager), cancelled (a cancellation inside the window) or unreachable (policy decides whether the first visit proceeds).

Recording the call is a state-law consent question (Calls, Texts & Email). Outcomes also feed the rep's record: a pattern of disputed verifications is the earliest signal a manager gets.

After Signing: The Handoff#

A signed packet starts processes owned elsewhere: the first visit, billing, the welcome message, the rep's commission. The cleanest design is an agreement state machine whose transitions publish events that downstream systems react to, rather than calls made inline from the signing screen (Events). The states are draft, out_for_signature, signed (window open, not billable) and active, with side exits to void (never signed, or expired) and cancelled (before it became active, reason recorded); after activation an agreement can be paused, on_hold or terminated (Service Agreements & Plans). The first visit is a milestone, not a state.

The event uses the CloudEvents envelope, with the agreement as the body:

ce-specversion: 1.0
ce-id: 0194c3c0-5b7e-7f12-8a40-1d9e6b2c7f35
ce-source: /agreements
ce-type: agreement.signed
ce-subject: 0194c3bf-2a61-7c08-b5d3-8e4f0a1c9b26
ce-time: 2026-10-26T18:42:10Z
Content-Type: application/json

{
  "id": "0194c3bf-2a61-7c08-b5d3-8e4f0a1c9b26",
  "account_id": "0194c3be-9d10-7e44-a7f2-3c5b8d0e6a19",
  "status": "signed",
  "cancellation_deadline_at": "2026-10-30T03:59:59Z",
  "cancellation_deadline_time_zone": "America/New_York",
  "sold_via": "door",
  "signed_via": "customer_device",
  "sold_by_staff_member_id": "0194c3a2-4f8b-7b30-9c61-2e7d5a0f8c44"
}

What each consumer does with it:

• Scheduling books the first visit. There's a business reason to book fast (one pest control owner in the PCT piece aims to complete the first service within 24 hours of the sale, "before the customer changes their mind") and a legal reason to be careful: a visit inside the window is performed while the buyer can still cancel. The rule's exclusions are narrow and are covered in Consumer Protection. Decide with counsel whether you serve inside the window and what you charge if the buyer then cancels; never let a rep mark a routine sale as an "emergency" to skip the window. Booking Appointments covers the booking itself.
• Billing creates the billing schedule and stores the payment method, and charges according to the payment design chosen above (Billing Recurring Service).
• Communications sends the welcome message with the packet and the cancellation notice if they weren't delivered at signing, and records delivery.
• Commissions creates a pending commission that only becomes earned after the window and the first service (Sales Teams & Commissions).

Publish events with an outbox in the same transaction as the state change, so a crash between "signed" and "event sent" can't lose a customer (Events). Make every consumer idempotent on the agreement ID, because e-signature webhooks retry and arrive out of order (Webhooks). And treat the provider's webhook as the trigger to fetch the envelope's status, not as the truth itself.

Cancellation and Rescission#

A cancellation inside the window is the reverse of the handoff, and every downstream effect needs an undo: cancel the booked visit and release its slot, void the pending commission, stop the billing schedule, refund anything collected within 10 business days, and cancel any financing application. Model it as an agreement.cancelled event with a reason (buyer_cooling_off, verification_failed, rescission, duplicate) that every consumer handles, and a saga that tracks each step to completion so a stuck refund is visible.

Accept cancellations on every channel and record them as Consumer Protection describes. Retention offers are fine after the window; inside it, the cancellation is a right, not a negotiation, and a script that argues with it misrepresents that right.

Cancellations after the window are governed by the agreement's own termination terms and state renewal and cancellation laws (Subscriptions, Collections & Retention). Keep them separate in the data: a cancelled agreement that never became active is a sales outcome; a terminated one is a churned customer. Mixing them corrupts both the sales metrics and the retention metrics.

Auditing#

The agreement is the record most likely to be subpoenaed, disputed or inspected. The field-specific records, append-only:

• The packet as signed: exact bytes and hash, template and clause versions, the jurisdiction resolution and its inputs, the provider's certificate, and whose device it was signed on.
• ESIGN consent and delivery: the disclosure version, the channel consent was demonstrated on, and where and when the copy and the cancellation notice were delivered.
• The deadline and its undo: the computed deadline with its holiday calendar version (and any override, with approver), the verification script, answers and outcome, and for a cancellation the channel, postmark, reason and each undo step, including the refund date against its 10-business-day limit.

Signing evidence in general is in Electronic Signatures & Records; record structure and retention follow Audit Trails, with field records in Audit Trails & Records. Together they answer a chargeback (Disputes & Chargebacks), a regulator's request for the contract and notice, and a commission dispute.

What This Means for the System You Build#

• A signing packet as one unit, with the agreement, cancellation disclosures, ESIGN consent and payment authorization executed and delivered together.
• Customer-device signing by default, with tablet signing as an offline fallback that can't complete until a copy reaches a verified contact.
• Templates resolved by rule and pinned by version, from a versioned clause library keyed by jurisdiction, trade, product, channel and buyer attributes.
• Cancellation deadlines computed by the system from a jurisdiction holiday calendar and the service address's time zone, printed on the notice and stored with their inputs.
• Payment and financing on hosted pages on the customer's device, storing tokens only, with a deliberate choice between charging after activation and charging at signing with a tracked 10-business-day refund.
• An agreement state machine with outbox events that scheduling, billing, communications and commissions consume idempotently, and a cancellation saga that undoes each of them.
• Commercial contracts recorded as such: no cooling-off notice, the MSA and purchase order referenced, and the signer's authority captured.
• Verification as a scripted, recorded workflow with outcomes that can hold a commission or cancel a sale.

References#

Specifications

• 15 U.S.C. 7001: Electronic Signatures in Global and National Commerce, the consumer consent and "reasonably demonstrates" requirement for records the law requires in writing
• eCFR: 16 CFR 429.1, The Cooling-Off Rule, the cancellation notice with the transaction date and last day to cancel, no misrepresentation of the right, and refunds within 10 business days of cancellation
• eCFR: 16 CFR 429.0, Definitions, consumer goods and services bought primarily for personal, family or household purposes, and business days excluding Sundays and federal holidays
• PCI SSC: FAQ 1292, SAQ A eligibility, payment pages delivered entirely by a validated third party, by redirect or iframe
• PCI SSC: FAQ 1588, SAQ A script criterion, two ways an embedded-form merchant confirms its page isn't susceptible to script attacks
• PCI SSC: FAQ 1229, SAQ C-VT, the eligibility criteria for manually keyed virtual terminal transactions

Reference

• FTC: Buyer's Remorse, the Cooling-Off Rule, Saturdays counting as business days, the four worked deadline examples, postmarked cancellations and exclusions
• NPMA QualityPro: Credentials, the US V6.1 standards and the termite warranty or service agreement requirement

In practice

• ServiceTitan: Send forms for e-signature, customers signing on their own devices with signed documents in the job audit trail
• ServiceTitan: Field Mobile App offline capabilities, signatures saved offline while contracts, proposals and financing need a connection
• FieldRoutes: Mobile offline mode, agreements signable offline, viewable only if opened online, and new contracts needing a connection
• Jobber: Quote approvals, drawn or typed signatures, approve and pay deposit, and signatures removed when an approved quote is edited
• SalesRabbit: Features, Digital Contracts and the Mobile eSignature add-on
• Enerflo, Docflo signing packets for solar sales
• Wisetack: How to use, customer-side applications by text link and funds released after the customer confirms completion
• Hearth, homeowners applying for financing directly
• PCT: Door-to-door sales in the pest control industry, phone and technician verification of every sale, and first service within 24 hours