How Changes Ship: Our Weekly Release Cycle

Coach Pulse ships on a fixed weekly cycle aligned with Tapestry’s change-management process. Knowing the rhythm tells you when to expect movement on any request.

Monday — this week’s slate is locked, and the following week’s work is scoped.

Tuesday — final QA and dev testing on this week’s changes.

Wednesday — the Change Advisory Board (CAB) meets and approves what ships.

Thursday–Friday — approved changes deploy to production, and a change summary is published at the end of the week.

Three horizons run in parallel: this week is locked, next week is scoped, and a dated backlog feeds future cycles. That’s why a request may sit in a Planned status for a bit — it’s queued into a cycle, not forgotten.