The Appraisal Data Schema file contains the list of 353 fields that can be saved to a user's database. Data is entered in Google Docs and Google Sheets via sidebar forms.
The schema includes calculation instructions for 40 fields, such as price per square foot, capitalization rate, expense ratio, etc. These calculations are performed via the Database Editor.
Data views for different types of records are defined in the schema file. There are five data views: Appraisal, Land Property, Commercial Property, Multifamily Property, Commercial Lease and Multifamily Lease. These views are selected in Database Editor.
Another important function of the data schema is the definition of lists (see the list of lists below). Standardized lists facilitate consistency and speed data entry.
These data populate templates and projects and provide a structured data framework that facilitates consistency across reports, and help ensure that data saved to the database is the correct kind of data. For example the schema helps prevent improperly formatted dates from being entered, or text in a numeric field and vice versa. In the case of list items, some fields require a selection from the list, like Property Types.
Appraisal files have a worksheet called ‘Data Connections & Lists’ which is automatically populated with the URLs of connected files. The Appraisal Data Schema file may require the user's permission to connect. Allowing the connection will populate the template or project file with lists and other information from the data schema.
Property Type defines the physical property and can include multiple types in the case of mixed-use properties.
Record Type defines the type of record(s) for the property. Types of records include:
There may be multiple records for a given property. For example, a sale may also be a lease and expense comp.
This is to prevent changes to the appraisal record that are not reflected in the appraisal file. Appraisal records can only be edited from the appraisal workbook via the export function. This, coupled internal business rules, will help maintain appraisal record integrity.
The Appraisal Data Schema is Read-Only. Why? Primarily to prevent well intended citizen developers from breaking the platform for other users. Schemas and databases are complicated. One of the value propositions of the StartDeck platform is it is ready to be used as is. We've done the heavy lifting for you so you don't have to build and host a database, define data types and calculations or organize lists. Appraisals vary widely across the country so don't expect a perfect match for your specific data, but you should find a reasonably good fit overall. If you have a data, calculation or list suggestion that will improve the schema for all or most users, let us know at support@startdeck.com.
All that said, you can make a copy of the data schema and customize it for your needs. While we don't provide support for customized data schemas we want you to be successful; email us at support@startdeck.com before you dive-in and we'll walk you through the basic steps and give you some tips on how to proceed.
A Field Name has certain requirements, such as no spaces or special characters.
A Field Label is more user friendly and can contain spaces and special characters.
How StartDeck uses names and labels: For the most part the StartDeck platform uses labels because they tend to be easier to recognize. One exception is the Database search UI, where we use field names.
Calculations are made in descending order, based on the field order in Appraisal Data Schema. For example, Price precedes Gross Building in the field order so that both values are available for the $/Sq Ft GBA calculation. Another example is the calculations for Effective Gross Income and Total Expenses precede the Expense ratio calculation.
Calculated fields are indicated by an icon. Calculations can be run for an individual field by clicking the icon. Be careful here if the calculated field relies on calculated precedent fields. For example, calculating the Expense Ratio depends on the precedent calculations of Effective Gross Income and Total Expenses. Therefore EGI and Total Expenses must be calculated before the Expense Ratio can be calculated.
Best Practice Tip: Run ‘Calculate All Fields’ after all comp data has been entered or after data edits.
See list content in schema file.
Comparables and Appraisal Database
Adding Records to the Database