TimeRetain Blog

How long does it take to crochet a blanket?

Sun, 11 Oct 2026 00:00:00 GMT

A crochet blanket can take anything from a few evenings to many months. In one Ribblr forum thread, a crocheter says they’ve made blankets that “took a couple of days and some that took several months.” The size, the yarn, the stitch, and your own pace explain most of the difference.

A general answer won’t tell you much about your blanket. Your own answer takes an evening or two to get: crochet a few squares or rows, time them, and multiply.

Why the answers are so far apart

Four things set the time.

Size. A 50 by 60 inch throw has more than twice the area of a 36-inch square baby blanket. A twin bed blanket roughly doubles the throw again.
Yarn and hook. Thicker yarn on a bigger hook covers each inch with fewer stitches.
Stitch. Tall stitches like double crochet (US terms) grow faster than single crochet. Textured stitches, color changes, and motifs slow you down.
You. Your speed, and how many evenings a week you actually pick up the hook.

Then there’s the part that’s easy to forget: joining squares, the border, and weaving in ends. On a blanket made of squares, finishing can add many hours. In the example below, it adds about 17.

Estimate your own blanket

Pick one repeating piece of the blanket. That’s a square for a granny square blanket, or one row for a blanket worked in rows. Then work through these lines.

Crochet blanket time estimate

CSVDownload CSV

Repeating piece (square or row):
Minutes per piece:
Pieces in the blanket:
Joining:
Border:
Weaving in ends:
Total minutes:
Minutes I crochet in a usual week:
Weeks to finish:

Repeating piece (square or row):
Minutes per piece:
Pieces in the blanket:
Joining:
Border:
Weaving in ends:
Total minutes:
Minutes I crochet in a usual week:
Weeks to finish:

Time two or three pieces, not one. The first one is often slower while you learn the pattern, so lean on the later times.

For a blanket in rows, count the rows from your swatch. If 4 inches of fabric has 10 rows, a 60-inch blanket needs about 150. Corner-to-corner blankets are the exception, because the rows change length. Count the small blocks instead, and time a few of those.

You can’t time the joining and border before you get there. Write down a guess and mark it as a guess. When you reach them, time the first strip or round and update the line.

An example: a granny square throw

Here’s an invented example. You want a throw of about 48 by 60 inches, made from 6-inch granny squares.

That’s 8 squares across and 10 down, so 80 squares. You time three of them: 38 minutes, 33 minutes, and 31 minutes. The first was slow while you learned the pattern, so you use 32.

Part	How you get the number	Minutes
Squares	80 squares × 32 minutes	2,560
Weaving in ends	80 squares × 4 minutes	320
Joining squares into strips	10 strips × 24 minutes	240
Joining the strips	9 long seams × 30 minutes	270
Border	3 rounds × about 55 minutes	165
Total		3,555

That’s a little over 59 hours. The squares are only about 72% of it. The other 17 or so hours are the parts that are easy to forget when you buy the yarn.

Now turn hours into weeks. If you crochet about 45 minutes on five evenings a week, that’s 225 minutes a week. At that pace, the whole blanket takes about 16 weeks, or roughly four months.

A twin size version of the same blanket would need 11 squares across and 15 down. That’s 165 squares, a little more than double, and the joining and border grow too.

If the blanket has a deadline

Say you want to give this throw for the holidays and it’s mid-October. Ten weeks is not sixteen weeks, and you can see that before you’ve bought all the yarn.

You have a few honest options. You can make it smaller, since a 36 by 48 inch lap blanket needs 48 squares instead of 80. Scaled down the same way, it comes to roughly 36 hours, which fits ten weeks with little room to spare. You can choose thicker yarn and a bigger hook, which gives bigger squares and fewer of them. Or, if you know the person would enjoy it, you can give it unfinished with a note.

Check again after the first two weeks. At 225 minutes a week and 32 minutes a square, you finish about 7 squares a week. If you’ve done 9 instead of 14, you know early. Changing the size in week three is easy. Changing it in week nine means you’ve already made squares you won’t use.

Keep the real numbers for next time

Your estimate is a guess until you finish. Keep a short note of the actual minutes as you go, like “squares 12 to 14, 95 minutes”. At the end, you’ll know what a throw takes with your hands, your yarn, and your pace.

That’s the number to use when the next blanket comes along. It’s also a good reply when someone asks if you could make one for them. A friend’s blanket of the same size might take half as long or twice as long, so compare your own projects with each other.

If you forget to time an evening, write “about 40” and mark it as an estimate. A total with a few marked estimates is still more useful than no total.

Keep your crochet time in TimeRetain

TimeRetain can hold the time side of the project. Record each session with a short note like “border, round 2”, keep the blanket’s sessions together, and see its total when it’s done. Then your next estimate starts from your real number instead of a guess.

No account is required. With Sync off, your record stays on your device. Optional Sync stores an encrypted copy on TimeRetain’s servers.

Time your next blanket session in TimeRetain.

Start tracking →

Homeschool hours log: track time for each child

Sat, 10 Oct 2026 00:00:00 GMT

If you want or need to track your homeschool hours, write down the date, the child, the subject, what they did, and the minutes. Then total each child’s minutes at the end of the week. Not every homeschool needs an hours log. It helps when someone asks you for hours, or when you want to see how much time each subject actually gets.

Find out who the log is for

Sometimes the log is just for you. You want to see how the week actually went, or whether science keeps getting pushed to Friday and then dropped.

Sometimes someone else will read it, such as a state office, an umbrella school, or an evaluator. Then the log has to fit what they expect, not just what suits you. Their rules, or your agreement with them, can set the format, the subjects, and the totals they need.

Ask them a few things before you start. Which activities count? Do they want hours per subject or per day? And do they want hours and minutes, or decimal hours?

Write their answers on the first page of your log. When you share it, include only what they ask for.

A log kept by child and subject can answer most of those questions later. A single daily total can’t be split back into children or subjects once the week is over.

A homeschool hours log you can copy

Use these fields in a notebook, a spreadsheet, or a plain document. One line is one block of learning for one child, or one shared lesson.

Homeschool hours log

CSVDownload CSV

Date:
Child:
Subject:
What they did:
Minutes:
Note:

Date:
Child:
Subject:
What they did:
Minutes:
Note:

Leave the note empty most days. Use it for the lines you’ll want to explain later: shared, alone, outside class, estimate, or changed.

Here’s a filled line from the example week below:

A filled-in log line

CSVDownload CSV

Date:: Monday, October 5, 2026
Child:: Maya and Leo
Subject:: Science
What they did:: Pond walk, then sketched leaves
Minutes:: 50
Note:: Shared

Date: Monday, October 5, 2026
Child: Maya and Leo
Subject: Science
What they did: Pond walk, then sketched leaves
Minutes: 50
Note: Shared

A worked example: three days, two children

This is an invented week in October 2026, an example of the record’s shape, not a target. Maya is 10 and Leo is 7. One parent teaches both, and Maya also has a piano lesson with an outside teacher.

Date	Child	Subject	What they did	Minutes	Note
Mon, Oct 5	Maya	Math	Adding fractions with a parent	40
Mon, Oct 5	Leo	Reading	Phonics cards with a parent	25
Mon, Oct 5	Maya, Leo	Science	Pond walk, then sketched leaves	50	Shared
Tue, Oct 6	Maya	Writing	First draft of a letter	30	Alone
Tue, Oct 6	Leo	Math	Counting coins game	20
Tue, Oct 6	Maya, Leo	History	Read-aloud about canals	35	Shared
Wed, Oct 7	Maya	Music	Piano lesson	45	Outside class
Wed, Oct 7	Leo	Math	Number line worksheet	15	Changed from 45 (timer ran through snack); alone

Each line says enough to recognize the session months later. “Math” alone wouldn’t tell you whether Leo did 20 minutes of coins or an hour of worksheets.

Log a shared lesson once

On Monday, both children spent 50 minutes on the pond walk. Write it once and put both names on the line.

Whether that walk adds 50 minutes to each child’s total is up to whoever reads your log, or up to you if the log is only yours. In this example, it does. Either way, the line holds what you need: who was there, what they did, and for how long.

The trap is the other direction. Maya’s three days add up to 200 minutes and Leo’s to 145, but you didn’t teach for 345 minutes. The two shared lessons (85 minutes) count in both totals, and 90 minutes happened without you: Maya’s letter and piano, and Leo’s worksheet. Your own teaching time is 170 minutes. Keep it apart from the children’s hours, because it answers a different question.

If your reader wants decimal hours, divide the minutes by 60. Maya’s 200 minutes is 3 hours 20 minutes, or 3.33 hours. Leo’s 145 minutes is 2 hours 25 minutes, or about 2.42 hours. Convert the weekly total, not each line, so small rounding errors don’t pile up.

Work done alone and classes someone else teaches

Maya wrote her letter by herself while Leo played the coin game. Mark lines like that “alone”. You may want them in her hours and out of your own teaching time, and the note lets you do either.

The piano lesson works the same way. Record the length of the lesson itself, not the drive or the waiting room. If the drive matters to you, give it its own line so it never gets mixed in by accident.

Everyday activities are where logs get vague. If Leo counted the change at the store and that was the point, write “counting change at the store, 10 minutes”. The description lets you, or whoever reads the log, decide whether it counts.

Fix mistakes the same week

The easiest log is the one you fill in before the details blur. Write right after each block, or at lunch and at the end of the day.

Leo’s worksheet first showed 45 minutes, because the timer kept running while he had a snack. He finished after 15. Change it to 15 and say so in the note: “Changed from 45 (timer ran through snack).” That note answers the question you’d otherwise ask yourself in June.

Missed days are harder. Say Thursday went by and you wrote nothing down. Look at what’s left: finished pages, a library receipt, photos on your phone. Add the lines you can, and mark the minutes as an estimate. Don’t round a vague memory up to a neat hour to make the week look complete.

If someone else reads your log, ask how they want estimates handled. Some readers will be fine with a marked estimate; others may want you to leave the day out.

Keep your own record with TimeRetain

TimeRetain keeps lesson time in a private record with a short note on each entry. It totals that time by child or by subject when you look back. Your log is there when someone asks for hours, and when you want to see how much time each subject gets.

Keep your own record of homeschool time.

Start tracking →

How to keep a garden journal you can use next year

Sun, 04 Oct 2026 00:00:00 GMT

To keep a garden journal, date your notes, identify the plant and its location, and record what you did or noticed. A notebook or a plain document is enough.

Start with something in your garden today. You don’t need to reconstruct everything you planted before you can write the first entry.

A garden journal entry you can copy

Garden journal entry

CSVDownload CSV

Date, including year:
Plant and variety, if known:
Location:
Work completed:
What I noticed:
Question to return to:

Date, including year:
Plant and variety, if known:
Location:
Work completed:
What I noticed:
Question to return to:

Leave a field empty when it has nothing useful to hold. A visit to look at a plant doesn’t need an invented task to count as an entry.

Here’s a filled entry from an imaginary garden:

Garden journal example

CSVDownload CSV

Date, including year:: May 9, 2026
Plant and variety, if known:: Marigold in planter B; variety not recorded
Location:: Round pot, moved from the back steps to beside the gate
Work completed:: Moved planter B. Planter A stayed by the steps.
What I noticed:: Neither plant has an open flower today.
Question to return to:: Does B open a flower later than A? Check both on the same day.

Date, including year: May 9, 2026
Plant and variety, if known: Marigold in planter B; variety not recorded
Location: Round pot, moved from the back steps to beside the gate
Work completed: Moved planter B. Planter A stayed by the steps.
What I noticed: Neither plant has an open flower today.
Question to return to: Does B open a flower later than A? Check both on the same day.

“Moved the marigold” leaves you guessing which plant went where. This entry keeps the move, its date, and the observation together.

These fields aren’t new. NC State Extension’s garden journaling guide includes plant names, planting dates, observations, and dated maintenance in its plant profiles.

You can start with fewer fields than that handbook covers. Add detail when it answers a question you actually want to ask later. A few additions tend to earn their place by next spring:

Where the plant came from. Keep the plant tag or seed packet, or photograph it. That’s often the only record of the variety.
Weather that affected the garden. A late frost, a storm, or a dry spell can explain entries that would otherwise look strange.
Problems and what you tried. Note the symptom, what you did, and what happened afterward.
Harvests and losses. A rough amount, or a plant that died and when, helps you decide what to grow again.

Follow two planters through a season

Imagine that you buy two marigold plants. You put one in a square planter and the other in a round pot. Neither purchase record identifies the variety.

Call the square planter A and the round pot B in your notes. Here are four invented entries from the same year:

Date	Record
April 26, 2026	Planted the two marigolds. A is the square planter by the back steps. B is the round pot beside it. Varieties not recorded.
May 9, 2026	Moved B beside the gate. A stayed by the back steps. Neither has an open flower today.
May 30, 2026	Looked at both today. A has an open flower; B has buds but no open flower. I didn’t record when the buds appeared.
September 27, 2026	Pulled both plants. Next year: keep the plant tags and write down the date each planter shows its first open flower.

These notes give you more than a list of garden jobs. They show which plant was where when you made each observation.

A photo can add something the words miss. If you take one, label it with the date and planter, or keep it beside that entry. A photo of an unidentified pot is another puzzle for next spring.

The dates are part of the invented example, not a planting calendar or a prediction about flowering.

Keep observations separate from explanations

The May 30 entry says what the gardener saw that day. It doesn’t establish the exact day that A’s flower opened.

It also doesn’t prove that moving B delayed its flowering. The varieties are unknown, and the record doesn’t compare watering, light, or the plants’ condition when purchased.

You don’t need to fill those gaps with a confident guess. Write the question you want to investigate:

B had no open flower when I checked on May 30. Was it a different variety? What else differed between the two plants?

That note preserves the uncertainty. “Marigolds don’t flower by the gate” turns one incomplete comparison into a rule the record cannot support.

Use gardening guidance appropriate to the plant and your conditions when you need to understand a problem. Your journal gives you observations to bring to that question.

Make the old entry easy to find

Choose an arrangement that matches how you’ll look things up.

For the example, one page or document called “Marigold planters, 2026” can hold all four entries. Keep the planter descriptions at the top and add dated notes underneath.

If you have several beds or containers, a page for each area can be easier to use than a separate page for every plant. Include the plant’s name in each note.

In a notebook with many pages, leave an index near the front. “Marigold planters, 2026: page 8” gets you back to the right record. In a digital document, a clear heading or filename serves the same purpose.

Keep location changes in dated entries. If you replace every old mention of “back steps” with “gate,” you lose where B was before the move.

When you replace a plant, name the replacement and its date. The same pot can hold several plants over the years; the pot’s name alone won’t identify them.

Use this year’s notes next spring

Return to the record when you have a decision to make, rather than waiting until you’ve already made it.

Suppose you’re deciding where to put next year’s marigolds. The example tells you that B moved on May 9. It also tells you which planter had an open flower on the one date you checked.

You can put “Compare the two locations more carefully” in next year’s plan. The record doesn’t justify “Never put a marigold beside the gate.”

An end-of-season note makes this easier. Before you clear a bed or empty a pot, write a few lines: what you’d grow again, what you’d change, and which questions are still open. The September entry in the example does that in one sentence. Next spring, read that note first.

Keep future intentions distinct from completed work. “Try a different position next year” is a plan. It becomes a record of a move only when you do it and add the date.

If you missed a month of notes, leave the gap visible. Start again with what you can observe now. You can still use the entries you kept without pretending that they cover the whole season.

A photo or an old note can sometimes supply a missing detail. If it can’t, “not recorded” is more useful than a date you made up.

Add gardening time only if you want it

Your journal can be complete without a timer.

Duration is useful when you want to know how much time you gave to a garden project. For example, an invented week with 25 minutes on Saturday and 15 on Wednesday contains 40 minutes of gardening.

Those minutes describe your work. They don’t measure plant growth, and the days between two journal entries aren’t hands-on gardening time.

A watch and a note can supply the durations. A manual time record is another option. Keep time with the activity so “40 minutes” still tells you what you did.

TimeRetain lets you look back at gardening session durations with short activity notes. Keep the plant observations and longer entries in your garden journal.

Before you put the notebook away, read the entry once. Next spring, will you know which plant it means, where it was, and what you actually saw?

Cleaning schedule for home: a plan that fits

Sat, 03 Oct 2026 00:00:00 GMT

To make a cleaning schedule for home, list your daily jobs, then assign extra jobs to days when you have time. Give each session a specific job and a time allowance. Leave one window free for unfinished work.

Your weekly cleaning plan

Home cleaning schedule

CSVDownload CSV

Week starting:

Daily routine

Extra sessions
Day	Extra work	Time available
Day	Specific job	Minutes

These sessions are in addition to your daily routine. Add a name to jobs you share.

Week starting:

Daily routine:

Extra sessions:
Day — Extra work — Time available
-  —  —
-  —  —
-  —  —
-  —  —

These sessions are in addition to your daily routine. Add a name to jobs you share.

If your week needs more sessions, copy the plan into a document. Write each extra visit on its own line, including separate laundry steps.

Find the time before you fill it

Start with your calendar, not a room-by-room checklist.

Look for time you can reasonably use for cleaning. Perhaps Tuesday has a spare half-hour, Thursday has a short window before you go out, and Saturday has several gaps while you’re at home. Leave already-full evenings alone.

Next, account for the small jobs that return throughout the week: dishes, kitchen surfaces and whatever else your household needs regularly. They use real time, even when you don’t think of them as a cleaning session.

Only then add the larger jobs.

