@jberberichpaycor Similar thing - we have a Slack form.  From that, create a JIRA ticket that has additional fields and info.

We are currently using Coda to take in requests. This has been helpful for non-technical requests, such as changes in email templates, updates to CTA fields, etc. 

I’d say this topic is hot for me too. You can’t prove anything later unless it’s recorded. We also have a possibility of logging a ticket where there will be such fields  as e.g. Reason, Priority, Outcome, but they are general. I was thinking more of the specific templates that the requestor should fill in. E.g. they are requesting a JO program - they should provide the steps/outreaches, the audience (where it’s supposed to come from). If it’s an email - to whom should it be delivered, if a CTA - to whom assigned, triggered based on what, is it supposed to have a playbook, etc. 
When you are speaking of forms, are they that advanced?

​@Maryia Matskevich - For our teams, we have Google Doc templates for each of those: “New CTA Request” or “Customer Journey Request”. On those docs, we have sections that prompt the requestor to provide all program requirements (entry criteria, target audience, content, etc.). When the template is complete, they then fill out our Gainsight Intake Form and link the template in one of the fields. This way our Admins can organize requests, assign out accordingly, and have access to the requirements doc when needed.