1. 1Define template — enter slug, display title, layer, optional description, and paste your checklist.
2. 2Clarify — answer AI setup questions (frequency, scoring, deploy mode, federal flag if applicable).
3. 3Review & create — confirm questions, schedule, score categories, then Create & deploy.

1. 1Click + Add Question in the top-right corner.
2. 2Fill in Question ID (unique key, e.g. PPE_05), Question Text, and Field Key (auto-filled from Question ID if left blank).
3. 3Choose the Section — Intake, Gate, Core, or Conditional.
4. 4Set the Answer Type. Yes / No / N/A / Not Sure is the most common; use Text for open-ended fields and Multi-select for checklists.
5. 5Set Display Order to control where the question appears in the form (lower = earlier).
6. 6Configure Photo, Scoring, and Conditional settings as needed (see sections below).
7. 7Click Save Question.

Click the Edit button on any row to open the edit drawer. All fields are editable including the question text, answer type, and scoring weight.

To change display order, edit the Order number in the drawer, or use the ⇧ ⇩ arrow buttons on the question row to move it up or down one position. Reordering updates display_order for all affected questions in a single batch.

Toggling a question inactive hides it from the mobile form without removing it from the database. Past submissions that answered the question are preserved and still visible in the Submissions tab.

There is no delete button by design — deactivate instead of deleting to preserve historical data integrity.

Each scorable question has a Score Weight (points) and a Score Category. When a question is answered, its weight is added to the category’s possible total. If the answer is a pass value (yes or na), the weight is also added to earned points.

Category score = earned ÷ possible × 100. Overall score is the same calculation across all categories combined.

Conditional questions that are never shown (parent answer did not trigger them) are excluded from scoring entirely.

1. 1Open the edit drawer for the question.
2. 2Scroll to Scoring. Set Score Category to the relevant category (or leave blank to exclude from scoring).
3. 3Set Score Weight (1–10). Higher weight = more impact on the category score. Most questions use 1–3; critical items (e.g. fall protection) may use 5–10.
4. 4Pass Values default to ["yes","na"] for yes/no types, ["pass","na"] for pass/fail, and ["4","5"] for number ratings. Only change when you need custom pass logic.

1. 1Create or edit the child question (the one that should be hidden by default).
2. 2Set Section to conditional.
3. 3In Parent Question, select the question whose answer controls visibility.
4. 4In Trigger Values, enter a JSON array of answer values that will show this question — e.g. ["no","not_sure"].
5. 5Save. The Branch Tree tab will show the new relationship immediately.

The Branch Tree tab renders the full parent–child hierarchy. Each parent question is shown with its trigger values and an indented list of the child questions it controls. Useful for auditing logic before adding new conditional questions.

Questions with no parent (top-level) are not shown in the tree — only conditional relationships appear.

The global row (Job ID = All jobs) applies to every job unless a per-job override exists. Override rows take full precedence for that specific job.

The lower section shows a live row for every job that has submitted at least one inspection. Each row displays the job’s next due date, current mode, last score, and whether Buildertrend reports active crew.

Use the Reset Due Date date picker and Set button to manually override the next due date for a job — useful for rescheduling after a site shutdown or holiday.

The first KPI chip label changes by template filter:

• Surveys — GC Check In and similar survey-style templates
• Inspections — Weekly Safety and QC templates
• Submissions — when viewing All Templates

Pass/fail coloring uses each question’s score_pass_values from question config:

A rating of 5 on a satisfaction survey should show Pass (green), not fail.

Click the Job ID link (blue, underlined) on any submission row to expand a full Q&A panel beneath it. Questions are grouped by section. Answers are colour-coded: Yes / N/A = pass, No = fail (row highlighted red), Not Sure = caution.

Photo thumbnails load at the bottom of the panel. Click any thumbnail to open the full-size image in a new tab. Signed URLs expire after 1 hour.

Click the Job ID again to collapse the panel.

The Delete button on a submission row permanently removes that record from the database. After deletion, the field user can re-submit a fresh inspection for the same job and date.

This is the correct way to reset a test submission or allow a crew member to redo an inspection that was submitted in error.

Use the toolbar at the top of the Submissions tab to filter by Job ID (partial match), Submitted By email (partial match), or exact Date. Filters apply client-side to the loaded batch of up to 200 records. Click Refresh to reload from the database.

Below the progress bar, each user sees a How to view toggle. This is a personal preference — admins do not force one layout for everyone.

The choice is saved in the browser (localStorage key jrco-inspection-display-mode) and applies to every inspection on that device until the user changes it. Users can switch modes at any time during a draft — answers are preserved.

Follow-up questions appear when a parent answer triggers them, in both view modes. In carousel mode, the step counter updates when new questions become visible.

Next is blocked until the current question is answered. If a photo is required, the user must attach one before advancing. Review Score still validates the full form and jumps to the first incomplete item.

Question IDs are not shown to field users. Validation messages use question text only.