A request to go on a course usually arrives as a vague email. "Can I do the data course?" Which one, when, and what will it cost? I want those answers up front. One link collects them, so I can say yes or no in one reading.
Who decides, and who only reads?
The manager or learning lead decides. The form only gathers facts. It has no approval step, so I reply myself and keep the CSV as the record.
What if the cost or the dates are unclear?
Only the course name, the format and the skill are required. A person can leave the cost and dates blank and add a link to the course page. I fill the gaps when I compare requests.
How does a person's AI help?
It can read the course page the person pastes in, then ask: "What is the course called?" Then "Which dates?" Then "What will you learn from it?" It shows the answers and sends them only after a yes. Learn more about agent-fillable forms.
Where it fits
Courses that need a trip pair well with a travel request. After the course, a training feedback form shows whether it was worth the time. If you run the course yourself and people sign up, an event registration form fits better. Browse HR and recruiting forms and forms for events.
Questions
How do I compare requests for the same course?
Sort the CSV by `course_title`. Several people asking for one course is a case for a group booking, and you can add up `cost_estimate` for the total.
Can I limit how many people ask for one course?
Yes, if you make one form per course. Set `max_responses` to close it at the seat count, or `close_at` to close it on a date.
Should I collect payment details here?
No. The form cannot take payments or card data. Collect the estimated cost as a number, then pay the provider through your normal process.