---
title: Next Level Confirmation Email — Priority Task
type: article
created: '2026-01-22'
updated: '2026-01-22'
source_docs:
- raw/2026-01-22-sprint-planning-meeting-116396706.md
tags:
- next-level
- email
- sprint-planning
- jeff
- karly
- priority
- deadline-enforcement
layer: 2
client_source: A New Dawn / Shine
industry_context: b2b-services
transferable: false
---

# Next Level Confirmation Email — Priority Task

## Overview

During the 2026-01-22 sprint planning session, the Next Level site build and its associated confirmation email were identified as high-priority deliverables. The due date had been altered without AM approval and was restored during the meeting. Karly took on action items to unblock Jeff so he could complete the build.

Related sprint context: [[wiki/meetings/2026-01-22-sprint-planning]]

## Status

**Active — In Progress**
Jeff is the assigned developer. Due date restored and content delivery from Karly is pending/in progress as of 2026-01-22.

## Background

The Next Level site build had been in Jeff's queue but was deprioritized in favor of other tasks. The due date was changed by the developer without AM approval — a process violation that was addressed directly during the sprint planning meeting. The date was restored to reflect the actual client launch target of Monday–Tuesday, February 2–3.

> *"I know dates can't move. So it's not actually, you know, I don't need it in hand today, if that makes sense. But I put it as today to keep [urgency]."* — Karly

This incident reinforced the team-wide rule: **developers must not change due dates without AM approval.** See [[wiki/process/deadline-change-policy]] for the broader policy context.

## Scope of Work

Jeff is responsible for two components within the Next Level task:

1. **Confirmation Email Build** — The email template/copy needs to be built out. As of the meeting, Karly had not yet provided the copy or format guidance.
2. **Learning Library Recategorization** — Events already exist in the system and need to be recategorized. Estimated at approximately one hour of work.

## Key Decisions

- Jeff remains the assigned developer for the Next Level build; no reassignment was made.
- Due date was restored to align with the client launch window (targeting February 2–3).
- Karly is responsible for delivering the confirmation email copy and recategorization instructions before Jeff can complete the task.

## Action Items

| Owner | Action | Status |
|-------|--------|--------|
| **Karly** | Provide Jeff with confirmation email copy and recategorization instructions | Pending |
| **Jeff** | Build confirmation email and recategorize learning library events once content is received | Blocked on Karly |

## Blockers

- Confirmation email copy not yet delivered to Jeff as of 2026-01-22.
- Client has not responded to Karly's request to schedule a final walkthrough before launch.

## Related

- [[wiki/clients/current/new-dawn-shine/_index]] — Next Level client index
- [[wiki/meetings/2026-01-22-sprint-planning]] — Full sprint planning meeting notes
- [[wiki/process/deadline-change-policy]] — Policy on developer due date changes