AI for roofing companies
Prepare a roofing pre-visit packet for roofing companies: three administrative tasks, a synthetic worked example, and a complete reviewed brief.
Quick answer
For roofing companies, start with a roofing pre-visit packet for the office project lead. Assemble scope and coordination evidence before a visit; weather questions and material choices remain decisions for the project lead. Righthand can help prepare the administrative draft from inputs you authorize; staff review its evidence and decide the next action.
Three desk tasks
1. Collect scope references
Link the accepted scope and current site notes. Separate a customer’s new request from work the contractor has already agreed to perform.
2. Prepare schedule options
Organize the approved availability and unresolved coordination questions. Do not move a crew or promise a new date without the lead’s decision.
3. List completion questions
Summarize missing photos or staff confirmations needed for the office record. Label absent evidence instead of deciding workmanship is acceptable.
Who owns each handoff?
| Input | Proposed assistant deliverable | Responsible person |
|---|---|---|
| approved project register and customer correspondence | roofing pre-visit packet with record references | office project lead |
| Missing or contradictory fields | Exception and source-linked question | Named source owner |
| Approved next step | Reviewable coordination draft | Staff authorize external action |
Worked example: three records, three outcomes
The following inputs and outputs are synthetic, not customer results. Read them as a test packet for this desk.
| Illustrative source row | Useful worked output |
|---|---|
| Project R-81: accepted quote is version two; customer attaches a later proposal covering extra work. | Keep the accepted scope as the reference and prepare a change-request question for the office lead. |
| Project R-82: office note suggests a weather contingency but no revised date is approved. | Show the contingency as proposed, leaving the existing appointment unchanged. |
| Project R-83: final photos exist, but the office’s required staff review remains blank. | List the missing review step instead of declaring workmanship accepted or the project closed. |
Correction check: Correct the proposal pointer without treating the newer document as an agreement. Ask the project lead to confirm any schedule revision before updating the client-facing draft.
Complete first-run brief
Prepare a roofing pre-visit packet from approved project register and customer correspondence. Cover October 12–16, 2026; use America/Los_Angeles for date cutoffs. Include these source fields: project ID, site, approved scope, appointment window, access contact, open materials query. Trigger: Monday at 9 AM. Output: a source-linked Markdown draft in my private review thread, grouped by next action and owner. Reviewer: the office project lead. Flag missing fields or conflicting versions. Leave inspections, workmanship acceptance, safety decisions, and material or warranty judgments to staff. Do not send messages, change source records, or spend money. Result check: Check scope version, appointment status, and outstanding evidence against the office project lead’s register.
Replace the illustrative dates and source locations before running this task. Use an approved extract when a native connection and its exact actions have not been verified; the extract remains a snapshot, not live synchronization.
First-week check and failure boundaries
Prepare one pre-visit packet and compare it with the office lead’s scope and scheduling review that afternoon. A quote revision can be confused with the accepted scope. A tentative weather contingency may be read as a confirmed reschedule; preserve the status of each. Leave inspections, workmanship acceptance, safety decisions, and material or warranty judgments to staff. When an input changes, rerun the affected comparison and retain its source reference; do not overwrite the authoritative operational record with a draft.
The Righthand documentation explains setup. Consult source-record guidance for the underlying system, and use Features to check the proposed task fit. Review Pricing against the actual pilot workload before expanding.