The contract was signed on a Tuesday, and by Friday the freelancer already had the feeling that something was off. The work itself was not hard: tidy up a start-up’s deployment pipeline, move a handful of services onto a managed container platform, leave behind clear notes. But the repository invitation had not arrived, the cloud account was still locked behind a manager’s approval, and the first invoice had been “forwarded to finance” days earlier. What follows is how a remote DevOps pair learned to keep a waiting-for list, and why it saved their next project.
The first project, and the quiet drift
The two of them, a freelance DevOps engineer and a part-time colleague who handled monitoring and documentation, had worked together for about a year. Both were comfortable with technology. Neither was comfortable with chasing. Chasing felt like nagging, and nagging felt like a risk to the relationship with a client who might send more work.
So they waited politely. The repository access came on the second Monday. The cloud permissions arrived the week after. The invoice, sent on the first Friday, was still unpaid in week five. Each delay seemed small on its own. Together they added up to a project that should have taken a month and stretched across two, with the freelancers working evenings to make up time that was lost on idle days.
When they reviewed what happened over a video call, the part-time colleague said something that stuck: “We never lost days because of the work. We lost them because we couldn’t remember who we were waiting on.”
The evening they wrote it all down
That night they opened a shared spreadsheet and listed every outstanding request from the past six weeks. Seeing them together was a small shock. There were eleven. Some were already resolved and simply forgotten. Three were still open, one of them the unpaid invoice.
They gave the sheet five columns: what was asked, who owes it, when it was asked, how it was asked, and the day to follow up. A sixth column, added a week later, simply read “what this holds up.” It turned out to be the most persuasive one, because it explained at a glance why a late reply mattered.
“It looked almost insultingly simple,” the freelancer later told a friend, “but it was the first time I could see the whole picture on one screen.”
The first nudge
On the Monday after, they sent their first scheduled follow-ups. The invoice reminder was the one they dreaded. The freelancer wrote three short lines: the date it was sent, the invoice reference, and a polite request to confirm that it had reached the right person. No apology, no edge.
The reply came within the hour. The invoice had been sitting with an assistant who had gone on leave, and nobody had noticed. It was paid that week.
That reply changed how they thought about chasing. The client was not ignoring them; the request had simply fallen through a gap, as requests do. A friendly reminder on a predictable date was not rude. It was help.
Building the habit into the week
They agreed on a routine. Every Monday morning, before touching any code, the freelancer would read down the list and send whatever reminders were due. On Thursdays, the colleague would glance at it again and update the status column. If an item had been nudged twice with no response, it went into a short note for the client’s main contact, setting out the date it was first requested and what it was holding up.
They also began adding to the list during client calls. When someone said, “I’ll send you that tomorrow,” one of them typed the item into the sheet while the call was still running, with a follow-up date two working days away. It took ten seconds, and it removed the need to hold the promise in memory.
The second project
Three months later they signed a new client, a small online retailer that wanted its release process modernised. This time they started the sheet on day one. Before the kickoff call finished, it held seven rows: repository access, staging credentials, the name of the person who approves production changes, the list of existing scheduled jobs, a decision on logging retention, the payment schedule and a contact for the domain registrar.
Several items arrived within a day. Others slowed. By Wednesday, the credentials row was flagged amber and the freelancer sent a one-line reminder explaining that the first task could not start without it. By Thursday it was in hand. In the old days, the same stall would have cost a week.
The retailer’s operations manager commented on the final call that the engagement was among the smoothest she had run, partly because she always knew what was needed from her side and by when. The freelancers had not explained the sheet to her. It had simply shaped how they asked.
The conversation that nearly went sour
Not every reminder landed gently. Midway through the second project, one request sat unanswered for ten days: a decision on whether logs from the old servers had to be kept after the migration. The freelancer had nudged twice by email. Frustration crept into the third draft, a message that began with the word “Unfortunately.”
Before sending it, they looked at the row instead. It said what was asked, the date, the two earlier reminders, and the line in the last column: “holds up decommissioning of the old servers.” Reading that, the freelancer rewrote the note to say exactly that, in a friendly tone, and offered to join a five-minute call to settle it. The answer came back the same afternoon.
The sheet had done something beyond tracking. It had supplied the facts in a calm form, which made it easier to stay calm too.
What the story teaches
The lessons they took from the experience are easy to copy:
- Silence is not agreement. A request with no reply is an open item, not a closed one.
- Dates make reminders polite. Deciding in advance when you will ask again removes the awkwardness of choosing in the moment.
- Record what it holds up. Linking each delay to its consequence makes the case for a prompt answer without any pressure.
- Park it in plain sight. A sheet buried in a folder does the job of no sheet at all.
If you are earlier in your own freelance journey, our guide for newcomers to DevOps freelancing covers the basics of getting started, and the habits above slot in easily alongside them. The same goes for relationships with clients; our article on earning trust from clients who are working with you for the first time notes that dependable communication is a large part of how trust forms, and a predictable follow-up rhythm is one visible form of it.
When the work is a side hustle
The technique matters even more for people who freelance around a full-time job. With only evenings and weekends to spare, an idle day waiting for access is a day you cannot recover. Should that describe you, the article on freelancing responsibly alongside a day job will resonate; a short waiting-for list costs almost nothing and guards the few hours you have.
A note on life outside client work
Eventually the two freelancers started using the sheet for personal errands as well. One of them, researching a flat to buy, spent some time reading general guides on Propraahi, an Indian site with property research material and discussion for home buyers, and kept a tab of questions sent to different people with the date each was asked. Nothing about it was complicated. It was the same tidy table, pointed at a different kind of waiting.
Try it for the next client
You do not need a perfect setup. Open a blank sheet before your next kickoff. Add a row for every promise made to you in that first call, with the person responsible and a date two or three working days away. On the day each date arrives, send a short, warm reminder. Strike rows as answers come in. Within a fortnight you will probably notice what the two freelancers noticed: the projects feel calmer, the clients feel looked after, and the invoices get paid on time.