Describe your transfer routes and review process. Makeform creates an online form for current enrollment, requested destination, course mappings, files, and the student's reason.
Route transfer requests to email, Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt it, or send it to the builder. The structure is a planning example.
Audience
Current students moving between course sections or subjects
Format
Request form with current and requested course details
Prompt size
268 chars
Example form structure
Request form with current and requested course details
Student name, ID, and institutional email
Current course code and section
Requested course code and section
Reason for requesting the transfer
Student confirmation
Suggested routing tags
Course change
Credit review
Program transfer
Ask for both the current course and the requested equivalent; a course code without its title, credits, and term rarely gives a reviewer enough context.
Step 1
Identify
student, program, and current enrollment
Step 2
Map
source course to requested destination
Step 3
Document
reason, syllabus, transcript, and prerequisites
Step 4
Route
registrar, advisor, or program reviewer
Why structure the request
Transfer reviews depend on enrollment, equivalencies, prerequisites, capacity, and records. Keep those inputs together without promising a change.
Pair source and requested courses with codes, titles, credits, terms, and the requirement at issue.
Keep syllabus, transcript, portfolio, or prerequisite uploads beside the request.
Route submissions to the registrar, advisor, department chair, or program office.
Common transfer paths
Start with the closest route, then add your terms, course lists, and required documents.
Capture current registration, requested section, timing, and alternatives.
Pair prior coursework with a local requirement and request supporting records.
Collect current pathway, intended program, prerequisites, advisor, and start term.
Record requested location, mode, affected courses, timing, and alternatives.
Application workflow
Gather consistent information while leaving the academic decision with your institution.
Specify a section change, external credit, program move, campus, or delivery mode.
Add your terms, programs, course codes, deadlines, documents, and confirmation language.
Show uploads, portfolio questions, or alternate sections only when relevant.
Notify the right inbox and connect responses to your review workflow.
Choose the intake method
Give students clear requirements and reviewers consistent inputs.
Field guide
Use six sections to collect the requested change, academic records, mappings, and supporting material.
Student record
Use identifiers the registrar can match and include the student's current academic context.
Current enrollment
Record the exact registration or prior study being evaluated.
Requested destination
Ask for one primary destination, its timing, and useful alternatives.
Course equivalency
Pair each source course with its proposed local course or requirement.
Evidence and context
Show document fields only when the transfer route makes them relevant.
Confirmation and routing
Confirm that submission starts a review rather than changing enrollment.
Related tools
Connect applications to advising, records, enrollment, selection, and feedback workflows.
Prepare advisor meetings with student goals, current courses, and questions about a proposed change.
Open toolCollect structured requests for records that may support a transfer or equivalency review.
Open toolBuild the next-step registration intake for courses a student is ready to select.
Open toolGather ranked course choices, alternatives, and term preferences before enrollment.
Open toolCollect core student and program details for a broader school enrollment workflow.
Open toolAsk students for structured feedback after completing a course or learning experience.
Open toolFAQ
Practical answers for registrars, academic advisors, and program administrators planning a consistent transfer intake.
It collects a student's request to change a course, section, program, campus, cohort, or treatment of prior coursework. It records identity, enrollment, destination, reason, mappings, and documents for review; it does not itself change enrollment.
Include student ID and contact, current program and term, source course, requested destination, effective term, reason, and alternatives. Credit reviews may also need source and target codes, titles, credits, completion details, a syllabus, and a transcript.
Yes. Repeat one mapping group for each source course and proposed equivalent. Include institution, code, title, credits, completion term, grade when relevant, target requirement, and syllabus. Keeping each pair together simplifies review.
Yes. Conditional logic can show external-credit questions, selected-program portfolios, or campus preferences only when relevant. Ask transfer type first, while keeping shared student and confirmation fields consistent.
Use labeled uploads for the transcript, syllabus, outline, portfolio, or prerequisite records your reviewers request. Explain expected formats nearby, and display uploads according to transfer type or destination.
No. State that submission begins review and does not change registration, award credit, reserve a place, or promise an outcome. Explain where follow-up comes from and whether staff may request more information.
Yes. Makeform offers unlimited free forms and responses. You can generate, edit, publish, and collect applications without a form or response cap; the paid tier only removes the Makeform badge.
Send submissions to the inbox for each transfer type and connect responses to Google Sheets, Slack, or Zapier when useful. Route by course change, transfer credit, program transfer, or campus move, and keep internal status in your review system.
Create transfer applications.
