SwiftReporter
Repair Requests That Stay With the Report
After the report is shared, buyers and agents select findings, sellers respond, and you monitor status—without a separate repair spreadsheet or email thread.
After the report is shared, buyers and agents select findings, sellers respond, and you monitor status—without a separate repair spreadsheet or email thread.
Post-Report Negotiation Without Leaving SwiftReporter
Clients already open shared reports and the customer portal for appointments, invoices, and contracts. Repair Request adds the missing step after delivery: a structured ask-and-response loop tied to the same observations you wrote in the field.
Inspectors enable the request on the web inspection hub. Parties work in the portal. You stay the facilitator—monitor status, then Close or Withdraw when the job is done.
For core reporting, see home inspection software. For how parties get into the report, see Sharing Reports and Invites.
What You Get
Enable From the Inspection Hub
On a completed, share-eligible inspection, open the Repair Request card, confirm participants from contact roles, optionally Notify parties, and select Enable repair request.
Askers Select Real Findings
Buyers, co-buyers, and agents pick observations from the report—title, severity, recommendation, and notes—then Submit repair request. No free-form “custom line” inventing outside your findings in this release.
Sellers Accept, Decline, or Counter
Responders act per line with Accept, Decline, or Counter plus a short note. Askers can accept or decline a counter. Status rolls up to Agreed, Declined, and related states you can see on the hub.
Portal Entry Parties Already Use
The dashboard always shows a Repair requests card (with an empty state when none apply). Parties use the same OTP or email-token sign-in as the rest of the portal; sellers and agents may land on a specific request, while buyers typically open the dashboard and continue from Repair requests.
Why It Matters for Your Business
- Fewer side channels — Repair asks stay next to the report instead of scattered across email and PDF markups.
- Clear roles — Buyers and agents ask; sellers respond; you enable and close.
- Same access rules as sharing — Unlock or reports subscription gates apply; no new paid Repair Request SKU.
- Switch-ready story — Named repair-request workflows are a common reason teams compare platforms; SwiftReporter covers the job without cloning competitor chrome.
Frequently Asked Questions About Repair Request
Is Repair Request a separate paid product?
No. It is included wherever report sharing already is (All-in-One / trial with unlock or reports entitlement). There is no new meter or SKU for enabling a request.
Can agents submit repair asks?
Yes. Primary customers, additional customers, and agents ask by default; sellers respond. Agents cannot Accept on behalf of the seller, and the hub does not let you reassign capabilities in this release.
Does this work on the mobile app?
Inspectors continue to complete and share on mobile. Enabling, monitoring, and portal negotiation are web and portal workflows in this release.
Does Repair Request change who can download the PDF?
No. Portal PDF download rules are unchanged. Repair Request access is separate from customer-only PDF gates.
Where can I read the how-to?
See the Repair Request docs for inspector and portal steps.
Keep Repair Asks Next to the Report
See how Swift Reporter ties findings, sharing, and portal responses together—or compare options in the best home inspection software guide.
