Currently, I have a Program Proposal form that is completed by an individual with personal contact information (name, address, city, state, postal code, email, phone number, etc.) and proposed program information.
The Program Development sheet then has 1 row for each program proposal (and each program proposal has a single presenter).
If the program manager decides to officially offer the program in a future term, she triggers an automation in the Program Development sheet to copy parts of the row to a Course Section Build sheet, which includes a column that assigns the section a CRN number ( a unique identifier such as 10343 or 63202). Each row in this sheet is a unique section, each with a unique CRN. The registration office uses the information in this sheet to build the registration site for our website.
Then, if the presenter is to be paid, the program manager triggers a different automation in the Program Development sheet to copy parts of the row to the Payment Request Approvals sheet. Each row in this sheet is a unique payment request. The CRN from Course Section Build sheet is entered into the payment request to let finance know which course section this request is associated with.
Summary:
Program Development Sheet: Each row = 1 program proposal = 1 presenter (e.g., "Caves in Vermont" presented by John Doe). Note: The same program might be offered multiple times, within one term or across future terms.
Course Section Build Sheet: Each row = 1 section on the schedule in a specific term with unique CRN (Section 1 "Caves in Vermont", presented by John Doe, in spring 2026 term, on certain start/end dates, CRN 34344). Note: The program may be on the schedule in a specific term more than once and/or the program may be on the schedule in multiple terms. However, each section has a unique CRN.
Payment Request Approval Sheet: Each row = 1 payment request tagged with a CRN ($500 payment request for John Doe for presenting the section 34344 in spring 2026). Note: John Doe might have more than 1 payment request if he is presenting the program more than once in a term or across future terms, but each would have a unique CRN.
This works great. However, we realize we may have a program proposal that has 2+ presenters, and the form currently only allows 1 person to provide their contact information. We looked at three possible solutions:
Adding Fields to the Form
- It would seem easy to just add fields in the form to accommodate, 2, 3, or whatever we decide might be the most number of presenters.
- However, now 1 row in the Program Development sheet could = 1 presenter, 2 presenters, etc.
- When parts of the row are copied to the Payment Request Approvals sheet, we'll only have one row in the sheet —- but technically, we'd need a separate row for each presenter since each presenter is paid separately (and the amount they are paid may be different).
- The program manager enters the payment amount and manages W-9 information for the one presenter in the one row. If this more than one presenter in a row, it would be impossible to manage some of this information knowing what goes with which presenter.
Duplicating the Row in the Program Development sheet
- Once one of the presenters submits the form (and indicates perhaps that there will be more than on presenter), the program manager can duplicate the row in the sheet.
- However, now each row is not a different program proposal., A program proposal could be 1 row, 2 rows, or even more.
- The program manager has to "manage" information about the presentation now across all of the rows, since information about the presentation (e.g., start/end dates) are copied to the Course Section Build sheet.
- We would be able to copy parts of each row then to the Payment Request Approvals sheet (3 rows copies to 3 payment request rows (each with same CRN), easy to know there are 3 separate payment requests for the same program).
Duplicating the Row in the Payment Request Approvals sheet
- We considered once a parts of the one row in the Program Development sheet is copied to the Payment Request Approvals sheet, we could just duplicate it so there is a row for each individual presenter.
- When I say "parts of the row" is copied, I mean that the entire row is not copied. Only a couple of columns, and the other columns use INDEX-MATCH to the Program Development sheet to populate the other columns. We did this to avoid copying the entire row (which has nearly 300 columns when only 8 to 10 are actually needed).
- Presenter names and contact information (needed to process payments) are populated via INDEX-MATCH formulas. So, unless we added an "Override" column, the current set up wouldn't allow us to edit name/contact information for the other two presenters.
- We built this ecosystem to automate many parts of the process, and this solution would "break" how we've set up automations.
I thought about a parent/child kind of solution, but I can't think of how to incorporate this without re-introducing a lot of manual data entry and duplicate data entry and management of the same data across multiple rows.
I am not sure if anyone has set up something like this —- the multiple presenters for a single program —- but I thought I'd reach out and see if anyone had a solution that I haven't considered (or even a better way to implement a solution I did consider).