# TVöD-SuE May 2026 Implementation Timeline

**Last Updated:** 2026-01-07  
**Target Implementation Date:** April 25-30, 2026  
**Effective Date:** May 1, 2026 (Entgelttabelle), January 1, 2026 (Jahressonderzahlung)

## Timeline Overview

| Phase              | Date Range        | Activities                                               |
| ------------------ | ----------------- | -------------------------------------------------------- |
| **Preparation**    | April 20-24, 2026 | Pre-implementation verification, backup, branch creation |
| **Implementation** | April 25-27, 2026 | Code updates, HTML table updates, content updates        |
| **Testing**        | April 28-29, 2026 | Comprehensive testing, bug fixes                         |
| **Deployment**     | April 30, 2026    | Staging deployment, production deployment                |
| **Monitoring**     | May 1-7, 2026     | Post-deployment monitoring, issue resolution             |

## Detailed Timeline

### Phase 1: Preparation (April 20-24, 2026)

#### Day 1: April 20, 2026 (Monday)

**Time:** 2-3 hours

- [ ] Review all documentation files
  - [ ] `TVOED_SUE_2026_VERIFICATION.md`
  - [ ] `TVOED_SUE_MAY_2026_CHANGES.md`
  - [ ] `TVOED_SUE_MAY_2026_IMPLEMENTATION_GUIDE.md`
  - [ ] `TVOED_SUE_MAY_2026_UPDATE_CHECKLIST.md`
- [ ] Verify source URLs are still accessible
- [ ] Confirm effective dates haven't changed
- [ ] Review current implementation documentation

#### Day 2: April 21, 2026 (Tuesday)

**Time:** 1-2 hours

- [ ] Backup `v2/pages/tools_tvoed_sue.php`
- [ ] Create git branch: `feature/tvoed-sue-may-2026-update`
- [ ] Set up testing environment
- [ ] Prepare value mapping spreadsheet for quick reference

#### Day 3: April 22, 2026 (Wednesday)

**Time:** 1 hour

- [ ] Final verification of all values
- [ ] Cross-reference with official sources one more time
- [ ] Prepare implementation workspace

### Phase 2: Implementation (April 25-27, 2026)

#### Day 4: April 25, 2026 (Thursday)

**Time:** 4-6 hours

**Morning (2-3 hours):**

- [ ] Update JavaScript data object version (Line 884)
- [ ] Update VKA Entgelttabelle values (Lines 891-907)
  - [ ] S2-S4 (18 values)
  - [ ] S7-S8b (18 values)
  - [ ] S9-S11b (18 values)
  - [ ] S12-S14 (18 values)
  - [ ] S15-S18 (24 values)

**Afternoon (2-3 hours):**

- [ ] Update Bund Entgelttabelle values (Lines 909-925)
  - [ ] Verify S2-S14 match VKA
  - [ ] Replace S15-S18 placeholder values with VKA values
- [ ] Update Jahressonderzahlung percentages (Lines 991-1003)
  - [ ] VKA: 4 percentages
  - [ ] Bund: 4 percentages

#### Day 5: April 26, 2026 (Friday)

**Time:** 4-6 hours

**Morning (2-3 hours):**

- [ ] Update HTML table values - Erzieher table (Lines 2923-2949)
  - [ ] S2: 6 values
  - [ ] S3: 6 values
  - [ ] S4: 6 values
- [ ] Update HTML table values - Sozialpädagogen table (Lines 2976-3002)
  - [ ] S7: 6 values
  - [ ] S8a: 6 values
  - [ ] S8b: 6 values

**Afternoon (2-3 hours):**

- [ ] Update HTML table values - Leitungen table (Lines 3029-3118)
  - [ ] S9-S18: 60 values (10 S-Gruppen × 6 Stufen)

#### Day 6: April 27, 2026 (Saturday)

**Time:** 2-3 hours

- [ ] Update FAQ content - Jahressonderzahlung (Lines 3348-3351)
- [ ] Update schema markup - FAQPage (Line 824)
- [ ] Update content sections (Line 2146, others)
- [ ] Search and update all percentage references
- [ ] Commit all changes with descriptive commit message

### Phase 3: Testing (April 28-29, 2026)

#### Day 7: April 28, 2026 (Sunday)

**Time:** 4-6 hours

**Calculation Testing:**

- [ ] Test all S-Gruppen × Stufen combinations (96 test cases)
- [ ] Verify Tabellenentgelt matches Entgelttabelle
- [ ] Verify Jahressonderzahlung calculations:
  - [ ] EG 1-8: 90% of Tabellenentgelt
  - [ ] EG 9-15: 85% of Tabellenentgelt
- [ ] Test part-time calculations (10%, 50%, 75%, 100%, 150%, 200%)
- [ ] Test VKA vs Bund switching
- [ ] Test edge cases (minimum/maximum values)

**Display Testing:**

- [ ] Verify HTML tables display correct values
- [ ] Verify calculator results display correctly
- [ ] Verify FAQ content displays correctly
- [ ] Verify schema markup validates correctly

#### Day 8: April 29, 2026 (Monday)

**Time:** 2-3 hours

**Browser Compatibility:**

