# Report Assembly

> Assemble the appraisal report draft — UAD 3.6 URAR sections and narrative addenda — from the job folder's intake, field notes, reconciliations, mechanicals, and comps. Use when the user says "draft the report", "assemble the report", or "write the addenda".

- Skill: `bedardandy/report-assembly` (Agent Skill)
- Install (CLI): `npx skillmds@latest add bedardandy/report-assembly`
- Raw SKILL.md: https://api.skillmd.com/api/skills/bedardandy/report-assembly/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: bedardandy (https://skillmd.com/u/bedardandy)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/bedardandy/report-assembly

---


# Report Assembly

Turn the accumulated workfile into a report draft the appraiser finalizes in their form software.
This produces **section-by-section content**, not the delivered XML — it's the writing layer.

## Preconditions

Check the job folder. If `field-notes.md`, `discrepancies.md`, or `comps.md` are missing or have
unresolved `MATERIAL` items, list them and ask whether to proceed with placeholders (each
placeholder becomes a `VERIFY:` block in the draft).

## Steps

1. Load `references/urar-uad36-outline.md` for the section map (and legacy mapping if the client
   requires an old form during the transition window — confirm from `intake.md`).
2. Draft `report-draft.md` section by section, pulling only from job-folder sources and citing
   the source file for each fact (`[field-notes]`, `[tax-card]`, `[deed]`…). If a file tool
   refuses the `report-draft.md` filename on a content heuristic, write it via shell to the
   same path — do not rename the file; the job-folder convention is fixed. Sections:
   - Subject & assignment (from intake — client, intended use/users, effective date)
   - Contract analysis (purchase assignments)
   - Neighborhood / market area description and trends — **fair-housing-safe language only**
   - Site (from field notes + state module items: zoning & overlays, flood, well/septic,
     road/access, waterfront)
   - Improvements (room-by-room from field notes; C/Q ratings as confirmed; mechanicals ages
     and update timeframes from `mechanicals.md`; UAD 3.6 room-level detail where captured)
   - Sales comparison (grid + support narrative from `comps.md`)
   - Other approaches: include cost approach (site value support, cost source, depreciation)
     and income approach only per scope of work; state why an approach was excluded
   - Reconciliation and appraiser's value conclusion (appraiser supplies; skill drafts the prose)
   - Assumptions, limiting conditions, extraordinary assumptions/hypothetical conditions
   - Certifications — include the **transparent AI-assistance disclosure block by default**
     (recommended language provided). Removal is a deliberate appraiser decision made against
     their practice policy and client requirements — removal, not omission, is the act that
     needs a record.
3. Weave in **discrepancy commentary**: every `MATERIAL` item from `discrepancies.md` must have
   its approved explanation sentence appear in the relevant section. QC will fail the draft if not.
4. Assemble the **exhibit list**: photo pages (mapped from `photos/` names to captions), sketch
   with GLA calculations, location/flood maps, tax card, deed, contract.
5. Update `workfile-index.md` — every document cited in the draft must appear in the index.

## Style

Report-quality prose: factual, past tense for observations, no hedging filler, no
superlatives, no fair-housing-problematic terms. Numbers must match their source files exactly —
if two sources conflict, stop and point at the unresolved discrepancy instead of picking one.

## Output

End with: sections drafted vs. placeholdered, the open `VERIFY:` list, exhibit checklist status,
and next skill (`appraisal-qc`).