Skip to content

Implement Drop and Transfer Workflows #77

@perigrin

Description

@perigrin

Overview

Implement drop and transfer workflows for program enrollment management that are currently marked as "will be implemented in a future iteration" in the integration tests.

Current State

Integration test file t/integration/drop-transfer-workflows.t exists with placeholder indicating future implementation.

Required Features

Drop Workflows

  • Student withdrawal from programs
  • Partial refund calculations based on timing
  • Notification to staff and parents
  • Waitlist progression when spots open
  • Data retention and historical tracking

Transfer Workflows

  • Move students between programs/sessions
  • Handle pricing differences and adjustments
  • Approval workflow for transfers
  • Schedule conflict detection
  • Communication to all stakeholders

Business Logic

  • Refund policy enforcement
  • Waitlist management integration
  • Capacity updates and rebalancing
  • Financial reconciliation
  • Audit trail for all changes

Technical Requirements

  • Integration with existing workflow processor
  • Payment system integration for refunds/adjustments
  • Notification system for stakeholder communication
  • Database updates maintaining data integrity
  • Background job processing for complex operations

User Stories

As a parent, I want to withdraw my child from a program and understand any refund implications.

As a parent, I want to transfer my child to a different session that better fits our schedule.

As a program administrator, I want to approve transfer requests and manage resulting schedule changes.

As an administrator, I want to automatically progress waitlisted families when spots become available.

Implementation Phases

  1. Drop Workflow: Basic withdrawal functionality
  2. Transfer Workflow: Program/session transfers
  3. Financial Integration: Refunds and adjustments
  4. Automation: Waitlist progression and notifications

Dependencies

Priority

Medium - Important enrollment management feature

Estimated Effort

Medium - Moderate complexity with multiple system integrations

Metadata

Metadata

Assignees

No one assigned

    Labels

    backendBackend/server-side developmentfeatureNew feature or requestmediumMedium complexity implementationmedium-impactMedium business impactworkflowWorkflow system

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions