> 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/records-in-context/records-list-in-practice.md).

# The Records List in Practice

The Records list (and the map card view, which shows the same Record summaries) is more than just a navigation aid — every row carries context that lets you spot trouble without opening the Record.

This page is the cheat sheet for what each indicator means.

***

## What every row shows

```
┌──────────────────────────────────────────────────────────────┐
│  ●  STP-005  (geom indicator)                       👤 [AV]   │  ← top line
│      ▼ Transect 1 / Block A                                  │  ← hierarchy hint
│      🟡 In Progress    📷 12                                  │  ← status + media
└──────────────────────────────────────────────────────────────┘
```

Reading top to bottom:

| Element                | What it tells you                                                                                          |
| ---------------------- | ---------------------------------------------------------------------------------------------------------- |
| **Color dot** (left)   | The archetype's symbology color — same as the map. Helps you spot which archetype this row is at a glance. |
| **Record title**       | The Record's name. May be auto-generated from a Ripple formula, or typed by the recorder.                  |
| **Geometry indicator** | Tiny point/line/polygon icon if the Record has a captured location. Absence means no geometry yet.         |
| **Assignee avatar**    | Who owns the Record. Default is the creator; can be reassigned.                                            |
| **Hierarchy hint**     | The parent chain — useful when Records of the same archetype have ambiguous names.                         |
| **Status pill**        | The Record's lifecycle state (In Progress, Ready for Review, Approved). Color-coded.                       |
| **Media count**        | Number of photos, videos, and files attached.                                                              |

***

## The map card

The same information shows up on the map when you tap a Record. The card is wider but carries the same fields:

* Title
* Status pill
* Assignee avatar
* Hierarchy
* Media indicator

Plus a few **action buttons** unique to the map view:

* **Center** — re-center the map on this Record's geometry.
* **Kebab menu** — the actions you can take on this Record (Add Child Record, Take Photo, Manage Relationships, Focus Lineage, etc.).

***

## Map view vs list view — same state

The map view and list view are **two windows on the same Records**. The state is shared:

* **A filter applied in the map** carries over to the list.
* **A Record selected on the map** is highlighted when you switch to the list.
* **A Record opened in either view** shows the same data — there's no "map version" and "list version" of a Record.

Use whichever view fits the moment: map for spatial relationships, list for hierarchical browsing.

***

## Assignees in practice

Every Record has an **assignee** — the person responsible for the Record. Codifi uses assignees for three things:

1. **Filtering.** "Show me only my Records" is one tap from the filter sheet — useful on a busy Project with multiple crew members.
2. **Workflow handoffs.** A common pattern: Record starts assigned to the field crew member who created it, gets reassigned to a QC reviewer when it moves to "Ready for Review," and possibly reassigned again to a report author when it moves to "Approved."
3. **Accountability.** When a regulator asks "who recorded this value?" the assignee plus the edit history gives you a clean answer.

To reassign: tap the assignee avatar on a Record card or list row and pick a new Project member.

> Note: A Record's *creator* is fixed in history; the *assignee* can change over time. Both are visible on the Record's [Edit History](/codifi-docs/mobile-app/edit-history-recall-and-project-history.md).

***

## Hierarchy hints in the list

The list view is where Codifi's parent-child structure becomes visible. Child Records are indented under their parents, so you can scan the Project's relationship tree:

```
▼ Site 1
   ▼ Feature 01
       ▼ Artifact (12)
   ▼ Feature 02
       ▼ Artifact (4)
   ▼ Shovel Test Probe (45)
```

Tap a parent row to expand or collapse. The collapse state persists across sessions for this Project, so big trees stay manageable.

***

## What to look for in row indicators

A few patterns crews use to spot issues at a glance:

* **A Record with no geometry indicator** that should have one — either the geometry was forgotten or never captured. Drill in and check.
* **A status pill that doesn't match the work done** — e.g., "In Progress" on a Record that's clearly complete, or "Ready for Review" on something with empty required fields. Pending tab will tell you more.
* **An assignee avatar that's wrong** — the Record was created on the wrong account, or hasn't been handed off. Tap to reassign.
* **A media count of 0** when photos were definitely taken — the photos might be attached to the wrong Record. Check the Photos layer (see [Photos on the Map](/codifi-docs/mobile-app/capturing-photos-and-media/photos-on-the-map.md)).

***

## Filtering and finding Records

The filter sheet (top of the map / list screen) lets you narrow by:

* **Archetype** — only show STPs, only show Sites.
* **Status** — only show In Progress, only show Approved.
* **Assignee** — only show Records assigned to a specific person.
* **Date range** — only show Records modified in the last N days.
* **Spatial** — only show Records within a polygon you draw on the map.

Filters stack — apply two or three and Codifi shows the intersection. Filters carry across map and list views and persist across sessions.

Clear filters with the **Clear** chip in the filter sheet.

***

## Common questions

### Why is a Record showing in the list but not on the map?

It probably doesn't have geometry yet. Open the Record and check the location card — if it's empty, the Record exists but has no spatial component.

### Why does the map show a Record but the list seems to be missing it?

Either a filter is hiding it from the list (check active filters), or the Record's parent is collapsed in the hierarchy view. Tap the parent to expand.

### Why is selection in one view not highlighting in the other?

It should. If it isn't, that's a bug — try sync or app restart.

***

## Related

* [**The Map Screen**](/codifi-docs/mobile-app/mapping-locations/understanding-the-map-screen.md) — the map view's controls, gestures, and Smart FAB.
* [**Fixing Wrong Parents**](/codifi-docs/mobile-app/records-in-context/fixing-wrong-parents.md) — what to do when hierarchy hints show a wrong relationship.
* [**QA Data Tables**](/codifi-docs/mobile-app/records-in-context/qa-data-tables.md) — the next step up: comparing fields across many Records at once.