# Merger Workflow Integration Kit — first-wave brief

Use this with your own team. Blank project answers are unknown, not verified facts.

## Receiving workflow

Which customer task must the receiving team complete?

Project answer: ___
Evidence / owner / next decision: ___

## Cohort and first consumer

Which cohort moves first, and which application or team consumes the new path?

Project answer: ___
Evidence / owner / next decision: ___

## Scoped identity

Which identifiers can overlap across source businesses, and how will the consumer distinguish them?

Project answer: ___
Evidence / owner / next decision: ___

## Required history

Which versions and effective dates must remain available, and what are the capture boundaries?

Project answer: ___
Evidence / owner / next decision: ___

## Authority and operating ownership

Who accepts access, actions, exceptions, coexistence and recovery?

Project answer: ___
Evidence / owner / next decision: ___

## Timing and next decision

What operating transition drives this wave, and which buyer decision comes next?

Project answer: ___
Evidence / owner / next decision: ___

## Proposed paid boundary

One policyholder, member or account workflow, one cohort and its first receiving consumer, including the required adapter, mapped data/API path, acceptance, cutover and operating handover.

## Remaining decisions

Access, exclusions, acceptance owners, operating handover, delivery dates and commercial scope remain to agree.

Local tool use does not send this brief. Choose what to share through https://www.jextra.com/campaigns/merger-workflow-integration#lead-form.