Bamboo Change Request

Standard JIRA ticket template. Product fills this out before refinement; developers should treat any missing or unanswered field as a blocker.

0. Ticket header

Change Request Title:

Requesting Product Owner:

Requester (if different from PO):

Date submitted:

Need By Date:

1. Effective dates

New Business (NB) Effective Date:

Renewal Effective Date:

Mid-Term Policy Changes

No Yes

Mid-Term Effective Date:

Mid-term handling rule for in-force policies:

2. Programs & Carriers Impacted 0 of 15

Pick the program-carrier-product combination for each affected program. Hit Add Product to commit each one; the saved entry appears below as Product #1, #2, etc. Add up to 15. To remove a saved entry, use its Delete button.

Build a product entry

Admitted

Carrier

Product

State

Change Requested

3. Description of changes requested

Freeform. Describe what is changing and why — business intent, scope, context, examples, edge cases, anything that helps refinement. Bullet points, numbered lists, or prose are all fine.

4. Policy lifecycle considerations

Each item below must be answered, even if the answer is "no impact." That confirms it was considered.

New business impact:

Renewal impact:

Grandfathering rules for in-force policies:

Effective date / transition logic:

Downstream systems impacted:

Other teams / workflows impacted:

5. Bamboo program reference table

Read-only source of truth. The Section 2 dropdowns are pre-filtered with these options.

#	Bamboo Offering	Program Type	Admitted	Carrier	Products	DIC