Direct download · XLSX checked with LibreOffice Calc
This free Excel template provides an attendance code configuration matrix for documenting and reviewing operational attendance code settings. Enter one configuration per row, use controlled lists for standardized fields, and review calculated checks for completeness, logic, uniqueness, and effective-date status.
The workbook includes fictional sample configurations for demonstration and 100 prepared input rows; it does not contain student attendance records or personal student information.
Preview 1 — “Dashboard” sheet Click to enlarge
In practice
What this template helps you manage
✓
Keep attendance code identifiers, categories, scope settings, status, counting behavior, credit, minutes, effective dates, import values, and notes in one structured matrix.
✓
Use validated lists for category, scope type, scope name, status, and Yes or No fields to support consistent data entry.
✓
Identify missing required fields and selected configuration conflicts through calculated review columns.
✓
Check whether Code ID and Import Value are duplicated within the same Scope Type and Scope Name.
How to use it
How to use the workbook
Start on the Dashboard and set the As of Date; the supplied default is September 7, 2026. Next, open the Code Matrix and review the fictional sample configurations before replacing or removing them as appropriate. Enter one attendance code configuration per row in the editable cells, using the available drop-down lists and permitted numeric or date ranges. Then review the calculated Configuration Key, Required Fields Check, Logic Check, Uniqueness Check, Date Status, and Overall Review columns. Correct rows marked Incomplete or Review, and return to the Dashboard to confirm the resulting counts and charts. If you intentionally change available drop-down choices, update the visible entries on Validation Lists and the related validation source ranges together. Do not enter personal student information.
Preview 2 — “Code Matrix” sheet Click to enlarge
Inside the file
Included features and controls
＋Four worksheets: Dashboard, Code Matrix, Validation Lists, and Instructions.
＋An Excel table named tblCodes covering A4:X104, with 100 prepared input rows from rows 5 through 104.
＋Calculated columns for Configuration Key, Required Fields Check, Logic Check, Uniqueness Check, Date Status, and Overall Review.
Standardize Attendance Code Configuration
The Code Matrix centralizes the settings used to define each attendance code. Fields cover Code ID, Display Name, Category, Scope Type, Scope Name, Status, Counts as Present, Counts as Absent, Excused, Instructional Credit %, Default Minutes, Requires Comment, Requires Approval, Effective Start, Effective End, Import Value, Sort Order, and Notes. The prepared table provides 100 operational input rows, while included fictional examples demonstrate how configurations can be entered.
Preview 3 — “Validation Lists” sheet Click to enlarge
Review Required Fields and Attendance Logic
Six calculated columns support configuration review. Required Fields Check tests whether expected entries are complete, while Logic Check identifies selected conflicting combinations. The workbook can flag a code that counts as both present and absent, an excused code that does not count as absent, or positive instructional credit assigned to a code that does not count as present. Overall Review then classifies populated rows as Ready, Review, or Incomplete.
Find Duplicate Codes Within the Same Scope
The Configuration Key combines the uppercase, trimmed Code ID with Scope Type and Scope Name. The Uniqueness Check looks for duplicate Code ID values and duplicate Import Value entries within the same Scope Type and Scope Name. This supports review of both All Locations and Location configurations without asserting that identifiers must be unique across unrelated scopes.
Preview 4 — “Instructions” sheet Click to enlarge
Monitor Readiness and Effective-Date Status
The Dashboard uses its As of Date to summarize configuration readiness and date status. Active records can be reported as In Effect, Not Started, Ended, or Missing Date based on their effective dates, while Draft and Retired records retain their corresponding status. Dashboard totals also show category distribution and Ready, Review, and Incomplete results, supported by two charts.
Common questions
About this template
The Code Matrix contains 100 prepared input rows, from rows 5 through 104. Some rows are populated with fictional examples, so 100 describes the prepared row capacity rather than the number of completed operational configurations.
Overall Review returns Incomplete when required fields are not complete. It returns Review when required fields are complete but the Logic Check or Uniqueness Check identifies an issue. A populated configuration is marked Ready when those checks pass.
Date Status compares each populated configuration with the As of Date on the Dashboard. Depending on Status, Effective Start, and Effective End, the result can be Draft, Retired, Missing Date, Not Started, Ended, or In Effect.
The Uniqueness Check tests for duplicate Code ID values and duplicate Import Value entries within the same Scope Type and Scope Name. It does not state that those values must be unique across different scopes.
The Validation Lists sheet contains the visible choices used by the Code Matrix drop-down fields. If the workbook design is intentionally changed, update both the visible lists and their associated validation source ranges so the controls remain aligned.
No. This workbook is for defining and reviewing attendance code configurations. It does not contain student attendance records, calculate student attendance rates, or import configurations into another system. Do not enter personal student information.
Editorial process
Prepared and reviewed against the workbook
Course Ops Workbook Team
Workbook preparation
This functional byline identifies the team role that structures the workbook, sample data, calculations, and operating checks.
Course Ops Editorial Team
Editorial review
This functional byline identifies the team role that checks the page against the generated workbook and states its limits.