Be specific about what each slot contains. “Kitchen” could mean wiping the counter or spending an afternoon cleaning cupboards. “Wash dishes and wipe food-preparation surfaces” gives you something you can finish.

If you share the work, add a person’s name to each job. “Bathroom on Tuesday” still leaves a decision unresolved if everyone thinks someone else is doing it.

A weekly cleaning schedule with room for catch-up

Here is an invented example for one person in a small home. The times are available work time, not claims about how quickly you should clean. The jobs and frequencies are starting points to change.

When	Planned work	Hands-on time available
Every day	Dishes and food-preparation surfaces	10 minutes a day
Tuesday	Bathroom: toilet, sink, mirror and shower	25 extra minutes
Thursday	Vacuum floors and mop the kitchen	30 extra minutes
Saturday	Sort and load laundry, then hang it to dry	15 extra minutes in separate visits
Saturday	Catch-up time (leave unassigned)	20 extra minutes
Sunday	Fold and put away dry laundry; dust accessible surfaces and empty small bins	30 extra minutes

The daily jobs use 70 minutes across the week. The assigned extra jobs use another 100 minutes. With 20 minutes left open, the weekly budget is 190 minutes: 2 hours 50 minutes assigned, plus 20 minutes of spare capacity.

The daily work still happens on days with an extra session. Tuesday therefore needs 35 minutes in total, not 25.

That Saturday gap is useful precisely because it has no job yet. It can absorb an unfinished task or a small occasional job. If nothing needs it, leave it free rather than finding something to fill it.

This example also assumes the laundry will be dry for Sunday’s finishing session. Machine and drying time need their own check, which the laundry section below covers.

Give each job a finish line

A vague job can grow while you’re doing it.

You start wiping the bathroom sink, notice a drawer needs sorting, then decide to scrub the grout. The original session runs long, but you haven’t necessarily learned that cleaning the bathroom takes longer. You changed the job halfway through.

Give recurring sessions a clear scope. For example:

Bathroom: clean the toilet, sink, mirror and shower. Put the supplies away. Drawer sorting and cupboard cleaning are separate jobs.

You don’t need a detailed procedure for every room. Just make the boundary clear enough to recognize when you’ve finished.

Keep a separate note for things you notice along the way. Unless something needs immediate attention, noticing it doesn’t have to mean doing it now.

This also makes future time estimates more useful. You can compare two ordinary bathroom cleans rather than one quick wipe-down and one accidental deep clean.

Plan laundry as several visits

Laundry is easy to misplace in a schedule. A short amount of work can stretch across much of a day, or into the next one.

The example gives it 30 minutes of hands-on time. Saturday gets 15 minutes for sorting, loading and hanging. Folding and putting away use 15 of Sunday’s minutes. Sunday’s other 15 minutes are for dusting and bins.

Those are separate appointments with the same job. The washing machine finishing is not the laundry finishing.

Before choosing the slots, check the sequence. Will you be around to unload the machine? Will the clothes be dry when you’ve planned to fold them? Will you need any of them sooner?

You can clean something else while a machine runs. But don’t count that waiting period as cleaning work, and don’t assume the next laundry step will fit into whichever gap happens to remain.

In your schedule, note when you need to return. In a time record, count the minutes you’re actually handling the laundry.

When a job runs long, change the plan

Suppose Thursday’s floor session has 30 minutes available, but a couple of ordinary attempts suggest the full job needs closer to 40.

That is useful information. Repeating the same 30-minute plan won’t make the missing time appear.

You could find a genuine 40-minute window, or divide the work into smaller jobs with clear boundaries. For example, clean the kitchen and living-room floors on Thursday, then give the bedrooms their own short slot on another day.

Check that the second session fits, including getting the vacuum out again and putting it away. Splitting a job can add work. If you take that slot from Saturday’s catch-up time, the buffer gets smaller every week, so decide whether what’s left is still enough.

You could also reconsider the scope or frequency where that makes sense for your home. Perhaps every room doesn’t need the same treatment every week.

What matters is making a deliberate choice before next Thursday. “Try to be quicker” isn’t much of a scheduling adjustment.

Measure the uncertain jobs, not every chore

A timer is most useful when it answers a question: does this job fit the window I’ve given it?

Time a few ordinary attempts. Include setup and putting things away. Pause when you leave for something unrelated, and note unusual extras rather than treating them as part of every clean.

If the job varies, plan for a normal slower attempt rather than your fastest one. A schedule with no room for ordinary variation is likely to keep needing repairs.

Have a smaller plan for busy weeks

Decide what you will protect when time gets squeezed.

That might mean keeping up with dishes, food-preparation surfaces, the bathroom jobs you consider essential, and laundry needed for the coming days. Dusting decorative shelves or sorting a cupboard may be easier to postpone.

The priorities depend on your home. The useful part is choosing them before everything feels equally overdue.

For a missed session, look at what remains, not just the unchecked box. Two unwashed loads of laundry are accumulated work. A missed dusting session doesn’t automatically mean you need two separate dusting sessions next week.

Move the actual work into available space. If Saturday’s catch-up slot is already full, something else needs to move, shrink or wait. Don’t turn the buffer into a second, hidden schedule.

The same rule applies to occasional jobs. Cleaning inside a cupboard may deserve a slot, but a 45-minute job won’t fit into a spare 20 minutes. Give it another window or split it at a sensible stopping point.

Use recorded time to make fewer guesses

A watch and a note are enough to check a chore’s duration. A manual timer can make it easier to add up separate stretches without including the pauses.

TimeRetain gives you a record to consult before you squeeze another chore into Thursday evening. Try timing “Vacuum bedrooms” a few times, then compare those entries when you choose next week’s time allowance.

Keep future jobs in your notebook or calendar. Use the recorded times to decide whether those jobs fit.

You don’t need a permanent log of every wiped counter. You need a schedule you can trust, with fewer unfinished chores competing for the same Saturday.

Find out how long your recurring chores take, then give them room in your week.

Start tracking →

What is a reading journal? A simple way to start

Wed, 23 Sep 2026 00:00:00 GMT

A reading journal is a personal record of what you read and your thoughts about it. You can use it for a reaction, a question, or a passage you want to return to.

Reading journal entry

CSVDownload CSV

Date:
Book and author:
Page, chapter, or audio position:
My note:

Date:
Book and author:
Page, chapter, or audio position:
My note:

Start with the book you are reading now. Record its title and author, the page or chapter, and one thing you want to remember. A notebook or a plain document is enough.

A list of finished books is useful when you want to find a title. Add a response when you also want to remember what interested you about it.

A reading journal example

Here is an invented entry. The book, author, and scene are fictional:

Reading journal example

CSVDownload CSV

Date:: September 23
Book and author:: The island timetable, by Lena Marr
Page, chapter, or audio position:: Chapter 4, the empty return crossing
My note:: Mara takes the ferry back for one passenger after complaining that the islanders expect too much of her. I trust what she does more than what she says. Does she see herself that way?

Date: September 23
Book and author: The island timetable, by Lena Marr
Page, chapter, or audio position: Chapter 4, the empty return crossing
My note: Mara takes the ferry back for one passenger after complaining that the islanders expect too much of her. I trust what she does more than what she says. Does she see herself that way?

The entry names something that happened and the reader’s response. It leaves a question open because the reader has not finished the book.

Compare that with “Chapter 4: Mara runs the ferry.” Both notes identify the scene. The longer one also records why it caught this reader’s attention.

You don’t need a response to every chapter. Write when there’s something you want to keep, whether that’s a whole paragraph or one sentence.

Make each entry useful

If you keep one page or document per book, put the title and author at the top once. Add dated notes underneath as you read.

The “My note” field can hold a response like the ferry example, a detail you enjoyed, or a question about an argument.

For nonfiction, an entry can separate the author’s claim from your response. For example, imagine a book recommends choosing one hobby and putting the others aside:

The author recommends concentrating on one hobby. I like switching between drawing and gardening, so I am unsure whether this advice suits what I want from either.

That is an invented response, not a quotation from a book. It records a disagreement that the reader can revisit without turning it into a formal review.

Leave enough detail to find the passage again

A note such as “Loved the conversation near the end” can be hard to use later. Add a location while the book is still open.

For a print book, record the page number. If you return to a different edition, a chapter number and a few words about the scene can help too.

For an ebook, use a page or location number that your reader displays, alongside the chapter. For audio, record the chapter and playback position. Say whether the position refers to that chapter or the whole recording.

For example, record chapter 4 and a position of 12 minutes within that chapter. Add “return crossing” to identify the scene.

If you copy a sentence, put it in quotation marks and keep the location with it. Write your response separately. When you return to the note, you can tell which words belong to the author.

You can also describe the passage in your own words and record its location.

Choose the detail you will use

Add fields when you have a reason to look at them later.

If you want to recommend books to friends, note who a book brings to mind and why. If you enjoy comparing translations, include the translator and edition. If you want a record of when you read a book, add start and finish dates.

A rating is optional. “Four stars” is quick to scan, but a sentence such as “I enjoyed the conversations and lost interest during the journey” explains your response.

Keep unfinished books in the journal if you want to. Write where you stopped and whether you want to return. You can record “Stopped at chapter 6” without deciding what you think of the whole book.

If your opinion changes, date a new note beside the earlier one. For the ferry example, a later entry can explain whether Mara’s choices changed the reader’s view. The first entry still records what the reader thought before reaching that part.

Decoration can be part of the pleasure. Leave space for it if you enjoy it. A plain entry is complete too.

Keep reading time optional

A reading journal can contain no time measurements at all. The entry above works without a duration.

If you want to see how much time reading took, add session lengths or keep a separate time record. For example, 20 minutes on Monday and 35 minutes on Thursday give you 55 minutes of reading.

The total tells you how much time you spent. It says nothing about what you thought of the book; that’s what the notes are for. You don’t need to turn either into a target for next week.

A manual timer can record sessions while you read. TimeRetain keeps those sessions and their total under a short label, such as the book’s title. Keep your responses in your journal.

How to log volunteer hours for your own records

Tue, 22 Sep 2026 00:00:00 GMT

To log volunteer hours, record the date, organization, activity, and actual start and stop times. Note breaks separately, then calculate the duration.

You can keep this record for yourself, even when nobody asks for it. If you need to submit hours, check the receiving organization’s requirements first. Your own log supplies the details; acceptance depends on its process.

Check where the hours need to go

If an organization already gives you a form or portal, use it. A second record is useful when you want your own copy or volunteer in several places.

Before the first session, ask which activities count, how to submit them, who must confirm them, and when they’re due. Check travel, training, and breaks if those affect your record.

For example, Shoreline Community College asks service-learning students to bring its time log so a site supervisor can confirm their service.

Keep the instructions for your program beside the log. If you only want a personal total, you can skip submission details.

A volunteer hours log you can copy

Copy these headings into a spreadsheet, or use them as labels in a notebook. Keep the organization on each row if you help in more than one place.

This is an invented example. The two organizations in it ask for active volunteer time, with breaks excluded. The entries below have been checked and corrected.

Date	Organization and activity	Start	Stop	Break	Time
Sep 14, 2026	Pantry: sorted donated food	09:10	11:05	15 min	1 h 40 min
Sep 16, 2026	Library: prepared book-sale tables	18:00	19:20	None	1 h 20 min
Sep 19, 2026	Pantry: packed collection bags	10:00	11:35	None	1 h 35 min

The first visit spans 115 minutes. Subtracting the 15-minute break gives 100 minutes, or 1 hour 40 minutes of active time.

For September 14–19, the pantry total is 3 hours 15 minutes. The library total is 1 hour 20 minutes. Together, that is 4 hours 35 minutes.

Keep those organization totals available separately. The library doesn’t need the pantry entries when it asks for your hours.

“Prepared book-sale tables” is enough detail to identify the activity. Leave out names or personal information about the people you helped. If the program requires a supervisor’s details, keep them in its designated fields.

Record the visit you completed

Write the start time when you begin and the stop time when you finish. You can use a watch, a phone note, or a manual timer.

A shift scheduled until noon may finish at eleven. Enter when you actually stopped. Keep any difference between time spent and hours credited visible instead of changing your times to match the schedule.

For a break, record its length or stop and restart the timer. Don’t subtract it twice. In the example, the 15-minute break is inside the start-to-stop span, so it is subtracted once.

If you also want to know how much of your day volunteering takes, record travel separately. That lets you see your personal commitment without assuming the program accepts travel as service time.

Correct a mistaken entry before adding it up

Suppose the library row originally ended at 19:40 because you forgot to stop the timer. The coordinator confirms that you finished at 19:20.

Correct the stop time and leave a short note explaining the change:

September 16 library entry: stop changed from 19:40 to 19:20 on September 17. Finished setup at 19:20; confirmed with coordinator.

That removes 20 minutes. The library entry becomes 1 hour 20 minutes, and the combined total becomes 4 hours 35 minutes, as shown above.

If you’ve already submitted the longer entry, ask how to correct that submission too. Editing your own copy doesn’t update the organization’s record.

For a missing entry, check any attendance record and ask the person who was there. Mark uncertain times as estimates in your notes. Resolve them through the program’s process before presenting them as confirmed hours.

Prepare only the hours being requested

When it’s time to submit, select the organization and reporting dates first. Then check each included entry for missing stop times, duplicate visits, and corrections.

For the example above, a pantry report covering September 14–19 contains two entries totaling 3 hours 15 minutes. The combined 4-hour-35-minute total belongs in your personal overview.

Match the form’s units. Three hours and 15 minutes is 3.25 decimal hours, because 15 ÷ 60 = 0.25. Writing 3.15 would mean 3 hours and 9 minutes.

Some durations don’t convert cleanly. The first pantry visit, 1 hour 40 minutes, is 1.666… decimal hours. If the form asks for decimals, check whether it wants 1.67, quarter hours, or something else before you round.

Copy the entries into the required form or portal, and get any required confirmation. Keep a copy of what you submitted and its submission date. If approval is required, distinguish submitted hours from approved hours in your notes.

Keep your own record with TimeRetain

TimeRetain helps you see how much time you give to each organization. Keep pantry visits and library shifts in one personal record, with a short note to remind you what you did.

You have your own record to look back on, whether you need it for a submission or just want to see your contribution.

Keep your own record of volunteer time.

Start tracking →

Writing log: remember edits and what to write next

Sun, 20 Sep 2026 00:00:00 GMT

A writing log is a short, dated record of what you tried, what you decided, and where to start next time.

Writing log

CSVDownload CSV

Date / project / section:
Changed or tried:
Why / still unsure:
Start here next time:

Date / project / section:
Changed or tried:
Why / still unsure:
Start here next time:

Keep a note beside your draft

Keep the log in a separate document or a notebook beside your draft.

Your draft contains the words you kept. It may not tell you why you deleted a scene, whether you meant to check a claim, or which of two endings you preferred.

Those details seem obvious when you close the document. A week later, you can spend part of a writing session trying to recover them.

A useful log gives you something more specific to return to than “continue working on the draft.” You don’t need to account for every minute or describe everything you did. Leave enough information to pick up the work.

Here’s an invented entry for an essay:

A filled-in writing log

CSVDownload CSV

Date / project / section:: 20 September / Housing essay / Opening
Changed or tried:: Moved the renter's example before the statistics.
Why / still unsure:: The numbers mean more once the reader knows her situation. The introduction may now be too long.
Start here next time:: Read the first three paragraphs without paragraph two. Does anything important disappear?

Date / project / section: 20 September / Housing essay / Opening
Changed or tried: Moved the renter's example before the statistics.
Why / still unsure: The numbers mean more once the reader knows her situation. The introduction may now be too long.
Start here next time: Read the first three paragraphs without paragraph two. Does anything important disappear?

The last line is worth including. It gives you an action you can take before you’ve fully found your way back into the piece.

For a shorter session, collapse the entry into a couple of sentences:

Moved the renter’s example ahead of the statistics. Next: try cutting paragraph two and check whether the introduction still makes sense.

You don’t need to repeat the project name when there’s only one project. You don’t need an entry for days you didn’t write.

Record the decision, not just the task

“Edited chapter two” tells you where you worked. It gives you very little to return to.

“Moved the confession before the train leaves, so the departure becomes a choice” records a decision you can judge when you reread the scene.

That doesn’t mean every entry needs a confident explanation. Uncertainty is useful when you identify what you’re uncertain about:

The argument sounds false. Both characters explain the family history, but neither seems to be trying to get anything from the other.

Now you have something to examine. “Fix the dialogue” would leave you with almost the whole problem to solve again.

Abandoned attempts belong in the log too. If you spent a session trying a different narrator and then reverted to the original, write down what you learned. The manuscript may look unchanged even though you’ve ruled something out.

One story, three writing log entries

Here is an invented example from a short story called The spare key. Ada visits her sister after a long absence and discovers that her key no longer fits.

Notice how each entry leaves something for the next session to pick up.

September 14: opening, draft 03

Wrote Ada arriving at the house. Started with the argument that kept her away all summer, then brought her to the locked door. I’m explaining the relationship before anything happens.

Next: make Ada try the key in the first paragraph. See how much of the argument the scene still needs.

September 16: opening, draft 04

Moved the key to the first paragraph and cut 180 words of family history. Kept the old opening in draft 03. I prefer discovering the problem before learning why Ada hasn’t visited.

Next: get her inside. Try a neighbor who has another key.

September 19: opening, draft 05

Tried the neighbor. Getting Ada inside was easy, but the conversation explained where her sister had gone and removed the question I wanted to keep open. Deleted the exchange.

Next: try the kitchen window instead. Write only as far as Ada getting into the house; leave the discovery inside for later.

