Approval evidence · Contractors
A text can show yes. Can it show what?
A message may be useful evidence, but sufficiency turns on the complete terms, intent to sign, identity and authority, the original agreement, applicable law, and a record both sides can retain.
The careful answer
Sometimes evidence. Not automatically a complete approval.
Federal E-SIGN law and many state electronic-transaction laws generally prevent rejecting a record or signature solely because it is electronic. That principle does not make every message a signature, prove who sent it, supply omitted terms, or override contract and consumer-protection requirements.
A text can help show notice, discussion, timing, or assent. Before relying on it to authorize extra work, ask whether the message identifies the exact change, money, schedule, signer, intent, and required form. When any answer is unclear, consolidate the decision into a signable approval.
Six-part sufficiency test
Do not ask only whether the text exists.
- 01
What exact record was approved?
Does the reply point to one dated scope, estimate, photo set, drawing, or change ID? “Go ahead” after several options may not identify which one.
- 02
Are the decision terms complete?
Look for additions and deletions, materials, price or pricing method, revised total, payment, schedule, assumptions, exclusions, and the limit of authorization.
- 03
Did the sender intend to sign?
Agreement to discuss, schedule, inspect, or receive an estimate is not necessarily intent to authenticate a contractual change. Use explicit adoption language and a deliberate signing step.
- 04
Can the act be attributed to the right person?
A contact name or phone number helps, but also confirm the individual, their role, account control, project relationship, and authority to approve the change.
- 05
Does the required form permit it?
Check the original contract and project law for signature, content, notice, timing, consent, delivery, and format rules. Some work requires more than an informal thread.
- 06
Can both sides retain the complete record?
Preserve participants, timestamps, preceding messages, attachments, version, delivery, and the final agreed record in a durable job file.
Ambiguous vs. complete
Turn “yes” into an identifiable decision.
“That sounds fine. Go ahead.”
The thread discussed two repair options, a rough range, and an unpriced paint match. It does not identify the selected option, maximum, schedule effect, payment, or who has contract authority.
Change CO-014 · July 10
Remove damaged sheathing in the taped 4 ft × 6 ft area shown in attached photos; install specified replacement; weatherproof and restore listed siding courses.
Net +$2,480 · two working days
Fixed addition includes labor, material, disposal, tax treatment stated in the record, and one remobilization. Revised contract total and payment milestone are shown.
Paint matching is excluded
Hidden framing decay outside the marked area stops work and requires a new written approval. The message cannot silently expand this boundary.
Named authorized customer signs
The customer deliberately adopts CO-014 through the agreed electronic process; the contractor countersigns and both dates are recorded.
One PDF plus its evidence
Both sides receive the final approval with attachments, audit details, and the earlier message thread preserved in the job record.
What a text may prove
Useful evidence and complete authorization are different jobs.
Timing and notice
When a condition, estimate, option, objection, or reply was communicated.
Identity and context
A known number, message history, project details, and surrounding conduct can help attribution analysis.
Assent to clear terms
A reply tied unmistakably to one complete proposal may be evidence of agreement, subject to governing rules.
Required change fields
Deleted scope, revised total, progress-payment effect, completion date, notices, and signatures may never appear together.
Intent to authenticate
Casual acknowledgment, thumbs-up, or scheduling language can be disputed as something short of signing.
Durable shared record
Cropped screenshots can omit participants, timestamps, attachments, edits, surrounding terms, and delivery of a final copy.
Risk signals
Escalate from messaging to formal approval.
Large price or material commitment
Use a complete, deliberate approval before ordering, demolishing, or scheduling irreversible work.
Tenant, employee, relative, or site contact
Verify who has authority under the agreement; access permission is not necessarily spending authority.
Required change order or notice
Follow the contract and jurisdiction even when the customer is enthusiastic by text.
Dispute has already started
Preserve the thread without editing it, stop disputed work when safe, and seek project-specific legal advice.
Field workflow
Use text for speed, then close the evidence gap.
- 01
Message the discovery
Send a concise condition summary and photos without presenting an unclear reply as final authorization.
- 02
Create one complete change record
State the full scope delta, price, payment, schedule, exclusions, stop point, and attachments.
- 03
Send the exact record for signature
Use the method allowed by the agreement and applicable law, with a clear action that shows intent to adopt it.
- 04
Verify signer and authority
Match the approver to the contract and confirm authority before relying on the decision.
- 05
Deliver and retain the final copy
Give both sides the completed record and preserve its attachments, timestamps, and audit details with the job.
Research basis
Electronic validity does not erase substantive requirements.
15 U.S.C. § 7001 generally says a record, signature, or contract may not be denied legal effect solely because it is electronic. It also preserves other rights and obligations, says no private person is generally required to accept electronic records, includes consumer-consent conditions for required written disclosures, and requires retained electronic records to remain accurate and accessible when retention is required.
California's UETA similarly recognizes electronic records and signatures, defines attribution by whether the record or signature was the person’s act, and looks to context and surrounding circumstances. Separately, California Business and Professions Code § 7159 and CSLB guidance require covered home-improvement change orders to be written and signed before changed work, with specified scope and price/payment or completion effects. California is an example, not a nationwide answer.
- 15 U.S.C. § 7001: electronic records and signatures ↗
- California Civil Code § 1633.7: electronic effect ↗
- California Civil Code § 1633.9: attribution and context ↗
- California BPC § 7159: home-improvement changes ↗
- California CSLB: home-improvement contracts ↗
General information only, not a conclusion about any message, contract, signature, claim, or jurisdiction. Preserve disputed communications and consult qualified local counsel before relying on or challenging an informal approval.
Text-message approval questions
Is a customer's text message legally binding?
Possibly, depending on terms, intent, attribution, context, contract, transaction, and law. Electronic form alone is neither automatic validity nor automatic invalidity.
Does replying “yes” count as a signature?
Not automatically. The facts must support intent to sign or adopt the specific record, plus attribution and every other applicable requirement.
Is a thumbs-up enough?
It may show acknowledgment or assent in context, but its meaning can be disputed and it may omit required terms or signing formalities. Use explicit approval tied to one complete record.
Should contractors screenshot text approvals?
Preserve the complete thread, participants, timestamps, attachments, and context. A screenshot can help, but a consolidated approval and durable export are stronger than an isolated crop.
From chat to record
Keep the speed. Make the decision complete.
Turn the field conversation into a clear JobSign approval with scope, price, schedule, evidence, signature, and a PDF both sides can retain.
Create a customer sign-off →