> 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/advanced-workflows/inspector-only-notes-and-narrative-shortcuts.md).

# Inspector Only Notes and Narrative Shortcuts

Inspector only notes allow Scribers to have check boxes built into their template that do not show in the printed report. This creates super flexible templates where you can accomplish two primary goals. 

1. Create short cuts to narratives that you use all the time. This is especially effective for dialing in ScribeWare for mobile. 
2. Create notes for your inspectors that have codes and other background information you may not wish to display in the report but which will help you do your job more effectively. 

### Video #1 Shows Using Inspector Only Notes for Creating Quick Access To Your Narratives. This is Fantastical For Mobile. 

{% embed url="<https://youtu.be/OeFZSURNE-8>" %}
Inspector Only Notes for quick comment access
{% endembed %}

### Video #2 Shows Using Inspector Only Notes to Build Hidden Information Into Your Template to Help Your Inspectors

{% embed url="<https://youtu.be/Dz63cet3zEs>" %}
Stay sharp when codes and installation information can be hidden in your template&#x20;
{% endembed %}


---

# 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/advanced-workflows/inspector-only-notes-and-narrative-shortcuts.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.