How to invoice for meetings without making it awkward

The kick-off call was 90 minutes. It’s not on the invoice.

Neither are the two feedback rounds. Nor the revision discussion that turned into two hours because the client wanted to go through everything live. Three calls. Four to five hours of direct, focused client time. Off the invoice.

You didn’t forget. The billing instinct just didn’t fire the way it would after handing over a deliverable.

Why meetings don’t make it onto invoices

Deliverables have a clear value signal — a file, a mockup, a completed section. Meetings don’t. The call ends, the tab closes, and somehow the time didn’t “produce” anything you can point to.

So it gets absorbed. Not laziness — a category error. You treated client-facing work as overhead.

It isn’t.

Which meetings are actually billable

The test is simple: was this meeting specific to this client and this project? Did it require your professional presence?

Billable:

• Kick-off and briefing sessions
• Feedback rounds and revision discussions
• Progress check-ins (client-initiated or contractually scheduled)
• End-of-project walkthroughs
• Discovery calls after the project has started
• Any session where the client asks questions only you can answer

Not billable:

• Sales and scoping calls (you’re pitching, not working)
• Calls you initiated to correct a mistake on your end
• Administrative coordination — rescheduling, finding a file, recovering access

The first list is client work. An employer would pay an employee for this time without question. You’re not an employee, but the logic is identical: focused time that can’t be used for anything else.

A 90-minute kick-off blocked in your calendar is 90 minutes you didn’t design, write, or build for anyone else. Bill it.

The line item problem

Most freelancers who try to bill meetings get stuck at the invoice. What do you actually write?

“Meeting — 1h” is too vague. It invites the obvious response: what meeting?

Be specific: "Feedback call — homepage revision — 14 March, 1h30". Date, subject, duration. The client remembers the call immediately. Nothing to dispute.

Don’t cluster meeting time at the bottom of the invoice as a separate category. Bill each one where it belongs, alongside the work it relates to. “Feedback call re: first draft” follows naturally after the line for the draft itself. Integrated into the normal flow, it reads as standard billing. Grouped at the end under “meetings: 3h,” it looks like something you added afterwards.

The structure of your invoice signals whether meetings are normal or exceptional. Make them normal.

The clause that removes the awkwardness

Awkwardness comes from ambiguity. If your contract says nothing about meetings, every invoice that includes one is a soft negotiation.

One sentence fixes this permanently:

“Meetings, calls, and review sessions directly related to the project are billed at the standard hourly rate.”

The client agreed to this upfront. Billing it isn’t a request — it’s execution. You’re not asking whether they’re comfortable with it. You’re invoicing for what was agreed.

For existing clients, add the clause at the start of the next project or renewal — not retroactively. For new clients, it goes in before the project starts. It’s not a warning. It’s just information, the same way you’d specify revision rounds or deliverable formats.

Once it’s in the contract, the awkwardness is gone. There’s nothing to justify.

The habit that makes this automatic

The real problem isn’t the invoice. It’s that the hours were never tracked to begin with.

By the time you’re building the invoice, you’re reconstructing. You remember there were calls, but not exactly how long. You find the calendar event, but it was scheduled for 60 minutes and ran 90. You leave 30 minutes off because it seems safer not to argue about it.

The prevention is upstream: tag every client call in your calendar the moment you schedule it. [ClientName] Feedback call. [ClientName] Kick-off. [ClientName] Revision session. That’s the full convention.

Most unbilled time hides in exactly this category — informal interactions that happened but weren’t logged. The fix is the same: get the block into the calendar before the call happens, not after.

Timescanner reads those tagged blocks and totals hours by client automatically. A 90-minute meeting in your calendar is 90 minutes on the billing report. Nothing to reconstruct, nothing to guess. It works with any iCal-compatible calendar — Google Calendar, Outlook, iCloud, Proton Calendar, Notion Calendar.

When a client pushes back

Some clients who’ve been getting meetings for free will notice when that changes.

Keep the response factual: “Per our agreement, meetings and review sessions related to the project are billed at my standard rate. The call on [date] was [duration] — it’s on the invoice.”

Don’t apologize. Don’t offer to split the difference. If it’s in the contract, it stands.

If it’s not in the contract because you added meeting billing mid-project — that’s harder. You’re unlikely to win that argument, and pressing it mid-project damages the relationship without a good payout. Finish the project on the current terms. Add the clause before the next one.

Every project after that, you’re billing correctly from the start.

The calculation worth running

Pick a recent month. Go through your calendar and total every meeting, call, and review session that doesn’t appear on any invoice.

For most freelancers doing this the first time, the number lands between 3 and 8 hours per client per month. At a rate that covers your actual costs, that’s €240–640 per client, per month, consistently not billed.

Across two clients over a year: €6,000–15,000. Not extra work — work already done.

That’s what the habit is worth.

Timescanner reads tagged calendar blocks and totals hours per client automatically — meetings included. No manual entry, no reconstruction. Works with any iCal-compatible calendar.