> 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/end-of-day-qa.md).

# End-of-Day QA Routine

Before you leave site each day, run a short routine that catches the problems still cheap to fix. The whole thing takes 5–15 minutes depending on the volume of Records captured.

The routine has three steps, increasingly zoomed-out, each catching different kinds of problems.

***

## The three-step pre-leave routine

```
Step 1: Per-record           Per-record completeness
        ↓
Step 2: Per parent/lineage   Per-transect / per-site cross-record check
        ↓
Step 3: Per project          Whole-project archetype-by-archetype review
```

Each step catches problems the previous one might miss.

***

## Step 1 — Per-Record: the Pending tab

For each Record you actively worked on today (especially the last few):

1. Open the Record.
2. Tap the **Pending tab** (or the equivalent indicator showing required-but-empty fields).
3. Fill anything that's empty and shouldn't be.

The Pending tab shows you what the Record's archetype requires that this particular Record hasn't satisfied. Quick fix-as-you-go.

You can skip Records that you closed cleanly — Pending will only have content if something's missing.

> **Time:** \~30 seconds per Record. Skip Records that are fully complete.

***

## Step 2 — Per parent / lineage: Focus Lineage + Data Tables

Pick a parent Record (a transect, a site) that anchors your day's work. Then:

1. Open that parent on the map.
2. Tap the kebab menu → **Focus Lineage**.
3. Both map and list now show only that parent's children.
4. Open a **Data Table** for the child archetype (e.g., STP).
5. Scroll the table. Check for:
   * Empty required fields (use the QA check toggle).
   * Inconsistent terminology between rows.
   * Records with no geometry that should have it.
6. Fix issues by tapping into the relevant cell to open the Record's form.

Step 2 is what catches **wrong parents** (see [Fixing Wrong Parents](/codifi-docs/mobile-app/records-in-context/fixing-wrong-parents.md)), inconsistent naming, and required-empty fields scoped to one logical unit of work.

> **Time:** \~3–5 minutes per parent if you have issues to fix; \~30 seconds if clean.

***

## Step 3 — Per Project: QA Data Tables across all archetypes

The widest sweep:

1. Open the **data table icon** at the top of the screen.
2. Pick an archetype.
3. Run through it with the **QA check toggle** on.
4. Repeat for each archetype actively used today.

This catches:

* Required-empty fields anywhere in the Project (not just today's work).
* Terminology drift between recorders.
* Records that look complete but have buried issues.

For big Projects, prioritize archetypes by recent activity. You don't need to QA-pass an archetype that hasn't been touched in weeks.

> **Time:** \~2 minutes per active archetype.

***

## Then sync

Once the routine is done:

1. Confirm the **cloud icon** is green or rotating. If red, you have no connectivity — sync will happen when you do.
2. Wait for the rotating cloud to settle to a green check before closing the app or stowing the iPad.
3. **For media uploads**: stay on the screen with Codifi foregrounded until media stops uploading. iOS pauses background uploads when the app isn't active — leaving site with media still queued is the most common reason a Record's photos "didn't sync."

See [Syncing & the Cloud Icon](/codifi-docs/mobile-app/getting-in-the-field/syncing-and-the-cloud-icon.md).

***

## What "good QA" looks like

A clean end-of-day exit means:

* ✅ Every Record from today has its required fields filled.
* ✅ No hierarchy warnings in the list view.
* ✅ Data tables for today's archetypes are consistent and complete.
* ✅ The cloud icon is solid green (or, on no-service days, you've confirmed sync is queued and ready for service).

It does **not** require:

* Every field filled — only required fields. Optional fields can be filled tomorrow or in the office.
* Every status moved to "Approved" — that's QC reviewer's job, not field crew's.
* Zero "In Progress" Records — many Records take more than one day to complete.

***

## If you only have 5 minutes

Start with **Step 3** — the per-Project QA tables. The QA toggle alone will surface most issues. Skip Step 1 unless you know which Records you actively worked on; Step 2 if you have time to spend on the specific parent that anchors the day's work.

***

## If you have a busy multi-day Project

For Projects running a week or more, add a weekly Step-3 pass even on days you didn't capture much — drift accumulates over time, and a weekly sweep keeps the Project clean.

For very long Projects (>2 weeks), consider syncing the Project to the web each day and having a teammate at the office run QA on the data table there. The web tables have more screen real estate, which helps with wide archetypes.

***

## Common pitfalls

* **Leaving site with media still uploading.** The Records sync; the media doesn't, because the app went to background. Wait for media to clear before closing Codifi.
* **Skipping Step 2.** Hierarchy issues only surface in Focus Lineage
  * list view. Step 3's data tables show fields, not parent relationships.
* **Running QA on archetypes that aren't used today.** Wastes time. Stick to recent activity.
* **Trying to mark everything "Approved" before leaving.** That's QC's role; field crews should leave Records in their authored status.

***

## Related

* [**QA Data Tables**](/codifi-docs/mobile-app/records-in-context/qa-data-tables.md) — the table view that powers Step 3.
* [**Fixing Wrong Parents**](/codifi-docs/mobile-app/records-in-context/fixing-wrong-parents.md) — what to do when Step 2 surfaces a hierarchy issue.
* [**Syncing & the Cloud Icon**](/codifi-docs/mobile-app/getting-in-the-field/syncing-and-the-cloud-icon.md) — what to watch for after the routine is done.
* [**Edit History, Recall, and Project History**](/codifi-docs/mobile-app/edit-history-recall-and-project-history.md) — for issues you don't catch during QA and need to fix later.