Contractor Reply Check

Paste the contractor's answer before you sign.

A helpful-sounding reply is not the same as a signed quote update. Check whether the answer actually resolves scope, allowance, payment, exclusion, permit, schedule, and change-order risk.

Check My Reply Build Questions First Review Before Signing

Input

Check the reply against the written quote.

Quote total Decision timing

Contractor reply

Reply is backed by a written scope or line-item quote section. Reply is backed by allowance, selection, quantity, or installed-cost detail. Reply is backed by exclusions, by-owner, or by-others language. Reply is backed by a payment schedule tied to milestones or delivered materials. Reply is backed by a written change-order approval and pricing rule. Reply is backed by permit, inspection, or code responsibility language. Reply is backed by start-date, delivery, delay, or schedule responsibility language. Reply is backed by warranty or owner-supplied responsibility language. A deposit, progress payment, or signature is due soon.

Output

Clarify before signing The reply has enough gaps that the next move should be written clarification, not a verbal yes.

Risk score 0/100

Reply length 0 words

Quote total not entered

Workflow reply check

Risk language detected

Clarity language detected

Written source gaps

Copyable response

Review This Reply First Build Questions Check Packet

Operating state

What this workflow is checking.

1. Source data

Quote text, contractor reply, written scope, allowance, payment, exclusion, permit, schedule, and change-order categories.

2. State transition

Reply received, written source checked, risk scored, response drafted, then either revise the quote or order a review.

3. Audit trail

The local result stores version, risk score, selected evidence, and status in the browser so the user can repeat the check.