> For the complete documentation index, see [llms.txt](https://documentation.taskmaverick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.taskmaverick.com/your-organization/people/time-timesheet.md). # Time (Timesheet) The Time page is where you record how many hours each employee works per week. This data powers all per-hour metrics across Taskmaverick - without it, Missions/Hour, Points/Hour, and Ratings/Hour in [Dashboard ](/analytics-and-monitoring/dashboards/performance-dashboards.md)and [Reporting ](/analytics-and-monitoring/reporting.md)show zero or inaccurate values. ## Why fill in the Timesheet? Taskmaverick calculates key performance metrics per hour - not just totals. A team that closes 50 Missions in 40 hours is more efficient than one that closes 50 Missions in 80 hours. But the system can't know this unless you tell it how many hours each person worked. **Example:** A restaurant manager reviews the [Unit Dashboard](/analytics-and-monitoring/dashboards/performance-dashboards.md#unit) and sees that the Kitchen team's Missions/Hour dropped this week. They check the Timesheet and realize two employees' hours weren't entered - fixing the data corrects the metric. ## How to use it Go to **Time -> Timesheet** in the top navigation. ### What you see A table with one row per active employee and one column per week. Each cell holds that employee's working hours for that week. ### Entering hours 1. Click any cell in the table 2. Enter the hours worked (decimals allowed — e.g. 37.5) 3. The value saves automatically {% embed url="" %} ### Filtering * Filter by **Unit** and/or **Team** (multi-select) to focus on specific locations or groups * Default: All Units, All Teams ### Selecting a date range Use the date picker to choose which weeks to display. Maximum selectable period is **12 weeks**. Each column represents one week (Monday to Sunday). ### Finding missing entries Toggle **Show only incomplete** to display only employees who have empty cells for any past week. The current week is excluded — you're not expected to fill in a week that hasn't ended yet. ## Deputy integration If your organization uses Deputy for shift scheduling and the integration is enabled in [Organization Settings](/your-organization/organization-settings.md#integrations), hours for connected employees are **filled in automatically** from their Deputy timesheets. Worked hours reflect billable hours with unpaid meal breaks excluded. For connected employees: * Hours update automatically when Deputy records change * Inline editing is **disabled** - you can't manually override Deputy data * Connected employees are marked with the Deputy logo in the table When the integration is turned off, manual editing becomes available for all employees again. ## Good to know * Only **active** employees appear in the Timesheet * [Pay Type](/your-organization/people.md#pay-types) and Name columns are **read-only** - only hours can be edited * Hours data feeds into: [Dashboard ](/analytics-and-monitoring/dashboards/performance-dashboards.md)(Team, Unit, Personal), [Reporting ](/analytics-and-monitoring/reporting/report-sections-at-a-glance.md#statistics-performance-and-points)(Performance and Points reports), and the mobile Leaderboard * Only [System Admins](/your-organization/people.md#roles) and [Organization Managers](/your-organization/people.md#roles) can access and edit the Timesheet --- # 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://documentation.taskmaverick.com/your-organization/people/time-timesheet.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.