The third session didn’t produce a scene the writer kept. It still produced a useful finding: the neighbor solved one problem by creating another.

Without the note, the writer might return a month later and try the same conversation again. With it, they can either test another route or deliberately reconsider the neighbor.

The log doesn’t establish that either choice is good. That still depends on the story.

Make the next step small enough to begin

“Finish the chapter” may be your goal, but it doesn’t tell you how to start.

A more useful handover names a passage and an action. Cut a paragraph, check a source, write an alternative exchange, or compare two versions of the ending.

When you’re stuck, leave yourself an experiment rather than demanding a solution:

Write the argument without either character mentioning last summer.

You haven’t committed to keeping the result. You’ve given yourself a way to investigate the problem.

And when a draft is ready to rest, say so:

Full draft finished. Leave it until Sunday, then read it through without editing. Note where the middle loses momentum.

There doesn’t always need to be another sentence to write.

Add word counts and time when they answer a question

You can keep a writing log without measuring anything.

If you’re interested in how the manuscript is growing, record its length before and after a session:

Manuscript: 2,400 → 2,700 words

That’s a net increase of 300 words, not necessarily 300 words written. You might have deleted and replaced a substantial passage.

When the total looks odd, read the note beside it before you treat the number as the result. “Cut 180 words” records a reduction. “Cut the family history so Ada reaches the locked door sooner” tells you what the reduction was meant to achieve.

Duration is optional too. Record whether the session was drafting, research, or revision if you want to compare those times. The duration won’t tell you whether a scene works.

For a digital option, TimeRetain lets you track session time and add a short description. Keep longer writing log entries beside your draft.

Use the log when you reopen the draft

Read the latest entry alongside the passage it refers to. Is the open question still relevant? Does the proposed next step still make sense?

You can disagree with your earlier self. Keep the old entry and add the new decision rather than rewriting the history:

Brought back the neighbor, but rewrote the exchange. The neighbor gives Ada the key without knowing where her sister went.

For changes you might reverse, save the earlier draft and mention its filename in the log. A note explaining a cut cannot recover the deleted text. Likewise, keep detailed research in your research notes and leave a reference to it when needed.

Start with the draft you’re working on now. There’s no need to reconstruct its entire history.

Before you close it, write down what changed and the first thing you could try when you return.

Music practice journal: see your playing time

Tue, 08 Sep 2026 00:00:00 GMT

A music practice journal can show how much time you spend with your instrument. Record each session’s duration and a few words about the activity. At the end of the week, you have an answer to “How much did I play?”

Music practice entry

CSVDownload CSV

Date:
Duration:
Activity:

Date:
Duration:
Activity:

Start with one entry per session

Ten minutes on the guitar while dinner cooks can be easy to forget. So can a short session after work. A personal log includes those moments alongside the Saturday afternoon when you had plenty of time.

You might be learning an instrument, returning to an old hobby, or playing songs you already love. All of that time can belong in your record.

The activity can be as short as “guitar after work” or “playing duets.” Add more detail if you want it, but a session doesn’t need a written review before you can count it.

For example:

A filled-in practice entry

CSVDownload CSV

Date:: August 18
Duration:: 20 minutes
Activity:: Guitar after dinner, mostly familiar songs

Date: August 18
Duration: 20 minutes
Activity: Guitar after dinner, mostly familiar songs

If you use a timer, start it when you begin playing and stop it when you finish. With a paper journal, you can write down the duration from a separate timer.

See how the smaller sessions add up

Here’s a made-up week of guitar playing:

Date	Activity	Duration
August 18	Familiar songs after dinner	20 minutes
August 20	Trying different strumming patterns	15 minutes
August 23	Playing with a friend	25 minutes
Total		60 minutes

No session lasted an hour, but together they added up to one. The record makes that hour visible without requiring a long session on any particular day.

A monthly total can answer the same question over a longer period. Suppose you spent six hours making music during a busy month. You can keep that record without setting a target for the next one.

Choose what your total includes

For a personal journal, you decide what counts as music time. You might include only time with the instrument in your hands. You might also want to include singing or playing with other people.

Use a short activity label when the difference matters to you. For example, keep “guitar” and “singing” separate if you want to see how much time went to each. If you only want one total for making music, a single category is enough.

Labels can also answer a question the total can’t. If you’re learning a new piece, keep it apart from “familiar songs.” After a few weeks, you can see whether the new piece is getting time or whether most evenings go to songs you already know. Neither answer is wrong, but it can help you decide what to play next.

Long interruptions need a little care. Suppose you play for 15 minutes, spend 30 minutes on a phone call, then play for another 10 minutes. That is 25 minutes of playing during 55 minutes of elapsed time. Stopping the timer for the call keeps the playing total accurate.

If you forget to time a session, mark an estimate as “about 20 minutes.” Leave the duration empty when you cannot make a useful estimate. Treat totals that include estimates as approximate.

Keep the record personal

Your journal doesn’t need to rank sessions or compare you with anyone else. An evening spent playing familiar songs can be worth recording because you enjoyed it.

The minutes tell you how long you played. They do not tell you how good the music sounded or how much you learned. You can have a satisfying short session and a frustrating long one; both still have a place in the total.

If you don’t play for a week, there’s no missing entry to complete. Record the next session when it happens.

Track your music time with TimeRetain

With TimeRetain, you can see a week’s playing time without adding up each session by hand. Ten-minute sessions count toward the same total as a long Saturday afternoon.

Keep your music sessions together, with a short description such as “guitar after dinner” to remind you what you played. Separate totals for guitar and singing can show how you divide your music time.

The same record can hold your other hobbies, with separate totals for music and drawing.

No account is required. With Sync off, your record stays on your device. Optional Sync stores an encrypted copy on TimeRetain’s servers.

Record your next music session in TimeRetain.

Start tracking →

Hourly billing: guide to tracking client hours

Thu, 03 Sep 2026 00:00:00 GMT

Hourly billing charges a client for the real time you spend on their work at an agreed rate. If the scope grows, the client pays for the extra hours they approve, within any agreed cap.

Track your billable hours, apply any agreed rounding, multiply by your rate, and send an invoice. The number alone doesn’t explain a longer-than-expected task or a line labeled “research.” That’s where clear notes and updates help.

Flat fee vs hourly billing

Picking between a flat fee and an hourly rate depends on who takes the risk of unexpected work.

A flat fee sets one fixed price for a defined deliverable. For example, a $3,000 design finished in ten hours brings in $300 per hour before business costs. Flat fees work well when the job is clear and you’ve done similar work often enough to estimate it well. If extra revisions stay within that fee, your revenue per hour drops.

Hourly billing moves the cost of approved extra work to the client. It fits work where needs change as you go:

Advisory and consulting: Technical guidance, code reviews, or advice calls without a fixed deliverable.
Discovery work: Initial research and audits done before anyone can estimate project scope.
Maintenance and fixes: Bug fixes, server updates, and repairs where diagnosis time varies.
Work with external delays: Projects where approvals, feedback, and client assets create extra coordination or revisions. Waiting alone does not add billable work hours.

Track fixed-fee work if you want to review what the job paid for your time. Once it is complete, divide the fee by all project hours and compare that figure with your target rate. The guide on billable vs non-billable hours explains how to track both parts of your week.

How to calculate your hourly billing rate

You could build an annual revenue target from the income you want, expected business costs, and a reserve that fits your situation. Divide it by the client hours you expect to bill. Exclude time off and time spent on sales, invoicing, and other non-billable work.

In a hypothetical example, $120,000 of planned revenue over 1,000 billable hours gives $120 per hour. That’s the rate that meets your target only if you bill all 1,000 hours. At 800 billed hours, the same rate brings in $96,000.

The result is a floor for your own numbers, not a market price. You could compare it with what clients pay for similar work before you quote it. The freelance rate calculator helps you explore how your target changes with costs and available hours.

Billing increments and the hourly billing chart

Timers record minutes and seconds, while invoices may use decimal or rounded hours. Divide minutes by 60 for decimal hours. An agreed increment is needed only when you round invoice hours.

Keep stored hours exact. Round a copy for the invoice, not the minutes in the tracker.

Two example increments:

Tenths of an hour (6-minute blocks): Each 6-minute block equals 0.1 hours. Under ceiling rounding, which always rounds up, a 14-minute call rounds up to 18 minutes (0.3 hours).
Quarter hours (15-minute blocks): Each 15-minute block equals 0.25 hours. Under ceiling rounding, an 8-minute review rounds up to 15 minutes (0.25 hours).

Here is a ceiling rounding chart for client invoices. It rounds minutes up to the next billable block:

Minutes	Tenths (0.1h)	Quarter hours (0.25h)
1–6	0.1	0.25
7–12	0.2	0.25
13–15	0.3	0.25
16–18	0.3	0.50
19–24	0.4	0.50
25–30	0.5	0.50
31–36	0.6	0.75
37–42	0.7	0.75
43–45	0.8	0.75
46–48	0.8	1.00
49–54	0.9	1.00
55–60	1.0	1.00

The rows split at 15, 30, and 45 minutes so both columns fit in one table. That’s why 13–15 and 16–18 minutes both show 0.3 hours in the tenths column. To convert minutes by hand, divide by 60 (15 / 60 = 0.25 hours, not 0.15). 15 minutes on a timesheet does that conversion.

Rounding every small task up on its own can add much more billable time than rounding their total. If you round three separate 2-minute emails up to 15 minutes each, the client pays for 45 minutes after 6 minutes of work. If your client agrees to round a daily total, group related tasks before rounding that total.

Apply the increment once. Do not round each entry and then round the daily total again.

Before work starts, you could agree with the client on the increment, rounding direction, and whether you round each entry or the daily total.

Timesheet rounding compares rounding durations with rounding start and end times.

How to make hourly invoices easier to explain

An agreed rate tells the client the price per hour. It doesn’t explain why a task took longer than expected.

These habits explain the work behind the total and give the client a chance to approve extra hours:

1. Agree on estimates and hour caps

Give your client an estimated hour range before starting work. For ongoing work, you could set a weekly cap (for example, “up to 15 hours per week without prior written approval”).

2. Warn clients before hitting limits

Do not surprise a client with a monthly bill that doubles your estimate. If unexpected system bugs or extra revisions push a 10-hour task toward 14 hours, tell the client at hour eight. Explain what slowed down the work and let them decide whether to approve extra hours or reduce scope.

3. Write outcome-based notes

Write each entry for someone who wasn’t in the room. Name what you finished, or explain your progress if the task is still open.

Weak note: “Research and coding (3.5h)”
Strong note: “Added failed-payment alerts and tested the retry flow (3.5h)”

Use terms your client recognizes.

4. Keep rework visible

Keep unplanned fixes separate from the testing and review you expected to do. That gives you a clear record when you decide what to include on an invoice and what to discuss with the client.

5. Invoice on a regular schedule

You could agree on a billing schedule, such as weekly or every two weeks. Each invoice gives the client a chance to query recent work before the project ends. For new clients, discuss a deposit or prepaid hours if you want to reduce work done before payment.

Where TimeRetain fits

TimeRetain helps you keep each client’s hours and work notes together, so you have more than a total to explain on invoice day. Keep unpaid rework in that client’s record too, even when you leave it off the invoice. You still need to know how much time the job took.

Your primary record stays on your device. Optional Sync stores an encrypted copy on TimeRetain’s servers.

If the week is already in a spreadsheet, the billable hours calculator totals those rows.

Keep a record you can explain on invoice day. Try TimeRetain with your next client task.

Start tracking →

Time tracking in project management

Wed, 02 Sep 2026 00:00:00 GMT

Time tracking in project management puts actual hours beside the plan. Compare them with remaining work to spot phases that need another look.

This guide is for a solo lead or contractor watching their own project hours. It isn’t a method for collecting other people’s timesheets.

If a phase has used most of its hours with half the work left, review what remains. Decide whether the estimate or the work needs to change.

Why project management needs real hours

A project plan can have neat phases, clear checkpoints, and assigned deliverables. Without recorded hours, you can’t compare each phase’s estimate with the time spent.

You compare planned hours with actual hours. The tracker supplies the hours you logged. The estimate lives in the plan or a sheet.

Overrun can mean scope creep, a weak estimate, or slow work. Do not treat every overrun as creep.

Unplanned client requests can look small in email threads. Extra revisions still consume remaining hours. The unused time in the plan is its current planned total minus the hours logged. That is a budget, not an estimate of how much work remains.

Past hours give you a starting point for similar projects. If discovery took ten hours on each of three comparable jobs, use that history when estimating the next one. Adjust for differences in scope and complexity.

Project time tracking is the daily habit of recording work sessions as they happen. A timesheet is usually the summarized table or export you review at the end of a week, a checkpoint, or a billing cycle.

The minimum project time entry

An effective project time entry needs five elements:

Field	Purpose
Date	When the work session occurred
Start and stop	Real boundaries. Mark a reconstructed block as an estimate.
Project	Which project the work belongs to
Phase or category	The phase of work, such as design, review, or testing
Note	The work done, its result, or what remains unfinished

A useful note names the result rather than the generic activity. Writing “Client call” tells you little when hours run over. Writing “Phase 2 scope review and feedback call” identifies the discussion.

Here is an example project log during an active delivery week:

Date	Start	End	Project	Phase	Note	Total
Sep 2	09:00	10:30	Client Portal	Discovery	Audited legacy database schema and export paths	1h 30m
Sep 2	10:45	12:15	Client Portal	Design	Drafted account settings and dashboard wireframes	1h 30m
Sep 2	13:15	15:00	Mobile App	Testing	QA testing on authentication flow and error cards	1h 45m
Sep 2	15:30	16:30	Internal	Proposals	Scoped architecture hours for upcoming pitch	1h 00m

If Client Portal and Mobile App belong to one client, keep both projects under that client. You can review each job separately or see the time you spent across both.

If you bill by the hour, distinguish billable from non-billable hours. Client work you choose not to bill still belongs in that client’s total, so the project review sees every hour it took. Keep your own proposals and business admin separate.

How to structure project time tracking

Track time by phase, not by every task minute. A milestone is a check in the plan, not another place to log hours.

1. Keep a separate total for each project

Keep each project’s hours separate so you can compare them with its estimate. A combined client total alone won’t tell you which job needs another look.

A project total shows time spent, not time still needed. Only your review of the unfinished work tells you that.

2. Group hours by phase

Within each project, label entries by the phase of work. For example, a web project might use Discovery, Design, Development, and Testing. Reuse labels on similar projects when they mean the same work. Internal proposals need a different label, as in the sample log.

When the project reaches a checkpoint, look at the hours for each phase. Compare them to the phase hours in your estimate.

If you planned six hours for design and used all six, look at what remains. If design is finished, six hours is a useful figure for the next estimate. If it still needs another review round, decide now whether that round fits the plan.

3. Review logged hours against the plan weekly

Schedule a ten-minute review at the end of each week. Compare the hours in the tracker with the planned hours you are working to. Keep the original estimate only if the plan has not changed.

If a phase planned for twenty hours already has eighteen hours logged, and half the work is left, review the remaining work now.

Source	Hours
Planned, in the scope sheet	20h
Logged, from the tracker	18h

If the second half goes at the same pace, it needs about another eighteen hours. The phase would land near thirty-six hours against a plan of twenty. That’s a rough projection, not a forecast, but it tells you the gap is worth discussing now rather than at hour twenty.

Eighteen of twenty hours with half the work left isn’t always creep. The estimate may have been light, or the work may be slower than you expected. Label hours for added requests as Extra when you log them. Then the review can show how much of the overrun came from new work.

For client work, discuss added requests or a revised estimate with the client. For internal work, involve whoever owns the plan. If the decision is yours, decide whether to allow more time, reduce the remaining work, or keep the plan, and write down the new planned hours before you continue.

An overrun alone isn’t a reason to cut scope or stop.

Start the timer when the block begins

Trying to rebuild Tuesday on Friday leaves you estimating session boundaries. A short delay or extra revision can disappear into one vague block.

Start a timer when a work block begins. Stop it when you switch to another project or phase.

Capturing the start and stop as they happen preserves those boundaries. If you miss a timer, use notes and calendar events to reconstruct the session that day, and mark it as an estimate.

Group small tasks for the same project when you only need its total. Keep work for another client separate, even when the reply is brief.

A 25-minute inbox pass is a real session. So is a three-hour build.

Keep the log private

For this personal log, you need the project, phase, and hours. You don’t need keystroke counts, mouse movements, or screenshots to compare those hours with your plan.

A plain log of intentional work blocks gives you the numbers you need. What is time tracking draws the same line: record hours, do not monitor people.

This log is yours. It is not a staff timesheet, an approval queue, or a utilization report.

Where TimeRetain fits

TimeRetain helps a solo lead keep a record of where project hours went. You can see how much time went to discovery, design, and testing. At your weekly review, compare those hours with the plan and decide what needs another look.

It works without an account. Your primary record stays on your device. Optional Sync stores an encrypted copy on TimeRetain’s servers.

You can use that record alongside the project plan you already keep.

TimeRetain does not collect other people’s hours. It does not take screenshots.

Bring recorded hours to your next project review. Start with your next work block.

Start tracking →

What is time tracking? How to track work hours

Fri, 21 Aug 2026 00:00:00 GMT

Time tracking is recording when work starts, when it ends, and what you worked on.

That’s the whole idea. You can track time with a physical notebook, a spreadsheet, a stopwatch, or an app. The tool you choose is secondary to the record itself: a list of work blocks with real timestamps and clear notes.

What a time entry includes

A useful time entry records:

