> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/works/specifications/functional-specifications/attendance-management.md).

# Attendance Management

## Overview

Attendance Management is divided into 2 parts:

1. Attendance Service
2. Muster-Roll Service

To verify the IDs of the individuals, the attendance service depends on the Individual Registry. It is an optional dependency. If the no individual registry is linked with the attendance service, then the IDs would not be checked for validity and assumed to be correct. 

## Features & Scope

Attendance Service manages the following:

1. Attendance-Register: It maintains a list of individuals enrolled for a given register.
   * Staff: Staff members manage the register. Staff can be created or deleted from a register.
   * Attendee: Attendees are the individuals participating in the register. Attendees can be created or deleted from the register. 
2. Attendance-Log: The log entries of the attendance. It will have events of entry and exit. 

Muster-Roll is a report built upon the attendance logs. It has computed attendance values. It will pass through an approval workflow. 


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digit.org/works/specifications/functional-specifications/attendance-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.