Edit a recurring appointment
Change the recurrence parent carefully and understand that previously generated appointments remain independent records.
What this feature does
Change the recurrence parent carefully and understand that previously generated appointments remain independent records. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
Editing the parent updates its stored appointment and recurrence settings under Edit permission.
Previously generated child appointments are not generic placeholders and retain their own saved details.
Future generation uses the current parent configuration and next-cycle state.
Step-by-step workflow
- Identify the recurrence parent.
- Review generated child appointments.
- Edit timing, provider, frequency or cycles as authorised.
- Save and confirm the next recurrence state.
- Update remote calendar events for affected existing records separately.
Important fields and decisions
What happens after completion
After this workflow completes, Britixo keeps the appointment and its supported relationships connected. Reopen the appointment and verify the saved status, date, timezone, customer or lead, service, provider, attendees, reminder state, calendar or meeting reference, invoice reference and history that apply to this feature. External email, SMS, Google, Microsoft or payment outcomes must be checked separately from the Britixo database save.
- Open the saved appointment and confirm the final status and source.
- Check the participant, provider, timing and timezone from the full detail page.
- Review the relevant table filter, calendar, history, report or linked invoice instead of relying only on a success message.
Controls, checks and common mistakes
- Do not assume one edit rewrites all existing children.
- Check availability after provider/time changes.
- Document material recurrence changes.
- Use the least destructive correction and retain the appointment history when the booking existed operationally.
- Never bypass a permission, availability, approval, client-access or verification control by changing an unrelated route or setting.
