Describe your term, course rules, and approval path. Makeform turns them into an online add drop form that captures the student's record, exact sections to add or drop, schedule conflicts, reasons, and required acknowledgments before routing a complete request to the registrar.
Send course change requests to email, Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a registrar workflow, adjust the details, or send the prompt to the Makeform builder. Each example shows a practical starting structure, not a processed student request.
Audience
Undergraduate students changing a current-term schedule
Format
Combined add and drop request with conditional sections
Prompt size
589 chars
Example form structure
Combined add and drop request with conditional sections
Student identity and academic program
Add, drop, or replace a course?
Course code, section, credits, and meeting time
Prerequisites, conflict, or permission details
Student acknowledgment
Suggested routing tags
Add request
Drop request
Needs review
Ask for both the course code and section number. A title such as Biology is not enough to identify the correct meeting time or instructor.
Step 1
Identify
student, term, program, and current schedule
Step 2
Change
exact courses and sections to add or drop
Step 3
Review
conflicts, prerequisites, deadlines, and permissions
Step 4
Route
adviser and registrar receive a complete request
Why use an online request
An email saying “please drop chemistry” leaves staff searching for the term, course number, section, student ID, and requested replacement. A structured add drop form asks for every processing detail at submission.
Conditional questions can separate add, drop, replacement, and late-change requests. Students see only the follow-up questions relevant to their selection, while staff receives a consistent record.
Required fields for term, course code, section, instructor, credits, and meeting time reduce the back-and-forth caused by course titles that appear in multiple sections.
Prerequisite evidence, permission notes, conflict explanations, and deadline exceptions stay attached to the same submission instead of being scattered across inbox threads.
Built around academic workflows
A routine section swap and a late withdrawal need different evidence. Start with the closest workflow, then adjust policy text, fields, choices, and routing in the builder.
Branch from a single action question. A replacement path can capture both the outgoing and incoming sections and show the expected credit total after the change.
Collect the assigned counselor or adviser and the student's prior conversation, then give staff the academic context needed to evaluate the request.
Show term-specific dates and ask late requesters for an explanation, supporting documents, and the effective date they are requesting without implying that submission ensures approval.
Use request type, school, program, or student level to organize notifications and downstream work so the appropriate reviewer receives the submission.
Build the workflow
The useful form is not merely a pair of course boxes. It reflects how your registrar identifies records, checks requests, gathers approvals, and communicates next steps.
Tell Makeform who may submit, which changes are allowed, the standard deadline, and which details an adviser or registrar needs. Include your own policy wording rather than relying on generic language.
Make identifiers required, create separate add and drop follow-ups, add course lists where practical, and show exception questions only when the selected date or request type needs them.
Preview a single drop, an add with prerequisite permission, a section swap, and a late withdrawal. Confirm that each path asks enough to make a review decision without collecting unrelated details.
Share the form from the registrar site or student portal, then connect submissions to the inbox, sheet, or automation your team uses to log status and follow up.
Request form vs email vs paper
The goal is not just to receive a student's intent. Registrar staff need exact record identifiers, decision context, and a clear history of what was requested and when.
Field guide
Use these six sections as a practical checklist. Keep the student-facing form focused, and place internal-only status or decision fields in the staff workflow where students will not mistake them for approval.
Student record
Start with the identifiers staff use to locate the academic record. Names alone can collide, personal email addresses may not match school records, and a request without a term cannot be applied accurately.
Requested action
A clear action choice determines the rest of the form. If students may change several courses, repeat the same structured block for each one instead of asking them to explain the entire schedule in a paragraph.
Course identity
The registrar needs the catalog code and the specific offering. Collect fields in the same format used by your course schedule so staff can distinguish lecture, lab, online, honors, and instructor-specific sections.
Eligibility checks
An add may depend on prerequisites, co-requisites, capacity, program restrictions, or permission. Ask students to identify the relevant condition and provide context, while leaving the actual decision to the responsible school staff.
Reason and acknowledgment
A concise reason helps advisers understand the academic need. Pair it with your school's own notice about deadlines and possible consequences, and state plainly that submitting a form starts review rather than completing the schedule change.
Routing and status
Decide who reviews each request and which statuses the office tracks. A consistent queue makes it easier to distinguish new submissions from requests awaiting information, under review, completed, or declined.
Related tools
Connect course-change intake with advising, registration, records, enrollment, and end-of-course feedback forms using these existing Makeform tools.
Collect goals, concerns, and preparation details before a student meets with an academic adviser.
Open toolCreate structured intake for initial course selections and registration details.
Open toolGather the identifying and delivery details needed for academic record requests.
Open toolBuild a focused signup form for classes, sections, participant details, and scheduling choices.
Open toolCollect broader student enrollment information before individual course selections are finalized.
Open toolAsk students for structured feedback after a course concludes and compare themes across sections.
Open toolFAQ
Practical answers for registrars, counselors, and academic teams moving course-change requests online.
An add drop form is a structured request a student uses to add a course, drop a course, replace one section with another, or request a related schedule change. It typically identifies the student and term, records the exact course and section, explains the requested action, and gathers any permissions or acknowledgments the school requires. Submitting the request does not by itself mean the academic record has changed; the school can communicate its review and processing steps in the form.
Include full name, student ID, school email, term, program, adviser, current credits, requested action, course prefix and number, section, instructor, credits, meeting time, requested effective date, and reason. Add conditional questions for prerequisites, instructor permission, conflicts, late requests, or supporting documents. Finish with your own policy notice and student acknowledgment, then keep reviewer status, notes, and completion details in the staff process.
Yes. Begin with an action question and use conditional paths. Students adding a course can see prerequisite, capacity, permission, and schedule-conflict questions. Students dropping a course can see reason, last-attendance, effective-date, or school-provided acknowledgment questions. A replace option can collect both sections together, which gives staff a clearer picture of the intended final schedule and credit total.
Show the applicable deadline and clearly identify the submission as an exception request. Ask for the course, requested effective date, reason the deadline was missed, previous conversations with the instructor or adviser, and supporting documents if your policy calls for them. State that the request will be reviewed and that submission is not approval. Route it to the reviewers specified by your institution rather than treating it like a routine change.
Yes. Use a repeatable course block with the same action, code, section, credits, instructor, and reason fields for every change. Also ask for current credits and expected credits after all requested changes. That summary helps reviewers understand the combined result, especially when one drop depends on a successful add or when the final schedule may affect the student's enrollment status.
The form can collect routing information such as assigned adviser, course instructor, department, campus, or program. Notifications and connected workflows can then send the submission to the appropriate team. Design the review sequence around your school's actual process and keep decision fields clearly internal. For student-facing language, explain who reviews the request, what confirmation to expect, and where the student should ask about status.
Yes. Makeform supports unlimited free forms and responses, so a school can generate, edit, publish, and use the add drop form without a response cap. The paid tier is for removing the Makeform badge. You can revise course choices, deadlines, notices, and routing as terms change while keeping the core intake structure consistent for students and registrar staff.
Run at least four realistic cases: a routine drop, an add that needs permission, a section replacement with two course records, and a late request with documentation. Confirm required identifiers are present, irrelevant questions stay hidden, uploads and acknowledgments appear only where intended, and each submission reaches the right reviewer. Also have staff verify all dates, course choices, contact details, and policy wording before publishing the link.
Replace incomplete course-change emails.
