> 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/the-narrative-template.md).

# The Narrative Template

ScribeWare's default Narrative Template produces a narrative style report that can be used for residential, light commercial, full condo, interior condo, and consultation inspections.

This is a narrative-style template that includes all of the needed pull-downs to describe the building. This includes a well-flushed-out library with thousands of comments, as well as gunnysack comments and parent-type comments that can be used with photo and caption techniques. This template can be used for residential inspections, light commercial inspections, condo inspections, interior-only inspections, one-item inspections, consultations, and more. It is designed as a report that you can get 50-90% done on-site and finish the report back in the office.

This is a northern climate based template and is west-coast so it has seismic considerations and standards. The following videos unpack some of the logic used to construct and use this template. These will help if you you are going to use and customize this template

## Formatting A Blue All Caps Observation Headings and a Parent Comment

The latest version of this template uses observation headings. This makes it a breeze for clients and agents to scan the summary page quickly despite the detailed narrative comments. This video will show you how to build these titles as well as a few other observation formatting tricks.

{% embed url="<https://youtu.be/hfUmOhNpGII>" %}

## Ideas for Customizing the Narrative Template to Suit Your Region.

This video shows how you can delete some of the things that may not apply to your region such as seismic protection. It also goes over several key words you can use in your library to quicky customize a lot of comments to suit your state and climate zone.

{% embed url="<https://youtu.be/zHU8s38LSAE?si=KnAWqe0-gsJIumwg>" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.scribeware.com/templates-specialty-templates-ancillary-services-and-odd-jobs/the-narrative-template.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
