> 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/qa-data-tables.md).

# QA Data Tables

**QA Data Tables** are the workhorse tool for reviewing many Records at once. Each table shows every Record of a single archetype with every field laid out in columns — so a value that one recorder entered as "Sand" and another as "sandy" jumps out instantly.

QA tables exist for every archetype that has data, and they're configurable per user.

***

## How to open a Data Table

From the top of the map or list screen, tap the **data table icon**. You'll see a list of archetypes in the Project — pick the one you want to review (e.g., "Shovel Test Probe," "Site," "Feature").

The table opens with every Record of that archetype in rows, every field in columns.

> **Screenshot placeholder:** *The data table icon at the top of the map screen, and the archetype picker that opens when you tap it.*

***

## What a Data Table looks like

```
┌──────────────┬─────────────┬──────────┬─────────────┬──────────┐
│ Title        │ Transect    │ Result   │ Top Depth   │ Bottom   │
├──────────────┼─────────────┼──────────┼─────────────┼──────────┤
│ STP-001      │ Transect 1  │ Negative │ 0           │ 30       │
│ STP-002      │ Transect 1  │ Positive │ 0           │ 45       │
│ STP-003      │ Transect 1  │ Negative │ 0           │ 25       │
│ STP-004      │ Transect 2  │           │             │           │  ← required gap
│ STP-005      │ Transect 2  │ negative │ 0           │ 30       │  ← inconsistent case
└──────────────┴─────────────┴──────────┴─────────────┴──────────┘
```

Every Record of the archetype is one row. Every field of that archetype is a column. The whole Project's worth of Records (for that archetype) is in one scroll.

***

## What you can do in a Data Table

| Action                        | Why                                                                                                         |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------- |
| **Search**                    | Find Records by value — "show me only Positive STPs," "show me Records mentioning charcoal."                |
| **Toggle column visibility**  | Hide noisy columns; freeze key columns on the left.                                                         |
| **Toggle completed Records**  | Hide approved/finalized Records when reviewing in-progress work.                                            |
| **QA check toggle**           | Highlight cells where required fields are empty.                                                            |
| **Filter By → global filter** | Send the data-table filter back to map and list views, so the whole workspace narrows to your QA selection. |
| **Tap a row**                 | Open that Record's full form for editing.                                                                   |

***

## Typical use cases

### Catch terminology inconsistencies

Different crew members sometimes use slightly different terms for the same thing — "sandy loam" vs "sandy-loam" vs "Sandy Loam." In a Data Table, these jump out because they're in adjacent rows.

Fix in place: tap the cell, open the Record, correct the value, save. Repeat across the Project until the column is consistent.

### Find required-empty fields

Tap **QA check** to highlight cells where a required field is blank. This is the cheapest way to spot Records that look complete but have a missed required value.

For each highlighted row, open the Record and fill the missing field before sync (or at least before deliverable prep).

### Search for specific results

"Show me only STPs that came up positive." Type "positive" in the search field; the table narrows to matching rows. From here you can review only the positives — useful for site documentation, sub-set exports, or photo-log cross-checks.

### Pivot to other views

After narrowing the table with search and filters, tap **Filter By** or **Apply to All** to send the same filter to the map and list. Now all three views show the same narrowed set, and you can switch between them based on what you need to see.

***

## QA Data Tables are per-archetype, not per-Record

This is the key conceptual difference from the **Pending tab** inside a Record:

* **Pending tab (per Record):** "Which fields of THIS Record are still empty?" — useful when finishing one Record.
* **QA Data Table (per archetype):** "Which Records of THIS archetype have problems?" — useful when reviewing many Records at the end of a session.

Both have their place; the table is the broader sweep.

***

## When to run QA tables

The shortest-and-best version: **run a QA Data Table for every active archetype before you leave site each day.**

A typical end-of-day pass:

1. STPs table — search for "positive" and confirm positive STPs all have follow-up notes; check QA toggle for empty required fields.
2. Features table — same QA toggle pass; eyeball for terminology consistency.
3. Site table — usually 1–3 Records; quickly scroll to confirm completeness.

For Projects with many archetypes, prioritize by which data was most actively captured today. Don't run QA on archetypes that haven't been touched.

***

## Common questions

### My table has no rows.

Either you have a filter applied that excludes everything, or you're on a fresh archetype with no Records yet. Check filters first.

### I want to see the same table on web.

Yes — QA Data Tables exist on both mobile and web. The web version has more screen real estate for wide tables and is easier when you're reviewing dozens of Records at once after sync.

### Can I edit values directly in the table?

Tap into a cell to open the Record's full form at that field. Make your edit there. The table updates when you return.

### The QA check toggle is showing things I don't think are required.

QA check uses the **required-field** configuration from the Composition. If a field is marked required in the Library but you think it shouldn't be, the fix is on the web side — talk to your project manager.

***

## Related

* [**End-of-Day QA Routine**](/codifi-docs/mobile-app/records-in-context/end-of-day-qa.md) — the full QA loop QA tables fit into.
* [**Fixing Wrong Parents**](/codifi-docs/mobile-app/records-in-context/fixing-wrong-parents.md) — for hierarchy issues that QA tables don't surface (since they're per-archetype, not cross-archetype).
* [**The Records List in Practice**](/codifi-docs/mobile-app/records-in-context/records-list-in-practice.md) — the lighter-weight per-row review.
* [**Web: The Project Workspace**](/codifi-docs/web-app/the-project-workspace.md) — QA tables on web have more screen real estate.