Date: when the session took place.
Start and stop times: the real boundaries of the work block.
Project or client: who the work was for or which project it moved forward.
Tag: the kind of work, such as Writing or Admin. Optional, but useful for comparing the same activity across projects.
Note: what you did during that block.

Here’s a hypothetical day in a clean log:

Date	Start	End	Project	Tag	Note	Total
Aug 21	09:00	10:30	Client A	Design	Drafted wireframes for checkout flow	1h 30m
Aug 21	10:45	12:00	Internal	Admin	Cleared inbox and processed vendor receipts	1h 15m
Aug 21	13:00	14:45	Client B	Development	Fixed database migration script	1h 45m
Aug 21	15:00	16:00	Internal	Writing	Wrote draft for new blog post	1h 00m

The gap from 12:00 to 13:00 is lunch. A private log can leave that gap.

If you bill clients by the hour, add separate columns for billable status and hourly rate. Keep non-billable client work in that client’s total, but leave it off the invoice. Still log unpaid admin. If you only want to watch your own hours, keep the table plain.

A descriptive note makes the entry useful two weeks later. Writing “Work” or “Client A” leaves the task unclear when an invoice is questioned. “Drafted wireframes for checkout flow” tells the reader what the session covered.

How people track time

Here are three ways to build that record.

1. Manual time tracking

You start a timer when you sit down to work. Stop it when you switch tasks or leave for a meal. You can also write the start and stop times by hand on paper or in a document.

With manual time tracking, you choose the label and mark the start and stop. A clear note tells you what the block represents later. If you forget to start or stop the timer, you’ll need to correct the entry.

2. Automatic time tracking

Automatic time tracking builds a log from computer activity, such as active windows and open applications. Before using a tool, check what it records, whether it takes screenshots, and where it stores that data.

An open editor tab isn’t proof of focused coding. A window title can identify the client, but a generic browser tab can leave that unclear.

If the log doesn’t identify the work, you’ll need to add that context before using it for billing or estimates. Automatic time tracking needs your judgment when the activity record leaves the task unclear.

3. Retrospective timesheets

You don’t time each block. After the work, you fill in a timesheet from memory, calendar invites, and sent emails.

The trouble starts when those clues leave gaps. Suppose a difficult 35-minute call feels like two hours, while scattered admin work leaves no calendar entry. You’d need another record to recover the actual durations.

Why track your time?

People track time for different reasons depending on their role.

For freelancers and consultants

Tracking billable hours gives you dated work blocks to refer to when a client asks about an invoice item. It shows unpaid admin, marketing, and proposal writing only if you also log those blocks.

For project pricing and estimates

For a completed fixed-fee project, divide the fee by all the hours you spent on the job. Suppose a 1,000-dollar project takes 10 hours: that’s 100 dollars an hour before expenses. If added work pushes it to 40 hours, that falls to 25 dollars an hour before expenses.

Compare tracked time with the original estimate to spot an overrun. Ask whether the work grew, the estimate was low, or a task took longer than expected. If you control the next quote, you could allow time for those tasks and include your costs when you set the fee.

For salaried employees

Salaried workers don’t invoice by the hour, but a private work record serves practical needs:

Workload evidence: a log can show how much time went to meetings and support tickets. Those hours give you something concrete to discuss when priorities compete.
Performance reviews: a dated list of completed work can support talking points you already have. Hours alone don’t show the quality of the work. This log is yours, not a manager dashboard.
Weekly hours: suppose a planned 40-hour week turns into 55 hours. Use that record to discuss which tasks fit the available time.

Keep the log private and choose which details to share in those conversations. Recording hours alone doesn’t reduce the workload. The log isn’t a substitute for payroll.

For a short time audit

You don’t have to track time forever. A three-day time audit shows how you spent the hours you recorded. Five workdays let you compare Monday with Friday, though one week won’t capture every pattern.

Suppose the log shows that inbox work fills the morning you wanted for a project. If you control when you answer nonurgent messages, move them to a later block and see whether the project gets that time. If nothing needs a closer look, stop tracking after the audit.

What is a time tracker?

A time tracker records work while it happens. It saves you typing each start and stop time, and keeps the hours beside your work notes.

A spreadsheet works as a log if you prefer to write the times yourself. Choose the method that takes the least attention while leaving a record you can use.

How to start tracking time

Try a small routine for one week:

Choose one question. Start with something you want to understand, such as how much time one client takes.
Record work blocks. Note the start, stop, and what you did. Keep breaks out of working time.
Tidy notes the same day. Replace vague labels while you still remember the work.
Use the record. Compare the hours with your plan and decide what, if anything, to change next week.

Where TimeRetain fits

TimeRetain is a manual timer for keeping a record you can read at the end of the week. See how long each client or project took, with notes that explain what you did.

There’s no account to create. The primary record stays on your device. If you enable Sync, an encrypted copy is stored on TimeRetain’s servers.

Track your next work block and keep a note you can use later.

Start tracking →

Time audit worksheet you can fill in privately

Wed, 19 Aug 2026 00:00:00 GMT

Copy the worksheet below into a note, or download the CSV. Write start when you begin, and write end when you stop or pause. When you begin again, use a new row.

Time audit worksheet

CSVDownload CSV

Day 1:
Date:
Log:: [start] | [end] | [note]
[start] | [end] | [note]
[start] | [end] | [note]
[start] | [end] | [note]
[start] | [end] | [note]
[start] | [end] | [note]
Day 2:
Date:
Log:: [start] | [end] | [note]
[start] | [end] | [note]
[start] | [end] | [note]
[start] | [end] | [note]
[start] | [end] | [note]
[start] | [end] | [note]
Day 3:
Date:
Log:: [start] | [end] | [note]
[start] | [end] | [note]
[start] | [end] | [note]
[start] | [end] | [note]
[start] | [end] | [note]
[start] | [end] | [note]
Review:
Where the hours went:
What surprised you:
Hours vs value:
Keep watching:
Let go:

Day 1:
Date:

Log:
-
-
-
-
-
-

Day 2:
Date:

Log:
-
-
-
-
-
-

Day 3:
Date:

Log:
-
-
-
-
-
-

Review:
Where the hours went:

What surprised you:

Hours vs value:

Keep watching:
-
-

Let go:
-
-

This page shows how to fill that worksheet. For the method, see what a time audit is. It isn’t a timesheet to submit.

What’s on the worksheet

The log has three tables, one per day, with start, end, and note. One row each time you begin. Rough times are fine.

Choose days that represent the routine you want to examine. If you are looking at travel time, log the trip. Three days are a snapshot. Three weekdays won’t show a weekend, and three days may not show a reliable Monday-versus-Friday pattern.

The review covers where the hours went, what surprised you, hours vs value. Under that, two lists: keep watching, and let go.

There’s no rate column or client field. The rows follow your activity changes rather than a half-hour grid.

How to fill each line

When you begin, write the start time. When you stop or pause, write the end. When you begin again, use a new row.

Start and end. Use the time you would tell a friend. 09:10 to 09:55 is close enough.
Note. Name the work. “Inbox and Slack” tells you something; “Busy” doesn’t. A few words beat a blank.

Write the times at each switch. If you keep forgetting, try a reminder at a natural break; change its timing if it interrupts your work. If you estimate a missed block later, mark it as approximate.

Leave unused rows blank. A blank row does not need a task to fill it. If a busy day needs more than six rows, add more.

A filled day

A made-up sample day:

Start	End	Note
09:10	09:55	Inbox and Slack, reactive
09:55	11:20	First pass on the proposal
11:20	12:00	Weekly catch-up, ran long
13:00	13:40	Receipts and calendar cleanup

Inbox took the first 45 minutes. The proposal gets 85 minutes, from 09:55 to 11:20. The weekly catch-up fills the last 40 minutes before noon.

The gap after 12:00 is a pause. The next row starts when work begins again.

Keep the notes for yourself, including blunt ones like “ran long.”

After three days, fill the review

Fill the review after you have three days of rows.

Before you reread the days, use a separate note to guess where you think the hours went.

Read the days once and add up rough minutes for each kind of note. Write:

Where the hours went. Which kind of work took the most clock time. One sentence.
What surprised you. Where the rows differ from your guess, or a block that felt short and wasn’t.
Hours vs value. The work that ate the day, next to the work that actually moved something.

Then split what you found. Keep watching is for a habit you’re changing, or hours you have to report. Let go is for the rest.

Choose one change within your control. If messages kept interrupting a project, try a separate block for nonurgent replies and see whether the project gets more time. If you cannot move those demands, use the notes to discuss priorities with whoever sets them.

A daily work log answers a different question: what finished, and what got in the way. Fill that at the end of the day if you want a handoff to tomorrow-you. Keep longer reflections separate so the time entries stay easy to scan.

Keep the file on your own device

Save the finished worksheet on your device. Don’t drop it in a shared drive “for later.” If you print it, don’t leave it in a stack someone else can read.

Use a local-first timer for the lines you keep watching. The audit can stay on paper.

If Keep watching includes inbox time, TimeRetain lets you see how much of each morning it takes after the audit ends. The primary record stays on your device. Optional Sync stores an encrypted copy on TimeRetain’s servers.

Keep a private timer for the few things the worksheet said to watch.

Start tracking →

Put the file away

When the three tables and the review are filled, close the file. Leave Keep watching for the few lines that still need a timer.

Time tracking for architects: know what a job takes

Thu, 13 Aug 2026 00:00:00 GMT

Time tracking helps you see what an architecture job really takes, including the extra site visit or the third kitchen design.

You don’t send that log to a boss. You keep it so the extras still have a date attached when you need them.

This guide is for a solo architect or a tiny studio where each person keeps their own record. You can use phase labels without taking on staff timesheet approvals.

What the fee alone cannot show

You might charge a percentage of construction, a fixed fee, hourly with a cap, or a mix: fixed through design, hourly once construction starts. The fee alone doesn’t tell you how many hours the work took.

Effective rate is the fee divided by the time you spent, before overhead. Your tracker supplies the hours. A fixed fee is a number you already have. A percentage of construction cost waits on that cost.

A two-hour site visit takes more than two hours if you also drive there, write field notes, and follow up. Count those hours too.

An extra visit can disappear into one construction administration (CA) pile. A kitchen you already finished can need a redraw. None of that shows up if the only number you have is the fee.

What to put on each entry

Keep the labels small enough that you’ll use them on a jobsite.

Field	Why keep it
Project	Which job the hours belong to
Start and stop	Record the start and end of each work block.
Note	The event, in words you’ll still understand next month: “Framing walk,” not “CA”
Kind of work	A tag you’ll filter on: site visit, extra, travel, modeling, admin. Skip tags you’ll never use

That’s close to manual time tracking for any solo practice, with one architect-specific rule: do not dump everything into construction administration. CA names a phase, but it doesn’t tell you what happened that day.

Two kinds of labels let you filter by project and activity. One says which project the work belongs to. The other says what kind of work it was, so you can total site visits across every job at once.

Start with the project and two kinds of work: extra and site visit. Add schematic, design development, and construction documents later if you need those totals. Use Extra for work outside your original plan.

A day that still makes sense in October

Here is a hypothetical day:

Date	Start	End	Project	Note	Kind	Total
Aug 13	09:00	11:40	Chen addition	Wall sections at the stair	Modeling	2h 40m
Aug 13	11:40	12:05	Chen addition	Contractor call on beam size	Admin	25m
Aug 13	13:30	16:10	Chen addition	Framing walk, drive included	Site visit	2h 40m
Aug 13	16:10	16:55	Chen addition	Kitchen after design approval	Extra	45m
Aug 13	17:00	17:35	Walsh kitchen	Permit comments	Admin	35m

The kitchen line names the extra work. That gives you a specific revision to discuss with the owner or allow for in the next quote.

Choose whether to include the drive in the visit or give travel its own entry. Use the same approach throughout the project so you can compare visits.

Separate a contractor call from modeling when you want to compare those activities. One project total is still useful if that is all you need.

What this log is for

Count the visits. Filter one project to site visits and look at the rows. Suppose you planned for six visits. If the next visit would go past that number, you could raise the extra visits with the owner before the trip rather than after it.

See the extras. Tag work that wasn’t in the original plan: a late revision, a quick look that became an evening, or unexpected permit comments. Extra shows how much time the plan missed.

Check the fee. For a completed project, open the full project total. Divide the agreed fee by those hours. If a $28,000 job took 280 hours, the fee works out to $100 an hour before overhead. If part of the fee pays consultants, such as a structural engineer, subtract their share first, or the figure will look better than it is.

For the next similar job, adjust the hours for differences in scope and complexity. You could multiply that estimate by your target hourly rate as a starting point for the fee. Pick a target that covers business costs as well as your pay. At $150 an hour, 280 hours would come to $42,000.

Capture on the phone. Clean at the desk

Start when the work starts. Pick the project, start the timer, write a rough note. Don’t pause the drawing to perfect the wording.
Stop when you switch. Keep different projects separate. Within one project, give a call or extra work its own entry when you want to compare those hours. Tiny interruptions for the same project can stay in its block.
Tag extras while you still remember they were extras. Next month, you might not remember why they were outside the plan.
Once a week, filter. Site visits on this job. Extra across every job. The hours so far against what the fee can carry.

If you forget a timer, look for clues: the field report, sent PDFs, email timestamps, the photos on your phone. Those clues can help you estimate a missing block, but they don’t establish every start and stop.

You don’t need a firm stack

For a one-person studio, look for a timer you’ll start in the driveway, a few labels, and edits when the day got messy. A CSV export gives you rows to share with the owner or your accountant.

Software built around staff timesheets and shared billing can add setup a solo practice doesn’t need. Automatic tracking based only on laptop activity won’t record a site visit while the laptop is closed. A tracker that requires a network connection won’t run in a basement with no signal.

If you want a private record, check where the tracker stores client names, notes, and rates.

Where TimeRetain fits

TimeRetain is a manual timer for keeping each job’s hours and notes together. When an owner asks about extra work, you can find the visit or revision and see how long it took.

You don’t need an account. The primary record stays on your device. If you enable optional Sync, TimeRetain stores an encrypted copy on its servers.

Once the job is complete, compare its hours with your fee. Use what you learn when you estimate the next similar project.

Keep a clear record of your next site visit.

Start tracking →

Start with one project

For one week, track a single job: project, start, stop, a one-line note, and Extra when the work wasn’t in the fee. If travel is part of the visit, start when you leave. Otherwise, give travel its own entry and start the site-visit entry when the visit begins.

Then read it back. Count the visits. Add up Extra. Divide the fee by all the project’s hours once it is complete, not just this week’s hours.

If unplanned work or visits took more time than expected, you could talk through the remaining work and budget with the owner while the job is still open. Use those hours when estimating the same kinds of work on the next project.

Time tracking for developers: keep your own record

Wed, 12 Aug 2026 00:00:00 GMT

Time tracking for developers can be a personal record of your own hours. You don’t need an editor plugin or an agent taking screenshots to keep one.

The log can show why a short task ate the week. It can also name the work better than “various stuff,” and total the time meetings took.

What the record is for

A personal time record can answer four practical questions:

What did I actually do this week? By review season it is a list of work with dates, not “worked on the platform.”
What does a task really cost? Compare estimates with recorded hours to see which parts you missed.
Where did the week go? Separate feature work, debugging, review, meetings, and yak shaving in the log. A meeting total gives you something concrete to discuss when priorities compete. Include preparation if you want to see the full time the meetings required.
What do I invoice? If you bill clients directly, the record needs hours with notes a client will recognize.

Keep a plain log for yourself: what you worked on, for whom, and for how long.

Use manual time tracking, with a few developer-specific twists.

The minimum developer time entry

Keep each entry small enough that you’ll actually write it:

Field	Why keep it
Project or client	Which product, codebase, or client the work belongs to
Start and stop	Real boundaries, not a duration typed from memory
Note	The outcome, with a ticket or branch name when one exists
Billable status	Only if you invoice; employees can skip this column

“PROJ-142: fixed checkout race condition” still makes sense at review time or invoice time. “Coding” doesn’t.

When the entry might reach a client or a manager, name the result in their words: what got fixed, shipped, or reviewed. The webpack fight stays in a private note.

You don’t need a task tree that mirrors the issue tracker.

Group project or client work together, and mark debugging, review, or meetings to compare those hours across projects.

On a plain day, a note alone is enough.

A day that still makes sense next month

Here’s a hypothetical day:

Date	Start	End	Project	Note	Kind	Total
Aug 12	09:10	10:40	Checkout	PROJ-142: fixed checkout race condition	Debugging	1h 30m
Aug 12	10:40	11:20	Checkout	Reviewed PR #418 on payment retries	Review	40m
Aug 12	11:30	12:20	Platform	Sprint planning	Meetings	50m
Aug 12	13:15	14:10	Checkout	Read payment-flow docs (estimated)	Research	55m

The last row is an estimate based on the developer’s notes and calendar. A later commit helps identify the task, but does not establish the session’s duration.

Track sessions, not editor activity

An IDE activity log leaves two gaps to consider in your personal record.

First, an open editor isn’t proof of work, and a closed one isn’t proof of rest. Reading library docs, sketching a data model on paper, and staring at the ceiling until the bug’s cause clicks are all part of the task. A tracker limited to editor activity can miss that work.

Second, the project or purpose can be missing. A repository name or window title can identify the project. A shared documentation page won’t necessarily tell you which client needed the research.

When labels are missing, you have to interpret the activity log after the fact. That is where automatic time tracking needs your judgment.

A background activity log can sit as a safety net you classify later. Use it to fill gaps in your session record.

Use the work session as the unit. Start a timer when you sit down to a task. Stop it when you switch tasks, meetings, or clients, and pause for breaks. A short note beside those boundaries gives you context for the later review.

