> For the complete documentation index, see [llms.txt](https://codifi-fdm.gitbook.io/codifi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codifi-fdm.gitbook.io/codifi-docs/mobile-app/creating-records/example-2-utah-site-form.md).

# Example 2 — Utah Site Form (forms-led)

You're documenting an archaeological site in detail. Your Project's Composition includes a **Utah Archaeology Part A** Record (the main site form with \~60 fields), with **Part B** child Records for individual loci or features within the site. The day's job is to fill the forms thoroughly; geometry can come later.

This example shows the full **forms-led** pattern — form first, geometry deferred — and demonstrates Ripple auto-fill from length × width, parent-name inheritance into child Records, and returning to capture geometry once the data is done.

***

## Setup before you start

1. Project synced, cloud icon green.
2. You're on the Project's map view.
3. Optional: turn off auto-numbering in [Mobile Project Settings](/codifi-docs/mobile-app/mobile-project-settings.md) → Record Auto-Numbering if you'd rather name Records yourself (some site forms have specific naming conventions that don't fit numeric suffixes).

***

## Step 1 — Create Part A without geometry

1. Tap the **+** button on the map screen.
2. Pick **Utah Archaeology Part A**.
3. You're offered two paths: **Create** (just create the Record, fill data first) or **Create and Map** (jump straight to geometry). Pick **Create**.
4. You land directly in the Part A form. No location capture step.

This is the forms-led move — defer geometry, focus on data.

***

## Step 2 — Fill the form

The Part A form has many fields organized into sections (Identification, Description, Cultural Affiliation, etc.).

A few mobile-side conveniences:

* **Tab / arrow keys with an external keyboard** move you between fields cleanly. If you're working on iPad with a Magic Keyboard, this is significantly faster than tapping.
* **Each field auto-saves** as you move to the next one — you'll see a green check briefly next to the label. No "save form" button needed.
* **Conditional sections expand** when you enter values that trigger them (e.g., a "Historic Period" section only appears when Cultural Affiliation = Historic).

Spend the time the form needs. You can stop at any point and come back — Codifi keeps your in-progress data.

***

## Step 3 — Watch Ripple auto-fill UTM and area

If your Composition is configured for it, you'll see auto-filled fields appear as you type. Two common ones:

* **UTM Easting / Northing** — auto-converts from GPS coordinates once you've captured a location (or pre-fills from a parent Record's geometry if one exists).
* **Area** — auto-calculates from Length × Width if your form has L and W fields.

These appear with an **FX icon** next to the field label, signaling they're computed. The form fills itself in as you go.

→ See [Ripple from a Field Crew's Perspective](/codifi-docs/mobile-app/creating-records/ripple-for-field-crews.md).

***

## Step 4 — Add a Part B child Record

A Part B Record documents a specific feature or locus within the site — e.g., "Hearth 01," "Roomblock 1." You'll typically have several Part Bs under one Part A.

1. With Part A open, tap the hierarchy button → **Add Child Record** → **Part B**.
2. Part B opens. Its title is **auto-populated** from a Ripple formula like *Part A name + " — Feature 01"* — you don't have to retype the parent site code or designation.
3. Fill Part B's fields.

This is **parent-name inheritance** — a Ripple pattern that gives child Records hierarchical names without crew effort.

→ See [Understanding Archetypes and Relationships](/codifi-docs/mobile-app/creating-records/understanding-archetypes-and-relationships.md).

***

## Step 5 — Come back for the location

Once Part A's data is solid, capture its geometry:

1. From Part A's Record screen, open the **location card**.
2. Tap **Draw**.
3. Pick a mode: **GPS** (walk the boundary and add vertices), **Manual** (drop vertices on the satellite imagery), or **Sketch** (freehand then refine).
4. **Commit** when the geometry matches the site extent.

Part B Records can each have their own geometry too — feature-level points or polygons under the site's polygon.

→ See [Creating Records with Locations](/codifi-docs/mobile-app/mapping-locations/creating-new-records-with-locations.md) for the three location-capture modes in depth.

***

## What you just demonstrated

In one \~3-minute workflow, you exercised:

| Feature                            | When it appeared                            |
| ---------------------------------- | ------------------------------------------- |
| **Create-only** path               | Deferring geometry on Part A creation       |
| **Per-field auto-save**            | The green check after each field            |
| **Conditional visibility**         | Cultural-affiliation-driven section reveals |
| **Ripple auto-fill**               | UTM and area calculations                   |
| **Add Child Record**               | Wiring Part B Records under Part A          |
| **Ripple parent-name inheritance** | Part B titles deriving from Part A's name   |
| **Deferred geometry capture**      | Opening Draw mode after the form is filled  |

That's the forms-led pattern in full.

***

## When to use this pattern vs GIS-led

Use **forms-led** when:

* The form is the deliverable's main content (SHPO submissions, agency reports, structured surveys).
* Geometry is incidental — site boundaries can be drawn from satellite imagery later.
* You're documenting one or two complex Records, not dozens of simple ones.

Use **GIS-led** (Example 1) when:

* Geometry IS the deliverable (transects, survey coverage).
* Records are numerous and similar (STPs, monitoring points, asset inspections).
* You're physically walking from Record to Record on site.

Some Projects use both — Forms-led for site documentation, GIS-led for features within a site.

***

## Where to go next

* [**Example 1 — Shovel Tests on a Transect**](/codifi-docs/mobile-app/creating-records/example-1-stps-on-a-transect.md) — the GIS-led counterpart.
* [**The Record Creation Screen**](/codifi-docs/mobile-app/creating-records/the-record-creation-screen.md) — fuller reference on the create options.
* [**Ripple from a Field Crew's Perspective**](/codifi-docs/mobile-app/creating-records/ripple-for-field-crews.md) — what the FX icon means.
* [**Records in Context — Fixing Wrong Parents**](/codifi-docs/mobile-app/records-in-context/fixing-wrong-parents.md) — what to do if a Part B ends up under the wrong Part A.