> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/boomerang-3-domain-administrator-manual/dashboard/control_points.md).

# Control points handling

Control points are used to remind users about the tasks they shall perform.

Control points are defined by an administrator. Every control point has a title, description, first expiration date and time and repeating period. It can also have an end date after which it will become not active and will not repeat any longer.

The control points may belong to regular or function objects.

There are three active control points on the screenshot below called ‘Weekly unit check’, ‘Daily CP’ and ‘Weekly CP’. They belong to regular and function objects respectively.

There is a control point frequency like “Weekly” and the date and time is the expiration time. There is “Sign” button to sign the control point once its task is done.

![](/files/szNsz3MYYNy1aWyLQJtK)

The start date and time and repeating period define together the nearest deadline for a given control point. This deadline is hereafter called the expiration time.

The control points functionality is described below:

1. In the initial state the CP was signed before its current expiration time and is not active. The CP is not visible in the dashboard.
2. When the current expiration time is reached the CP is activated and appears in the dashboard with the next expiration time shown as its deadline.
3. The user performs the CP task and signs the CP to register the fact. He must click ![](/files/VgPqsdnN8n9h10X7Wj3n) to open the signing form. A comment may be added in the form.
4. The signed CP is removed from the dashboard as it is not active. The flow returns to point 1. The signing is registered in Logbook as “Control Point Signed” event.

![](/files/Fc5nhyUUWjGFYLHrNDFG)

5. If the user did not sign the CP before its expiration time, it is signed automatically by the system. The signing is registered in Logbook as “Control Point Expired” event. In this case, after automatic signing the CP is again shown in the dashboard with the next expiration time because the condition from point 2 was fulfilled just after the signing.

![](/files/e05KoRn5MvtioKKkXM99)

Click the object and select “Control points” tab to perform more actions.

![](/files/uOiDSlm7O5oIwqACR9zC)

![](/files/1fb4uF4t0qKUphkkLgug) ![](/files/B7dVsay4UUpq69twHiJM)

The “Open / Signed” presents the control point state. Click ![](/files/TIwyRaOh1P4kkEaB4cBf) to sign. Click ![](/files/UgkJeojy8CAXvSYYHIEW) to see the history. Click ![](/files/rBS9lEtN0kKZnKOPmnv1) to see the details.


---

# 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:

```
GET https://help.boomerang3.com/boomerang-3-domain-administrator-manual/dashboard/control_points.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.