> 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/fixing-wrong-parents.md).

# Fixing Wrong Parents

A Record's geometry can be correct while its **parent relationship** is wrong — the STP shows up at the right spot on the map but is listed under the wrong transect. The map looks fine, so it's easy to miss. The list view (and your reports later) tell the real story.

This page walks through how to spot, diagnose, and fix this kind of problem.

***

## How the problem appears

You're scrolling the list view at the end of the day. Under **Transect 14** you notice **two Records both named "STP 2."** They shouldn't both exist — each transect has unique STP numbers.

Codifi shows you an info warning on the row that triggered the duplicate (essentially: "another Record with this title exists at this hierarchy level"). That warning is the signal.

The wrong-parent Record might:

* Be visually fine on the map (it has accurate geometry).
* Have correct field data inside it.
* Just be linked to the wrong transect — maybe Transect 14 instead of the Transect 13 it was actually under during capture.

The fix is to **reassign the parent**, not to delete and re-create.

***

## The fix workflow

### Step 1 — Open Focus Lineage on the suspect transect

Tap **Transect 14** to open its Record card. From the kebab menu, choose **Focus Lineage**.

Focus Lineage **scopes the entire workspace to one parent's family**. Map and list both narrow to just Records under Transect 14 (and its sub-children, like STPs).

You'll now see only the Records that *claim* to be part of Transect 14 — including the misplaced one.

### Step 2 — Spot the out-of-place Record on the map

With the map now showing only Transect 14's family, the misplaced STP should stand out — it'll be positioned somewhere that doesn't fit Transect 14's spatial run. Maybe it's a hundred meters off the line, or in a different field block entirely.

Tap that STP on the map to confirm it's the one with the duplicate number. Open it.

### Step 3 — Reassign the parent

From the Record screen, open **Manage Relationships** (typically under the kebab menu).

You'll see the current parent (Transect 14) and the option to:

* **Change** the parent — pick a different transect from the list.
* **Add** an additional parent — if your Composition allows multi-parent (some archetypes do, like an Artifact that belongs to both a Site and a Feature).
* **Remove** the wrong parent after adding the correct one.

Pick the correct transect (e.g., Transect 13). Save.

### Step 4 — Confirm in the list view

Clear the Focus Lineage filter. Open the list view.

The misplaced STP now appears under Transect 13. Transect 14's duplicate is gone. The map didn't change at all — geometry was always right.

***

## When this happens

Common ways crews end up with a wrong-parent Record:

* **Auto-parent inference at high creation rate.** When you're rapidly creating Records with Quick Actions, occasionally the suggested parent isn't the one you intended — the previous one was a different transect. The Record gets created under the wrong parent.
* **Editing while a different parent is selected on the map.** If you open a transect on the map, then drift to another part of the Project, then tap **+**, Codifi may suggest a child of whatever's currently selected — which could be wrong.
* **Creating a child from the wrong starting Record.** Tapping "Add Child Record" on Site B when you meant Site A.

None of these are catastrophic — Focus Lineage + Manage Relationships handles all of them in under a minute.

***

## Why map placement isn't enough

It's tempting to think "the Record is in the right spot, so it must be under the right parent." But Codifi's relationship structure is **logical**, not spatial — Records relate to each other by parent-child links, not by proximity on the map.

Your reports, exports, and hierarchical analysis all use the logical structure. If a child Record is linked to the wrong parent, your report will count it under the wrong transect — even if the GIS export shows it at the correct coordinates.

That's why the list view and Manage Relationships matter even when the map looks fine.

***

## Daily routine

A quick scan for hierarchy issues at end of day:

1. Open the list view.
2. Look for **info warnings** on rows — these flag duplicate names under a parent.
3. For each warning: open Focus Lineage on the parent, find the misplaced child, reassign.

This is rarely more than a one-minute task on a normal day, and catches issues that would compound into hours of report-cleanup later.

***

## Related

* [**The Records List in Practice**](/codifi-docs/mobile-app/records-in-context/records-list-in-practice.md) — what each row indicator means; spotting issues at a glance.
* [**QA Data Tables**](/codifi-docs/mobile-app/records-in-context/qa-data-tables.md) — the more zoomed-out review that catches consistency issues across many Records at once.
* [**End-of-Day QA Routine**](/codifi-docs/mobile-app/records-in-context/end-of-day-qa.md) — the wider routine this fits into.
* [**Understanding Archetypes and Relationships**](/codifi-docs/mobile-app/creating-records/understanding-archetypes-and-relationships.md) — the underlying parent-child model.