--- title: "Timesheet Software with Approvals | Orangescrum" description: "Weekly timesheets filled in once and routed to an approver, with billable and non-billable hours that feed invoicing and project cost." canonical: https://www.orangescrum.com/timesheet --- # Timesheet Software with Approvals | Orangescrum > For the complete documentation index, see [llms.txt](https://www.orangescrum.com/llms.txt). [Home](/) / [Features](/features) / Timesheet Timesheet # Timesheets Your Team Will _Actually Fill In_ One weekly grid instead of task by task entry. Managers approve before the hours count, and approved time flows straight into billing and cost reports. Available in[Cloud](/pricing "Cloud - included")[Self-Hosted](/self-hosted "Self-Hosted - included")Open Source [Start Free Trial →](/sign-up?utm_source=website&utm_medium=feature&utm_content=timesheet)[Book a Demo](https://calendly.com/orangescrum) Free forever plan · No credit card required · Set up in minutes ## What is a project timesheet? A project timesheet records how many hours each person spent on each piece of work over a period, usually a week. Orangescrum keeps timesheets attached to real tasks and projects, adds an approval step so a manager checks the hours before they are used, and then feeds the approved time into invoicing, project cost, and utilisation reporting. The problem ## Why timesheets _get ignored_ Filling them in is tedious Logging hours task by task takes longer than the work sometimes did. ✓ One weekly grid covering every project at once. Nobody checks them Hours go straight to billing with no review, so errors reach the client. ✓ Approval puts a manager between the log and the invoice. The data goes nowhere Hours are collected and then rekeyed into a finance spreadsheet. ✓ Approved hours feed invoices and cost reports directly. What you get ## Weekly timesheets with _a real approval step_ The whole timesheet module, grouped by the week it goes through: filling it in, the rules it follows, submitting it, deciding on it, and what the approved hours then feed. 01Grid - ### One week, every project Fill in a whole week across every project in one screen rather than task by task. - ### A cell for each day Type hours into a cell for every task and day, and mark that cell billable or internal. - ### Add lines as you go Add a project and task row to the week without leaving the grid. - ### Running totals Totals per day, per row and for the week update as you type. - ### Holidays and weekends marked Non working days are shaded in the header and holidays are named, so nobody logs into them by accident. - ### Move between weeks Jump to any week with a date picker, step forward or back, or return to the current week. - ### Clear a week Remove every entry for a task across the week in one action. - ### A daily view too A one day at a time screen for people who would rather log as they go than fill in a week. 02Rules - ### Estimated hours cap A cell that would push a task past its estimated hours is refused unless the person is allowed to exceed it. - ### Open dependencies flagged Saving the week reports back any task whose dependencies are still open. - ### Closed tasks are protected Logging against a closed task needs its own permission. - ### A submitted week is read only Once it is with an approver, the grid locks until a decision is made. 03Submission - ### Pick your approver Choose from the approvers set up for your company and add a comment with the week. - ### Hours check first Before you submit you are told whether the week is short of, over, or exactly the hours expected. - ### One per week A week that is already pending or approved cannot be submitted a second time. - ### Rejected weeks reopen A rejected week becomes editable again so it can be corrected and sent back. 04Approval - ### Accept or reject with a reason A rejection requires a note, and that note goes back to the person who submitted. - ### Bulk decisions Select several weeks and approve or reject them together. - ### Queues by state Pending, my pending, approved, rejected and my activity, with a count on what is still waiting. - ### Open the week See every entry in a submitted week grouped by project and task, with a total for each day. - ### Email on submit and decision The approver is emailed when a week arrives, and the submitter is emailed with the outcome. - ### Audit trail Every decision is written to an approval log, so the history of a week is recoverable. 05Approvers - ### Manage the list Add approvers, deactivate them, or remove them as your reporting lines change. - ### Protected while work waits An approver who still has timesheets pending cannot be deleted or deactivated. 06Downstream - ### Billable and non billable Each cell is chargeable or internal, so invoices only pick up work you can bill. - ### Cost and invoicing Approved billable hours become project cost and client invoices with no re keying. - ### Timesheet report Estimated, billable, non billable, approved, rejected and pending hours by project or by person, exported to a spreadsheet. - ### Timesheet PDF Produce a PDF of a person's timesheet for a date range. 07Access - ### Unlimited users Every person who logs time is included, because there is no per seat cost. How it works ## How a week _gets closed_ 1 Log through the week Hours are captured against tasks as work happens. 2 Submit The person reviews the weekly grid and submits it. 3 Approve A manager checks the hours and approves or returns them. 4 Bill and report Approved hours feed invoices, project cost, and utilisation. Who it's for ## For teams that _bill their time_ Agencies Accurate client billing with a review step before the invoice goes out. [Learn more →](/agency-project-management) Professional services Utilisation tracking so billable capacity is not quietly lost. [Learn more →](/professional-services) Internal teams Real effort data to compare against budget and plan. [Learn more →](/budget-and-cost-management) Availability ## Which edition includes _what_ Orangescrum runs as managed cloud, self-hosted on your own servers, or as the open-source Community Edition. Here is exactly what each one includes. Timesheets and approvals are on the Pro plan and above, and in Self-Hosted. | Capability | CloudManaged SaaS | Self-HostedOn-premise / private cloud | Open SourceCommunity Edition | | Log time against tasks | ✓ | ✓ | ✓ | | Daily timesheet | Pro | ✓ | ✗ | | Weekly timesheet grid | Pro | ✓ | ✗ | | Billable and non billable per cell | Pro | ✓ | ✗ | | Estimated hours cap on entry | Pro | ✓ | ✗ | | Submit a week for approval | Pro | ✓ | ✗ | | Hours check before submitting | Pro | ✓ | ✗ | | Approve or reject with a reason | Pro | ✓ | ✗ | | Bulk approve and reject | Pro | ✓ | ✗ | | Approver management | Pro | ✓ | ✗ | | Approval audit log | Pro | ✓ | ✗ | | Email on submit and decision | Pro | ✓ | ✗ | | Timesheet report and Excel export | Pro | ✓ | ✗ | | Timesheet PDF | Pro | ✓ | ✗ | | Invoicing from approved hours | Premium | ✓ | ✗ | | Attendance clock in and out | ✗ | ✓ | ✗ | Frequently asked questions ## Timesheet _FAQ_ ### Does Orangescrum have timesheets? Yes. Orangescrum has weekly timesheets where people fill in a whole week across every project in one grid, with an approval step before the hours are used for billing or reporting. ### Which plan includes timesheets? Timesheets and approvals are available on the Cloud Pro plan and above, and are included in the Self-Hosted edition. Basic time logging against tasks is in every edition. ### Can managers approve timesheets? Yes. Timesheets are routed to a nominated approver who can accept them or send them back with a comment, so errors are caught before they reach an invoice. ### Can I separate billable hours? Yes. Each entry is marked billable or non billable, so client invoices only include chargeable work and internal time still shows up in cost reporting. ### Does approved time feed invoicing? Yes. Approved billable hours can generate a client invoice directly, with no re entry into a spreadsheet. ### What stops a week being submitted with the wrong hours? Before you submit, Orangescrum compares the week against the hours expected and tells you whether you are short, over, or exactly on. A cell that would push a task past its estimated hours is refused unless you are allowed to exceed it. ### Can an approver see who has not submitted? The approval screen shows a pending queue with a count, and the approver settings show how many timesheets are waiting on each approver. There is no automatic reminder email, so chasing is still a person's job. ### Can I export timesheet data? Yes. The timesheet report exports to a spreadsheet, and you can produce a PDF of a person's timesheet for a date range. ### What is the difference from attendance? A timesheet records effort against project work. Attendance records working hours with clock in and clock out. Attendance is a separate module in the Self-Hosted edition. ## Close the week in minutes Timesheets with unlimited users. No per seat pricing. [Start Free Trial →](/sign-up?utm_source=website&utm_medium=feature&utm_content=timesheet_cta)[Book a Demo](https://calendly.com/orangescrum) ## Related capabilities [Time trackingTimers and task level logging](/time-tracking)[Invoice softwareBill from approved hours](/invoice-software)[Budget and costCost against budget](/budget-and-cost-management)[Attendance and leaveClock in, clock out, leave](/attendance-leave-management)