> For the complete documentation index, see [llms.txt](https://teranoapps.gitbook.io/missing-worklog-reminder/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://teranoapps.gitbook.io/missing-worklog-reminder/usage/view-reminder-raport.md).
# View Reminder Raport
#### See how your team performs against a single reminder policy
The **Reminder report** page lets you analyse how well one specific reminder policy is being met over time.\
It answers questions like:
* *How many users are covered by this policy?*
* *What is our overall compliance rate?*
* *Who is missing worklogs, and on which days?*
You open this view from the **Worklog Reminders** by selecting a reminder and choosing its **View raport**.
***
#### πΈ Raport Preview
The example below shows a **Reminder report for a daily reminder**.
Reminder report for Daily reminder
The report combines a high-level KPI summary with a detailed, user-by-day matrix, so managers can quickly scan for problems and then drill into specific users or dates.
***
### π KPI Summary Bar
At the top of the page, a summary bar highlights key metrics for the selected policy:
* **Users tracked** β how many users are currently in scope for this reminder.
* **Compliance rate** β the percentage of entries where the requirement was met (for example, daily hours logged correctly).
* **Needs attention** β entries where some work was logged, but the policy threshold was not fully met.
* **Missing logs** β entries where required worklogs are completely missing.
* **Avg hours/day** β average logged time per day for the selected users and period.
* **Period coverage** β how many days are included in the report window.
These indicators give you an instant sense of how healthy your teamβs time-tracking is for this specific policy.
***
### π Timeline Matrix (Users Γ Days)
Below the summary youβll find the main **matrix view**:
* **Rows** represent individual users in the policy.
* **Columns** represent time windows (for a daily policy: days; for weekly or monthly policies: weeks or months).
* **Cells** show the result for a user in a particular window.
Visual cues make it easy to read at a glance:
* **Green cells** β requirement met, policy fully satisfied.
* **Amber cells** β partial compliance, some work logged but below the expected threshold.
* **Red cells** β missing logs where time was required.
* **Grey cells** β no target for that window (for example, user not yet in scope or policy not active).
Each cell displays the logged time (for example, `1d 2h 46m`). When you hover, a tooltip can show the difference versus the target, so you immediately see how far away from compliance a given entry is.
***
### π Search and History Window
Above the matrix, the report includes controls that let you focus on the most relevant data:
* **Search users** β filter the report by display name to quickly locate a specific person and see only their row.
* **History window selector** β choose how many of the most recent entries to display (for example, last 5 days for daily policies). The available options adjust automatically to the type of policy window (daily, weekly, or monthly).
When you change the history window, the report reloads to show only the most recent runs, keeping the view fast and focused.
***
### π€ Exporting the Report
Use the **Export** button to download the current view as a CSV file.
* Each **row** in the file represents a user.
* Each **column** represents a time window (day, week, or month, depending on the policy).
* Each **cell** contains the same formatted time value you see in the UI (for example, `2h 30m`).
This makes it easy to bring the data into spreadsheets, BI tools, or internal audit documents without additional cleanup.
The Export button is enabled only when there is data to download, preventing empty files.
***
### π£ Typical Manager Workflow
1. Open **Project settings β Worklog Reminders**, select a reminder, and navigate to its **report**.
2. Review the **KPI summary bar** to see overall compliance and how many entries need attention.
3. Scan the **matrix** for red or amber cells to spot users or days with missing or partial logs.
4. Use **search** to focus on specific team members, and adjust the **history window** to analyse trends over the last few days or weeks.
5. Click **Export** if you need to share the data or include it in financial, billing, or HR reviews.
The Reminder report turns raw policy runs into an actionable, visual overview β helping you keep time-tracking clean, spot recurring issues early, and support your team in staying compliant.
---
# 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://teranoapps.gitbook.io/missing-worklog-reminder/usage/view-reminder-raport.md?ask=&goal=
```
`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.