Freelance infrastructure work often starts with a short call and a rough estimate. Behind that estimate sit a dozen unspoken premises: the client has a staging environment, credentials will arrive on day one, a named person can approve changes. This explainer describes the habit of writing down assumptions for each engagement in simple terms, so that you can use it on your next project without extra tooling.
What an assumption means in client work
An assumption is a condition you are relying on, which you have not verified, and which would change your plan if it proved false. It is neither a promise nor a risk in the usual sense. It sits earlier than both. “The application already has automated tests” is an assumption. If the tests turn out not to exist, the estimate for a deployment pipeline grows, and you want to have noticed that on day one.
For a solo practitioner the distinction matters because there is no team to catch the gap. You alone carry the project in your head, and heads are unreliable stores.
Why it suits independent engineers in particular
Freelancers face three conditions that employees rarely do. They enter systems they did not build. They work with partial access. And they often serve several clients in a week, which makes context switching costly. A short written list per client acts as external memory. When you reopen a project after ten days, the list tells you what you believed then and what you had already confirmed.
It also supports professional conversations. If a client asks why the work took longer than estimated, you can point to a specific line, such as “the build server can be reached from the staging subnet,” and the date on which you discovered it was false. The discussion becomes factual rather than defensive.
The anatomy of a useful list
Use three columns, nothing more elaborate.
- Statement: a single clear sentence describing the belief.
- Confidence: high, medium or low, based on what you have actually seen.
- Check: the quickest action that would confirm or refute it, plus who can perform it.
Add a date column if the engagement is long. Mark each row as open, confirmed or wrong. Over time, the proportion of wrong rows tells you something about how well you read new environments.
Examples grouped by area
Access. You will receive administrative rights in the target account. Read-only access suffices for the first week. Multi-factor prompts will not block unattended scripts.
Environment. A non-production copy of the system exists and resembles production closely. The deployment can be rolled back. Secrets are held in a managed store rather than in configuration files.
People. One named contact answers technical questions within a working day. Another person signs off on production changes. The client’s team can attend a short weekly review.
Dependencies. Third-party services stay available during the project. Licences for any required tools are already in place. Network rules allow the traffic your design needs.
If any line in the access or environment groups is low confidence, it is worth settling before you begin billable work, because it can swing the schedule most.
Where the list sits beside your proposal
The list does not replace a proposal or a statement of work; it supports them. When you prepare an estimate, you can read the low-confidence lines and decide whether to add a margin or split the job into a discovery phase and a delivery phase. Newcomers who want general orientation on starting out can read these answers to common questions from people entering freelance DevOps work. Anyone balancing client work with a job will find the assumptions list especially handy, as time is scarce; the discussion of taking on freelance projects responsibly next to full-time employment addresses that context.
Plain-language walkthrough of one small project
Imagine a request to containerise an existing web application. Before quoting, you write six lines:
- The application starts from a single command. Confidence: medium. Check: ask for the current start procedure.
- It stores uploads on local disk, not in object storage. Confidence: low. Check: search the code for file write paths.
- The database is reachable from where containers will run. Confidence: medium. Check: test a connection from a scratch host.
- The client owns the domain and certificates. Confidence: low. Check: ask who renews them.
- Traffic is modest and a single node suffices. Confidence: medium. Check: request a week of access logs.
- Someone on the client side can restart services outside your working hours. Confidence: low. Check: ask directly.
Three low-confidence lines in six is a signal. You might propose a short paid assessment first, or quote a range rather than a single figure.
When one of your beliefs proves false
At some point a row will flip from “believed” to “wrong.” Handle it in four small moves. First, mark the row and add the date and what you found. Second, work out which parts of your plan relied on it, which is usually only one or two tasks. Third, tell the client promptly and in neutral terms: what you assumed, what is actually the case, and how it affects the schedule or effort. Fourth, adjust your estimate for similar future projects by adding a standing question to your intake list.
Clients tend to respond well to this pattern. It shows that you were reasoning openly, and it limits the argument to a single fact rather than a general feeling that the project is going badly. Over a year of engagements, you will see the same wrong lines recur, such as “credentials arrive on day one,” and you can turn them into standard questions for your first call.
Keeping it truthful
The list only works if it is honest. Resist the temptation to raise a confidence rating because the client sounded sure. Sureness is not the same as evidence. And resist making the list a weapon; its job is to organise your own thinking, not to build a case against anyone.
Learning more about the practice
Material on the subject appears in engineering handbooks and training sites. As one example of the latter, NoOpsSchool is an India-based training website that presents itself as running certification courses plus consulting and services for IT professionals. Whatever source you consult, adapt the format to a size that you will actually maintain.
A short checklist to keep nearby
- Create the list on the day you accept the work.
- Write every entry as a sentence another engineer would understand.
- Resolve low-confidence access and environment lines first.
- Update the status whenever you learn something, and keep wrong entries visible.
- Reread the list before each invoice and before each handover of a milestone.
That is the whole method. It takes minutes, it travels with you from client to client, and it turns the vague unease of working in unfamiliar systems into a short list of things you can check.