What this solves
Release notes matter when they change a workflow you depend on. Focus on the route, the audience, the visible state, and what action changed.
Read by workflow
Look for whether the update affects worker applications, employer posting, readiness checks, messaging, payouts, closeout, or support routing.
A visual change is only important if it changes where a record appears, what action is available, or what support context is collected.
When an update seems wrong
If a release appears to break a route, include the page path, device, account role, expected action, and what actually happened.
Do not assume a release caused every missing shift or notification. Check account state, market filters, readiness, and device settings first.
Support routing
Support needs to know whether you are a worker, employer, or organization admin. Route-specific issues should include the affected page and record.
If the change affects money, safety, identity, or production account data, it may require deeper review and cannot be resolved by a public article alone.
Before you open support
Update is tied to a workflow, route, and user role.
Support request includes expected versus actual behavior.
Account state and filters are checked before filing a bug.
Sensitive route changes are handled through support review.