> 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/my-worklog-reminders.md).
# My Worklog Reminders
#### Your personal hub for worklog compliance
The **My Worklog Reminders** page shows **results of your organisation’s time-tracking policies**.\
Each reminder is created automatically after a policy check completes for the selected time window (daily, weekly, or monthly).
***
**📸 Page Preview**
**🔔 Top summary**
* **Action Required** — how many reminders currently need your attention.
* **Total Reminders** — how many reminders you’ve received in the selected timeframe.
* **Status History** — a quick visual of recent outcomes (compliant vs. not compliant), so you can spot trends at a glance.
***
**🗂 Views**
* **Recent Reminders** — the most recent items first (today, this week, etc.).
* **All Reminders** — your full history, useful for audits or month-end reviews.
***
**🧾 Reminder card anatomy**
Each card gives you everything you need to decide what to do next:
* **Title & timestamp** — when this reminder was created.
* **Status badge** — e.g., **Action Required** if you’re currently not compliant.
* **Rule label** — the policy, such as **WEEKLY ≥ 6 DAYS**.
* **Reporting window** — the exact dates evaluated.
* **Progress bar** — e.g., **5d of 6d** logged for the window.
* **Actions** — **Mark as Resolved** and **Ignore**.
If a policy isn’t met, the card is visually highlighted so it’s easy to spot what needs attention.
***
**✅ Mark as Resolved**
Use this when you’ve **updated your worklogs** and want to confirm the reminder is handled.
What happens next:
* The reminder’s status changes to **Resolved**.
* In-product flags for this reminder stop showing.
* The item moves into your history, keeping a clean audit trail.
***
**🚫 Ignore**
Use this when the reminder **shouldn’t apply** (e.g., approved leave, special assignment, known exception).
What happens next:
* The reminder is marked **Ignored** and won’t prompt you again.
* The item stays visible in history with its final state for transparency.
***
**👣 Typical flow**
1. Open **My Worklog Reminders** from the app menu.
2. Check **Action Required** and review the highlighted cards.
3. Click through to your time tracking to finish logging.
4. Come back and **Mark as Resolved** — or **Ignore** if it’s an approved exception.
5. Use **All Reminders** to see your personal history and outcomes.
***
**💡 Tips**
* Use **Recent Reminders** daily; visit **All Reminders** for weekly/monthly reviews.
* If a reminder repeats, check the **Rule label** and **Window** to confirm what exactly is required for compliance.
---
# 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/my-worklog-reminders.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.