Manage report templates in Attik instead of spectora

Objective

Let client care add, duplicate, and repair Spectora-linked report templates directly from the Attik work order so they no longer bounce through Spectora for common template fixes, including optional templates that are not tied to a charge.

Background

• Today many corrections require Spectora UI plus a resync, which is slow when templates were wrong at booking time.
• Required report wiring already flows through helpers such as attik-backend/src/util/functions/spectora/getInspectionReportsAndRequired.ts, which merges service primaryOnly rules with existing Spectora reports.
• The work order surface renders report rows through attik-frontend/src/app/tools/inspections/[id]/components/reports/Reports.tsx, which is the likely home for new “add template” affordances.

Scope

Frontend

• Add actions from the report bucket to clone the template tied to a charge, add an unattached template via dropdown, and extend the charge or agreement change modal so users can see which template will be created and optionally skip creating a blank template.

Backend

• Confirm Spectora APIs support posting additional templates to a live job before exposing controls; spike results should drive error handling and idempotency rules.

References

• attik-frontend/src/app/tools/inspections/[id]/components/reports/Reports.tsx
• attik-backend/src/util/functions/spectora/getInspectionReportsAndRequired.ts
• Feature sync notes captured in related planning docs

Transcript notes (Apr 16 feature sync)

• Feature sync added three concrete UX directions:
• add another instance of the charge-linked template from within the existing report bucket,
• allow adding an extra unassigned template from a dropdown / actions menu,
• when adding a charge that would normally create a blank report template, let the user explicitly skip creating that template.
• A real operational use case came up: inspectors or client care may need to add the right report quickly without going back into Spectora, especially when the original required-report mapping was wrong.
• The team also noted a spike question before fully committing to UI work: confirm that Spectora APIs can reliably post additional templates directly to a live job.