A central feature of many templates—including Move In, Tenant Move In, and Move Out—is the condition table.
For example, a standard condition table appears in a Move-Out inspection like this in zInspector 3.
To start, you will see the list of areas:
This hallmark zInspector inspection feature works great for most users as specified in the standard (default) templates; however, through multiple field options, they certainly can be fully customized to suit your needs.
This very short video explains how to begin customizing a template and is essential viewing for all users:
To begin customizing any template, go to Settings → Document Templates, locate the template you wish to edit, and click on the New Draft icon to the left; it looks like this:
Condition Table Template Options
A condition table is added to a template using an Inspection Table code similar to the default version below:
Z:[[Inspection Table | Move-Out Conditions | [N=New,E=Excellent;S=Satisfactory,F=Fair,P=Poor;D=Damaged;all;picture;both;] ]]
Let’s break this down to understand each portion:
Z:[[Inspection Table This is the field type.
| Move-Out Conditions | This is the title we see on the template for the Inspection Table.
[N=New,E=Excellent;S=Satisfactory,F=Fair,P=Poor;D=Damaged; This defines the actual condition values. See that the the condition value categories are separated from each other by semicolons (;). The first condition listed within each category is the primary condition value. Additionally there can be secondary condition values within each category: they follow the primary condition value and are separated by commas (,). (For more info on customizing the condition values, see this article.)
all; This specifies the Areas that are contained within the property that will be included in the condition table. In this case, it’s “all” meaning that all areas available for the specified property will be present in the inspection table. Alternately, you can specify areas, separated by commas (e.g., bedroom,bathroom;) to only include the listed areas in the table. Specifying yard; or exterior; would include any areas with the word “yard” or “exterior” in the area name (such as Front Yard/Exterior, Back Yard/Exterior, and Side Yard/Exterior).
picture; This defines what documentation is required when an Action item (!) is selected for a detail. In this case, a photo must be taken of the detail. Other options here are comment; (where a comment is required), both; (where a photo and comment are required) or none; (where no documentation is required).
both;] ]] This defines what documentation is required when a Damaged (D) condition is selected for a detail. In this case, both a photo and comment must be taken for the detail. Other options here are picture; or comment; or none;
On the following table you can see some more examples for the different ways inspection tables can be setup:
|System Fields – Inspection Table||Z:[[Inspection Table | Move-In Conditions | [N=New, E=Excellent; S=Satisfactory,F=Fair,P=Poor; D=Damaged; all] ]]||Move-In condition table that includes all Areas and Details. No documentation (photos or comments) is required for Action (!) and Damaged (D) items.|
|Z:[[Inspection Table | Move-In Conditions | [N=New, E=Excellent; S=Satisfactory,F=Fair,P=Poor; D=Damaged; all;none;none;optional] ]]||Same condition table as in the previous example BUT the table itself in this case is optional, and again no pictures or comments are required for Action (!) and Damaged (D) Items.|
|Z:[[Inspection Table | Move-In Conditions | [N=New, E=Excellent; S=Satisfactory,F=Fair,P=Poor; D=Damaged; all;none;picture;optional] ]]||Same optional condition table as in the previous example, but in this case a photo is required for Damaged (D) Items.|
|Z:[[Inspection Table | Bedrooms | [N=New;S=Satisfactory;D=Damaged;bed] ]]||Required condition table only covering the bedroom Areas. Photo and comment documentation is optional.|
|Z:[[Inspection Table | Bedrooms | [N=New;S=Satisfactory;D=Damaged;bed;picture;both] ]]||Same as in the previous example, but a photo is required for Action Items (!), and both a photo and comment are required for Damaged (D) Items.|
|Z:[[Inspection Table | Full Property (no Yards or Roof) | [N=New;S=Satisfactory;D=Damaged;!yard,!roof] ]]
||Required condition table for all Areas—except for any yard and roof areas, which are excluded. Photos and comments for all condition values are optional.|
Another potentially helpful field that you can use to add an instructive prompt as a prefilled comment within a particular detail is as follows:
Z:[[Instruction | AREA_DETAIL | [bedroom;;closet; check for dust] ]] This field adds a placeholder on the Area Detail level, in the comment field. In the above example, the placeholder is for the Bedroom Area, under the Closet Detail.
Z:[[Instruction | AREA_DETAIL | [;;lock; Check if locks] ]] If you wish, you can omit the Area specifier from the previous example, to apply the comment to any/all areas that contain the specified detail, as shown here.
These two examples will appear as follows in the zInspector 3 app:
Area Summary Table Options
As an alternative to the Condition Table, zInspector offers the Area Summary. Instead of a table with conditions covering the property on the Area Detail level, there will be a table with a list of all the Areas of the specified property (by default), along with photos and comment documentation options. As with the condition table, for the Area Summary photos and/or comments can be required or optional. Area Summary examples follow.
|System Fields – Area Summary||Z:[[Area Summary | Areas Conditions | [all] ]]||Shows a list of all Areas (no condition table or area details). Requires photos and comments.|
|Z:[[Area Summary | Areas Conditions | [all;optional-comments] ]]||Shows a list of all Areas. Requires photos but comments are optional.|
|Z:[[Area Summary | Areas Conditions | [all;optional-picture] ]]||Shows a list of all Areas. Requires comments but photos are optional.|
|Z:[[Area Summary | Areas Conditions | [all;optional] ]]||Shows a list of all Areas. Comments and photos are optional.|
This article only covers the condition table fields. For info on all other template fields, see this article.
- Before you begin customizing any template, always make sure you have removed the following field on the very top of the template:
Z:[[System | [SYSTEM_DOCUMENT] ]] If you do not remove this field, you won’t be able to save your customized template.
- To view the recent changes you made to a template in the zInspector 3 app, don’t forget to tap the Sync (cycling arrows) button in the app’s main menu bar.
Questions? Email us any time at email@example.com.