Everhour brings absence entries into team timesheets for Basecamp work, keeping approved hours ready for payroll review.
Try with my Basecamp
$10k of $15k
Hourly
0:00:00
Alejandro Luna0:00:00Kai Nani0:00:00Kai Nani0:00:00Click!
Dave Jung0:00:00Alejandro Luna0:00:00Dave JungThe calculator gives you the number — Everhour takes it from there.
One click and you're timing. Start a timer, add an entry, edit the details. This is exactly how it feels in Everhour.
Set a budget, assign rates, and get alerted before you're over.
Measurement
Track your budget through time or costs
Every report you need — configured your way, always up to date.
Tracked hours flow straight into a polished invoice — no copy-paste, no manual math.
Managers need a weekly view that explains team availability across Basecamp projects. Basecamp holds projects, to-do lists, to-dos, assignees, due dates, files, schedules, and project discussion. Time off belongs in the same review cycle as tracked work time because payroll and staffing review need to separate project hours, working hours, and absence hours.
A useful record shows the person, week, project context, tracked work, and approved time off. That gives the reviewer a complete total without forcing absence into a project to-do. For payroll review, the weekly record should show who submitted time, which entries were approved, and whether any late correction changed the totals after review.
A reliable weekly cycle starts with team members entering project hours against Basecamp to-dos and recording time off in the same timesheet period. Managers review totals by person, compare expected capacity with submitted time, and return entries that need correction before payroll or client reporting uses them.
The approval step matters because submitted and approved time should stop moving. Regular members should not keep changing entries after a manager has approved the week. If an approved period needs a correction, an admin should make the change with a clear trail, then rerun the affected report or export before anyone uses the record for payroll, billing, or staffing decisions.
Absence hours explain capacity, but they should not inflate a client project, a Basecamp to-do, or a task estimate. A week with 32 project hours and 8 hours of paid time off tells a different story than 40 hours charged to one project.
Use project time for actual work on Basecamp to-dos. Use time off for vacation, sick leave, holidays, or other non-project absence. If your team reviews working hours and project hours, keep both visible so the manager can see the full week and still preserve accurate project totals.
A one-off record is enough when you only need to note an absence for a small team or export one weekly view. A managed workflow becomes necessary when multiple people submit time, managers approve it, periods lock after review, and payroll or billing depends on the same numbers staying stable.
Everhour supports that managed workflow with timesheet approvals, locked periods, admin time correction, team timesheet exports, and time off included in gross timesheet totals according to each member's working capacity. Everhour Expenses tracks project costs with receipts, unit-based categories, budget inclusion controls, invoice integration, and expense reports for reimbursement and profitability review.
This content is for general information only, may not be fully up to date, and is provided without any warranty or liability.
High Performer
G2
Summer 2026
Best Ease Of Use
Capterra
Summer 2026
Rated in the top time trackers across G2, Capterra, and TrustRadius — with consistent praise for ease of use, integrations, and support.
Time off should be reviewed before the manager approves the weekly total. Absence explains why a person has fewer project hours, and project hours show which Basecamp to-dos received actual work. Reviewing both together keeps capacity, payroll context, and client reporting consistent before the period closes.
Paid holidays should appear in the same weekly review period as the related project hours when the team uses gross timesheet totals for payroll review. Keep the holiday entry separate from Basecamp to-dos so the weekly total reflects paid time while project reports still show only work actually performed.
The record should show the person, date, time off category, hours, and the week being submitted. Managers also need project hours in the same review period so they can compare absence with expected capacity. Missing notes matter less than incorrect dates, because date errors move hours into the wrong payroll week.
A partial-week absence should sit beside the person's project hours for the same week. For example, 24 project hours and 16 hours of approved time off should stay as two categories. That structure helps the manager confirm the person's total availability without assigning absence to a Basecamp to-do.
Late edits change totals after someone has already used the timesheet for payroll, billing, or staffing review. Approved periods should stay locked for regular members. If an absence was missed or entered on the wrong date, an admin should correct it deliberately and refresh any affected report or export.
Everhour Expenses tracks project costs alongside billable hours, using receipts, unit-based categories, budget inclusion settings, invoice integration, and expense reports. That gives managers a separate cost workflow for reimbursement and profitability review without turning expenses into timesheet entries.
Everhour Timesheets let team members submit weekly project hours or working hours for review, then managers can approve, reject, or partially approve submitted time. Submitted and approved time is locked for regular members, while admins can correct entries when a payroll or billing record needs cleanup.
Track absence, project time, and project expenses through reviewed workflows. Everhour connects Basecamp work to approvals, locked periods, exports, and expense reports for cleaner payroll and profitability review.
14-day free trial · No credit card · Cancel anytime
