Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.holace.io/llms.txt

Use this file to discover all available pages before exploring further.

A HoLaCe investigation request is paired with an investigation form — the structured data the field investigator fills out and submits. Today the platform ships one canonical form (the California habitability form) with more in the pipeline as Innate Fox and other partners expand into adjacent case types. [Screenshot: The investigation forms listing in the firm dashboard showing the available form types with descriptions]

​
Today’s catalog

Health & Safety (CA Habitability)

The flagship form. Walks an investigator through nine violation categories on a residential property. Powers the Woods demand-letter pipeline. InvestigationType: HOUSING_CA.

Witness Interview

Coming soon. Free-form interview capture with audio attachments and structured Q/A blocks. Used in personal-injury and witness-credibility cases.

Scene Investigation

Coming soon. Photo-heavy form for accident-scene documentation, with skid-mark measurement, signage capture, and weather-at-time-of-incident fields.

Court / Records Run

MyFile Runner partnership. Court filing and records retrieval across TX, CA, IL. Tracked as a request, but the “form” is a confirmation of filing/retrieval rather than field data. Q3 2026.

​
Health & Safety — what it captures

Because this is the only form active in production today, here’s what a finished submission contains:
Address, unit number, tenant name and phone, landlord name, investigation date, investigator name. These either pre-populate from the firm’s request or are confirmed by the investigator on-site.
Each category has its own bundle of (a) checkbox-style violations with built-in severity, (b) a free-form notes field, and (c) a photo bucket:
  • Electrical — wiring, outlets, lighting, GFCI presence
  • Plumbing — leaks, pressure, drainage, hot water, mold, roof
  • HVAC — heating/cooling adequacy, filters, vent damage
  • Pests — cockroaches, rodents, bed bugs, ants, other
  • Water Damage — stains, mold growth, dampness, flooding, intrusion
  • Structural — wall/foundation cracks, floors, windows, doors, roof
  • Safety — smoke and CO detectors, railings, lead paint, asbestos
  • Paint & Surfaces — peeling paint, holes, water-damaged surfaces
  • Elevator — function, certificate currency
Investigators don’t pick severity — each violation has a baked-in low, medium, or high. “Exposed wiring” is always high. “Inadequate lighting” is always low. This keeps reports comparable across investigators and across firms.
Photos are uploaded immediately on capture and tagged to the category they were taken for. Each photo stores: the file URL, the investigator’s caption, capture timestamp, GPS coordinates (when granted), and EXIF metadata (camera model, original date taken).
A single boolean Urgent action required? raises the report’s prominence in the firm’s review queue. A general Additional notes field captures any narrative that doesn’t fit a category.

​
Where the form lives in the data model

A submitted Health & Safety form is an InvestigationForm record linked to its parent InvestigationRequest. Photos belong to InvestigationPhoto, violations to per-category records on the form. The full schema is intentionally normalized so the demand-letter pipeline can group by category, sort by severity, and embed photo evidence inline without touching freeform text.

​
Adding a new form type

Form types are not user-configurable yet. New types (e.g. WITNESS_INTERVIEW, SCENE_INVESTIGATION) are added by the HoLaCe team as the Innate Fox partnership expands and as new providers come online. If your firm needs a form type that doesn’t exist, file feedback through the in-app Bug Report button — describe the use case, the fields you need to capture, and any state-specific requirements.
The most recent shipped feature on this form is per-category save, which means an investigator no longer loses 30 minutes of work to a network blip mid-form. See Per-Category Save for why and how.