Product Update - May 14, 2026

Inspections — All 12 Field Types in Conduct Mode — full field-type support for workplace inspections and safety audits

The Inspections conduct flow now renders a purpose-built input for every field type defined in a template: boolean pass/fail buttons, numeric inputs with optional units, star ratings, live sliders, photo capture with camera access, in-app signature pads, single and multi-select dropdowns, and date/time fields. Previously, every checklist item — regardless of its type — showed the same pass/fail buttons, forcing inspectors to work around the UI or lose structured data. Now, numeric and slider responses are automatically graded against the template's configured min/max range, and the inspection's score breakdown updates in the sidebar after every answer without a page reload. The actions menu has also been refined: completed inspections can be deleted with an appropriate confirmation prompt, and the "Continue" button is shown only to team members who have edit rights.

Use case: A safety manager conducting a temperature-monitoring audit can enter exact readings (e.g., 38°F) directly into a number field — the system flags any reading outside the safe range as failed and updates the inspection score in real time, eliminating the need for a separate spreadsheet.

Available in: Inspections → Conduct Inspection → Checklist Items

---

Forms — Per-Field Default Values and Read-Only Mode — pre-fill and lock form fields for compliance and standardization

Form builders can now set a default value on any text, number, email, phone, URL, select, or radio field, and optionally mark it as read-only so respondents see the value but cannot modify it. The lock is enforced server-side on every submit path — in-app, public forms, mobile, and API — so a client-side workaround cannot override a configured field. The form builder surfaces both controls in a single collapsible "Default & read-only" panel, and a badge on the canvas card shows the current state at a glance. Date and datetime fields with the read-only flag skip the calendar picker entirely, so the field is visually inert. A misconfigured required + read-only field with no default is blocked in the builder before it can be saved.

Use case: An HR team can add a "Per Diem Rate: $75" field to an expense form, pre-fill it with the standard rate, and lock it — so every submission carries the correct value without relying on employees to type it in correctly.

Available in: Forms → Form Builder → Field Properties → Default & Read-Only

---

Job Board — Hiring-Team Collaboration Notes on Candidates — structured candidate notes for recruiting teams

Hiring teams can now post threaded notes directly on a candidate's profile in the Job Board. Each note includes a visibility selector — "Hiring team" (visible to anyone who can manage the candidate) or "Just me" (author-only) — so sensitive observations and general feedback can coexist in the same space. Authors can edit their own notes within a 15-minute window; admins can edit or delete any note at any time, and an "edited" badge appears after a note is changed. The notes list updates via Turbo Streams without a full page reload, and all mutations (add, edit, delete) are recorded in the candidate's existing audit trail. This replaces a single overwritable text field that could only hold one person's comments at a time.

Use case: A recruiter posts an initial phone-screen note visible to the full hiring team, and the hiring manager adds a private "strong preference" note visible only to themselves — both stay attached to the candidate throughout the pipeline.

Available in: Job Board → Candidate Profile → Notes