Process a delegate substitution by recording a change against the booked place and scheduled event, then updating the affected attendee records through an approved workflow. Keep the original attendee history. Do not overwrite one person's details with another's and lose the evidence of who was originally booked.
Check whether the existing training or event platform already supports substitutions and audit history. A native substitution function is preferable when it preserves the required relationships. A custom coordination step should address specific gaps between the booking system, CRM, communications, and access records.
Keep the booking place distinct from the attendee
Fictional Linden Learning has booking B-410 for six places on event E-22. Place P-3 was assigned to Maya Reed. The customer requests that Daniel Hart attend instead. The commercial booking still contains six places, but the person assigned to P-3 changes after staff approve the request.
| Record | Before substitution | After approved substitution |
|---|---|---|
| Booking | B-410, six places | B-410, six places |
| Event | E-22 | E-22 |
| Place | P-3 | P-3 |
| Attendee assignment | Maya Reed | Daniel Hart |
| Change history | Original assignment | Replacement request and decision |
This structure makes it possible to explain the change without treating Daniel as a renamed Maya. It also avoids accidentally creating a seventh place when a second attendee record is added.
Confirm scope and authority
Record who requested the substitution, the source message, the affected event and place, and the staff decision. If the request names only the old attendee but the customer has several upcoming events, ask for clarification. Do not infer the intended event from whichever booking is closest in time.
Staff should determine whether the substitution is allowed under the applicable booking process and whether any commercial change is needed. The tool can organize the evidence and prepare the update list. It should not invent terms, fees, or approval authority.
Update linked systems deliberately
Create an explicit list of affected records: attendee roster, contact record, joining-instruction queue, access arrangement, and any other scoped system. Each update needs its own completion evidence. A successful CRM update does not prove the attendee portal or message queue changed too.
Before creating Daniel's record, check whether the approved person identifier already exists in the attendee system. Use the actual platform's stable person identifiers, and inspect possible duplicates before creating another contact. Never merge people because they share a company or because one replaced the other on a booking.
Review communications and access separately
- Remove the replaced person from future event-specific preparation queues where appropriate.
- Prepare current joining instructions for the replacement attendee.
- Check whether earlier access needs to be revoked or reassigned.
- Keep general communication preferences attached to the correct person.
- Record which notifications staff approved and which remain pending.
Do not copy the original attendee's preferences or personal notes to the replacement. If the process includes information that is not needed for the new attendee, leave it out of the handoff. A substitution should not become a reason to expose another person's details.
Where one attendee has several upcoming bookings, apply the substitution only to the specified place and event. Keep their other assignments intact unless the request explicitly covers them. A person-level record update can otherwise spread a legitimate change far beyond the intended booking.
Test partial failure and repeated requests
Use fictional cases where the same request arrives twice, one system update fails, the replacement is already enrolled, and a second substitution follows the first. Include an event with several delegates sharing similar names. Confirm that retries do not add places or send duplicate instructions.
For Linden, compare the completed updates with the original approved substitution request before closing the task. Test the actual systems' behavior and reconcile the final roster against the approved assignment history. Measure wrong-person updates, duplicate places, and staff recovery effort. Clear Anvil's workflow approach can frame this bounded coordination task while staff retain authority over booking changes and external messages.
Sources and further reading
AI-assisted research and writing, checked against the linked sources. Worked examples are fictional. Product features can change; confirm the details in your own account.