Constraints - Grade Related

For definitions on some of the terms below or refreshers on constraint basics, please visit our Constraints article!

This article contains constraints that deal with limiting courses and requirements based on their grades. The constraints are listed at the top and bottom of the article, with the bottom of the article containing more details about each constraint.

Constraints at a Glance

• Non-letter grade passed courses can satisfy this requirement
• Allow ungraded courses to count for specific terms only
• Pass with minimum grade [x]
• At most [x] courses/units with defined grades
• At most [x] courses/units with transfer grades

---

Constraint Details

Non-letter grade passed courses can satisfy this requirement [Secondary Constraint]
This constraint is most often used for Pass or CR grades, which most institutions do not permit to count freely throughout audits but do permit in specific requirements. (Such settings are determined via the institution's Configuration settings.) For example, a major audit may  include core courses, for which only letter grades are permitted, but then an electives section for which students can take courses with a P grade. Using this "Non-letter grade passed courses can satisfy this requirement" constraint would allow a P to count only within that section of the audit. 

 

Additional context: This constraint was formerly and is equivalent in behavior to: "Ungraded passed courses can satisfy this requirement." While the "ungraded" language is no longer included in our requirement editor, you may still see the constraint functioning in audits that were built in prior years. 

 

Allow ungraded courses to count for specific terms only [Secondary Constraint]

This constraint is the same as the constraint above, but limits ungraded passed courses to count only for specific terms. A common use for this constraint were the extenuating grading circumstances that happened for many universities in Spring 2020 with COVID 19 changes.

 

Pass with minimum grade [x]  [Secondary Constraint]

Stellic will only count passing grades towards requirements, but if a certain requirement must have a higher grade, you can use this constraint.

 

At most [x] courses/units with defined grades [Secondary Constraint]

• This constraint allows you to dictate how many courses above or below a certain grade, or how many transfer courses, can be allowed to count for the requirement. To make sure that no courses of a certain grade or no transfer courses would fill the requirement, set the count to ‘0’.
• You can select the scope of the "defined grades" to be:
  • Grade, Grade or lower, Grade or better, Multiple grades, Transfer grades, Transfer status

or

 

At most [x] courses/units with transfer grades  [Secondary Constraint]

• This constraint checks for if the grade of a course is marked as a transfer grade within the backend of the system (this would have been established during initial Stellic set up - contact your campus Stellic admin for more information), and then limits the number of units of courses with transfer grades. There can be multiple grades that fall within this constraint (for example, if your institution used all of these for various types of transfer credit, they would all fall under this constraint: T, TA, TR, etc.)

 

The following courses [x] will not count with these grades [x]   [Secondary Constraint]

This constraint allows you to specify a grade criteria for specific courses (or courses with attributes, course range, or a course pattern) that are exceptional to the rules. In the example below, C- is the standard grade for the courses in the program, but we want computer science courses to have a higher grade standard than the other courses.