Your log answers your questions. You can keep it separate from any monitoring your employer uses. Keep the notes within what your employer or client lets you write down outside their systems.

Recover a missed session while it is fresh

A commit or pull request can remind you what you worked on. Your calendar and messages can help fill in the rest.

Use those clues to estimate a missed session, and label it as an estimate. Two commits an hour apart do not prove an hour of work. You might have taken a break or switched tasks between them.

Research and debugging can leave no commit at all. Include that work when you remember it, rather than treating code changes as the whole job.

If you cannot recover a useful estimate, leave the duration unknown. For the next session, record the time as you work.

Use tracked hours to review your estimates

If you record the task’s full time, your log shows how it compares with the estimate.

Write your estimate on the ticket, track the task, then compare. Look for two things across comparable tasks:

Room for work you missed. If similar fixes repeatedly need review and testing beyond your estimate, include time for those steps next time. Allow more uncertainty for unfamiliar work.
Where the overrun lives. Compare time spent on coding, debugging, integration, environment setup, and review. When your log shows a pattern, estimate those parts separately.

This works for fixed-price work too. Once the job is complete, divide the fee by all its hours to see hourly revenue before costs. Use the hours to plan similar work. You could check the next fee against your costs and income goal rather than repeating that rate.

Record debugging and rework for client projects

Skip this section if you do not work for clients. Debugging and rework can disappear inside a vague development entry.

Debugging. Record the session and name the result: “Traced and fixed duplicate-webhook bug in payment flow” is a line a client can understand.

Keep testing, debugging, and rework as separate entries when that helps you review the work. Your record can include time you don’t invoice.

Mark rework clearly so you can review the hours it took. The billable vs non-billable split can help you organize the record.

Rabbit holes. A dependency conflict can consume four hours despite a brief task description. Record the real duration and describe the obstacle.

If your invoice uses a smaller figure, leave the four hours in your own log. Changing the source record to “maybe two” loses information.

Keep non-client work visible too. Proposals, invoicing, and learning a framework no client asked for come out of the same week you bill from. Leaving them out understates how much of your week the business needs.

Where TimeRetain fits

A developer’s time log holds the systems you touch, your late nights, your real meeting load, and, if you bill, client names and rates. You don’t have to upload that record to keep it.

TimeRetain is a manual timer for keeping that record on your device. You can see how much time went into review, meetings, or debugging, and what each session produced. Nothing watches your IDE.

If you invoice, use the notes to explain the work delivered. Keep uncharged rework in your own record so you can see what the project really took.

The primary record stays on your device. If you enable Sync, TimeRetain stores an encrypted copy on its servers.

Keep a week you can explain. Track your next session in TimeRetain.

Start tracking →

Start with one week

Don’t build a system. For one week, track only real work sessions: project or client, start, stop, one-line note with the ticket. Use git and notes to estimate missed sessions while the day is fresh. Leave gaps you can’t support.

Then read it back. Check the meeting total against what the week felt like. Compare one or two tasks against what you estimated for them. If the record helps you review your work or prepare an invoice, and the effort feels worthwhile, keep tracking.

What is timesheet rounding and when to avoid it

Mon, 10 Aug 2026 00:00:00 GMT

Timesheet rounding turns exact work times into fixed blocks. A task that took 14 minutes might become 15 minutes on the timesheet.

If you track your own time, keep the stored hours exact. If an invoice needs rounding, use a copy and keep the original hours.

Use rounding when the billing method calls for it, rather than to make the record look tidy. It can change the charged total whenever the recorded time isn’t already on that increment.

How timesheet rounding works

You can round each entry’s duration to the nearest quarter hour: a 14-minute task becomes 15 minutes. Or you can round the start and end times, then calculate the duration.

The two methods can give different results for the same work. A 44-minute block from 09:08 to 09:52 rounds to 45 minutes as a duration.

Round its start and end times instead, and the block becomes 09:15–09:45. That is 30 minutes, even though the work took 44 minutes.

The examples below round start and end times to the nearest quarter hour. They use whole-minute values.

Within each block, minutes 1–7 round down to the block start and 8–14 round up to the block end. Here’s an example day:

Worked	Rounded (nearest 15)	Difference
09:08–09:52	09:15–09:45	−14 minutes
10:07–11:23	10:00–11:30	+14 minutes
11:31–12:29	11:30–12:30	+2 minutes
Total		+2 minutes

Difference is what rounding did to the record: − is time removed, + is time added.

These three entries add two minutes overall. That doesn’t mean another day’s entries will balance out.

What rounding does to your record

Rounding changes the record, not the work.

A 22-minute call from 10:08 to 10:30 becomes 10:15–10:30: seven minutes gone.
Moved five minutes earlier, 10:03–10:25, it becomes 10:00–10:30: eight minutes you did not work.
A 7-minute fix from 10:12 to 10:19 vanishes: both times land on 10:15.

The rounded record hides what changed. Lost minutes are gone, and added minutes look like work.

Even when the daily total comes out right, rounding can move time between tasks. One client’s total can rise while another’s falls.

Nearest rounding isn’t the only method. For durations, rounding up moves every partial block to the next block edge.

Three 2-minute emails rounded up to 15 minutes each become 45 minutes after 6 minutes of work. Combine those durations first, and rounding up gives 15 minutes.

When to avoid it

Avoid rounding your stored record. Once the exact times are gone, you can’t check a rounded total or switch methods later.

Be careful with per-entry rounding when you log many short tasks. Rounding each duration to the nearest block can move every entry by up to half a block. Rounding up, or rounding start and end times, can move it by almost a whole block, as the 44-minute example showed. Those changes can cancel out or pile up.

If you need a rounded figure, rounding the combined total once puts the tightest limit on the change. With nearest rounding and whole minutes, the total moves by at most 7 minutes for 15-minute blocks, or 3 minutes for 6-minute blocks (a tenth of an hour).

Keep the exact record

A manual timer records when you start and stop. Keep those times so you can compare an exact total with a rounded copy later.

If you round time for an invoice, you could agree on the method with the client before work starts. Specify the increment, direction, and whether you round each duration, each start and end time, or the combined invoice total.

The billable hours calculator can turn your hours and rate into an amount. It does not apply a billing-rounding rule.

Where TimeRetain fits

TimeRetain helps you keep the hours behind an invoice, so you can explain the original times later.

When an invoice needs rounded hours, you can export a rounded copy while your saved entries keep their exact times.

Keep exact minutes on your own device. Use a copy when you need rounded totals.

Start tracking →

Billable vs non-billable hours: what to track

Thu, 06 Aug 2026 00:00:00 GMT

Billable hours are work your client agreed to pay for as a separate time charge. Use non-billable for work with no client charge. Put fixed-fee and fixed-price retainer work in a third category so you can compare its price with the hours you spent.

Keep these categories separate when your work includes all three. Billable hours feed an hourly invoice. Paid-through-price hours show what a fixed fee or fixed-price retainer bought. Non-billable hours show what your rate must cover. If you track only invoice hours, the rest of your working week disappears from the calculation.

This article is for the person who bills their own work and wants to compare revenue with the whole working week.

What counts as billable

An hourly charge can cover delivery work: drafting, client calls, revisions, or research. The same task may be part of a fixed-price project instead. Before work starts, agree with the client on which tasks you will charge separately and which the fixed price includes.

What counts as non-billable

Non-billable hours are real work no client pays for directly:

Writing proposals and estimates
Invoicing, bookkeeping, and chasing payments
Marketing, networking, and portfolio updates
Free discovery calls, whether or not the lead signs
Learning that no client asked for
Tool setup and admin

“Non-billable” doesn’t mean optional. It means the client doesn’t pay for that hour. You still spent it.

Sort the gray areas

Decide which hours you plan to show as a separate charge, which are part of a fixed price, and which have no client charge. Keep these categories in your log.

A free discovery call belongs with work that has no client charge. A paid workshop billed by the hour is a separate charge. One sold at a fixed price stays inside that price. Discuss travel, research, and revision charges with the client before the work starts, then label those hours to match.

Track rework separately, whether or not you invoice it. Rework lowers the job’s revenue per hour when it adds time without an added charge. If every hour is billed at the same rate, more billed hours leave that rate unchanged.

What the categories tell you

In this hypothetical week, you invoice 25 hours at $80. That is $2,000. Then count the 15 hours you spent on proposals, invoicing, and unpaid follow-ups.

You worked 40 hours for a $2,000 invoice. That is $50 in invoiced revenue per working hour, even though your hourly line rate was $80. Collected revenue can be lower if the invoice is not paid.

Fixed-price work needs its own check. Say a project sells for $1,200 and your log shows 20 hours of delivery. That’s $60 per delivery hour, below your $80 line rate, before you count any unpaid hours around it. If those 20 hours were mixed into either of the other totals, you wouldn’t see that gap.

The $50 is revenue before business costs and personal reserves. You could set your client rate to cover those costs and the work you don’t charge for directly. The freelance rate calculator helps you set that target.

Use the totals to decide what you can change:

If your rate or a fixed price doesn’t cover the work, consider quoting higher next time.
Reduce avoidable unpaid work, such as repeated tool setup, while keeping time for necessary admin.
Limit repeated unpaid follow-ups when a lead shows no interest.
Follow up on overdue invoices.

If you discount or write off hours, keep those totals separate from the hours you invoiced.

For a solo worker, the question is: how much of my working week did clients buy, and does my rate cover the rest?

Where TimeRetain fits

Use TimeRetain to see how much time a client takes, including the work you don’t charge for. A record of delivery work, revisions, and follow-ups helps you judge the whole job before you quote the next one.

Keep a view of your general admin and marketing too. Those hours explain why an $80 client rate does not mean $80 for every hour you work.

The primary record stays on your device, and you don’t need an account. Optional Sync stores an encrypted copy on TimeRetain’s servers.

Start with one client in TimeRetain. Record the delivery work and unpaid follow-ups, so you can judge the job by all the time it takes.

Start tracking →

Time tracking for consultants: hours you can explain

Sun, 02 Aug 2026 00:00:00 GMT

Time tracking for consultants is a plain record of client work. It shows the client, engagement, time spent, and work you delivered.

Use that record to explain the month to a client or review your price before the next scoped project.

This guide is for the independent consultant who needs a trustworthy personal record. You don’t need to run a firm to have several engagements in flight.

What consultant time tracking is for

Consultant time tracking answers a few practical questions:

Which client and engagement did this work belong to?
Was the time hourly, retainer, fixed fee, or non-billable?
What did the client get, in words they would recognize?
Can you explain the entry next week without reconstructing the day?

That’s close to freelance time tracking. Here, the examples focus on retainers and hourly scoped work. Keep a billable record you can explain in a client summary.

If nobody else needs to approve your time, shared approval features add little to this workflow. Start with a timer you’ll use, labels that match how you sell the work, and an export for your billing setup.

The minimum consultant time record

Strip each entry down to what you will need later:

Field	Why keep it
Client	Who pays, or who the work is for
Engagement	Project, retainer, or advisory block
Date	When the work happened
Start and stop	Real duration. Mark a reconstructed block as an estimate.
Work note	The result, in client language. This is the line a client might see
Type	Hourly, retainer, fixed fee, or non-billable
Rate	Only when the hour has a price attached

A useful note names the outcome: “Mapped current hiring funnel and gaps,” not “Zoom + Notion.” Keep private asides in your own notes. The client-facing line should still make sense on its own.

Here is an example day for a retainer review:

Date	Start	End	Client / engagement	Note	Type	Total
Aug 3	09:00	10:15	Acme retainer	Reviewed Q3 pipeline notes before weekly call	Retainer	1h 15m
Aug 3	10:15	11:00	Acme retainer	Weekly advisory call; agreed next hiring screen	Retainer	45m
Aug 3	13:00	15:30	Northwind scope	Drafted phase-1 research plan and interview list	Hourly	2h 30m
Aug 3	16:00	16:40	Internal	Updated proposal template for fixed-fee work	Non-billable	40m

Use those rows in the invoice you already send or to explain a retainer month. This example records two retainer hours, two and a half hourly hours, and 40 minutes of internal work.

Hourly, retainer, and fixed-fee work

Keep the same basic record for these three pricing methods, then change how you use it.

Hourly work needs clean start and stop times and notes that support the invoice. Group lines by what you delivered before you send them.

Retainers benefit from the same record. The hours may not appear line by line on the invoice. The record shows the work you logged against the monthly fee. For a retainer sold as “about eight hours of advisory a month,” compare the hours used with those eight hours.

For retainers with an hour allotment, check during the month. If week two already shows most of that allotment, discuss what work to prioritize before it runs out. Use those totals when you review the scope or price of future work.

Fixed-fee work also deserves a record when you want to review the price. After the engagement ends, divide the fee by all its hours to get revenue per hour before costs. If that falls below your target, look at what took the time. Recurring revisions can call for a higher fee or less included work next time. A one-off problem does not automatically belong in every future estimate.

Before you quote, use the freelance rate calculator to check a fixed fee against planned hours and extra revisions. After delivery, check it again with the hours you recorded.

Keep non-billable work visible. Proposal writing, admin, unpaid follow-ups, and “quick” Slack answers belong in their own labels. Keep client-specific unpaid work attached to its engagement: it still costs time and reduces the effective rate. Mark it separately from hours that count toward a retainer allotment, and keep general business admin separate.

Track travel as a separate entry, even when you leave it off an invoice. The total helps you price future on-site work.

A light workflow for a busy week

Capture first. Clean later.

Start when the work starts. Pick the client and engagement, start the timer, and write a rough note. Do not pause the work to perfect the wording.
Stop when you switch. A new client or a non-billable block gets its own entry. Keep small related tasks together, but separate work for another client or unpaid work.
Clean the same day, then once a week. Rename vague notes while you still remember them. Split mixed entries and check retainer totals against the allotment.
Review before you share. Use your timesheet to explain the work delivered. Keep unpaid client work visible when you review the engagement, even though you do not bill it.

Keep stored time exact. If the invoice uses hourly lines, you could agree on the rounding method before work starts and round a copy for the invoice. If your method rounds up, three separate 2-minute emails can become three billed blocks, so you might also agree whether to group related tasks first.

Hourly billing shows 6-minute and 15-minute increments you can agree with a client. Timesheet rounding is why the stored hours stay exact.

Optional start and stop reminders can flag a missed timer.

If you still miss one, use sent files, messages, and your calendar as clues. They can help you estimate a session, but do not prove its start and stop. Mark reconstructed time as an estimate.

Where consultant time tracking goes wrong

One trap is treating every engagement like a firm project code.

You don’t need five layers of tasks to explain who the work was for. Start with client and engagement. Add tags for meetings, research, or delivery only when you will actually filter on them later.

The second failure is writing notes only for yourself. “Sync with Sarah” is fine on Tuesday. It names the person, but leaves out the work. Use the client’s words when the line might be shared.

The third failure is buying features you won’t use. Shared approvals, client portals, and utilization dashboards can help when your work calls for them. Without that need, they’re another system to maintain.

If your billing already lives in accounting software or a spreadsheet, your tracker should feed that workflow, not replace it.

The fourth failure is relying on automatic tracking when its activity log doesn’t identify the engagement or task. A window title might name a client document, or it might only say “Untitled” or “Inbox.” When it doesn’t name the client, add that context while you remember it.

What to look for in a consultant time tracker

Can you walk into a client conversation already knowing where the hours went?

A running total per engagement, so you can compare hours used with the retainer allotment during the month.
Notes you would be willing to show. If an entry can go into a client summary unedited, the record is doing two jobs at once.
Edits when the day got messy, so you can fix a timer you forgot during a client call.
Labels that match how you sold the work. One level for the client, one for the engagement. Try the setup with a short advisory call before you commit to it.
Offline capture if you work at client sites, on trains, or anywhere a connection can drop.
A plain CSV export, so the record can go with you when a client or your accountant asks for it.

For this record, focus on hours and work notes. Screenshots and activity scores don’t replace an explanation of what you did for the client.

Where TimeRetain fits

Client names and rates are sensitive. TimeRetain keeps the primary record on your device without an account. Optional Sync stores an encrypted copy on TimeRetain’s servers.

TimeRetain lets you group each client’s work and see each engagement’s total. When a retainer feels stretched, you can see the hours behind it and read what those hours covered.

Bring that record to your next client conversation. Use it to explain what the month covered and whether the next month needs a different scope.

Keep the hours and notes for your next retainer review in TimeRetain. Start with one client. No account required.

Start tracking →

Start with one client

For one week, track a single client: engagement, start, stop, and a one-line outcome note. Start when the work starts. Stop when you switch, including to internal work.

Then read it back. Can you explain the hours? Does the retainer still fit? If a note would confuse the client, rewrite it before next week.

Manual time tracking without surveillance

Fri, 03 Jul 2026 00:00:00 GMT

Manual time tracking means you record work time yourself, on purpose.

That can be a timer, a table, or a row in a notebook. You decide what the entry means: who the work was for and what you did. A background process did not guess those labels.

It’s not screen capture. It’s not keyboard monitoring. It’s not an app quietly building a log you’ll have to explain later.

Naming the work as you start gives the hours some context. A note such as “Reviewed the launch plan” is more useful next week than “Browser.” You still need to correct a forgotten timer or a note that no longer matches what you did.

Who manual time tracking is for

Manual time tracking fits people who want to choose what goes into their work record.

The method is the same if you bill hours or keep a private record of your own job. Record the block while it is fresh, with enough context to trust it later.

It is also a good fit when your time data is personal. A work log reveals a lot: clients, rates, bottlenecks, late nights, what keeps interrupting you. That kind of record is worth keeping under your own control.

