Keeping my blog on track while holding down a part-time gig

Running a personal blog while working a part-time job is something a lot of Australian creators quietly juggle. Between penalty rates, casual shifts, and the cost of smashed avo brunches that somehow still feel reasonable, finding time to publish consistently can feel like trying to fold a fitted sheet on a windy Bondi afternoon. The trick I've landed on isn't glamorous, but it works: treat the blog like a second job with its own roster, build small repeatable habits, and accept that consistency is a workflow problem, not a willpower problem.

This piece walks through the practical systems I rely on to keep publishing on schedule. It's aimed at bloggers who work shift-based or casual roles, have unpredictable weeks, and want to stop letting the calendar win. None of this requires fancy software or a co-working desk in Surry Hills. Just a few honest habits, some scheduling muscle, and a willingness to protect your posting rhythm the same way you'd protect a Friday arvo off.

Treating the blog like a rostered shift

When I picked up my part-time role at a physio clinic in Brisbane, the first thing I did was block out my shifts in Google Calendar the same way my employer did. Then I did the same thing for the blog. Every Tuesday and Thursday evening from 7 pm to 9 pm AEST is "blog time," and the calendar entry is labelled like a real roster, not a wishful reminder. Treating it as a non-negotiable slot means I'm far less likely to slide it when something unexpected pops up, like a last-minute shift swap or a mate asking me to grab a beer at the local in New Farm.

The mindset shift matters as much as the calendar entry. Most part-time workers already understand that a rostered shift is something you turn up to, even on days you don't feel like it. I've started applying the same logic to writing, editing, and scheduling posts. If it's on the roster, I show up. Some sessions are gold, some are mediocre, but the slot exists either way. That's how streaks survive flat weeks, when motivation tanks or the Brisbane heat makes staring at a laptop feel unbearable.

I also colour-code everything. Green is paid work, blue is the blog, and grey is personal. Seeing the week laid out in three colours makes it obvious when balance has drifted, and gives me a clear visual cue to push a personal commitment rather than a blue blog block. It takes about ten minutes to set up, and it stops the vague feeling of "I should write today" from floating around unanchored.

Batching content on my days off

The single biggest change to my posting rhythm has been batching. Rather than writing one post a day across the week, I carve out a four-hour block on Sunday morning and try to draft two or three posts in one sitting. I usually start with a flat white from the local café and a quick brainstorm in a Notes app, knocking out rough outlines before any single sentence gets polished. That Sunday session also covers images, internal links, and the metadata I forget about if I leave it until the day of publishing.

The benefit of batching is that it smooths out the variability of part-time work. Casual shifts at the clinic sometimes get added with only a few days' notice, especially around school holidays when other staff take leave. If I'd planned to write one post each weekday evening, a surprise Saturday shift would derail the entire week. With batching done up front, the rest of the week is mostly editing, scheduling, and replying to comments, which can fit into much smaller windows.

There's a real Australian flavour to this approach too. Sunday is when a lot of us catch up on errands, watch the AFL, or head to Bunnings for that one thing we definitely don't need. By booking out a chunk of the morning for content, I'm being realistic about how the rest of the day will go. The blog is finished before the footy starts, and the week's publishing is locked in.

Scheduling tools and quiet automation

A consistent posting schedule is nearly impossible to maintain if every step of publishing is done manually on the day. I lean heavily on WordPress's built-in scheduler, which lets me load up a week or two of posts in advance and walk away. Once a post is queued, the system publishes it at the right AEST or AEDT time, depending on daylight saving. That means a post written on a Sunday can appear on Wednesday at 7 am without me touching anything, even if I'm up at 5 am for an early shift at the clinic.

Beyond the native scheduler, I use a handful of small automations that remove decisions. A plug-in handles social sharing the moment a post goes live. Another tool pulls draft posts into a Trello board so I can see what's queued versus what's still being written. Email subscriptions run through a service that batches the weekly newsletter automatically, drawing from whatever's been published in the last seven days. None of this is revolutionary, but together it removes about twenty minutes of fiddling per post, and that compounds across a month.

The other piece of automation is backups. Australian internet can be patchy in some suburbs, especially during storms or peak evening hours on congested NBN nodes. I back up the site to a cloud drive every Sunday night, which doubles as a routine that closes the week's batching session. If something breaks, recovery takes minutes rather than days, and I can keep publishing without panic.

Managing energy, not just time

Plenty of bloggers talk about time management, but for shift workers the harder problem is energy management. A 6 am physiotherapy shift in Perth or Adelaide leaves me cooked by mid-afternoon, and writing detailed tutorials at 9 pm is a losing battle. I learned the hard way that scheduling my hardest writing tasks after a draining shift is a recipe for short, sloppy posts that need redoing.

Instead, I match the task to the energy window. High-focus work like outlining, writing introductions, and editing lives in the morning of my days off, when my brain is actually cooperative. Lower-effort tasks like uploading images, formatting, and replying to blog comments happen in the evenings after shorter shifts. This sounds obvious, but it's tempting to "just write whenever" when a deadline is approaching, and the quality drop is obvious in the analytics a week later.

Seasonal realities matter here too. Australian summers can be brutal, and sitting in a non-air-conditioned home office through a 38-degree Brisbane day is not where good writing happens. I keep a desk fan, plenty of water, and accept that some January weeks will be lighter than May weeks. Working with the climate rather than against it has saved me from burning out twice.

Saying no to scope creep

Consistency breaks down fastest when the blog's scope quietly expands. A new affiliate partnership, a sponsored request, a redesign, a podcast idea, a fresh newsletter cadence — every one of these is a real opportunity, but each one adds work to a calendar that was already full. I learned to keep a "later" list, separate from the publishing calendar, and to evaluate every new idea against the same question: does this help me hit my current posting rhythm, or does it compete with it?

If something competes, it goes on the later list with a rough date for reconsideration. This is especially useful for sponsored content, which can be tempting when a brand reaches out with a reasonable budget. The part-time job still pays the rent, and the blog's main job is to keep publishing reliably. A sponsored piece that pushes my schedule back a week isn't worth it, no matter how nice the brand is on the call.

I also batch small admin tasks together. Invoicing, affiliate payouts, plugin updates, and email triage all happen on a single Friday afternoon rather than scattered through the week. That small boundary stops blog admin from seeping into every evening and keeps the calendar honest.

Reviewing and adjusting every month

The final habit is the simplest, and the one most likely to get skipped: a monthly review. On the first Sunday of each month, I sit down with a coffee, open the analytics, and look at what actually got published versus what I planned. The point isn't to beat myself up about missed targets, but to spot patterns. Maybe my Thursday evening slot is consistently underused because I'm usually shattered after a back-to-back shift day. Maybe batching on Sunday morning is the only thing that works, and everything else is theatre.

These reviews have led to small but useful changes. I moved one of my weekly slots from a Wednesday evening to a Saturday morning after noticing I never used the Wednesday slot during casual weeks. I dropped a low-performing newsletter segment that was eating time. I added a recurring "commenting on other blogs" block to Sunday afternoon, which has done more for traffic than any single new post.

Consistency isn't about being perfectly productive. It's about being predictable to your readers and to yourself. A part-time job gives structure that a lot of full-time bloggers have to manufacture from scratch, and that's actually an advantage if you treat the schedule like the asset it is. The blog keeps publishing, the shifts keep getting picked up, and the rhythm holds even when individual weeks don't.