> 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/health/v2.1/access/public-health-product-suite/health-campaign-management-hcm/attendance-and-payments-user-manual/proximity-supervisor.md).

# Proximity Supervisor

Approve attendance registers

## Overview

Reviews attendance registers at the end of each billing period and approves them to trigger payment. Can also add, remap, and disable workers during the campaign.

At the end of each billing period, the Proximity Supervisor receives the attendance registers mapped to them. They review worker performance and attendance days, make any corrections, and approve the register. This approved register is what the Bill Generator uses to create a payment bill.

## Steps

{% stepper %}
{% step %}

### Log in to HCM Console

Use your Proximity Supervisor credentials (UAT: Nd-psup-1, eGov\@123). Navigate to Attendance, then Attendance Registers.
{% endstep %}

{% step %}

### Find the register pending approval

Registers that are ready for approval will show as Pending. Click on a register to open it.
{% endstep %}

{% step %}

### Review the register summary

At the top of the register, you will see the boundary, the Attendance Officer, total attendees, event duration, attendance duration, and the current status. Below this is the worker list with their role, Performance (number of registrations or interventions), and No. of Days Worked.
{% endstep %}

{% step %}

### Edit days worked if needed

Click the plus or minus buttons next to each worker's No. of Days Worked to adjust. You can also click on a worker's name to view their full details, including User ID, phone number, Team Code, and payment information.
{% endstep %}

{% step %}

### Save changes

Once all edits are done, click Save Changes. The register status updates.
{% endstep %}

{% step %}

### Approve the register

Click Approve. Add an optional comment. Once approved, the register status changes to Approved and becomes available to the Bill Generator.
{% endstep %}
{% endstepper %}

Figure 6: The Proximity Supervisor's attendance edit screen. Use the plus and minus controls to adjust the No. of Days Worked for each worker. The status shown here is Approved.

{% hint style="info" %}
**Tip:** The Performance column shows registrations and interventions. This is a rough confidence check, not a strict pass or fail. A few fluctuations are expected.

If you need to add or remap a worker during the campaign, use the Edit Register option to add individual users or upload an updated user list via Excel.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digit.org/health/v2.1/access/public-health-product-suite/health-campaign-management-hcm/attendance-and-payments-user-manual/proximity-supervisor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
