Describe your institution's exceptions and evidence requirements. Makeform builds an academic petition form with student and course details, conditional questions, uploads, acknowledgments, and review routing.
Send petition submissions to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a petition workflow, adapt its prompt, or send it to the builder.
Audience
Students requesting withdrawal after the published deadline
Format
Conditional petition with timeline and supporting documents
Prompt size
255 chars
Example form structure
Conditional petition with timeline and supporting documents
Student and program details
Course, section, instructor, and term
When did the circumstances begin?
Explain why the deadline was missed
Upload supporting documents
Suggested routing tags
Registrar review
Department review
More information needed
Ask separately for the requested outcome, relevant deadline, and reason for the exception.
Step 1
Identify
student, policy, course, and requested exception
Step 2
Explain
timeline, rationale, and prior resolution steps
Step 3
Document
syllabi, correspondence, and relevant evidence
Step 4
Route
registrar, advisor, chair, or committee review
Why a structured petition form
A structured form gathers the policy, requested outcome, academic context, and supporting documents while keeping petition types distinct.
Conditional paths show dates, appeal steps, or course comparisons only for the selected petition type.
Students add syllabi, graded work, correspondence, and other relevant documents beside their explanation.
Program, course, and petition category fields help staff identify the appropriate reviewer.
Common petition workflows
Start with the nearest workflow, then apply your institution's policy wording and requirements.
Capture the deadline, circumstances timeline, affected courses, advisor contact, and documents.
Ask for the policy ground, requested resolution, prior discussions, and course materials.
Compare required and proposed courses by credits, content, and learning outcomes.
Add follow-up fields for overloads, prerequisites, residency rules, or repeat limits.
Build the workflow
Turn your registrar's or department's review questions into a consistent form.
Name accepted exceptions, owners, deadlines, prior steps, and required documents using current policy language.
Require core details, then reveal petition-specific dates, comparisons, or appeal questions by category.
Share or embed the form, notify intake staff, and explain next steps without promising a decision date.
Sort submissions by department or type, identify missing information, and track internal review status.
Form vs email vs document
Petitions need narrative, evidence, and structured academic details in one record.
Field guide
Use these six field groups as a starting point, then align them with your policies.
Student identity
Collect the identifiers staff need to find the academic record and contact the student.
Academic context
Structured course and term fields make the affected academic context unambiguous.
Requested outcome
Separate the requested action from the explanation so reviewers can identify the exception quickly.
Rationale and timeline
Request dates, events, and how the circumstances connect to the policy exception.
Supporting materials
Show only relevant upload prompts and explain accepted formats.
Acknowledgment and routing
State that submission starts a review rather than determining the result, then collect routing data.
Related tools
Connect petition intake with advising, records requests, student concerns, progress reporting, and registration forms already available in Makeform.
Collect advising goals, questions, and course-planning context before an appointment.
Open toolCreate a separate intake path for transcript and academic record requests.
Open toolRoute broader student concerns that are not requests for an academic policy exception.
Open toolGather structured progress information from instructors or support teams.
Open toolCollect planned courses and student details before formal registration opens.
Open toolAnswer program and admissions questions before someone becomes an enrolled student.
Open toolFAQ
Answers for registrars, departments, advising offices, and review committees.
An academic petition form is a student's structured request for an exception or appeal under institutional policy. It gathers the requested outcome, academic context, rationale, prior steps, and supporting documents for late withdrawal, grade appeal, course substitution, or another defined exception.
Include student ID and contact, program, course and term, category, requested outcome, deadline, factual explanation, prior steps, supporting uploads, accuracy acknowledgment, and routing fields. Show petition-specific questions conditionally.
Yes. Use a petition-type dropdown and conditional paths for withdrawal timelines, appeal grounds, or course comparisons. Keep processes separate when they have different owners or notices.
Label upload fields by petition type, such as a syllabus for a substitution or relevant correspondence for an appeal. State accepted formats and avoid collecting unrelated documents.
No. Submission starts review under the institution's policy; it does not promise approval or another outcome. Explain the actual next steps and contact point.
Collect department, program, course, and category as structured fields, then notify the intake team. Base routing on current responsibilities and explain multi-reviewer sequences in the confirmation.
Yes. Makeform offers unlimited free forms and responses, so you can generate, edit, publish, and collect petition submissions without a form or response cap. The paid tier removes the Makeform badge.
Yes. Replace example categories, deadlines, acknowledgments, documents, and routing with current institutional wording. Review the form with process owners and update it when policies or responsibilities change.
Turn exception requests into complete submissions.
