> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-sups-managers/timekeeping/timekeeping-overview-2.md).

# Best Practices

#### **Permissions**

Make sure your staff all have access to view their own timesheets - this can be configured in [Roles and Permissions](/flaik-knowledge-base/for-administrators/admin-settings-general-settings/roles-and-permissions.md).

#### **Check daily**

Encourage staff to check their timesheets daily using the My Timesheets page, and to submit disputes through flaik so that you can quickly resolve discrepancies as they arise. 

#### **Fixing issues & disputes**

When you need to fix an issue with a timesheet, try to fix it *upstream of Timekeeping* first. Chances are the issue was caused by missing or incorrect data in Scheduling or Class Management. Adjusting the data there will automatically fix the timesheet, but it will also ensure other features (like staff metrics) stay accurate as well. If you really get into a bind, [drop us a line!](/flaik-knowledge-base/welcome/readme/meet-our-customer-success-team.md)

#### **Configuring your paid activities**

Set up your paid activities in accordance with your accounting/labor reporting guidelines. For example, if your school needs to report on individual base areas within your accounting system, you should have a different version of a given paid activity for each base area so that the reporting features in flaik align with your accounting practices. 

{% hint style="info" %}
The [**Paid activity reporting**](#paid-activity-reporting) dashboard will show you quick totals of how much you're paying in labor for specific paid activities. The more paid activities you use, the more precise the dashboard can become. 
{% 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 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://knowledgebase.flaik.com/flaik-knowledge-base/for-sups-managers/timekeeping/timekeeping-overview-2.md?ask=<question>&goal=<endgoal>
```

`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.