Manual tracker vs. manual timesheet vs. automatic tracker

A manual tracker captures time, and a manual timesheet stores the record. An automatic tracker watches activity before you review it.

Method	Plain meaning	Best use	Watch out for
Manual tracker	A timer or app you start and stop yourself while work happens	Daily tracking, billable work, private work records	Forgetting to start or stop
Manual timesheet	A row-based record you fill in, clean up, review, or export	Payroll, invoicing, weekly review, exports	Rebuilding too much from memory
Automatic tracker	Software that watches activity in the background before review	A draft of computer activity you still have to label	Window titles that don’t name the work

A manual tracker can produce a manual timesheet, but they are not the same thing. The tracker captures the work block. The timesheet is the record you review, submit, export, or use later.

An automatic log can save a session you forgot to time. It needs review when the activity does not identify the work or client.

That is where automatic time tracking needs your judgment. A manual tracker lets you name the work at the start, but remembering the timer becomes your job.

A plain manual time tracking method

A manual system can stay at three steps.

Record who and what. Name the client, course, or employer, then the activity. Later, you can find one client’s work or see how much time went into meetings.
Record the block as it happens. A good entry needs context, activity, start, end, and a note. Start when the block begins, stop when you switch, and write a note you’ll understand later.
Review the day once. Fix rough notes and split a block if it covers different clients. A daily work log can hold a longer note about what remains unfinished.

Here is a hypothetical day for a freelancer with one client:

Date	Start	End	Context	Activity	Note	Total
Sep 1	09:00	10:30	Hartwell	Admin	Reconciled August receipts	1h 30m
Sep 1	10:45	12:00	Hartwell	Writing	Drafted August status memo	1h 15m
Sep 1	13:00	14:30	Hartwell	Meetings	Scope call on Q4 retainers	1h 30m
Sep 1	14:45	16:00	Internal	Admin	Invoiced August and cleared inbox	1h 15m

Write the note rough, then clean it up once. Replace vague wording with a plain description; do not turn the entry into a report. “Worked on project” will not help later; “reconciled August receipts” will.

Write the record while the context is fresh

The record gets shaky when you wait too long to write the entry.

By Friday, Tuesday afternoon has often turned into fog. A 35-minute call might feel like an hour, and a small admin task might disappear entirely.

If those hours affect an invoice, a retainer, or a workload decision, try not to rebuild that block from memory days later.

Start the timer when the work starts. Stop it when the work stops. Add a rough note now; clean it up later if you have to.

That rhythm also helps with billable hours. The invoice doesn’t need your whole day, only entries you can still explain weeks later.

Keep labels boring

Too many labels make manual tracking harder than it needs to be.

If choosing a label keeps interrupting your work, try fewer labels. Keep a detailed task structure only when you use that detail later.

Keep work for each client, course, or employer together. A few broad activity labels make the entries easier to scan:

Admin
Meetings
Writing
Research
Support
Study

Put the detail in the note. “Writing” keeps similar work together; “drafted August status memo” tells you what happened in that block.

If you only need one total, keep one group of entries. Add labels when you need to distinguish the work.

What to leave out

Manual time tracking shouldn’t record your whole life.

You don’t need to log breaks as entries. Stop the timer when you step away, and the break stays out of your working total. If an employer timesheet asks for breaks, follow its format there; your private record doesn’t have to copy it.

You do not need a description of every interruption. Leave out anything you’d only write down to look busy.

The goal is a record you trust, not proof that every minute counted. If you want to understand a few days, run a short time audit. If you need a billing record, identify the billable work. Keep unpaid work too when you want to understand what the whole job took. Do not turn every ordinary day into a report.

Privacy checklist for a manual time tracker

A manual tracker should protect the record.

Run through this checklist before you settle on a tool:

Local storage: your time data starts on your device.
No screenshots: the tool doesn’t capture your screen.
No keyboard or mouse monitoring: the tool doesn’t score your activity.
No employer-surveillance defaults: the tool is built for your record, not for watching workers.
Easy export: you can take your entries with you as CSV or another plain format.
Optional sync: if sync exists, it’s a choice, not a requirement.

Offline access means you can keep recording when the connection drops. It does not tell you who can read the record later. Look at storage and sharing separately.

Where TimeRetain fits

TimeRetain helps you keep a record you can read next week: what you worked on, who it was for, and how long it took. A short note keeps the reason for each block beside its hours. If you miss a stop, you can correct the time before you use the record.

I built TimeRetain so you can keep that record without an account. Your primary record stays on your device. Optional Sync stores an encrypted copy on TimeRetain’s servers. It does not take screenshots, log apps, or watch the keyboard.

You can take your record into a spreadsheet when you want to review the hours there.

Keep a work record you can explain next week. Try one work block in TimeRetain.

Start tracking →

Try manual tracking for three days

Don’t rebuild your whole system first.

For three ordinary workdays, track only real work blocks. Keep each entry to context, activity, start, end, and note. Use a few broad labels. Fix rough notes once at the end of the day.

After three days, read the record back and ask four questions:

Work: Can you tell what you worked on?
Time: Can you see where the time went?
Trust: Can you trust the entries enough to use them?
Friction: Did tracking stay light enough to keep doing?

If tracking takes too much effort, simplify: fewer labels, shorter notes, less cleanup. If the record is unclear, add the missing context. If times are wrong or missing, correct them and try a reminder at work boundaries.

If the record answers those questions and stays easy to keep, keep going. Manual time tracking isn’t about proving you were busy. It’s about keeping a record that still makes sense after the day has moved on.

Why I built a tracker instead of a spreadsheet

Sat, 27 Jun 2026 00:00:00 GMT

A time tracking spreadsheet is good enough when you only need a small manual log. For me, the extra work began when I wanted it to act as a live timer.

I used to keep hours in Excel. Not because spreadsheets are bad.

Excel has formulas, tables, charts, formats, filters, pivot tables, and automation. It can do a lot.

That was the problem. The spreadsheet did not fail because it was weak. It failed because I kept asking it to become a time tracker.

First it was a few rows. Then it needed daily totals. Then weekly totals. Then cleaner notes and better grouping.

Then I needed a way to fix a forgotten stop time. Then I wanted a pause button. By that point, I wasn’t just filling in cells. I was maintaining a small app.

A simple time tracking spreadsheet

If you want the spreadsheet version, here is a fictional day to copy:

Date	Start	End	Task	Project	Notes	Billable?	Total
Jun 26	09:10	10:25	Draft article	Marketing	First pass	No	1h 15m
Jun 26	10:40	11:30	Client email	Client A	Reviewed launch notes	Yes	50m
Jun 26	13:00	14:45	Fix invoice copy	Client B	Rewrote line items	Yes	1h 45m

That is a useful record. One row per work block. A start, an end, a label, and a note you can understand later.

If all you need is a timesheet, this may be enough. Put a formula in Total (End minus Start), sum the day, and move on. Do not type 1h 15m from memory. Format the totals as elapsed time, such as [h]:mm in Excel, so a week over 24 hours doesn’t wrap back to a small number.

Do not turn it into a shrine to precision. Do not add twelve columns because you might want them someday. If a field does not help you review, bill, or understand the work, leave it out.

If you need to exclude a pause within a work block, subtract a break duration or split the row.

When a spreadsheet is enough

A spreadsheet works when the record is small and calm.

It is fine for a short time audit. Record a few days that represent the routine you want to examine, then review them.

It is fine for occasional billable work. If you only bill a few blocks each week, a small table can support the invoice.

It is fine when the work happens in clean chunks. Start at 9, stop at 10:30, write the row, done.

The spreadsheet gets worse when the day does what days do.

You switch tasks. You get interrupted. You forget to stop. You come back after dinner.

Now the spreadsheet is storing time and being asked to understand it.

Time input is the first annoyance

Typing time is small friction, but it repeats all day.

09:10. 10:25. Project, note, billable, total. Next row.

That is not hard. It is annoying. There is a difference.

If typing each row interrupts your work, it’s tempting to leave it until later. But then you have questions to answer.

Was the client call 45 minutes or 70? Did the follow-up happen before lunch or after? Was that admin work part of Client A, or was it only inbox cleanup?

The spreadsheet did not create the memory problem. It failed to catch the work while it was happening.

When you press start and stop as the work happens, a timer records those times for you. You don’t have to type them later. A forgotten button press still leaves a gap to reconstruct.

Pause is where the spreadsheet becomes software

The pause button sounds harmless.

You start work at 9:10. Someone calls at 9:35. You pause, resume at 9:48, and stop at 10:25.

In a timer, that is normal.

In a spreadsheet, you now need a rule. You can add a break column, split the row, or keep a separate pause table. If you add buttons that write timestamps, you also need a way to correct a mistaken press.

Excel can support this. Of course it can. Depending on how far you go, you might use formulas, tables, scripts, or macros.

That can be a fun project if the project is the spreadsheet. If maintaining the sheet interrupts the work you want to track, a separate timer is worth trying.

When the totals become another task

A short day is easy to add up. A late session or an interrupted afternoon can make you pause over the numbers.

If work runs past midnight, you still want a useful daily total. A plain End minus Start goes negative for that block, so the formula needs another rule. If you keep both a work total and a deep-work total, they overlap. Two focused hours inside an eight-hour day do not turn it into ten hours.

A spreadsheet can handle that. But every extra view needs to stay consistent with the others.

That was more spreadsheet work than I wanted. I wanted to see where the week went, without inspecting the formulas before trusting the answer.

Spreadsheet vs. time tracker vs. timesheet

These three things get mixed together, and that is where the trouble starts.

A spreadsheet stores and calculates rows. It is good at tables.

A time tracker captures work while it happens. It gives you a start, a stop, and a record you can correct later.

A timesheet is the cleaned-up record you review, submit, export, or use for billing.

Those are different jobs.

I wanted one spreadsheet to do all three. That was the mistake.

Why I built the tracker

I did not build TimeRetain to beat Excel at spreadsheets.

I built it because I wanted to stop maintaining a spreadsheet-shaped app.

I wanted a manual record. I wanted to keep the reason for each block beside its hours.

Automatic capture can pick up minutes you never timed. I still wanted to choose what went into my record and correct mistakes later.

I wanted to see one kind of work across clients without forcing every entry into a project. Now you can keep Client A’s hours separate from Client B’s, and still see how much time went into the same activity across both.

I still use a spreadsheet when I want to work with the hours there. I don’t want the spreadsheet to be the thing I operate all day.

The billable parts came later, after a feature request. A clear record helps you explain the hours on an invoice. You still send the invoice with the tool you already use.

And I wanted the record on my own device first, because time data is personal. It shows clients, habits, rates, bottlenecks, late nights, and the shape of a working life. That is worth protecting.

Use a spreadsheet until it gets in the way

If a time tracking spreadsheet works for you, keep it.

A spreadsheet is portable, familiar, flexible, and easy to inspect. It is often the right first version.

But be strict about the line.

If you are typing times from memory instead of updating the log close to the work, the spreadsheet is already leaking.

If you want the sheet to pause and resume a live timer, you are building software.

If every extra view has to stay consistent with the others, the spreadsheet is making you think about the wrong thing.

If week totals require you to audit formulas before you trust them, the tool has become part of the work.

That was the line for me. My spreadsheet did not need one more formula. It needed to stop being the timer.

TimeRetain is the version I wanted after the spreadsheet got annoying.

I can record the work as it happens and correct a mistake later. The hours stay beside the notes that explain them.

See the hours for each client, course, or job without building another sheet. You can take the record back to a spreadsheet when you want to work with it there.

The primary record stays on your device. If you enable Sync, an encrypted copy is stored on TimeRetain’s servers.

Try one workday without typing every start and stop time.

Start tracking →

Use a spreadsheet if it works for you.

What is a timesheet? Guide to tracking work hours

Thu, 25 Jun 2026 00:00:00 GMT

A timesheet is a record of when work happened, how long it took, and often what the work was for.

This page is about a personal or freelance record you keep for billing, planning, or seeing where a week went. It’s not an employer payroll form.

A timesheet can be a paper form, a spreadsheet, a time tracker export, or a simple table in a note.

The useful version answers one plain question: if you look at this next week, can you tell what happened?

What a timesheet is

A timesheet records work time in a structured way.

An employee can still keep a private log of their own hours. That log isn’t the payroll form.

For a freelancer, the record might support an invoice. For a student, founder, or solo worker, it might show where a week went.

Those uses still share the same core: date, time, work, and total.

You don’t need to make it fancy. Every extra field asks for attention, and attention is the thing you were trying to spend on the work.

A simple timesheet example

Here’s a small timesheet for a hypothetical day:

Date	Start	End	Break	Project	Note	Total
Jun 25	09:00	10:30	0m	Client A	Drafted onboarding email	1h 30m
Jun 25	10:45	12:00	0m	Admin	Reconciled receipts	1h 15m
Jun 25	13:00	15:00	30m	Client B	Reviewed contract redlines	1h 30m

That table gives you the date, duration, project, and result of each block. Add detail only when you need it later.

The 30-minute pause on the Client B row is excluded from this personal total. The day comes to 4h 15m.

If you bill by the hour, add a rate or billable column. If you only want to understand your week, skip it.

What to put on a timesheet

Start with the smallest useful record:

Date: when the work happened.
Start and end time: the real shape of the work block.
Break time: a pause you want to exclude from your own total.
Client, project, or course: the context, if you have more than one. Put it on the row when you capture the block.
Note: what you did, in words you’ll still understand later.
Total: the time you want counted.

“Work” is too thin. “Email” is usually too thin too. A better note names the result: “drafted onboarding email,” “fixed checkout copy,” “reviewed contract redlines,” “practice problems 4-9.”

You don’t need to describe the whole task. Keep enough detail to tell this block from the next.

Timesheet vs. time tracker vs. daily work log

These three records overlap, but they do different jobs.

A time tracker captures time while you work. You start a timer, stop it, put the block on a client, project, or course, and maybe add a short note. The tracker is the tool you use during the day.

A timesheet is the clean record you can review, export, or use for billing. It can come from a tracker, a spreadsheet, or handwritten notes.

A daily work log explains what changed: what you finished, what blocked you, what you decided, and what comes next. You write it at the end of your day, as a reflection. A timesheet says how long the work took.

Sometimes you need both. Suppose a timesheet says Client A took 3.5 hours when you planned two, and a work log says the pricing copy arrived late. The timesheet shows the overrun. The log gives you a likely reason, which helps when you explain the invoice or plan the next project.

Common timesheet mistakes

The first mistake is rebuilding the week from memory.

A calendar invitation won’t tell you whether Tuesday’s 30-minute call ended on time or ran for 70 minutes. A start and stop time will, if you recorded them.

If the record affects an invoice, a retainer, or a decision about your workload, capture it closer to the moment.

The second mistake is tracking too much.

For a total per project, you don’t need a row for every browser tab or tiny interruption. If those fragments belong to one task, one row can hold its time and note.

Automatic time tracking needs your judgment when its app or window labels don’t identify the project. Add that context while you still know what the work was for.

The third mistake is using private shorthand.

“CA sync thing” might make sense today. In three weeks, you might need the client name and meeting topic. Use names and notes you could explain to someone else if you had to, even if the record is only for you.

A simple weekly workflow

A workable timesheet workflow is capture first, clean up once.

During the day, record the work blocks. Keep the entry rough: client, project, or course, note, start, stop. Don’t pause the work to polish the table.

At the end of the day, fix obvious mistakes. If one block covered two projects, split it into two entries with the correct times. Rename “misc” while you still remember what it meant.

At the end of the week, review the record. For billable hours, each row should already name the client and project.

For personal planning, compare planned blocks with recorded time. Suppose admin took two hours instead of one, and you still need to finish the client work you planned next. If you expect similar admin next week and control your schedule, allow more room for it. If someone else sets priorities, use those entries to discuss what can move.

You can also use a timesheet for a short time audit. Track three ordinary days, or a full work week if you need Monday-versus-Friday. Then stop tracking the parts that no longer teach you anything.

Where TimeRetain fits

TimeRetain helps you build a timesheet you can understand next week. Keep related work together by client, course, or project, so you can see where the hours went.

Use the record to explain a busy week, discuss a client invoice, or plan room for work that took longer than expected.

You don’t need an account. The primary record stays on your device. If you enable optional Sync, TimeRetain stores an encrypted copy on its servers.

Try TimeRetain for one workday, then review your hours and notes.

Start tracking →

Daily work log: what to record each workday

Tue, 23 Jun 2026 00:00:00 GMT

A daily work log is a short, private record of what you finished, what got in the way, and what comes next. You write it yourself, because the thinking is the point. A few lines at the end of the day give tomorrow-you a place to start.

Daily work log

CSVDownload CSV

Date:
Worked on:
Done:
Blocked / slow:
Decided:
Next:

Date:

Worked on:
-
-

Done:
-

Blocked / slow:
-

Decided:
-

Next:
-

Copy the template into a note. Keep one dated entry per workday. A short line can be enough for each field, and you can leave a field blank when nothing applies.

A daily work log example

A filled-in day might look like this:

A filled-in day

CSVDownload CSV

Date:: Thu 18 Jun
Worked on:: Newsletter draft, launch email sequence
Reviewed ad performance
Done:: Newsletter draft finished, sent to design
Blocked / slow:: Launch email sequence waiting on final pricing copy, pinged product
Decided:: Pausing the low-intent ad group for now, spend is outrunning signups
Next:: Draft the LinkedIn launch post while pricing copy is pending

Date: Thu 18 Jun

