> ## Documentation Index > Fetch the complete documentation index at: https://www.planmyrounds.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # What changes when you edit something? > How editing a Shift Requirement, Shift Schedule, doctor profile, or leave affects existing Duty Plans versus Duty Plans generated afterward. PlanMyRounds reads doctor profiles, shift definitions, and approved leave **fresh every time it generates a roster**. It doesn't watch for changes and update rosters that already exist. That one fact explains most of the surprises admins run into. | You change... | An already-generated Duty Plan | The next Duty Plan you generate | | ----------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | A Shift Requirement's timing or staffing | Not affected. [Check the specific roster](/docs/troubleshooting/shift-timing-is-wrong) rather than assuming it updated. | Uses the new timing and staffing. | | A Shift Schedule's composition | Not affected — a Shift Schedule is only read when a roster or Auto Duty cycle is generated against it. | Uses the updated pattern. | | A doctor's profile (department, seniority, hour limits, excluded shifts) | Not affected. See [Doctor profiles](/docs/team/doctor-profiles#edit-a-doctors-profile): "changes take effect on the next roster you generate." | Uses the updated profile. | | Approve a leave request | Not affected if the roster was already generated or published — [edit it manually](/docs/rosters/editing-a-published-roster) or regenerate. See [Approving leave](/docs/leave/approval-workflow#approve-a-request). | Excludes the doctor on those dates, since only Approved leave is a hard constraint. | | Scheduling rules (max consecutive days, rest hours, ratios) set in the wizard | Not affected — these are set per Duty Plan at creation, not read from a shared setting. | Only applies to a new Duty Plan created with those rules, or via [Retry with relaxed constraints](/docs/rosters/retrying-a-failed-roster) on an existing one. | | Auto Duty settings (cadence, automation toggles, Shift Schedule) | A cycle already in progress runs to completion as normal. See [Turning automation off mid-cycle](/docs/auto-duty-planning/setting-up-an-auto-duty#turning-automation-off-mid-cycle). | The next Planning Cycle uses the updated settings. | | A doctor's department, pod, or location (used by Auto Duty's doctor pool) | Not applicable — the pool isn't attached to a past cycle. | The doctor pool is re-queried fresh at Notify and Generate time on every cycle, so the change is picked up automatically. See [How much runs on its own](/docs/auto-duty-planning/overview#how-much-runs-on-its-own). | ## The one exception: manual edits Editing a **published** roster directly (drag-and-drop reassignment, adding a doctor, removing an assignment) changes that roster immediately — it doesn't wait for a regeneration. See [Editing a published roster](/docs/rosters/editing-a-published-roster). This is different from editing the *inputs* (shifts, profiles, leave, rules), which only take effect on the next generation. ## If you're not sure Don't assume. Open the specific Duty Plan and check it directly — regenerate or edit it if it doesn't reflect the change you expected. ## Next steps Where generation sits relative to every other stage. "Fresh data every run" and the full list of inputs re-read on generation.