> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/relate/public-calendar/public-calendar-monitoring-your-calendar.md).
# Public Calendar - Monitoring your Calendar
The Public Calendar can be used as a powerful tool for **meeting tracking**, providing a clear view of what is coming up and what has already happened.
***
***
#### Upcoming Meetings
In this view, you can keep track of all meetings **scheduled**, making it easier to plan and organize the agenda.
Allows you to view:
* Meeting date and time
* Responsible party
* Meeting type
* Status (scheduled)
This view helps avoid schedule conflicts and ensures everyone is aligned with upcoming commitments.
***
#### Past Meetings
Here are recorded all the meetings that have already taken place or that were not held as planned.
They are automatically classified by status:
* **Attended**: meeting successfully held
* **Did Not Attend**: absence of one of the parties
* **Canceled**: meetings canceled before taking place
This history is essential for performance analysis and productivity tracking.
***
### Meeting Pending Items
The **meeting pending items** indicate commitments that have already taken place, but **the contacts' attendance has not yet been recorded**.
> ⚠️ It is necessary to mark the contacts' attendance in the meetings below to keep the data correct and ensure reliable analyses.
This step is essential so that attendance, best day, and best time indicators are calculated correctly.
***
#### How to resolve pending items
1. Access the pending meeting in the calendar
2. Mark the contact status:
* Attended
* Did Not Attend
After this record, the meeting no longer appears as pending.
***
### Recent Activity
The section **Recent Activity** shows the moments when the calendar was **created or updated**, providing more control and traceability of actions.
In it, you can follow:
* Calendar creation
* Date and time changes
* Configuration updates
This history helps to understand changes in the schedule and makes audits or internal alignments easier.
***
### Indicators and Analytics
Based on meeting data, the system makes it possible to identify important patterns for decision-making.
#### Attendance
Track attendance rates to understand:
* Participant commitment
* Scheduling efficiency
* Need for communication adjustments
***
#### Best Day
Identify which days of the week have the highest attendance rate, helping define more strategic schedules.
***
#### Best Time
Analyze which times have the best attendance performance, allowing you to optimize future scheduling and reduce no-shows.
***
### Conclusion
The use of the **Public Calendar** for meeting tracking goes beyond agenda viewing. It becomes a strategic tool, allowing you to monitor results, identify patterns, and continuously improve meeting efficiency.
With this information, your team can schedule meetings on the **best day**, at the **best time** and with a higher attendance rate, making time management much smarter.
The use of the **Public Calendar** for meeting tracking goes beyond agenda viewing. It becomes a strategic tool, allowing you to monitor results, identify patterns, and continuously improve meeting efficiency.
With this information, your team can schedule meetings on the **best day**, at the **best time** and with a higher attendance rate, making time management much smarter.
---
# 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.sprinthub.com/en/topics/relate/public-calendar/public-calendar-monitoring-your-calendar.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.