Describe your term, course catalog, and approval process. Makeform turns the brief into a course request form with student details, ranked selections, prerequisite checks, alternate choices, scheduling constraints, and the routing information a registrar or training coordinator needs to plan enrollment.
Send course requests to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose the workflow closest to yours, replace the sample rules with your catalog details, or send the prompt into the Makeform builder. The fields shown here are example structures, not live AI results.
Prompt ready4 formats
Audience
Students choosing next-term electives with counselor review
Format
Ranked request form with grade-specific course lists
Prompt size
551 chars
Brief qualitySends to builder
Example form structure
Ranked request form with grade-specific course lists
Prompt exampleEditable in builder
Student details and next-year grade
Short answerFirst ask
2
Rank your first three course choices
Dropdown
3
Choose two alternate courses in order
Dropdown
4
Prerequisites completed or in progress
Checkboxes
5
Scheduling needs for counselor review
Long answer
Suggested routing tags
Suggested
Ready for review
Prerequisite check
Schedule conflict
Ask for alternates in preference order. A registrar cannot resolve a full section efficiently when every backup is recorded as an unranked comment.
Step 1
Identify
student, program, grade, adviser, and term
Step 2
Request
ranked courses, alternates, credits, and sessions
Step 3
Review
prerequisites, capacity, conflicts, and approvals
Step 4
Route
registrar queue, counselor follow-up, and status
Plan from usable requests
A course list is only the beginning of a scheduling workflow.
The registrar needs to know not just what a student wants, but which choices matter most, what can substitute, and what may block placement. A structured form turns that context into fields that can be sorted and reviewed.
Rank choices and alternates
Separate first, second, and third choices from alternates. Explicit order gives the scheduling team a usable fallback when a section is full or clashes with a required course.
Surface eligibility details
Ask for current grade, program, completed or in-progress prerequisites, and adviser information beside each request so exceptions do not disappear inside an open comment.
Route the right review
Use program, grade, course type, or manager as routing fields. Requests needing a prerequisite check or schedule discussion can be separated from straightforward submissions.
Match the request stage
Use the same foundation for four different planning jobs.
A request form may guide formal academic advising, estimate demand before sections exist, or collect employee training approval. Change the language and decision fields to match what happens after submission.
Secondary school course selection
Filter electives by next-year grade, capture graduation-related context, rank alternatives, and send unusual combinations to a counselor for discussion.
College advising and pre-registration
Collect course codes, sections, credits, prerequisites, and adviser details while stating clearly that a submitted plan is not a confirmed registration.
Workplace learning requests
Connect the requested course to a skill need, preferred session, time away from work, manager decision, and any internal budget reference.
Demand and schedule planning
Collect serious interest, ranked topics, delivery mode, and workable time blocks before deciding which community or continuing-education sections to offer.
Request workflow
From course catalog to a reviewable planning queue.
Give Makeform the rules a staff member normally explains by email. Then refine the generated form so each submission contains enough context for the next decision without pretending the request is already approved.
Name the term, audience, course options, number of choices, prerequisite rules, and who reviews each submission. Include what the form must not imply, such as guaranteed enrollment or a reserved seat.
02
Edit choices, conditions, and language
Replace sample options with exact course titles and codes. Show advanced-course questions only when relevant, make alternatives distinct from primary choices, and put request-status language near the submit button.
03
Share within the request window
Publish one link for the intended student or employee group, include the deadline and term in the introduction, and send a submission receipt that repeats what happens next and whom to contact for corrections.
04
Review and export a clean queue
Tag requests by grade, program, adviser, prerequisite status, or manager. Send structured submissions to a sheet or connected workflow, then track review status separately from the student's original selections.
Request form vs email vs registration
Choose a tool that matches where you are in the enrollment process.
Course requests help plan and review possible schedules. They are not the same as informal email suggestions, and they should not be presented as final enrollment when capacity, eligibility, or approval still needs review.
Approach
What it captures
Best use
ApproachEmail or paper wish list
What it capturesCourse names and scattered context in inconsistent formats, often without ordered alternatives.
Best useA small one-off conversation where staff can clarify every request manually.
Approach
Course request form
What it capturesConsistent identity, ranked choices, alternates, prerequisites, conflicts, and routing details.
Best usePlanning demand and reviewing possible schedules before placement is confirmed.
ApproachRegistration or enrollment system
What it capturesConfirmed section selection tied to live capacity, formal eligibility checks, and institutional records.
Best useCompleting enrollment after the school or training team is ready to offer seats.
Field guide
What a useful course request form should include.
The strongest form mirrors the decisions made after submission. These six sections give registrars, counselors, advisers, and training coordinators the information they need while keeping the distinction between a preference and a confirmed seat clear.
Requester identity
Match the request to the right student or employee.
Collect only the identifiers the reviewing team actually uses. In a school, that may be student ID, next-year grade, program, and counselor. In workplace training, department, role, manager, location, and work email may be more useful. Use separate structured fields instead of asking the requester to compress everything into one line.
Full name, preferred contact, and the relevant institutional identifier.
Grade, program, concentration, department, or role for routing.
Counselor, adviser, or manager responsible for the next review.
Primary choices
Record priority, not just interest.
A checkbox list proves that several courses sound appealing but does not reveal which one protects a graduation plan or solves an urgent skill need. Use clearly numbered choice fields, include course codes where names are similar, and prevent the same option from being selected in more than one rank when the builder supports that rule.
First, second, and third choice as distinct required fields.
Course title, code, section, credit value, or delivery mode as needed.
A concise reason only when reviewers use it for prioritization or advising.
Alternates & constraints
Give schedulers practical fallback options.
Alternates should be courses the requester is genuinely willing to take, ranked separately from primary choices. Pair them with non-negotiable constraints such as a required course, work placement, travel between campuses, accessibility need, or session availability. Avoid a single broad comments box when a set of day and time choices would be easier to compare.
Ranked alternates with a clear minimum number requested.
Unavailable periods, workable sessions, campus, and delivery preference.
Conflict notes that distinguish a hard constraint from a preference.
Eligibility context
Flag what needs verification without deciding it in the form.
Ask requesters to identify completed or in-progress prerequisites, placement level, or required approvals, but let the designated staff member verify eligibility. Conditional follow-up can appear for restricted, advanced, overload, or out-of-program choices. This produces a focused review queue without promising that a self-reported answer grants access.
Prerequisite course and completion term or current status.
Placement, program, or grade information used for staff review.
Exception explanation and the person expected to review it.
Review & status
Separate the original request from the staff decision.
Preserve what the requester submitted, then track advising notes, approval, placement, waitlist, or follow-up as review data. Do not overwrite a first choice with the final assignment. Separate records make it possible to compare initial demand with actual placement and to explain which request still needs attention.
Received, reviewing, needs information, approved, or unable to place status.
Internal reviewer, review date, and a concise decision note.
Requester-facing next step that does not expose internal comments.
Expectations & corrections
Tell requesters exactly what submission does.
Place a short explanation before the selections and repeat the key point at submission: the form records preferences for review and does not itself guarantee a place. State the request deadline, when students can expect an update, how conflicts are handled, and where to send a correction. Clear expectations reduce duplicate submissions made only to check whether the first one worked.
Term, deadline, review sequence, and expected communication channel.
A plain-language statement that a request is not confirmed enrollment.
Correction instructions and a stable request reference when available.
Related education tools
Build the steps around course planning and enrollment.
Use a focused tool when the next job is academic planning, schedule changes, pre-registration, formal course registration, training applications, or feedback after the course.
Practical answers for registrars, counselors, advisers, and training coordinators collecting requests for an upcoming term.
What is a course request form?
A course request form collects the classes a student, learner, or employee would like to take during a future term or training period. It usually records identity, program or grade, ranked choices, alternate courses, prerequisites, schedule constraints, and the appropriate reviewer. The submission supports planning and review; it should say clearly whether a separate registration or placement step follows.
What fields should a course request form include?
Start with the requester details used by your team, the term, and the relevant grade, program, department, adviser, counselor, or manager. Add separate fields for ranked primary choices and alternates, course codes or sections, prerequisites, credit totals, delivery preference, and hard schedule conflicts. Include acknowledgment of the process, a correction path, and only those open questions reviewers will actually read.
How do I collect ranked course choices and alternates?
Use a separate dropdown for first choice, second choice, and each additional rank rather than one checkbox list. Give alternates their own numbered fields and explain that they should be acceptable substitutes. Where available, add validation or conditional rules to discourage duplicate selections. Keep course labels identical to the catalog, including codes when titles could be confused, and export each rank to its own column.
Is a course request the same as registration?
Not necessarily. A request often expresses preferences before staff review capacity, prerequisites, conflicts, or approvals. Registration is the later process that places a learner into an offered section according to the institution's workflow. If your form is for requests, state that near the choices, submit button, and receipt. Explain the next step without suggesting that submission reserves or confirms a seat.
Can the form show different courses by grade or program?
Yes. Start with a grade, program, pathway, department, or location question, then use conditional sections to show the relevant course list and follow-up questions. Keep a shared identity and acknowledgment section so reporting remains consistent. Review every branch before publishing, especially students who change grades or programs, and provide a contact option when the expected course is missing.
How should prerequisites and exceptions be handled?
Ask requesters to identify prerequisite status in structured fields, such as completed, currently enrolled, planned before term, or unsure. Show a follow-up field for restricted or overload choices and route those submissions to the appropriate reviewer. Treat the response as context for verification, not automatic proof of eligibility. Preserve the student's original choice while tracking the review decision separately.
How can registrars reduce duplicate or incomplete requests?
Put the term and deadline at the top, mark the essential identity and choice fields required, and show a confirmation page or receipt with the selected courses. Explain how to correct a request instead of telling students to submit again. Structured alternatives, prerequisite prompts, and schedule choices reduce follow-up. If you use a student identifier, reviewers can also flag multiple submissions and decide which version to treat as current.
Is this course request form generator free?
Yes. Makeform supports unlimited free forms and responses, so a school or training team can generate, edit, publish, and collect course requests without a response cap. The paid tier removes the Makeform badge. You can still revise the catalog choices, add conditional questions, preview each route, and share the published form from the free version.
Replace scattered wish lists with structured choices.
Generate a course request form built for the next term's review workflow.
Unlimited free forms and responsesRanked choices and alternatesPrerequisite and schedule context
