Thanks for the added info.
Am I correct in assuming that the month specifier is in a single-select field? If so, you might be able to get what you want by changing it to a link to another table. I’m going to call this
[Months] for now, but use whatever name you want. To easily convert from your current single-select to the new link, just change the field type. Airtable will ask if you want to make a new table, and you can give it a name at that time. When the new table is made, it should already have records based on the months you had previously assigned. You may need to fill some gaps depending on how many months were used before, but that should be pretty easy.
Because you probably want to keep historical info and not reuse “May” from 2020 for your 2021 tracking, you may want to consider including the year in the primary field. Your records in the
[Months] table would then have names like this:
Anyway, you now have a table that others can tie into. In your form on the
[Pipeline] table, it would ask the user to pick the month (from that linked table) for their submission.
Because the records in the
[Months] table are now linked to both the
[Vision 2020] and
[Pipeline] tables, you can pass any month-specific data between them via lookup and rollup fields, which you can then use in your formulas.
Does that get you started in the right direction?