Agreed. No reason for an individual record.

This is a huge issue that has wasted hours of my time. We are using the online registration form to collect sponsorships for our fundraiser dinner. I have the form set to allow organizations to register. In my mind, this would mean that the organization is the sponsor and any information collected on the form would pertain to the sponsoring organization. Of course, there needs to be a contact person, or the name of the person actually completing the form, but this person does not need a participant record or a constituent record.

As it is currently, when Sally fills out the form for her organization, both Sally and the organization become participants in the event. Both are also created as new constituents, but the organization record is basically empty except for the empty participant record for the event. It simply lists the event but has no other information like participant options or contact info. Sally's record has all the contact information and the participant options collected on the registration form. Sally and the organization are also not linked by any relationship.

To fix this, I have to manually add the participant options to the organization's participant record within the event. Then, delete Sally's participant record. Then, convert Sally's constituent record from an individual record to an organization record - this is done in database view - so that the two records can then be merged in web view. In the end, I have just the organization record as a participant and as a constituent and I have the contact information for the organization listed on the organization record. I then add Sally as a contact person for the organization, but she herself is not a constituent.

Clearly, this multi-step process is very time-consuming and inefficient. This should be changed such that when an organization registers for an event or gives a gift through the online donation forms, the gift and the information collected through the form are stored on the organization's record and not on the record of the person completing the form. The name of the person completing the form could still be visible on the organization's participant record and it could even be added as a relationship on the organization's constituent record, but it is totally unnecessary and illogical that the person filling out the form would automatically be added created as a constituent and added to the event as a participant when they are registering "as an organization". Most of the time, the person who will be representing the organization at the event (i.e. the president, CEO, etc.) is not the person who fills out the registration form (i.e. the business office secretary or executive assistant).

Agreed - adding additional full constituent records for no other reason than a contact at an organization is very messy and increases record counts unnecessarily