> 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.md).

# Records in Context

You've created Records. You've taken photos. Now what?

This section is about everything that happens **between captures and sync** — reviewing what you have, catching mistakes, fixing wrong relationships, running quality checks. It's the "check" beat in the field-day loop, and it's what separates a productive field day from one that creates rework.

***

## What's in this section

| Page                                                                                                       | Use it when you want to…                                                                                 |
| ---------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| [**The Records List in Practice**](/codifi-docs/mobile-app/records-in-context/records-list-in-practice.md) | Understand what each row, card, and indicator on the map and list views actually means                   |
| [**Fixing Wrong Parents**](/codifi-docs/mobile-app/records-in-context/fixing-wrong-parents.md)             | A Record's geometry is fine but it's linked to the wrong parent — how to find and fix it                 |
| [**QA Data Tables**](/codifi-docs/mobile-app/records-in-context/qa-data-tables.md)                         | Review every Record of one archetype side-by-side, catch inconsistencies, find required-but-empty fields |
| [**End-of-Day QA Routine**](/codifi-docs/mobile-app/records-in-context/end-of-day-qa.md)                   | The three-step pre-leave-site check that catches problems while you can still fix them                   |

***

## The three layers of QA in Codifi

Codifi gives you quality-control tools at three layers, increasingly zoomed-out:

| Layer                    | What you check                                        | Tool                                   |
| ------------------------ | ----------------------------------------------------- | -------------------------------------- |
| **Per Record**           | One Record's required fields                          | The **Pending tab** on each Record     |
| **Per parent / lineage** | All children of one transect, site, or other parent   | **Focus Lineage** + an open data table |
| **Per Project**          | Every Record of an archetype across the whole Project | **Data Tables** (QA view)              |

A good end-of-day routine touches all three. See [End-of-Day QA Routine](/codifi-docs/mobile-app/records-in-context/end-of-day-qa.md).

***

## Why this matters

Field data is most fixable **while you're still on site**. A wrong parent caught at the trailhead is a 30-second fix; the same wrong parent caught at the office two weeks later requires you to remember which STP belongs to which transect (or rely on photos to figure it out, or worst case, re-visit).

The features in this section exist because the cost curve is steep:

* **On site, in the moment:** cheapest to fix.
* **End of field day:** slightly harder; you may need to retrace thinking.
* **Back at the office:** much harder; you're working from memory and photos.
* **After deliverable submission:** essentially unfixable for client purposes.

The point of QA tooling is to push the catch as early in that curve as possible.

***

## Related

* [**Syncing & the Cloud Icon**](/codifi-docs/mobile-app/getting-in-the-field/syncing-and-the-cloud-icon.md) — what happens after QA when you reconnect.
* [**Edit History, Recall, and Project History**](/codifi-docs/mobile-app/edit-history-recall-and-project-history.md) — the audit trail of changes, including the Recall flow for reverting a wrong value.
* [**FAQ for Field Crews**](/codifi-docs/frequently-asked-questions/field-crews.md) — quick answers to common QA-related questions.