- [ ] Chrome (latest)
- [ ] Firefox (latest)
- [ ] Safari (latest)
- [ ] Edge (latest)
- [ ] Mobile browsers (iOS Safari, Chrome Mobile)

**Final Checks:**

- [ ] Code review
- [ ] Fix any bugs found during testing
- [ ] Final verification of all values
- [ ] Documentation review

### Phase 4: Deployment (April 30, 2026)

#### Day 9: April 30, 2026 (Tuesday)

**Time:** 2-4 hours

**Morning (1-2 hours):**

- [ ] Deploy to staging environment
- [ ] Run staging smoke tests
- [ ] Verify staging calculations
- [ ] Fix any staging issues

**Afternoon (1-2 hours):**

- [ ] Deploy to production
- [ ] Run production smoke tests
- [ ] Verify production calculations
- [ ] Monitor error logs

**Evening:**

- [ ] Monitor for first few hours
- [ ] Check user feedback channels
- [ ] Document deployment

### Phase 5: Monitoring (May 1-7, 2026)

#### Day 10: May 1, 2026 (Wednesday) - Effective Date

**Time:** 1-2 hours

- [ ] Monitor calculation accuracy
- [ ] Monitor error logs
- [ ] Check user feedback
- [ ] Verify no regression issues

#### Days 11-16: May 2-7, 2026

**Time:** 30 minutes/day

- [ ] Daily monitoring of calculation accuracy
- [ ] Daily check of error logs
- [ ] Daily review of user feedback
- [ ] Document any issues found
- [ ] Resolve any critical issues immediately

## Rollback Plan

### If Issues Discovered During Testing (April 28-29)

1. **Immediate Actions:**

   - Document the issue
   - Assess severity (critical vs. minor)
   - Fix if minor, rollback if critical

2. **Rollback Steps:**

   ```bash
   git log --oneline  # Find commit hash
   git revert <commit-hash>
   # Or restore from backup
   ```

3. **Post-Rollback:**
   - Investigate root cause
   - Fix issue
   - Re-test thoroughly
   - Re-implement when ready

### If Issues Discovered After Deployment (May 1+)

1. **Immediate Actions:**

   - Assess severity
   - If critical: Rollback immediately
   - If minor: Fix in hotfix branch

2. **Rollback Steps:**

   - Revert production deployment
   - Restore previous version
   - Communicate to users if necessary

3. **Hotfix Process:**
   - Create hotfix branch
   - Fix issue
   - Test thoroughly
   - Deploy hotfix
   - Monitor closely

## Critical Milestones

| Milestone                     | Date     | Status Check |
| ----------------------------- | -------- | ------------ |
| Documentation Review Complete | April 20 | ✅           |
| Backup & Branch Created       | April 21 | ✅           |
| JavaScript Data Updated       | April 25 | ⏳           |
| HTML Tables Updated           | April 26 | ⏳           |
| Content Updated               | April 27 | ⏳           |
| Testing Complete              | April 29 | ⏳           |
| Staging Deployed              | April 30 | ⏳           |
| Production Deployed           | April 30 | ⏳           |
| Effective Date Reached        | May 1    | ⏳           |
| Monitoring Complete           | May 7    | ⏳           |

## Risk Mitigation

### Risk 1: Value Errors

**Mitigation:**

- Double-check all values against verification spreadsheet
- Use copy-paste from verified sources
- Test calculations with known values

### Risk 2: Missing Updates

**Mitigation:**

- Use comprehensive checklist
- Search for all percentage references
- Review all file locations

### Risk 3: Browser Compatibility Issues

**Mitigation:**

- Test on all major browsers
- Test on mobile devices
- Use responsive design best practices

### Risk 4: Calculation Errors

**Mitigation:**

- Test all S-Gruppen × Stufen combinations
- Test edge cases
- Verify against official sources

### Risk 5: Deployment Issues

**Mitigation:**

- Deploy to staging first
- Run smoke tests
- Have rollback plan ready

## Communication Plan

### Internal Communication

- **April 20:** Notify team of upcoming implementation
- **April 25:** Start implementation, daily updates
- **April 30:** Deployment notification
- **May 1:** Effective date confirmation

### External Communication (if needed)

- **May 1:** Update any public-facing documentation
- **May 1:** Monitor user feedback channels
- **May 1-7:** Respond to user inquiries

## Success Criteria

- [ ] All values updated correctly
- [ ] All calculations produce correct results
- [ ] All HTML tables display correct values
- [ ] All FAQ content updated
- [ ] Schema markup validates correctly
- [ ] No browser compatibility issues
- [ ] No calculation errors
- [ ] No user complaints about accuracy
- [ ] Deployment successful
- [ ] Monitoring shows no issues

## Notes

1. **Timeline Flexibility:** Dates are targets. Adjust as needed based on actual progress.

2. **Effective Date:** Entgelttabelle changes are effective May 1, 2026. Jahressonderzahlung changes are effective January 1, 2026 (calendar year).

3. **Testing Priority:** Focus on calculation accuracy first, then display, then browser compatibility.

4. **Documentation:** Keep all documentation updated throughout implementation.

5. **Communication:** Keep stakeholders informed of progress and any issues.