> 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/getting-started/scribeware-and-desktop-basics.md). # ScribeWare and Desktop Basics ### The Home Page and Creating a New Report {% embed url="" %} ScribeWare overview of the finished report and back end {% endembed %} ## Creating a New Report This guide explains the different ways to create a new report and introduces the basic layout of the report editor. ### Creating a New Report From the Home screen, you'll see your list of existing inspections along with several options for creating a new report. #### Option 1: Create From Your Last Template The **Create Last Report** button creates a new report using the same template you used most recently. If you primarily perform one type of inspection, this is usually the fastest option. #### Option 2: Create From a Template Select **Create From Template** to choose from any of your available templates, such as: * Residential Inspection * Sewer Scope * Written Consultation You can have as many templates as you like. For more information on template management, see the Templates video. #### Option 3: Create From ISN, Keystone or Other Schedulers If an inspection has been imported from ISN, Keystone, or another scheduling system, simply open the inspection and select the template you want to use for that job. #### Option 4: Copy an Existing Report You can also create a new report by copying an existing one. 1. Right-click an existing report. 2. Select **Copy to New Template**. 3. Choose the template you want.
This is especially useful when performing multiple inspection types for the same client. For example, after completing a home inspection, you can copy the report into a Sewer Scope template. The client's information is automatically carried over, eliminating duplicate data entry. *** ## Understanding the Report Editor When a new report opens, ScribeWare loads all of the chapters and sections for your template. #### Top Toolbar The toolbar contains commonly used functions, including: * Publish Report * Template Management * Settings * Feedback * Flagged Items The **Flagged Items** counter shows required fields that still need to be completed before the report is finished. *** ## Report Organization Reports are organized into three levels: 1. **Chapters** (Grounds, Roof, Exterior, etc.) 2. **Sections** within each chapter 3. **Observations** within each section Every part of this structure can be customized. You can rename chapters, change their order, add or remove sections, and tailor the template to your workflow. *** ## Completing Required Fields Many sections include descriptive dropdowns used to document the property's characteristics. Required fields appear in **red**. Each completed required field reduces the number shown in the **Flagged Items** counter, making it easy to track what still needs attention before publishing. Every inspector can decide which fields are required. It's recommended that any information you want consistently included in every report be marked as required. *** ## Adding an Observation To add a comment: 1. Open the appropriate section. 2. Click **Add Observation**. 3. Use the keyword search to find the desired comment. For example, typing **corrugated** will display all comments related to corrugated storm drain piping. Select the appropriate comment, then drag and drop your photos directly into the observation. *** ## Report Text vs. Inspector Notes Each observation contains two types of information. ### Report Fields (Bold) The fields at the top are displayed in the final client report. ### Inspector Notes (Italic) The italicized fields below are for the inspector only. These notes never appear in the published report and serve as shortcuts to speed up report writing. *** ## Using Quick Checkboxes Many comments include customizable checkboxes for common recommendations. For example, if a drainage system needs servicing, simply check **Recommend Cleaning and Servicing** instead of typing the recommendation manually. Inspectors can customize these checkboxes to match their own reporting style and common findings. *** ## Using Logic Trees Many sections include expandable logic trees that organize related comments. For example, selecting **Catch Basins** displays common observations such as: * Clogged * Keep Clear * Missing Components * Other related comments Other categories, such as **Rain Barrels**, work the same way. These logic trees provide quick access to related comments without requiring keyword searches. *** After learning these basics, you'll be ready to create reports, complete required fields, add observations, attach photos, and publish your inspection reports efficiently. --- # 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/getting-started/scribeware-and-desktop-basics.md?ask=&goal= ``` `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.