Compliance USACC 104-R
Validation Checks by Instafill.ai
1
Student Name format and completeness (Last, First, MI)
Validates that the Student Name is present and follows the required ordering: last name, first name, and middle initial (if provided). The check should reject entries that are only a single token (e.g., just a last name) or that include invalid characters (numbers, excessive punctuation). If validation fails, the submission should be blocked and the user prompted to re-enter the name in the required format to prevent identity mismatches across ROTC and school records.
2
Cadet ID required and conforms to expected ID pattern
Ensures Cadet ID is provided and matches the organizationâs expected format (e.g., numeric-only with a defined length, or an approved alphanumeric pattern). This prevents duplicate or unresolvable records when the form is used for scholarship term calculations and program management. If the Cadet ID is missing or malformed, the system should flag the field as invalid and prevent submission until corrected.
3
Academic Major required and consistent with CIP Code presence rules
Checks that Academic Major is not blank and is a meaningful major name (not placeholders like 'N/A' or 'Undecided' unless explicitly allowed by policy). Also enforces the form instruction that CIP Code is only required for HQ STEM scholarships; if a STEM scholarship indicator exists in the workflow, CIP must be present, otherwise CIP may be optional. If the rule fails, the system should require correction or an explicit exception/override reason to ensure scholarship eligibility determinations are supportable.
4
CIP Code format validation (standard CIP structure)
Validates that the CIP Code, when provided, matches a standard CIP format (commonly a 6-digit code with a decimal, such as '14.0901', or an accepted variant defined by the program). This reduces downstream errors when categorizing majors for STEM scholarship processing and reporting. If the CIP Code does not match the accepted pattern, the system should reject the value and request a corrected CIP code.
5
All date fields use MM/DD/YYYY and are real calendar dates
Validates that all date fields (As of Date, Student Signature Date, Registrar Signature Date, Cadet Signature Date on the Statement of Understanding, and PMS Signature Date) follow MM/DD/YYYY and represent valid calendar dates. This prevents ambiguous or non-parsable dates that break audit trails and annual review requirements. If validation fails, the system should block submission and highlight the specific date field(s) needing correction.
6
Signature dates are logically ordered and not in the future
Ensures signature dates are not later than the current system date (unless future-dating is explicitly permitted) and that the certifying officialâs date is on or after the studentâs signature date for the same section. This supports authenticity and prevents invalid certification sequences. If the ordering is violated, the system should flag the inconsistency and require corrected dates or re-signing.
7
Degree type selection constrained to allowed values
Validates that Type of Degree Currently Pursuing (and Degree Type in the review section, if separate) is selected from the allowed set: Bachelors, Masters, or Associates (MJC only), per the instructions. Free-text or unrecognized degree types can cause incorrect scholarship term calculations and policy misapplication. If validation fails, the system should require the user to choose a valid degree type and, if needed, capture an exception justification.
8
Academic School Identification is one of Host / Extension Unit / Cross-Town
Checks that Academic School Identification is selected and matches one of the defined options: Host, Extension Unit, or Cross-Town. This is important because ROTC attendance rules differ depending on whether the academic school is the host or a partner school. If the value is missing or outside the allowed set, the system should prevent submission and prompt for a valid selection.
9
Host School and Academic School required; conditional consistency with identification
Ensures Host School and Academic School names are provided and applies a consistency rule: if Academic School Identification is 'Host', Academic School must match Host School; if 'Extension Unit' or 'Cross-Town', Academic School should be different from Host School (unless an explicit exception is recorded). This prevents misrouting and incorrect assumptions about where ROTC classes are taken. If validation fails, the system should flag the mismatch and require correction or an exception note.
10
Credit hour fields are numeric, non-negative, and within reasonable bounds
Validates that all credit-hour inputs (total required, ROTC hours not counted, completed-to-date, transfer credits, remaining, required per term, authorized semesters/quarters, and per-course hours) are numeric and not negative. It should also enforce reasonable upper bounds (e.g., total degree hours typically 30â200; per-course hours typically 0â6) to catch data entry errors. If validation fails, the system should reject the offending value and require correction.
11
Credit hour arithmetic consistency (required, ROTC excluded, remaining)
Checks that Academic Total Hours Required for Degree equals Total Credit Hours Required for Degree plus ROTC Hours That Do Not Count (per the formâs described calculation), and that Credits Remaining for Degree equals Academic Total Hours Required minus (Completed to Date + Transfer Credits Accepted). This ensures the scholarship term calculation and graduation feasibility are based on coherent totals. If the math does not reconcile, the system should flag the conflicting fields and require correction before submission.
12
Semester/Quarter selection drives authorized term logic
Validates that the user selects whether the school uses semesters or quarters and that Number of Authorized Semesters or Quarters is consistent with that selection (e.g., integer count, within a plausible range such as 1â12). This is important because Block 5 calculations depend on the correct term system and term count. If validation fails, the system should require a valid term system selection and a corrected authorized term count.
13
GPA format and range validation (current and cumulative)
Ensures each entered GPA is numeric with an allowed precision (e.g., 0.00â4.00 or 0.00â5.00 depending on institutional scale, as configured) and not negative. It should also enforce that cumulative GPA is not blank when a term is marked completed and that values like 'A' or 'Pass' are not entered in GPA fields. If validation fails, the system should prompt for a valid numeric GPA and, if needed, require selection of the correct GPA scale.
14
Term GPA entries align with term completion and initials/date counseling
Checks that if a term has a Current GPA/Cumulative GPA entered (indicating completion), the corresponding Student Initials & Date for that term is present, and vice versa. This supports the requirement that completed terms are counseled and documented. If the alignment fails, the system should flag the specific term and require either the missing initials/date or removal of completion indicators.
15
Course row completeness per term (No., Title, Hours; Grade required if completed)
Validates that for each course row where any field is entered, the minimum required set is present: Course Number (or identifier), Course Title, and Credit Hours. Additionally, if the term is marked completed (via GPA entry or initials/date), each listed course must have an Achieved Grade populated. If validation fails, the system should highlight incomplete rows and prevent submission to avoid unusable academic plans.
16
Total Term Hours equals sum of course hours for that term
Ensures the Total Term Hours field for each term matches the sum of the Credit Hours for all populated course rows in that term. This prevents incorrect workload projections and downstream scholarship term calculations. If the total does not match, the system should either auto-calculate and overwrite the total (preferred) or block submission and request correction.
17
Distance Learning (DL) indicator is boolean and consistent across duplicate DL fields
Validates that DL indicators are captured as true/false (checked/unchecked) and resolves cases where the form has both a checkbox and a separate 'Distance Learning' field for the same row. If both exist, they must not conflict (e.g., checkbox checked but 'Distance Learning' says 'No'). If validation fails, the system should require the user to reconcile the DL status to ensure accurate compliance and reporting.
18
Review section requires exactly one of Yes/No and enforces exceptions requirement
Checks that the Review question (all courses required for degree) has exactly one selection: Yes or No (not both, not neither). If 'No' is selected, the system should require an exceptions entry (e.g., an attached note, reverse-side text field, or an exceptions list) and still require Completion Date (Month, Year) and Academic Discipline. If validation fails, the system should block submission until the review choice and required supporting details are provided.