---
fragment_id: oscar.map.report-types.002
domain: MAP
rule: Report type picker — four templates with distinct metadata blocks
source: app/src/map/ExportMenu.tsx
bound_to_modules:
  - oscar.map
status: SHIPPED
version: .002
---

# Report type picker (per Item 7 of operator design)

When the operator selects PDF format in the export menu, a report-type picker is shown first. The chosen report type determines which metadata block is included in the PDF title block, which fields are required, and which optional sections appear.

## Four report types

### 1. Site visit note

Internal-use record of a site visit. Low formality. Author + operator are typically the same person.

**Required metadata:**
- Project name
- Visit date
- Author name
- Operator name (defaults to author)

**Optional metadata:**
- Weather / site conditions
- Equipment used
- Free-form observations

**Sections:**
- Title block (project + date + author)
- Layer map (one per page or grouped)
- Layer table (id, name, kind, vertex count, date, version)
- Notes appendix (operator's free-form observations)

### 2. Client report

Shareable report for the customer (typically the property owner). Polished, branded, summary-focused.

**Required metadata:**
- Project name
- Customer name
- Customer address
- Visit date
- Author name
- Operator qualifications (e.g. "Arboriculturist, Level 4 Diploma")

**Optional metadata:**
- Customer reference number
- Site address (if different from customer address)
- Executive summary (1 paragraph)

**Sections:**
- Title block with customer branding
- Executive summary
- Layer map(s)
- Layer table
- Recommendations / next steps
- Sign-off block (author signature + date)

### 3. Planning submission

Formal submission to a local authority planning department. Includes methodology and qualifications.

**Required metadata:**
- Project name
- Local authority name
- Planning application reference number
- Site address
- Visit date(s)
- Author name
- Operator qualifications
- Methodology statement (free-form, multi-line)
- Statement of conformity (free-form)

**Optional metadata:**
- Tree survey reference (BS 5837 citation)
- Related planning policies

**Sections:**
- Title block with local authority branding
- Methodology
- Statement of conformity
- Layer map(s)
- Layer table
- Recommendations
- Author signature + date + qualifications

### 4. Expert witness bundle

Court-grade bundle for legal proceedings. Auditable chain of custody, every version preserved.

**Required metadata:**
- Project name
- Matter reference (court case number)
- Witness name (declarant)
- Visit date(s)
- Author name
- Operator qualifications + professional body membership
- Witness declaration (sworn statement, free-form)
- Audit hash (computed at export time)
- Chain of custody block (every edit per layer, summarised)

**Optional metadata:**
- Instructing party name
- Court / tribunal venue
- Bundle index

**Sections:**
- Title block with matter reference + court branding
- Witness declaration (sworn)
- Chain of custody (per-layer version history)
- Layer map(s)
- Layer table (id, name, kind, vertex count, date, version, audit hash per layer)
- Methodology
- Author signature + date + qualifications + professional body membership

## Court-grade requirement (per rules.md §11)

The expert witness bundle is the court-grade output. It must satisfy:

- Audit hash per layer (SHA-256 of the canonical layer JSON)
- Chain of custody block summarising every `LayerVersion` record per layer
- Witness declaration text preserved verbatim from the operator's input
- Page footer on every page: `Generated {timestamp} — Matter {ref} — Doc {docId} — Hash {docHash}`

The other three report types do not require audit hashes or chain of custody but inherit the page footer with timestamp + docId.

## Default report type

If the operator skips the picker, the default report type is `site-visit-note`. Operator can change the default in Settings later (future feature).