Hours Calculator

Totals and conversions for hours and minutes.

Calculate time

Result
Details

TL;DR

Quick time math for real life: convert minutes ↔ hours, compute totals, and sanity-check your logs. Use it for one-off checks (work logs, meetings, billing) when you don’t want to open a spreadsheet.

Who this is for

  • Contractors preparing invoices and wanting quick “does this total make sense?” checks.
  • Employees tracking hours for internal reporting.
  • Anyone converting “minutes” into human-friendly time (e.g., 450 minutes → 7h 30m).

When to use this vs the other time tools

How to use it

  1. Enter the time values (hours/minutes) in the mode you need.
  2. Read the computed result (often shown both as minutes and as h:m).
  3. Copy the result into your timesheet, invoice, or internal report.

Practical tips (especially for billing)

Decide your rounding rule once

If you bill clients by the hour, rounding is where disputes happen. Agree up front:

  • do you round to 5 minutes, 10 minutes, 15 minutes, or 0.1h?
  • do you round per session or per day?

Then keep the same rule in every invoice to stay consistent.

Rounding examples (quick cheat sheet)

If your rule is “round to 15 minutes”:

  • 7 minutes → 0.25h (15m)
  • 22 minutes → 0.50h (30m)
  • 38 minutes → 0.75h (45m)
  • 52 minutes → 1.00h (60m)

If your rule is “round to 6 minutes” (0.1h):

  • 1–6 minutes → 0.1h
  • 7–12 minutes → 0.2h
  • 13–18 minutes → 0.3h

Whatever you pick, write it into the contract or into an email agreement so both sides share the same expectation.

Keep a simple evidence trail

If you’re ever asked “why is this billed time higher than expected?”, you want a clear story:

  • session times or daily totals
  • breaks and non-billable periods
  • short notes for context Monthly tracking is easier in Monthly time log.

Worked examples

Example 1: meeting duration (quick check)

Compute 09:15 → 10:05 using Time difference, then paste the result into your daily log.

Example 2: daily total from multiple sessions

You worked 2h 20m in the morning and 3h 45m in the afternoon. Use this tool to sum them and get a daily total.

Example 3: convert minutes to hours

Convert “450 minutes” into “7h 30m” for a report or invoice attachment.

Example 4: estimate “billable hours” from tracked minutes

If your tracker exports minutes (common in tools), convert to hours and apply your rounding rule before invoicing.

Edge cases & gotchas

  • Crossing midnight: simple tools can miscount; split the interval into two (before/after midnight) and add.
  • Time zones: treat times as local unless your contract explicitly uses a specific timezone.
  • Daylight saving time: rare, but if you work during the DST change, verify the actual duration.
  • Rounding can change totals noticeably; decide your rule and apply it consistently.

FAQ

Does this replace a timesheet?

No. Use Monthly time log for monthly logs and CSV exports.

What if I need breaks included?

Use Schedule with breaks or track breaks per day in Monthly time log.

Is this “Romania-specific”?

No — it’s pure arithmetic. The Romania-specific part is usually how you bill/round in contracts and how you report time in employment workflows.

What you’ll get (outputs)

  • Conversions between minutes and hours in a format humans can read.
  • Totals you can copy into invoices, weekly reports, or HR timesheets.
  • A consistent way to sanity-check month-end numbers before you hit “send”.

Common mistakes (and how to avoid them)

  • Mixing billable and non-billable time: keep separate totals (or separate rows) so invoices stay defensible.
  • Rounding multiple times: compute first, then round once (ideally per day).
  • Copying totals without notes: add a short context note (feature, incident, meeting) so totals have meaning.
  • Ignoring breaks: if breaks are excluded use Schedule with breaks first.
  • Treating “hours” as “decimal” by accident: 1h 30m is 1.5h (not 1.30h).
  1. Track sessions (start end) → Time difference
  2. Subtract breaks if needed → Schedule with breaks
  3. Sum and convert for billing → Hours total
  4. Export and keep an audit trail → Monthly time log

Copy/paste templates

Daily log (simple)

2025-12-28 — 3h 45m — API integration + review

Weekly roll-up (client status update)

Week 52 — 18h 30m total — Main focus: performance + bugfixes

Next steps (IT Jobs List)

For timeMonthly time logs, consistency beats “granularity”: same rounding rule and the same style of context notes.

Quick recommendation

  • Save your assumptions (rates, breaks, thresholds) so you can reproduce the result.
  • If you use the output in an invoice/offer, include a short explanation (what’s included and what’s not).

Practical checklist (IT Jobs List)

  • Decide: rounding per session or per day (and write the rule down).
  • Track breaks separately if they’re not billable.
  • At month end, export and keep an audit trail.
By Ivo Pereira Last updated: 2025-12-28