Freelancing gives you freedom, and also nobody who asks on Monday morning whether last week went well. If you are a DevOps freelancer, you are the delivery lead, the account manager, the bookkeeper and the support desk at once, and the only way I know to keep all those hats from sliding off is a weekly review. Here are eight things worth looking at in yours, in a friendly order you can run through in about half an hour.
Quick note: this is general workflow advice for independent engineers, not tax or financial guidance. For anything involving money rules, ask a qualified professional where you live.
1. Hours and deliverables: what did you actually do?
Open your time notes, calendar and commit history and write three sentences about the week. Where did the time go, and was that where it should have gone? Freelancers often discover that a “quick favour” for one client quietly ate a whole afternoon. Seeing it in black and white is the first step to either pricing it or declining it next time.
2. Open client threads: who is waiting on you?
Scan your inbox and chat tools for messages you have not answered. List each client with a single line on what they are waiting for. Replies you owe are the most common source of damaged trust, and they are also the cheapest thing to fix. Send the short answers on the spot and put the longer ones on next week’s list with a day attached.
3. Things you are waiting on: who is holding you up?
The mirror image of item two. Access you asked for, feedback on a pull request, a decision about an environment. Note each blocked item with the date you asked. Anything older than a week deserves a polite nudge. Writing that nudge during the review, while it is on your mind, beats remembering it at midnight.
4. Invoices and paperwork: is the admin keeping pace?
Check that invoices for finished work have gone out and that receipts for work expenses are saved somewhere sensible. Admin that is done weekly takes minutes; admin saved up for the month’s end takes an evening. Keep this to bookkeeping hygiene and leave advice on tax questions to professionals; the site has a useful general read on first-year tax habits for DevOps freelancers if you want a starting point for your questions.
5. Pipeline of work: what is coming next?
List the conversations you have going with prospects and past clients. Who needs a follow-up? Who went quiet and deserves a friendly check-in rather than silence? A freelancer without a short, current list of leads is a freelancer who panics when a contract ends. Even one outbound message per week keeps the pipeline warm.
6. Your own skills: what did you learn, and what do you need?
Write down one thing you learned this week, even something small like a better way to structure a Terraform module or a monitoring gotcha. Then name one thing you wish you knew. Over a few months that second list becomes a personal curriculum, and it is the best guide to what to study in your unpaid hours.
7. People: who helped, and who could you help?
Independent work can be lonely, so use the review to spot connections worth keeping alive. Did someone answer a question for you? Say thanks. Did you see a job that suits a peer? Pass it along. The article on building a dependable freelance support network goes deeper, but a single kind message a week already does a lot.
8. Next week’s three: what will make the week a good one?
Finally, look ahead. Choose three things for next week: the most important delivery, one admin or marketing task and one item that protects your energy, such as blocking a day off. Put them where you will see them on Monday. If a week has no room for rest, plan it in; burnout is the freelancer’s most expensive failure.
A tiny extra for freelancers who work with hiring teams
Many DevOps freelancers end up helping companies onboard engineers or contractors. If that is you, it helps to know how HR teams think about the joining period. One product aimed at that world is DayOneFlow, a web app for HR departments; according to its pages, it covers the span from an accepted offer through to confirmation as an employee. Knowing such tools exist makes your technical handover notes easier to fit into a client’s process.
Making the review a habit
Pick a fixed slot, perhaps Friday afternoon or Sunday evening, and guard it like a client meeting. Keep one running file, newest entry first, and reuse the same eight headings, so you never face a blank page. If thirty minutes feels like too much, shorten the sections rather than skipping the review; a rushed review still beats none.
Do not worry about doing it perfectly. The first couple of reviews will feel clumsy, and you may find some headings do not suit your kind of work. Swap them. The structure matters less than the regular act of stepping back.
One more tip: end every review by closing your laptop for a minute and asking how the week felt, not just how it went on paper. A job that looks fine in a tracker can still be wearing you down, and the review is the only scheduled moment where you can notice that and adjust your workload, your rates or your client mix before it becomes a problem.
A quick recap
- Look back at hours and deliverables.
- Clear the replies you owe.
- Chase what is blocking you.
- Keep admin current.
- Feed the pipeline.
- Note your learning.
- Thank people.
- Pick next week’s three.
Run that list for a month and see how it feels. Most freelancers I talk to report fewer Sunday-night worries and fewer dropped balls, and that alone makes the half hour a bargain.