PDF-based termite reports cannot contribute items to the repair list

Objective

• Enable repair list functionality for jobs that include PDF-based termite (WDI) reports, so agents and clients can build and share a repair list from termite findings the same way they can from HTML inspection reports.
• Unblock SE and other markets that regularly include termite reports on multi-service jobs and are receiving agent requests for repair list access on those reports.

Background

• The repair list feature works by reading individual defect items from Attik's structured HTML report format and allowing users to select and add them to a repair list. PDF-based reports — including termite/WDI forms like NPMA-33, state-specific WDI forms, and similar regulated PDF formats — have no selectable items because their content is rendered as a flat PDF rather than structured data.
• Catherine Lemoine (SE/Residential Inspector) raised this during the Implementation meeting on June 23, noting that a buyer's agent had asked about repair list access for termite findings that same day. She confirmed the issue affects multiple states, each with their own PDF form requirements.
• Chris Scott confirmed there is no current solution: the PDF structure does not expose item-by-item content to the repair list system. Two roadmap approaches were discussed:
• Option A — Pull form fields into actionable items: Build tooling that extracts structured data from the inspector's form input (as they fill out the PDF in Spectra) and surfaces those as selectable repair list items alongside the PDF export. This is the more complete long-term solution and aligns with the new Attik report writer direction.
• Option B — Stripped-down parallel template: Create a lightweight Attik-native report template alongside the PDF that captures key defect observations in structured form, allowing repair list selection from that template while the PDF serves as the official deliverable. Chris noted this is the current workaround at Scott's team for rental license inspections.
• Both approaches are on the roadmap. Chris noted Option A becomes significantly easier once Attik controls the data input layer (i.e. once the Attik report writer replaces Spectra for these form types), which is still in development.
• Catherine committed to communicating to affected agents that the team is aware and working on a solution.

Product Decisions

Locked

1. No immediate workaround to ship — Converting toggles to dropdowns or other field-level hacks are not acceptable solutions. The fix must provide genuine repair list item selectability from termite report findings.

Open

1. Approach selection — Option A vs. Option B — Which roadmap path to pursue first? Option A (form field extraction → actionable items) is the better long-term solution but depends on Attik report writer progress. Option B (parallel stripped-down template) is shippable sooner but adds operational overhead for inspectors. To be decided by Chris and Ryan — likely after the report writer reaches a stable enough state to assess Option A feasibility.
2. PDF form coverage — A full inventory of PDF form types in use across all markets is needed before implementation: NPMA-33, state-specific WDI forms, rental license inspections, four-point forms, etc. Scope will vary by approach chosen.

Scope

Frontend

• attik-frontend/src/app/client/reports/components/RepairListProvider.tsx — Manages repair list state and the add-to-list action; will need to support items sourced from non-defect-card origins (e.g. manually entered or form-extracted items) once an approach is chosen.
• attik-frontend/src/app/client/reports/components/DefectCard.tsx — Current entry point for adding defect items to the repair list; PDF reports have no equivalent component. The approach chosen will determine whether a new component is needed here or upstream.
• attik-frontend/src/app/client/reports/components/ReportSections.tsx — Renders report sections containing defect cards; PDF report sections will need their own rendering path that can surface selectable items.

Backend / Report Service

• The data extraction or parallel template approach will involve attik-report-service or the new report writer pipeline — exact files TBD based on approach selected.

References

• Implementation — All Regions transcript, June 23, 2026 (Catherine Lemoine, Chris Scott, Ryan Wagner)