# Appraisal Intake

> Start a new residential appraisal assignment — engagement details, scope of work, assignment conditions, and a pre-inspection research packet. Use when the user says "new appraisal job", "new assignment", or gives a subject property address to begin work on.

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

---


# Appraisal Intake

Set up the assignment so nothing surprises the appraiser at the property or at delivery.

## Steps

1. **Create the job folder** `jobs/YYYY-NNN-short-name/` (next sequence number; short name from
   the street). Copy `templates/field-notes-template.md` → `field-notes.md`,
   `templates/workfile-index.md` → `workfile-index.md`, and
   `templates/discrepancies-template.md` → `discrepancies.md`.

2. **Load the state module** for the subject property from `states/<state>/module.md`. If the
   state has no module, warn the appraiser and proceed generically.

3. **Capture engagement details** (ask only for what's missing; record in `intake.md`):
   - Client / lender and AMC; intended users; intended use
   - Loan type (conventional / FHA / VA / USDA / non-lender) — this changes inspection scope
     (e.g., FHA MPR items) and report requirements
   - Report form/format: UAD 3.6 URAR (default in 2026) vs. legacy — confirm with client;
     UAD 3.6 is mandatory for GSE work Nov 2, 2026
   - Effective date type (current, retrospective, prospective); fee; due date
   - Assignment conditions, extraordinary assumptions, hypothetical conditions (if any)

4. **Run the engagement checklist** in `templates/engagement-checklist.md` — competency check,
   prior-services disclosure (USPAP Conduct: any service on this property in the prior 3 years?),
   conflict of interest, E&O coverage confirmation.

5. **Build the pre-inspection research packet.** For each item, record the source and date pulled
   in `workfile-index.md`; anything not obtainable becomes a `VERIFY:` line in `discrepancies.md`:
   - Municipal **tax card / assessment record** (see state module for where and what it looks like)
   - **Deed** and current vesting; recent transfer history (3-year sale history is required
     analysis; 12-month listing history for the subject)
   - **Purchase contract** if applicable (analyze concessions, personal property, atypical terms)
   - **Zoning** designation + overlay districts (state module lists common overlays — e.g.,
     Maine Shoreland Zoning)
   - **FEMA flood map** panel and zone
   - Prior **MLS listings** and photos of the subject
   - **Permits** on file with the code office (additions, decks, systems)
   - Plat/survey or lot dimensions from GIS

6. **Pre-draft the inspection plan**: known question marks from research (e.g., tax card shows
   3 bedrooms but old listing says 4 → measure and confirm), plus loan-type-specific items.
   Write these as a "watch list" at the top of `field-notes.md` so the site-visit skill
   surfaces them on-site.

## Output

End with: job-id created, engagement summary table, research items obtained vs. `VERIFY:` list,
the inspection watch list, and pointer to the next skill (`site-visit`).