Logging hours in the work diary

On an hourly contract you log the time you work and the client approves it weekly. The cycle is simple; the habits around it determine whether you get paid smoothly or spend your weeks explaining yourself.

The cycle

1. The client funds a buffer covering the coming week before it starts.
2. You work and log hours as you go.
3. The week closes on a fixed boundary.
4. The client reviews and approves.
5. Approved hours release to your wallet.
6. The buffer tops back up for the following week.

The important reassurance: the money for the week is already funded before you start it. You are never working against an unfunded promise. If the client's payment fails, you are still paid for hours you already logged and approved, out of money already held.

Logging as you go, not at the end

Log daily. Reconstructing a week on Friday afternoon produces vague notes and hours you are unsure about, and both show.

It also protects you. A diary written as the work happened is a contemporaneous record. One written from memory five days later is a reconstruction, and if a week is ever queried the difference matters.

The notes matter more than the numbers

This is the part most freelancers underinvest in, and it is the single biggest determinant of whether your weeks get approved without friction.

A client looking at "8 hours — development" has no idea what they bought. A client looking at "3h fixing the checkout validation bug, 2h refactoring the cart reducer, 3h writing tests for both" knows exactly, and approves without thinking about it.

Good notes are not about proving you worked. They are about making approval easy. A client who has to ask what the hours went on is a client who delays, and delay costs you.

Write them as you log, in a sentence, in plain language. It takes seconds and it is the cheapest insurance available to you.

The weekly hour cap

The contract sets a maximum you can bill in a week. It is what makes an hourly arrangement safe for the client, which is why they agreed to it.

Do not exceed it and expect payment. Hours beyond the cap are not funded, and there is no obligation to pay them.

If the work genuinely needs more time, raise it before you do the hours. The cap can be increased, which funds the difference. Working over and asking afterwards puts the client in the position of paying for something they did not agree to, and it is the fastest way to sour an otherwise good contract.

If you are consistently hitting the cap, that is a conversation about the arrangement, not something to absorb quietly.

Approval

At the end of the week the client reviews and approves. Approved hours release to your wallet, then go through clearance before you can withdraw. See How and when you get paid.

If the client does nothing, the week auto-approves after a period and releases. This protects you from a client who goes quiet — you are not dependent on their attention to be paid.

If a client approves fewer hours than you logged

It can happen. Take it in order:

Ask why, calmly and specifically. There is usually a reason, and often a misunderstanding — work they thought was in a previous week, or a task they did not realise had been agreed.

If it was a misunderstanding, it is usually resolved by explaining, and the remainder can be handled in the following week.

If you disagree and it is not resolved, the dispute process exists. Your work diary notes are the evidence, which is the practical reason to write them properly.

If it becomes a pattern, end the contract. A client who routinely cuts hours is not one to keep working with, and continuing to hope it improves costs you more than the contract is worth.

When the contract pauses

Either side can pause, and a pause returns the unused buffer to the client. Your approved hours are unaffected — they were released when approved.

A failed client payment also pauses the contract. You are paid for approved hours from the funded buffer; the contract simply stops rather than continuing unfunded. This is the system protecting you, not a problem with your account. The client fixes their payment method and reactivates.

If a contract pauses and you were mid-task, log the hours you have already worked before it closes.

Ending

Either side can end an hourly contract. The final week settles normally and the unused buffer returns to the client.

Do not simply stop working without ending it. An abandoned contract damages your completion rate, which is weighted heavily in your rank. If you need to stop, say so and end it properly — the record shows a completed engagement rather than an abandoned one.

Practical habits

Log daily, with a real note.

Never bill time you did not work. It is the one thing that will end an account rather than earning a warning.

Flag blockers immediately. Logging four hours against "waiting for client feedback" is not billable time and looks like padding. Say you are blocked instead.

Watch the cap through the week, not on Friday.

What a good diary entry looks like

Compare these two entries for the same three hours.

Weak: "3h — development."

Strong: "3h — fixed the checkout validation that was rejecting valid postcodes, added tests for the three cases we found, deployed to staging."

The second one gets approved without a question. It also protects you completely if the week is ever queried, and it takes about fifteen seconds longer to write.

The rule of thumb: write the entry so that somebody who was not there can tell what changed.

Managing time across several contracts

If you are running more than one hourly contract, log against the right one as you go rather than reconstructing later. Reconstruction is where mistakes happen, and a mistake here looks like billing for time you did not work even when it was genuinely an error.

Watch each contract's weekly cap separately. Hitting one cap does not free up hours on another.

And be honest with yourself about total capacity. Two contracts at twenty hours a week is a full week with no slack for anything going wrong, and something always does.

Non-billable time

Some time is genuinely not billable and logging it damages trust badly.

Waiting for the client to respond is not billable. Learning a technology you said you already knew is not billable. Redoing work you got wrong through your own error is not billable.

Time spent understanding the client's existing systems generally is billable, and so is time in meetings they asked for, but say so in the note rather than folding it into something else.

If you are blocked and cannot work, say so in a message rather than logging hours against waiting. Clients notice, and it is the fastest way to lose one.

Getting the first week right

The first week of an hourly contract sets expectations for the whole engagement.

Log daily from day one, with real notes. Do not wait to see whether the client is the sort who checks — establish the habit before it matters.

Check in mid-week with a short summary of where things are. It takes two minutes and it is what makes a client comfortable with hourly work, which is otherwise the model clients find most nerve-wracking.

Raise anything unexpected immediately rather than at approval. A surprise in the diary is worse than a message about it three days earlier.

When the cap is too low

If you are consistently hitting the weekly limit, the arrangement is not right and pretending otherwise helps nobody.

Say so, with specifics: what is taking the time, what is not getting done, and what limit would actually fit. Clients raise caps routinely when there is a reason, because the alternative is work not progressing.

What not to do is work over the cap and hope. Hours beyond the cap are not funded, and asking to be paid for them afterwards puts the client in the position of paying for something they never agreed to. It is the fastest way to sour a contract that was going well.

Ending an hourly contract cleanly

Log everything you have worked before the contract closes, then let the final week settle normally.

Hand over properly: where things are, what is unfinished, anything the next person needs to know. Hourly contracts are often ongoing work with no natural end point, which makes the handover more important rather than less.

Then it records as a completed engagement, which is what your rank and your reviews are built from.

Common questions

Can I log hours for a past week? Log as you go. A late entry is possible but harder to justify if the week is queried.

What if I forget to log a day? Add it as soon as you notice, with an accurate note.

Is time in meetings billable? Generally yes if the client asked for the meeting. Say so in the note.

What if the client disputes my hours? Your diary notes are the evidence, which is the practical reason to write them properly.

Related

• How and when you get paid
• Delivering work and handling revisions
• Disputes and mediation