> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Handle a Record That Belongs to Two Processes
- URL: https://blog.jestor.com/record-that-spans-two-processes/
- Published: 2026-09-17T22:34:18.000Z
- Updated: 2026-09-17T22:34:18.000Z
- Author: Bruno Bannach

Handling **a record that belongs to two processes** — a deal that becomes a project, a ticket that becomes a bug — is a structural question. Duplicating it is the wrong answer; connecting is usually the right one.

## Why duplication is tempting

Each process wants its own phases, fields, and owners, which makes a second record look natural.

- The same client details entered twice
- Two records that disagree after an edit
- No way to see the full lifecycle in one place
- Reporting that counts the same work twice

## Three options

| Approach                    | Fits when                                        |
| --------------------------- | ------------------------------------------------ |
| **One record, more phases** | The same team continues the work                 |
| **Two connected records**   | Different teams, phases, and fields apply        |
| **Two views of one record** | The phases are the same but the audiences differ |

## How to build it in Jestor

1. Where the same team continues, extend the phases on the existing **Kanban** in **Jestor**.
2. Where teams differ, create a connected record and trigger its creation from the status change.
3. Connect both to the same client record so details are never entered twice.
4. Surface the originating record on the new one through the connected display.
5. Where only the audience differs, build a second app over the same table rather than a second table.

## Why choose Jestor for lifecycle continuity?

Because **Jestor** can trigger record creation from a status change, the handoff between processes happens automatically — the project exists the moment the deal closes.

The connected display then surfaces the original deal's value and terms on the project card, so the delivery team sees what was promised without opening anything else.

## Frequently Asked Questions

### Should I duplicate the record?

No — connect them, or extend the phases. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Can the second record be created automatically?

Yes, triggered by the status change.

### Can the project see the deal's terms?

Yes, through the connected display.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.