Campus Credit · Form Management
Build the form once. Attach it to any application.
A form is what a person fills out to start or move a request forward. In Campus Credit you configure it once and attach it at any level — the application itself, plus the waivers and acknowledgments that follow — guided and validated so it arrives complete on the first try, and tied to one student record.
Part of Campus Credit — built on a 24-year foundation in enrollment-pathway software.
Application Form
A form should start a workflow — not a paper chase.
Applications, consents, and acknowledgments are where every pathway begins. When they live as email attachments, the work is really in the chasing: incomplete forms, missing signatures, and data typed twice.
Campus Credit replaces paper and email attachments with configurable forms that validate as they're filled, attach to the right application, and stay tied to the student record — so what reaches your staff is complete, signed, and ready to review.
One form engine, everywhere a person has to fill something out.
Form Management is a foundational function in Campus Credit — the same tool builds an application, a waiver, or an acknowledgment, and attaches it wherever the workflow needs it.
Configure any form
Applications, waivers, and acknowledgments, built from structured fields — text, dates, selections, uploads, and signatures.
Attach at any level
Put a form on a program's application, or on the checklist steps that come after admission — the same form works anywhere.
Nest sub-forms & documents
A form can carry sub-forms — like an i-20 support form — and require documents that upload straight to the record.
Guided & validated
Required fields and documents block an incomplete submission — so staff never receive a half-finished request.
E-signature built in
Waivers, releases, and acknowledgments are signed online and timestamped — no separate tool, nothing on paper.
Routes to review & the record
A submitted form enters the right review queue, and everything it collected stays tied to one student record.
Configure the fields, documents, sub-forms, and signatures a request needs.
Because forms are a foundational function, the same builder serves an application, a waiver, or an acknowledgment. Add the fields you want, mark the ones that are required, attach the documents a request must include, and save it as a reusable template.
Form Management · Template
One template, reused across every program.
Because forms are a foundational function, the same builder serves an application, a waiver, or an acknowledgment. Add the fields you want, mark the ones that are required, attach the documents a request must include, and save it as a reusable template.
Mark any field or document as required so nothing is skipped
Embed sub-forms — like an i-20 support form — inside the main form
Save as a template and reuse it program to program
Form Template
Set up the program, select the form, publish — and it's live in the student portal.
When you create a program, you choose the application form template students complete when they apply. Define which documents are required, then publish. A program has to be published before students can see it or apply — a saved draft won't appear in the portal.
Program Setup
The form attaches where students actually apply.
On the program's setup screen, the Application Form template is a field you select — the form you built in step one. The required document types you define here are the ones the portal will collect from every applicant.
Select the application form template on the program
Define the required documents the portal will collect
Publish to make the program — and its form — live to students
Create Program
Guided, validated, and complete before it can be submitted.
In the self-service portal, the student works through the form, uploads the required documents, pays any application fee, and submits. Validation won't let them submit until it's complete — and if a reviewer requests corrections, the student updates and resubmits without starting over.
Student Portal
What arrives is finished — not a half-filled draft.
The applicant is walked through each section. Required fields and documents are enforced, so an incomplete application can't be submitted. On submit, it enters the review queue tied to the student's record; requested corrections come back to the same application.
Required fields and documents block an incomplete submission
Any configured application fee is collected in the same flow
Reviewers request corrections; the student resubmits in place
International Student Application
The same engine handles the waivers and checklists that come next.
Once a student is admitted, the forms don't stop. Pre-arrival checklists, housing and health intake forms, conduct agreements, and liability waivers all run on the same engine — signed online and tracked to completion, on the same record, with reminders for anything outstanding.
Checklists & Waivers
Consent and clearance, tracked to done.
Acknowledgments and waivers are e-signed and timestamped; intake and logistics forms are collected on a checklist staff can monitor. Everything stays attached to the student's record — so clearance is visible at a glance, not scattered across a shared inbox.
Required fields and documents block an incomplete submission
Any configured application fee is collected in the same flow
Reviewers request corrections; the student resubmits in place
Pre-Arrival Checklist
Every kind of form your workflows depend on.
From the first application to post-admission clearance, the same form engine covers the whole journey — across dual enrollment, articulation, study abroad and away, noncredit, international admissions, and credit for prior learning.
The form that starts a request — an international application with its i-20 support form, a guided CPL intake that routes to the right pathway.
Conduct agreements and liability releases signed online — collected before a student is cleared to travel or enroll.
Policy acknowledgments and pre-departure training or quizzes — captured and timestamped as part of the workflow.
Transcripts, passports, portfolios, proof of funds — uploaded securely and tied to the right request, not a shared inbox.
Housing, health intake, and insurance steps on a post-admission checklist staff can monitor and send reminders on.
Structured forms for staff too — configure a program or course and attach syllabi or materials from one screen.
Forms that finish the job — and stay on the record.
The value isn't the form itself; it's what happens around it — completeness enforced, signatures captured, and everything tied to one student record instead of an inbox.
Validation stops incomplete submissions before they ever reach staff — no chasing missing fields.
Consent, waivers, and acknowledgments are captured online, with a record of who signed and when.
Every form and its documents stay attached to the student's record — nothing sensitive floating in shared email.
Who filled it out, who signed, and who approved — captured on the record for any review or site visit.
Signed consents, health and safety disclosures, and conduct acknowledgments live on the same record as the application they belong to — the health, safety, and participation documentation peer-review teams look for, ready to pull when a review asks.
Every form your students fill out — built once, attached where it belongs.
See Form Management run against one of your own programs in a short walkthrough — from building the template to a completed, signed application on the record.
