The White Space Between Contracts

There is a particular kind of silence on a résumé that belongs only to people who work in short contracts. It sits between the lines: three months here, six weeks there, then a stretch of nothing, then a run of overlapping projects that seem to contradict the calendar. Anyone who has tried to describe a freelance career on a document designed for long employment knows the feeling. The page was built for one story, and we are trying to tell another.

A form that expects a single thread

The traditional résumé is a narrative of continuity. It assumes that a person moves from one employer to the next, that each step lasts long enough to be named, and that the spaces between steps are short and explainable. In that format, a gap is an absence. It invites a question, and often suspicion.

For someone whose working life is made of engagements rather than positions, the format quietly misrepresents what happened. A gap of two months may have been the most productive period of the year, spent finishing a build for one client while scoping another. A list of twelve contracts may read as restlessness when it was, in fact, steady demand. The trouble is not that the work was fragmented. The trouble is that the document can only show work as a line, and contract work is closer to a field.

It helps to name this plainly, because many independent professionals carry a low, persistent embarrassment about their own history. They compress it, round it off, or hide the smaller jobs. In doing so they erase exactly the evidence that would show how capable and in demand they have been.

What the gaps actually contain

If we look closely at the white space in a contract career, it is rarely empty. It usually holds some combination of the following:

• Time spent winning the next engagement: proposals, conversations, small trial tasks.
• Overlapping work that the résumé cannot display because two lines cannot share the same months.
• Learning that was deliberate, such as picking up a new framework because a client needed it.
• Rest, which is not a failure but part of any sustainable working rhythm.
• Work done under confidentiality, which cannot be named in public at all.

None of this is shameful. Most of it is the ordinary labour of being independent. The difficulty is that a reader cannot see it, and a reader who cannot see something tends to assume the worst.

Reading the record differently

A more honest approach is to stop treating the résumé as the primary record and to treat it instead as a summary of something more complete. What a careful client or employer wants to know is fairly simple: did this person do real work, for real people, and did they deliver? Dates matter, but mostly as evidence of reliability, not as a test of uninterrupted presence.

This is why verified histories have become more interesting than polished narratives. When each contract is recorded at the time it happens, with its milestones and delivery dates, the question of the gap changes shape. Instead of asking "what were you doing in March?", a reader can see that March held two small engagements and the start of a third. The gap closes not through explanation but through evidence.

Some marketplaces have started to build around this idea. https://workli.tech/ describes itself as a place where businesses hire independent professionals for project-based work, with every contract adding to a verified work history on the freelancer's profile. Its Work Passport shows only contracts recorded there, nothing self-reported, along with things like repeat clients and a 24-month activity strip. It is a newer and smaller platform than the established names, but the underlying premise is worth considering whatever tools one uses: the record should be built as the work happens, not reconstructed afterwards from memory.

Practical ways to soften the silence

Even without a verified system, there are habits that make a contract history easier to read.

Group engagements by theme rather than listing them in strict sequence. A section called "Product builds for early-stage companies" with five short projects beneath it reads as a body of work, where five scattered lines read as drift.

Keep a private log with dates, deliverables and the name of whoever approved the work. It does not need to be elegant. It needs to exist, so that when someone asks, you are not relying on recollection.

Acknowledge overlap openly. A short note such as "several engagements ran in parallel" removes the confusion before it forms.

Treat confidential work as real work. You can describe its scope and type without naming the client, and a thoughtful reader will understand.

Ask satisfied clients, at the moment a project ends, whether they would be willing to confirm it later. The goodwill is warmest at the finish, and it fades quietly with time.

The shape of a different kind of career

The gaps in a résumé made of short contracts are not really gaps in a working life. They are gaps in the form we inherited for describing working lives. As more people build careers from many engagements rather than one long tenure, the form will need to bend, and in some places it already is.

Until then, the most useful thing we can do is refuse to apologise for the shape of our own history. The white space between contracts is where much of the real work of independence happens. It deserves to be read with patience, and recorded with care.