Class Attendance Policy Roster

How to use Class Attendance Policy Roster

Declare status credits between zero and one and whether each counts in the denominator. Enter one ordered mark per student for every dated session; null means pending. Exclude canceled sessions globally, then inspect each student's exact credit, included weight and session decisions.

1. Use the example as the schema; replace its labels and entered model assumptions.
2. Declare status credits between zero and one and whether each counts in the denominator. Enter one ordered mark per student for every dated session; null means pending. Exclude canceled sessions globally, then inspect each student's exact credit, included weight and session decisions.
3. Calculate, inspect the complete witnesses and limitations, then copy or download the JSON report.

Good to know

• Up to 30 students,12 statuses and 100 sessions. Session weights are positive at most 1,000 with six decimal places. Every marks array must exactly match roster length; all status IDs and dates must be valid, even in canceled sessions.
• An excluded status must have zero credit. Multiple sessions on the same date are allowed and keep source order. No automatic attendance collection, login, course grade, headcount-only presence rate, legal threshold, institutional policy or LMS interchange is inferred.
• Local calculation with no upload, input persistence or outside lookup. Model JSON is limited to 30,000 characters and 10,000 values. Decimal quantities are strings with up to six places; count fields use plain JSON integers. Exact fractions are capped at 8,192 bits. The complete JSON output is limited to 1,000,000 characters; approximate numbers preserve their stored values. Unsupported states fail explicitly.