A question that comes up often: how does the system know a student volunteer isn't the same as a general one? The answer is one field.
When someone submits the signup form, the system checks whether the Program field is filled in.
1
Program field left empty. This is a general volunteer, a straightforward record with a straightforward path.
2
Program field filled in. This is a student on a placement. The system checks whether their school already exists as a record, links to it or creates it, and tags the volunteer accordingly.
3
Both paths land in the same contact record, with the right notifications firing automatically to the right people.
The two journeys still end up in the same place, but they get there differently, because they aren't really the same relationship. A general volunteer chose the organisation. A student's school chose the organisation, and the student came with it.
This is the unglamorous part of automation work. Not the flashy feature, just making sure the system makes the right call, quietly, every time. That's the difference between a form that collects information and a system that actually understands what it's collecting.