---
title: Repair Request
description: >-
  Enable a Repair Request on a completed inspection, let buyers or agents select
  findings in the portal, and track seller Accept, Decline, or Counter responses.
canonical: 'https://www.swiftreporter.com/docs/repair-request'
pathname: /docs/repair-request
category: reports
date: '2026-09-27T00:00:00.000Z'
---

# Repair Request

Repair Request lets buyers and agents ask for repairs from findings on a completed report, and lets sellers respond—without leaving SwiftReporter. You enable and monitor the request on the inspection hub; parties negotiate in the customer portal.

## Before you begin

- The inspection status must be **completed**.
- Sharing eligibility must already apply: a report credit used for this inspection, or an active/trial subscription that includes reports (same gate as [Sharing Reports and Invites](/docs/sharing-reports-invites)). A **Paid** job badge alone does not unlock Repair Request.
- Add contacts with roles on the inspection (buyer, seller, agent). Repair Request uses those roles for who can ask and who can respond.
- Share the report with the parties who need to participate so they can see findings.
- Negotiation happens on the **web** inspection hub and **customer portal**. There is no mobile negotiation screen in this release.

## Who does what

Default capabilities come from contact roles when you enable the request (they cannot be edited in the hub UI in this release):

- **Primary customer**, **additional customer**, and **agent** — **Ask** (select findings and submit).
- **Seller** — **Respond** (Accept, Decline, or Counter each line).
- Other roles default to **View**.

You (the inspector) enable, monitor, **Close**, or **Withdraw**. You do not Accept or Decline as a negotiation party.

## Enable a Repair Request (inspector)

1. Open the completed inspection on the web at **Inspections →** the job.
2. Find the **Repair Request** card (near Share and Contacts).
3. Confirm **Default participants** look right: buyers and agents **Ask**; seller **Respond**.
4. Leave **Notify parties** checked if you want email notifications when the request opens.
5. Select **Enable repair request**.

The card shows status badges such as **Open**, **Awaiting response**, **Countered**, **Agreed**, **Declined**, **Closed**, or **Withdrawn**. Expand a row with **Details** to see participants and line items. Use **Close** when negotiation is finished, or **Withdraw** to stop an active request.

If the inspection is not completed, the card asks you to complete it first. If contacts are missing, add roles before enabling. If the report is not unlocked, creating a request requires the same unlock as sharing.

## What buyers and agents do (portal)

Parties sign in to the [customer portal](/docs/customer-portal-dashboard) with the same one-time code or email link as today. Buyer emails typically open the portal dashboard; from there open **Repair requests**. Seller and agent emails may deep-link to `/portal/repair-requests/{id}`.

1. On the portal dashboard, open the **Repair requests** card (**View all**), or go to **Repair requests**.
2. Open the request for the inspection.
3. Under **Select findings**, choose observations from the report and optionally add a short note per item.
4. Select **Submit repair request**. Status moves to **Awaiting response**.

Role hints on the list show **Your role: request repairs**, **respond**, or **view**.

## What sellers do (portal)

1. Open **Repair requests** from the portal dashboard (**View all**), or use an email link when it points at the request.
2. For each item, choose **Accept**, **Decline**, or **Counter**.
3. For **Counter**, enter a short counter proposal (and optional note), then save the response.

When a seller counters, the asker can **Accept counter** or **Decline counter** on that line. One counter round is enough for this release—there is no unlimited back-and-forth UI.

## Statuses you may see

| Status | Meaning |
| ------ | ------- |
| **Open** | Enabled; asker has not submitted items yet |
| **Awaiting response** | Asker submitted; waiting on responder |
| **Countered** | At least one line has a counter pending asker review |
| **Agreed** / **Declined** | Rollup after responses |
| **Closed** | Inspector closed the request |
| **Withdrawn** | Inspector withdrew the request |

Line items show **Pending**, **Accepted**, **Declined**, or **Countered**.

## Notifications

Participants can receive email when a request opens, when items are submitted, when someone responds, and when the request closes. SMS is not sent for repair requests in this release.

## Packaging

Repair Request is included wherever report sharing already is (All-in-One / trial with unlock or reports entitlement). There is no separate Repair Request plan or per-request fee.

## Troubleshooting

- **Enable is disabled or unlock message appears:** Complete the inspection, unlock the report (credit or qualifying subscription), and add contacts with roles.
- **Party cannot see findings:** Share the report with their email first ([Sharing Reports and Invites](/docs/sharing-reports-invites)).
- **No repair requests in the portal:** The inspector must enable a request and include that contact as a participant.
- **Agent cannot Accept for the seller:** Only the seller (responder) Accepts, Declines, or Counters submitted lines. Agents ask by default and cannot be reassigned as responders in the hub UI in this release.

## Related

- [Sharing Reports and Invites](/docs/sharing-reports-invites)
- [Shared Inspections and Viewer Access](/docs/shared-inspections-viewers)
- [Customer Portal: Dashboard](/docs/customer-portal-dashboard)
- [Viewing the Report](/docs/viewing-report)