Worked on:
- Newsletter draft, launch email sequence
- Reviewed ad performance

Done:
- Newsletter draft finished, sent to design

Blocked / slow:
- Launch email sequence waiting on final pricing copy, pinged product

Decided:
- Pausing the low-intent ad group for now, spend is outrunning signups

Next:
- Draft the LinkedIn launch post while pricing copy is pending

Tomorrow morning, that entry names the finished draft, the missing pricing copy, and a task you can start while you wait.

The same six fields also work for a drawing review. Stay close to output and decisions.

“Worked on drawings” is too vague. Write what changed because you touched them.

A drawing review

CSVDownload CSV

Date:: Thu 18 Jun
Worked on:: Beam schedule, connection details
Done:: Updated second-floor beam sizes after load review
Blocked / slow:: Waiting on revised architectural grid from the design team
Decided:: Flagging the cantilever detail for senior review before issue
Next:: Check revised grid against column layout, then update detail S-412

Date: Thu 18 Jun

Worked on:
- Beam schedule, connection details

Done:
- Updated second-floor beam sizes after load review

Blocked / slow:
- Waiting on revised architectural grid from the design team

Decided:
- Flagging the cantilever detail for senior review before issue

Next:
- Check revised grid against column layout, then update detail S-412

Record what changed

A list of activities can leave out the result: “Attended standup. Answered emails. Worked on the campaign. More emails. Meeting with Sarah.”

That list names the activities, but leaves out what changed. You still need to know whether the campaign draft is ready or the meeting left a decision open.

The useful question is simple: what’s done now that wasn’t done this morning? “Launch email draft finished” tells you more than “worked on the campaign.” “Cut the webinar follow-up from five emails to three” tells you more than “meeting with Sarah.”

When you write the Done line, state the result. If the task is unfinished, record a useful change: “Ruled out two causes of the export error” or “Drafted the opening section.”

If you rebuild the day from timer or calendar entries, their titles rarely name the result, so add that yourself. A title can still leave the task unclear.

Record what held up the work

Use the Blocked / slow line when something delays the work.

The Done line records what changed. If you also need to know whether it worked, add that to the same line. The Blocked / slow line records a specific delay: pricing copy you waited two days for, or a campaign review that sat unanswered.

Across several entries, look for delays that repeat. Those dates give you specific cases to discuss. A single entry records that delay, not the whole explanation for the week.

If someone asks why the campaign slipped, point to the dated entries. “Launch emails waited on pricing copy from Tuesday through Thursday” names one delay.

Keep the note factual. Record what you needed, when you asked for it, and what you could do while you waited.

The “next” line is for tomorrow-you

End every log with one line about what comes next. Where you stopped. What to pick up first.

Name the task and the first action. In the drawing example, “Check revised grid against column layout” gives you a place to resume once the grid arrives.

If the next step depends on someone else, name that dependency too. You can still choose another task tomorrow if priorities change.

Keep the log small

A daily work log goes wrong when it tries to be complete.

You don’t need every task or a minute-by-minute account. Leave out lunch, coffee, the walk, and the group chat unless they explain a detail you need later.

Keep details that help you resume work or explain a decision later.

Leave out anything you’d only write to look busy.

Keep dated blockers and decisions even after the week has passed. Those lines preserve details you can refer to when you discuss a delay.

If the work involves patients or confidential client matters, keep identifying and clinical details out of this note. Those belong in the record your workplace already uses.

Where a work hours log fits

A daily work log is a record of what. Sometimes you also want the how long.

That’s where a work hours log helps. Run a timer while you work, with a short description such as “Newsletter draft.” Group the blocks by client or project so you can find the work behind each summary.

If you start and stop with each work block, the timer records its duration. At the end of the day, you add the result, the blocker, and the next step.

For a rough account of your day, whole-block timing is fine. A couple of hours on the launch page, forty minutes on ad review. This is not a billing record (that’s a different job, and a stricter one).

“I felt slammed” and “I spent four hours in meetings and ninety minutes writing campaign copy” are very different sentences. The second gives you something to investigate: which meetings helped, and which can you shorten or skip?

A time audit worksheet helps when you want to study where the hours went. You don’t need one to write tomorrow’s starting point.

Choose where to keep it

You can keep a daily work log in a notebook, a notes app, a text file, or a spreadsheet. Pick the one you’ll actually open at the end of the day.

The catch is remembering what happened after meetings, messages, and context switches.

A manual timer gives you raw material: a short list of the work blocks you chose to record. Use it to recall the day, then add the decisions and results yourself.

TimeRetain helps you remember the work behind today’s log. A list of the blocks you timed can jog your memory about the newsletter draft or ad review, and shows roughly how long each one took.

Look back at the day’s work when you fill the Worked on line, then add what changed and where to resume.

No account, and no screenshots. Your time records live on your device. Optional Sync stores an encrypted copy on TimeRetain’s servers.

Try timing tomorrow’s work blocks in TimeRetain. Use the list to write what changed and where to start next.

Start tracking →

Try it for three days

Start with the template at the top of this article. Skip the setup work. Use a note, unless spreadsheets already feel natural.

For three workdays, fill the six fields at the end of the day: Date, Worked on, Done, Blocked / slow, Decided, Next. Keep it rough. Fragments are fine.

After three days, read it back. If it feels useless, stop. No productivity ritual deserves a permanent slot in your life because an article told you to try it.

But if you read it back and think, “oh, this helps,” keep going.

Then look at the friction. If the log takes a minute or two, you already have the right setup. If it takes five or ten minutes because you’re piecing the day together from memory, try timing your work blocks. Keep the timer only if those records help you write the log.

How to track study time without adding more homework

Tue, 16 Jun 2026 00:00:00 GMT

Record focused study sessions by course and activity, then compare the hours with your plan once a week.

For work you still need to do, the study time calculator checks whether your remaining study work fits the hours available before a deadline.

“I studied for four hours” can mean almost anything.

Perhaps you worked for two hours, spent another half hour skimming without taking much in, and lost the rest to messages and snacks. Four focused 45-minute sessions would give you three hours of study, even if you spent the whole afternoon at your desk.

An open textbook doesn’t pour anything into your head, and sitting at a desk does nothing for your grades on its own. Track the focused minutes, not the time you occupied a chair.

By the end of a week you should be able to answer:

Where does my study time actually go?
Which courses take longer than I expect?
How much time goes to rereading and to practice?
Do I study in long blocks or short ones? Mornings or evenings?
What change could I test next week?

A good study log helps you see patterns. It shouldn’t turn into another assignment.

Give each session a clear start and stop

Choose the task before you start the timer. For a problem set, start with the first question; for an essay, start when you begin outlining or writing. Getting your books out and finding a seat happen before the session.

Keep the timer running while you work through the task, including time spent thinking about a difficult answer. You do not need to produce a line of text every minute for that minute to count.

When you leave the task for a conversation, a drink, or your phone, pause the stopwatch until you return. For example, a session from 14:00 to 14:50 with a ten-minute break gives you 40 minutes to record. The break stays outside the study total.

If you use a countdown to plan a session, record how long you actually studied. A planned 25-minute block that ends after 16 minutes contributes 16 minutes to the log.

Use the same start and stop rule across your courses so the weekly totals are comparable. If you miss a timer tap, edit the entry the same day from what you remember. Mark the duration as an estimate if you are unsure. Leave it blank if you cannot make a useful estimate.

The minimum useful study log

You don’t need a complicated system. A course, a short note, and a duration are enough to start.

Keep sessions for each course together, using a code you recognize, such as STAT 101. Label the activity: lecture, exam prep, assignments, practice.

An example Tuesday to review on Sunday:

Course	Activity	Description	Start	Stop	Total
STAT 101	Practice	practice drills, redo 4–7	09:10	10:05	55m
STAT 101	Lecture	lecture review, summarize §3	13:20	14:00	40m
BIO 210	Exam prep	quiz chapter 4	19:00	19:45	45m
HIST 140	Assignments	essay outline, draft the intro	20:00	21:10	1h 10m

The course tells you which subject received the time. The activity names the session, such as lecture or practice. The description is a breadcrumb for next time: where you stopped, what comes next.

practice drills, redo 4–7
lecture review, summarize §3
essay outline, draft the intro

The note gives you a place to resume when you sit back down.

Write descriptions you can search

A common mistake is logging everything as “Study.”

That gives you a total without the detail. After two weeks you might know you studied eighteen hours, but how much went to reading, problem sets, flashcards, or essay work?

Those labels let you compare how you spent your time. They don’t tell you which activity taught you more.

Use the same activity label for similar work so you can total related sessions even when their descriptions differ. Reuse recognizable phrases in descriptions to make searching easier.

In a searchable log, you can pull up one course and find “drills” without rereading every entry.

During the weekly review, compare lecture time with practice time. Then check course totals and compare assignment sessions with the time you allowed for them.

Don’t overbuild the system

When the work itself feels uncomfortable, building a system is a tempting way to avoid it. You can spend an evening arranging a dashboard or choosing ten categories without reading a single page.

Keep the setup small enough to use during a busy week. Choose the course, name the activity, add a short description, and start the timer. Add detail only when it helps your review.

Let sessions be the length they need to be

A study session can fit before a lecture, between classes, after dinner, or while waiting for a train. Short sessions belong in the log too.

A 17-minute review still counts. So does a 12-minute flashcard run.

You don’t need every session to look impressive. You need the record to match what you did.

Countdowns can help, as long as they don’t become the whole system. A 25-minute timer gives some tasks a clean start and a clean stop. Not everything fits in 25 minutes.

A dense chapter might need shorter bursts. Essay writing might need a long stretch. Problem sets break naturally after each question.

Review the week

Daily tracking gives you a record. A weekly review lets you compare it with your plan.

At the end of the week, look at the log: What took longer than expected? Which course got less time than I planned?

Hours alone can’t tell you what you learned. Look at checked answers and feedback alongside the log to see which topics still need work.

Allow five to ten minutes for this review. A time audit also starts with reading the record for patterns. If your workload or understanding calls for a change, choose one to try. If the plan still fits, keep it.

Depending on what you find, that might mean:

Start the lab report earlier.
Try practice questions on a topic you’ve only reread.
Try a morning session if late study keeps running into bedtime.
Ask for help on this topic instead of circling it alone.

Choose what your daily average measures

Choose the average that answers your question.

Calendar-day average: 14 hours over 7 days is 2 hours a day.
Active-day average: if the work happened on 4 of those days, that’s 3.5 hours per study day.

The active-day number gives the average duration on days you studied. The calendar average spreads the workload across the week. Keep the weekly total and number of study days alongside either average. One four-hour day and four four-hour days have the same active-day average.

Not every day has to be a study day. Keep planned days off in mind when you read the calendar-day average.

Know when not to track

Don’t track every minute of your life. Leave lunch, the walk across campus, rest, time with friends, and sleep out of it.

Don’t track breaks so you can punish yourself for taking them.

If tracking makes you anxious in a way that hurts the work, stop. Every untracked minute can start to feel wasted. The point is to see your study time, not to watch your whole life.

Track focused study sessions, and leave normal life alone. Breaks, rest, and days off are fine.

Pick a tool you’ll actually keep using

You can track study time on paper, in a spreadsheet, in a notes app, or with a dedicated tracker. The habit is more useful than the tool.

A digital tool should make the habit easier. Look for a fast start and stop, course totals, searchable notes, and an export you can keep. On paper, a course, a note, and a rough duration are enough. No option should force a long setup or turn studying into a performance dashboard.

Privacy should be part of the tool choice too, especially for students. Your study habits say a lot about you: your schedule, your courses, your stress periods, your exam timing. Not everyone wants that sitting in a cloud account.

A tool’s privacy depends on what it stores on your device and what it sends to a server. A local-first tracker keeps the primary record on your device. If a tool syncs, check whether the copy on its servers is encrypted.

Where TimeRetain fits

With TimeRetain, you can look back at STAT 101 and see the hours you gave it. Search your session notes to find where you stopped, whether that was practice drills or an unfinished essay outline.

The primary log stays on your device. You can use it without an account. Optional Sync stores an encrypted copy on TimeRetain’s servers.

At the end of the week, compare your course totals with your plan. If similar work is coming, use this week’s hours to plan room for it.

See where your study week went. Start with your next session.

Start tracking →

What is a time audit? Find where your hours go

Sun, 31 May 2026 00:00:00 GMT

A time audit is a short private look at where your hours go. Do it once to learn something. It isn’t a habit you need to keep forever.

It doesn’t require an app, a spreadsheet full of formulas, or an alarm every thirty minutes. It can be one line written when you switch tasks, like this example:

09:10-09:55 - email and Slack - reactive

That line already tells you something: 45 minutes went to messages. The note labels that block as reactive. Write a few more lines, look at the pattern, and you have run a time audit.

The audit can become its own job. If logging every minute interrupts your work, start with broader blocks.

The gap a time audit closes

Imagine a day that feels like, “I spent the morning on the project.” Your notes put that project between three Slack threads, a meeting that ran long, and an inbox detour.

That gap is the point of a time audit. You’re comparing your memory with a record, then deciding whether anything needs to change.

Three days is a light snapshot. A full work week lets you compare Monday and Friday, such as a meeting-heavy Monday and a reporting Friday.

A three-day light audit

Here is a version short enough to finish. If you want rows already laid out, use the time audit worksheet.

Pick three ordinary days. If you want to understand your usual routine, skip a launch, a travel week, and an unusually slow week after a deadline. If travel is what you want to examine, log the trip.

Choose five or six broad categories. Stop there. Extra detail gives you more decisions to make at each switch.

Buckets like deep work, meetings, communication, admin, breaks, and other are enough. If choosing a bucket takes longer than writing the note, try broader categories.

Capture by block, not by clock. When you change what you’re doing, write one line: rough start and stop, the category, and a few words. If you forget to write the lines, try a reminder.

Rough times are enough for pattern-finding. If you also bill those hours, record accurate start and stop times as you work.

Keep it light on purpose. If a reminder interrupts your work, space it out or log at natural breaks.

Task-switch notes have gaps too. You might miss a glance at Slack you never named as a switch. For this check, notes you finish beat a stricter log you drop.

After the days you logged, review for patterns. Before you add anything up, write down your guess for each category. Then total the real hours per category and put the two numbers side by side. The categories where the two differ most are worth a closer look.

Next, mark each block with one word: more, less, or fine. Look for where the time went, what surprised you, and the gap between what took the most hours and what had the most value.

Decide what comes next

After you have the notes, decide what still needs a closer look.

You can run the same check again in a few months. That is a later audit, not a reason to keep a timer on every category.

Aim for a short list. Look at each category and make one call: keep watching it, or let it go.

If mornings vanish into reactive work and you control your schedule, reserve a morning block for focused work. Track mornings for two weeks to see whether that block survives and helps.

If you bill for your time, that is a separate habit, covered in freelance time tracking. If you keep a timer for billable work after the audit, record non-billable overhead too. If you only record billable hours, admin won’t appear in your totals.

Other things can stop. You don’t need to keep timing lunch if its length isn’t something you want to change. If a category has stopped teaching you anything, let it go.

If a daily note is still useful, keep it.

Keep it private, and keep it yours

Keep details you don’t want to share in a record you control.

If you start editing your notes for a manager, the audit becomes a report. You lose whatever you choose to leave out.

For example, renaming a distracted hour as focused work hides a pattern you wanted to see.

Keep the original note so your review still reflects what you recorded.

Keep the two records separate. A personal audit is for you. It helps you decide how you want to spend your time.

If an employer needs hours, provide the record they request. Your personal observations can stay separate from that timesheet.

A detailed log includes the tasks, breaks, and distractions you chose to record. If you don’t need to share it, keep the record on your own device and avoid a shared folder.

An app log or screenshot can contain activity you didn’t label as a task switch.

A three-day notebook can miss brief distractions, but you choose what goes into it. Read more about when a captured title still needs a decision.

Examples of what the notes can show

These are hypothetical examples. The method stays the same, but the next step depends on what you want to change.

If the notes show	What to do next
You finished practice questions in two short windows before lunch. Other study blocks were rereading with a phone nearby.	Protect those windows if they help you learn. Keep rereading under its own label, and compare practice results alongside the time.
Meetings and messages fill the day; focused work gets the leftover afternoon	If you control your schedule, reserve a morning block for focused work. Watch it for two weeks to see whether it helps.
A side project got twenty minutes across three days	If you want more time for it and have room in your week, put a recurring block on the calendar.

A short checklist

Pick days that represent the routine you want to examine.
Three days for a snapshot; a work week if Monday and Friday differ.
Choose five or six broad categories and stick to them.
Write one line each time you switch tasks; rough times are fine for patterns.
Use reminders only if they help you keep the record without disrupting the work.
After the days you logged, guess each category’s total, then add up the real hours and compare.
Look for patterns: where time went, what surprised you, and value versus volume.
Decide what to keep tracking: what you are changing, what you bill, and overhead you would otherwise miss.
Keep personal observations separate from records you need to share.

After you have the notes

You now have a record of a few days, with whatever gaps your notes left. Decide whether anything needs to change. If the notes answer your question, you can stop. If they leave a gap, choose a few things to watch more closely.

When a few things still need a closer look, TimeRetain helps you follow up without repeating the whole audit. If you reserved mornings for focused work, time those sessions for a week and compare the total with the hours you planned.

The primary record stays on your device.

Optional Sync stores an encrypted copy on TimeRetain’s servers.

It doesn’t watch the days you leave blank, and it doesn’t take screenshots.

See how much time you make for the habit you chose.

Start tracking →

How to track billable hours without the busywork

Sat, 30 May 2026 00:00:00 GMT

