> For the complete documentation index, see [llms.txt](https://docs.scribeware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scribeware.com/templates-specialty-templates-ancillary-services-and-odd-jobs/re-inspections.-everyones-favorite.md).

# Reinspections. Everyone's Favorite!

## Reinspection Using Observation Tags to Make a Custom Reinspection Report Within The Full Report 

This is my favorite way to do a reinspection. It takes a little setup, but it offers super-clean report delivery. 

{% embed url="<https://www.youtube.com/watch?t=36s&v=sYfA6U4Uf2o>" %}

## Performing a Reinspection Using a Report Copy and Observation Tags&#x20;

### Overview

There are several ways to perform a reinspection in ScribeWare. This method creates a separate reinspection report while maintaining a connection to the original inspection report. The result is a professional workflow that allows clients and agents to view either the complete report or only the reinspection findings.

### Step 1: Request a Reinspection Item List

Before scheduling a reinspection, ask the client or agent to use ScribeWare's **Inspection Request Tool** to generate a PDF containing the specific items they would like reinspected.

This provides:

* A clear scope of work
* Documentation of what was requested
* Protection against misunderstandings regarding inspected items

### Step 2: Create a Copy of the Original Report

1. Open the original inspection report.
2. Select **Copy Report**.
3. Create an exact duplicate of the original job.

#### Why Create a Copy?

Creating a copy preserves the original report in its untouched state while allowing you to document reinspection findings separately. This can be beneficial for recordkeeping and liability purposes.

### Step 3: Attach the Reinspection Request

1. Open the copied report.
2. Navigate to **General Comments → Reinspection**.
3. Attach the PDF generated from the Inspection Request Tool.

This ensures the requested reinspection items are documented within the report.

### Step 4: Flag All Items to Be Reinspected

Before going into the field:

1. Navigate to each item that requires reinspection.
2. Flag the observation.

#### Benefits of Flagging

When using the mobile app, flagged items create a focused list of only the observations that need attention. This allows you to quickly move from one reinspection item to the next without searching through the entire report.

This is especially helpful when reinspecting multiple items.

### Step 5: Complete the Reinspection in the Field

Using the mobile app:

1. Open the list of flagged items.
2. Review each observation.
3. Take updated photographs as needed.
4. Update the observation based on the current condition.

For example:

* Change a modifier from **Major Concern** to **Completed Item** if repairs have been made.
* Add notes documenting the observed corrections.

### Step 6: Tag Reinspection Findings

To create a dedicated reinspection summary:

1. Open the observation.
2. Select **Tags**.
3. Apply the **Reinspection Findings** tag.

If your template is configured with a Reinspection Findings summary page, tagged observations will automatically populate that section.

### Step 7: Optional - Gray Out Original Photos

For a cleaner presentation on desktop:

1. Open the observation photos.
2. Use the photo filtering options to gray out original inspection photos.

This creates a clear visual distinction between:

* Original inspection photos
* New reinspection photos

Many inspectors find this provides a more professional appearance.

### Step 8: Update Reinspection Status

After reviewing each item, assign the appropriate modifier:

* **Completed**
* **Partially Complete**
* **Incomplete**

Once an item has been reviewed and documented, remove its flag.

This helps track progress and confirms that all requested items have been addressed.

### Step 9: Publish the Report

When all reinspection items have been updated:

1. Publish the report.
2. Send notifications if desired.

### Understanding the Final Result

This workflow creates two useful views:

#### Full Inspection Report

The complete inspection report remains available and reflects the updated observation statuses.

#### Reinspection Findings Report

The tagged observations generate a dedicated Reinspection Findings summary page.

This allows you to:

* Send only the reinspection findings to a client or agent.
* Share a direct link to the reinspection summary.
* Allow recipients to navigate back to the full inspection report if needed.

### Recommended Workflow

1. Receive a PDF request list from the client or agent.
2. Copy the original report.
3. Attach the request list to the copied report.
4. Flag all items requiring reinspection.
5. Perform the reinspection using the mobile app.
6. Update modifiers and add photos.
7. Tag observations as Reinspection Findings.
8. Publish the report.

This approach creates a professional reinspection report that is both independent of and connected to the original inspection report.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.scribeware.com/templates-specialty-templates-ancillary-services-and-odd-jobs/re-inspections.-everyones-favorite.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.