Everhour turns UX project hours into reviewable timesheets, so design work stays connected to billing, budgets, and approvals.
Enter your time in and out for each day. Overtime and gross pay are calculated automatically.
| Day | Time In | Break Start | Break End | Break | Time Out | Total |
|---|
The 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.
You need a record that shows where design effort went: discovery interviews, journey mapping, wireframes, prototypes, usability testing, design systems, visual design, and stakeholder review. A useful UX time entry names the client or internal project, the deliverable, the task, the date, the person, and the hours worked. That structure gives a freelancer, agency lead, or in-house manager a practical view of effort without turning design work into vague admin notes.
UX designers often split time across research, design production, meetings, and development handoff. A single label such as "design" hides the difference between a two-hour prototype revision and a moderated usability session. Clear categories also help compare actual time with the project plan, timeline, and budget. For U.S. billing or payroll workflows, use USD for rates and amounts unless the contract or employer process requires another currency.
A strong UX time entry connects hours to the work someone can review later. Use categories such as discover, explore, test, and listen for research work, then add task names for specific artifacts. A useful entry reads like this: "Client portal redesign, usability testing, moderated checkout session notes, 1.5 hours." That line gives enough context for a client invoice, budget review, or project retrospective.
Task-level tracking also supports common UX collaboration patterns. Designers meet with clients or management, work with users, coordinate with development teams, and use tools such as Figma, Jira, and Google Analytics. Time records should follow the place where the work is assigned or reviewed. A Jira ticket can hold implementation support time, while a design-system project can hold component documentation, review cycles, and visual design updates.
UX work mixes client-facing deliverables with internal activity. Billable time usually covers contracted research, design, testing, workshops, and implementation support. Internal time covers portfolio cleanup, team critique, training, reusable templates, or unpaid sales discovery. Mixing those categories makes invoices harder to defend and makes utilization look cleaner than it is.
Freelancers and agencies need this split because 10% of web and digital interface designer jobs were self-employed in 2024, and client billing is a real workflow for part of this group. In-house UX teams need the same separation for capacity planning. A product manager does not need an invoice, but they do need to know whether effort went into planned roadmap work, stakeholder requests, design debt, or research follow-up.
A free one-off tracker is enough when you need a weekly total, a quick client summary, or a simple record of time spent on one UX project. It works for a solo designer logging research, wireframes, prototypes, and review calls before preparing an invoice. The limit appears when several people touch the same client, budget, sprint, or approval cycle.
A managed workflow fits better when UX time needs approval before billing, payroll, or reporting. Everhour Timesheets collect weekly project hours and working hours by person, then let managers approve, reject, partially approve, and lock submitted time. That matters when research, design, and development support all feed the same client budget or when a team needs a stable record before invoices go out.
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.
Track research, wireframing, prototyping, design-system work, visual design, usability testing, stakeholder meetings, and development handoff as separate categories. Those categories match the way UX work is planned and reviewed. Separate entries make it easier to explain an invoice, compare actual effort with a project timeline, and see whether time went into discovery, production, testing, or collaboration.
Project phase gives a clean summary, and task tracking gives better review detail. Use both when possible: the phase shows whether time belonged to discovery, exploration, testing, or listening, while the task identifies the deliverable or session. For example, "test" is the phase, and "mobile checkout usability session notes" is the task.
Usability testing time should include the work the designer actually performs, such as session setup, moderation, note review, analysis, and findings preparation. Unmoderated testing tools may capture session video and metrics such as success rate, task time, and perceived ease of use, but the designer still needs separate time entries for analysis and reporting work.
Covered employers under the FLSA must keep accurate records for non-exempt workers, but federal rules do not require one specific timekeeping system. For employees covered by the FLSA minimum wage or overtime provisions, records must include hours worked each workday and total hours worked each workweek. State rules, contracts, or employer policy can add more requirements.
Weekend UX work alone does not create a federal overtime premium under the FLSA. Unless exempt, covered employees must receive overtime pay for hours worked over 40 in a fixed 168-hour workweek at not less than one and one-half times the regular rate of pay. A state law, contract, or employer policy can create a different result.
Everhour Timesheets collect weekly project hours and working hours by designer, so managers can review UX time before billing, payroll, or reporting. Submitted time can be approved, rejected, partially approved, and locked, which keeps client-facing research, prototype, testing, and design records stable after review.
Everhour can track time inside tools such as Asana, ClickUp, GitHub, Linear, Jira, Monday, Notion, Trello, and Basecamp. UX teams can log time where tasks already live, then use one reporting layer for project hours, budgets, utilization, and billing review.
Use Everhour Timesheets to collect UX project hours, submit weekly time, and lock approved records before billing or payroll review, with Everhour keeping the approval trail organized.
14-day free trial · No credit card · Cancel anytime
