Visiting Party: Section 3 - Separate the Individuals and Organizations in the Form

Discuss with SMEs if this can wait for a later MVP since this is for non-branch users.

**Background from SMEs UAT1 Feedback:**
**Scenario: Is the workflow workable for working with non-Branch users: Searching for an association**
Site Visit Team Member list should be limited to Individuals and exclude Organizations. See point 7 from this [word doc](https://bcgov.sharepoint.com/:w:/r/teams/06659/Shared%20Documents/BCAP%20Shared%20Team%20Files/Build%20Requirements/Arch%20Branch%20working%20documents/UAT/UAT%201%20(Feb%2012%20-%2028)/BCAP%20UAT1%20feedback%20CL%20LT%202025_03_01.docx?d=wd4fda4caf44c442a914177b28bc60792&csf=1&web=1&e=6QSVne) for our request to keep Individuals and Organizations separate under a Contributors umbrella (instead of all Individuals and Organizations being mixed together).

**Details on fields needs for the forms:**
- Organization and Individuals should be separated more clearly; should be done via 2 separate forms (so if you click Individual, the Individual fields appear; if you click Organization, the Organization fields appear)

- **Individual**: Fn, Ln, Affiliation - picklist (Refer to the Tabular data fields excel sheet), Comments (optional with a help icon to assist the team), Active? (Yes/No) and other auto fields like Modified By and On
- Note: There was a discussion about people changing affiliations which is a concern. The team needs to know the previous values. Is this being tracked in a different way. Brett previously suggested he had some ideas. This needs further discussions with INV-DEV-BA

- **Organization** (Contributors List combines individual and companies): Only need the Name (mandatory), Comments (optional with a help icon to assist the team), Active? (Yes/No), Affiliation field is not needed because it will be the Organization and other auto fields like Modified By and On.
- Refer to Site_Visit_Affiliation Table from HRIA.


Review the linked UAT1 feedback, the Tabular data fields spreadsheet, and the Site_Visit_Affiliation table from HRIA before choosing an implementation path. Confirm how Individual and Organization forms should be separated and how affiliation history is tracked; done means each form shows its specified fields and excludes the other contributor type.

Written by the indexing model from the issue text.