Track billable hours so each line can go on an invoice and still be explained later. Keep the record light enough that it never takes over your day.

One way to miss billable time: you plan to log the day, then rebuild it from memory. By invoice time the sheet is half empty. You guess whether a call was forty minutes or seventy, and round whichever way feels fair.

Over-tracking is the other miss. You log every tab, label every break, and cut the day into tiny slices. The tracker then needs as much attention as the work you meant to bill.

What a billable record is for

A productivity log and a billable record can look alike, but they answer different questions. A productivity log asks where your time went. A billable record asks what the client should pay for, and why.

That changes the goal. You’re not trying to record your whole day. You’re trying to write one line you could explain three weeks later if a client asked, “What was this?”

If an entry can answer that question, it’s good enough.

The minimum billable-hours record

Strip a time entry down to what an invoice needs:

Field	Why keep it
Client	Who you are billing.
Project	Which job it belongs to when a client has more than one.
Date	When the work happened.
Start and stop	Real boundaries, not a number typed from memory.
Work summary	What you did, in words the client would know.
Rate	Which rate this entry uses, if you bill at more than one.
Billing status	Whether the work belongs on the invoice.

Everything else is optional: mood, energy, a running story of the day. If a field doesn’t change the invoice or help you back up a line, it’s clutter.

Here is a hypothetical Thursday with notes you can explain three weeks later:

Date	Start	End	Client / project	Note	Total
Sep 3	09:10	11:00	Hartwell › Onboarding	Drafted onboarding email sequence.	1h 50m
Sep 3	11:15	12:00	Hartwell › Onboarding	Reviewed and marked up contract redlines.	45m
Sep 3	13:00	14:30	Northstar › Website	Built checkout error states.	1h 30m
Sep 3	16:00	16:25	Admin	Bookkeeping and proposal template edits.	25m

Say Hartwell pays $120 an hour. Its two entries add up to 2h 35m, which comes to $310 before any rounding. The 25 minutes of general admin stay in your working-week total, but do not belong on a client invoice.

If you already have the week in a spreadsheet, the billable hours calculator will total the rows in your browser. For work you have not logged yet, you still need this record.

An easy workflow for tracking billable hours

Capture first and clean up later. Save polished invoice wording for a daily pass so it does not interrupt each task.

Capture while you work. Start a timer when you begin. Record the client and project as you start, then add a rough note. Stop the timer when you switch tasks.
Review once a day. Clarify vague notes and correct mistakes while the work is fresh. Keep each client’s hours separate.
Review before you bill. Include the work you agreed to charge for, at the agreed rate. Group related work under descriptions the client recognizes.

A weekly pass is for totals, retainers, and whether the rate still covers the week. It is not the first time you read the notes.

How detailed your notes should be

A billable note should show the value of the work to someone who wasn’t there. That sets a floor and a ceiling.

Below the floor are notes too thin to back up. “Work: 2h” tells a client nothing, and tells your future self even less.

Above the ceiling is the minute-by-minute log: every app and keystroke, all day. Those details don’t necessarily explain the work. If an app or window title doesn’t identify the task, you still decide whether that entry can support an invoice. When a captured title still needs a decision covers that case.

A useful note names the result or explains progress on unfinished work. “Drafted onboarding email sequence” beats “wrote in Google Docs.” “Reviewed and marked up contract redlines” beats “read a PDF for 90 minutes.”

The cases that trip people up

A clean workflow handles a normal day. The messy moments are where billable time leaks. The fix is a small rule you follow every time.

Interruptions chop your record into little pieces. If a quick follow-up belongs to the same client, work, and rate, leave it inside the surrounding entry. If it doesn’t, give it its own entry, even a short one.

Related pieces for the same client at the same rate can become one invoice line. Do not lump unlike work into a generic “small tasks” line.

Store real start and stop times. If you round, you could agree on the increment, direction, and billing unit before work starts, and apply that rule to a copy of the record. Timesheet rounding explains why the source times stay exact. Hourly billing shows 6-minute and 15-minute examples.

If you forget to start or stop a timer, look for evidence in sent emails, saved files, and calendar events. These can narrow down a work block, but one timestamp cannot prove its full length. If you can’t support a block, leaving it off the invoice is the safer choice.

For a flat-fee project, track hours if you want to review what the job paid for your time. Once it is complete, divide the fee by all project hours to see revenue per hour before costs. If that falls below your target, review which tasks took longer than expected. Where you can change the next quote, you could use that evidence to revise the time estimate, price, or scope.

Keep general business admin separate from client work. Keep unpaid client work in that client’s record, even when it stays off the invoice. If you set an hourly rate, compare billable hours with total hours. You could factor the unpaid hours into that rate, so the billable ones cover them.

How a time log supports an invoice

A billable record gives you the dates, work descriptions, and hours behind an invoice. It cannot guarantee that a client will agree or pay.

Group line items by what you delivered, not by random chunks of time.

Match the detail to the client. Some want a line per task, others want one line per project. Use their words, not your private shorthand.

If you have one description field, that note is the one a client might see. Keep your own exportable copy. Then a question is a record you can open, not a memory you have to argue for.

How TimeRetain fits

TimeRetain keeps each client’s hours and work notes together, so you have the detail behind an invoice line. The record gives you something to refer to when a client asks what a task involved.

Review a project’s hours to see what the job took, or look back at a client’s work when they ask about an invoice.

It works without an account. The primary record stays on your device. Optional Sync stores an encrypted copy on TimeRetain’s servers.

Start with your next client task. Keep the hours and the note you’ll need when you invoice.

Start tracking →

Freelance time tracking without losing control

Fri, 29 May 2026 00:00:00 GMT

Freelance time tracking is a portable work log. Record who the work was for, what you did, how long it took, and which rate applies. It isn’t a billing suite.

You keep that log to invoice, check a retainer, or price the next job from real hours. The invoicing app, spreadsheet, or bookkeeper you already use still sends the bill.

An example Tuesday with four small jobs that are easy to forget by Friday:

Date	Start	End	Client	Note	Total
May 26	09:10	09:40	Hartwell	Slack thread on homepage copy.	30m
May 26	09:45	11:15	Lumen & Loom	Homepage draft after the review call.	1h 30m
May 26	11:20	12:05	Apex Labs	Extra payment-error test after handoff.	45m
May 26	13:00	14:30	Hartwell	Contract reread, then support research.	1h 30m

The example assumes you recorded the times as you worked. If you rebuild the week from memory, you risk rounding by how the work felt. The total won’t tell you whether those guesses averaged out.

Keep each client’s work together so you can see its total, including work you choose not to bill. Start and stop times recorded as you work give you more to check than a duration you guess later.

A note should still make sense at invoice time. Leave unpaid work off the invoice, but keep it with the client or project it belongs to. It still took time, and the total should show that. Keep general business admin separate from client work.

Why freelance time tracking is useful

For a completed flat-fee project, divide the fee by all the hours you spent. In a hypothetical example, a 2,400 fee that took 40 hours, including calls and revisions, comes to 60 per hour. That effective rate is gross revenue per hour before costs, not a target to copy into your next quote.

Use the hours to estimate the next similar job. You could set its price using a rate that covers business costs, unpaid work, and your income goal. If this job ran long, decide whether the next one needs more hours or a narrower scope.

A ten-minute call, a quick revision, client messages, and troubleshooting after delivery leak if they never get a row. Write it down. Decide later whether to bill it, batch it, or leave it unpaid on purpose.

Rounding every four-minute message up separately can inflate the invoice. With 15-minute rounding, three four-minute messages become 45 minutes on the invoice for 12 minutes of work. You could agree with the client on whether to round each task or a combined total.

If a retainer includes a set number of hours, subtract only the hours that count toward it. Leave out work you choose not to bill, and tell the client when you’re near the limit.

When a time tracking app gets in the way

Projects, tasks, subtasks, budgets, invoice templates, client portals, and team permissions can add more setup than you need.

A budget helps when a retainer has an hour cap. Keep only the features your workflow uses.

Check which fields the app requires before you can start tracking, and whether you can archive old clients.

A required hierarchy can look neat in a demo: a client, then a project, then a task, then a subtask, before the timer starts. On a Tuesday with four small jobs, it’s friction.

Built-in invoicing can be great when the format matches how you already bill. Before switching, check whether the tracker makes you use a project tree that doesn’t fit how you bill.

If you already have a billing setup, another invoice system can mean duplicate entry and uncertainty about which version is right. An integration can remove that copying. Keep invoicing where it already lives when the setup works for you.

Export helps when the next place you bill can use the hours, notes, and project names you already keep.

Always-online accounts, cloud-only storage, activity scores, screenshots, and team monitoring may all fit a workplace product. They’re a poor fit when you want a private record that works without a connection. If a client or platform requires a work diary, keep that separate from your own log.

Keep the log portable

When you already bill somewhere else, the useful tracker is a work log you can export. Review the rows, then add them to the billing workflow you already have.

The Library of Congress describes CSV as widely used to exchange tabular data between systems. Its simple format makes it useful here.

Before choosing a tracker, try a sample export with the tool or person that handles your invoices. Make sure the record is useful there.

How to keep the log

Capture first. Clean the same day. Export when you invoice.

Start when the work starts. Don’t wait for a perfect project tree. Stop the current timer when you switch clients, so each stretch of work has a clear entry.
Group work by client. Keep each client’s hours together, and separate projects only when you need to review their individual totals.
Separate work you want to compare. Meetings, writing, and support can be useful groups if you want to see which takes the most time.
Write a note a client could read. “Homepage draft after the review call” beats “Hours.” The billable hours test is whether the line still explains itself in three weeks.
Use the record when you bill. Review the client’s work for the billing period and include the hours you agreed to charge for.

If you forget a timer, use the calendar, sent files, and messages to estimate the missing time while the work is fresh. Mark uncertain estimates.

Use the rounding method you agreed with the client. Hourly billing walks through 6-minute and 15-minute examples. Keep stored time exact, and round a copy for the invoice.

What to look for in a freelance time tracking app

Start quickly, and fix mistakes later. Write enough detail that an entry still makes sense at invoice time.

Look for a clear total for each client and a way to see what the time went toward, such as meetings or writing. You need to handle different client rates and one-off jobs without changing the rate for unrelated work.

Edits should be easy for the times you forget a timer. If captured app names don’t identify the client or task, review the automatic record before you bill from it. You can keep that record as a private check while you prepare the invoice from your edited log.

Period totals should help you check hours and earnings without turning the tracker into bookkeeping software.

If an app is free but your records are trapped inside it, the deal is weaker than it looks. Choose a tool that lets you take your record with you. If you work without a reliable connection, make offline access a priority.

Where TimeRetain fits

TimeRetain helps you keep your own record of client work without an account. The primary record stays on the device. Optional Sync stores an encrypted copy on TimeRetain’s servers.

Keep a client’s calls, drafts, and follow-up work together so you can review the full total before you bill. Separate meetings from writing when you want to see where the hours went. You can take the record into a spreadsheet when you want to review it there.

Start with your next client task. Keep a note with the hours, so you have a record you can explain at invoice time. No account required.

Start tracking →

What is offline time tracking?

Thu, 21 May 2026 00:00:00 GMT

Offline time tracking means you can record work hours without an active internet connection.

You can keep a record on a train, at a client site, or wherever the connection drops. Start the session, finish the work, and keep the hours for later.

The goal is the same as ordinary time tracking: know how long the work took and what it covered. You do not need to rebuild the journey from memory when you reconnect.

Why offline time tracking is useful

Offline time tracking can sound rare if you work on Wi-Fi most days. A good connection isn’t a sure one.

Trains go through tunnels. Plane internet isn’t always available. Hotel Wi-Fi can stall on a login page, and mobile coverage drops during ordinary work.

For billable work, a missing start or stop can leave billable time unrecorded or make it harder to invoice. The app should treat a dropped connection as normal, not as a crisis.

A timesheet can show your clients, rates, and work habits. Keeping it only on your device avoids a server copy.

Offline access and privacy answer different questions. One is whether you can record the work. The other is who can see that record.

The tracker watching your screen is a separate risk. Saving offline doesn’t stop screenshots.

Offline access and control of your record

An app can work offline and still upload your hours when you reconnect. If you want a record that stays on your device, look for that separately.

Local-first means the primary record lives on your device. Some apps also offer an optional copy elsewhere, so consider both where you keep the hours and where you want to review them.

That has a tradeoff. A record that lives on one device can go with that device: a lost phone or cleared browser data can take the hours with it. Keep a backup or a second copy you trust.

The practical questions are simple: can you record a session without Wi-Fi, read it later, and keep a copy you control?

Where TimeRetain fits

TimeRetain helps you keep a work record between connections. You can finish a session on the train and review the hours before you are back online.

The primary record stays on your device. Optional Sync stores an encrypted copy on TimeRetain’s servers.

Record the work you do between connections.

Start tracking →

Who needs offline time tracking?

Offline time tracking is most useful when a missing record has a real cost.

For freelancers, a lost timer can mean lost billable time. If consulting takes you to client sites, offline tracking lets you record work before joining their network.

If you study across libraries and trains, write the session where you are. Read the week’s total when you have a connection again.

For a personal work log, choose where you keep the record and which details you share. An employer-provided system may have access rules you do not control.

Choose for the work you do

Pick a tracker that covers the parts of your day you need away from Wi-Fi. If you work during a commute, starting and stopping a timer can be enough. If you prepare client summaries while traveling, you also need to read totals and fix entries offline.

Test it before you rely on it. Turn off Wi-Fi and mobile data, then try what you’d do on the trip:

Start a timer, close the app, reopen it, and check that the timer is still running.
Stop the timer and correct the start time.
Look at today’s or this week’s total.

If any step fails, you know before the trip, not after it. A paper note with start and stop times is a fine fallback; you can enter it when you’re back online.

Keep a backup of hours you cannot afford to lose.

When automatic time tracking needs your judgment

Wed, 20 May 2026 00:00:00 GMT

Automatic time tracking records activity. When the same app serves several clients or tasks, you still need to explain what the time was for.

Recording activity and storing it on a server are separate choices. A manual timer lets you name the block up front, but forgotten starts and stops still need correction.

A report full of detail can still leave you with a basic question: which client was this for?

Activity is not intent

An app or tab title doesn’t always say why you opened it.

Suppose your tracker says you spent 45 minutes on Facebook yesterday.

It even captured the page titles:

Sarah Mitchell | Facebook
Daniel Cho | Facebook
Marta Alvarez | Facebook

And 30 more profiles like them.

The names alone don’t separate client contacts, campaign prospects, and company research from old classmates or random clicks from your feed.

In this example, the software recorded the activity without enough context to assign it. You still need to separate the work from the browsing before deciding what was billable.

Automatic capture still needs a person

Tracking time is more than collecting minutes. It is attaching meaning to those minutes.

The same browser tab can serve different clients and projects. A calendar meeting might be billable strategy work or unpaid admin, even when both invitations say “Catch-up.”

Automatic tracking can record the activity. A generic app title cannot distinguish those uses. Rules can help when a window title reliably identifies the project, and automatic capture can recover activity you forgot to time.

For ambiguous blocks, the cleanup still lands on you. You review the blocks, rename them, and delete noise. Then you sit there explaining to yourself why a weird-looking chunk of the day was work.

When most of the day looks like that, the “automatic” part can start to feel less useful.

Review AI labels you cannot explain

If your tracker suggests AI labels, judge them against work you can identify.

A label you can’t verify is not the same as a record you can explain. If next week’s invoice says “Campaign research,” you need to know which work supports that line.

Suggested labels help when they are accurate and save more effort than they take to review. If you must rewrite them, compare that cleanup with naming the work when you start.

You can outsource the logging, but you still need to explain the bill. An AI label alone does not establish what the work was for.

Where the log lives is a separate choice

How a block gets recorded and where it lives are separate choices.

Depending on the tool, an automatic log can hold more detail than the work you meant to record, such as page titles or screenshots. Check what yours keeps, and prefer a record that holds only the blocks you chose to name.

Then check where that history goes and who can read it. Automatic capture alone does not answer that question.

If you want to avoid storing that history on a server, choose a record that stays on your device.

Start and stop on purpose

If you already have an automatic log for this week, do not treat every app block as billable hours. Keep the stretches you can explain, write a note you could read in a week, and set unclear blocks aside. Use messages or your calendar to review them before billing.

If ambiguous blocks take too long to review, try a manual record for the next week:

Start when the block starts. Name the client or project so you can find the time again when you review the week.
Stop when you switch. A new client, a meal, or a different kind of work gets its own entry.
Write one note. Name the work while you still know what the tab was for.
Edit forgotten boundaries. Use notes, messages, or your calendar as clues. Mark uncertain durations as estimates; leave them unknown when the clues are not enough.

If those 45 minutes were one stretch of prospect research for a hypothetical client, Hartwell, the Facebook session could become this entry:

Start	End	Client	Note	Total
13:10	13:55	Hartwell	Reviewed prospect profiles for the Q3 campaign	45m

If the minutes were scattered across the day, or only some profiles were for Hartwell, record only the stretches you can name.

Where TimeRetain fits

TimeRetain is a manual timer for keeping a record you can explain. Keep the client and reason beside the hours, so next week you still know what those 45 minutes were for.

You choose what goes into that record. TimeRetain does not take screenshots or watch your apps and tabs. If you forget a start or stop, you can correct the entry.

No account is required. The primary record stays on your device. If you enable optional Sync, TimeRetain stores an encrypted copy on its servers.

Try TimeRetain for your next client task. Keep the reason for the time alongside the minutes.

Start tracking →