Users of the August Schools platform often solicit and store various documents and other information for students that may required for a school policy or program requirement. The Requirements feature helps users to determine whether a student or group of students meet a specific school policy or program criterion based on information housed on the student's record in August Schools. The Requirements feature does this by allowing users into define each requirement of the policy or criterion and then visualizes whether the students meet the requirement. Users create several requirements into a single requirement set that represents what is needed for a student or group of students to meet the policy or criterion. In this way, users can have a visual representation of whether the data they have collected for a student to date is sufficient, and can then follow up as needed via student groups, form requests, messages, etc.
The Requirements feature set can be accessed from the left navigation bar.
The Requirements page will show you a table view of all the requirement sets to which you have visible. These are called requirements sets because it a collection of requirements that together, and not independently, determine whether that policy or criterion is met.
Each requirement sets has a grid that visualizes whether each student meets each requirement in the set and can be exported.
Simply select the 'Grid' tab to see this visualization.
Users may also download this grid into a document to share externally or with themselves by selecting the 'Download' button on this Grid view.
Each requirement in a Requirement Set has a requirement rule that is powered by a Query and has exportable results that can also be turned into student groups.
Clicking into a Requirement Set will show each requirement added to it. That requirement can then show the user what the requirement rule is being used to determine if the requirement is being met by the student(s). The requirement rule is an Query like a user would see/use in the Reporting feature set or when setting up supplemental request rules in the Forms feature set.
Each requirement visualizes a list of students who are complaint (and thus meet) the requirement, and a list of students who are non-compliant (and thus do not meet) the requirement. Users can toggle between these lists when viewing the requirement rule.
Users may also download either list into a document to share externally or with themselves by selecting the 'Download' button on either the Compliant or Non-compliant view.
Likewise, users may also create a student group from either list by selecting the 'Create group' button on either the Compliant or Non-compliant view. This is how a user would, for example, begin the process of sending a form request to solicit missing information for the non-compliant students.
Requirement sets can be edited at any time to change how they are named, to whom they are visible, and to which students they apply.
This achieved by selecting the 'Update details' button and confirming the necessary changes in the popup window.
Requirement Sets that are visible to platform users can be viewed on the Requirements tab of the Student Card.
Likewise, Requirement Sets made visible to portal users are visible on the student's record in the Portal under the Requirements section.
Requirement sets can also be archived when no longer needed.
This is achieved by selecting the 'Archive requirements' button and confirming the action in the popup window.
