Skip to content
allanninal.dev/build
Collaborate

Part 4 of 7 · Offer letter generator series ~5 min read

How an unusual term stops the draft

This is the only hard stop in the whole series. Everywhere else, a system that cannot proceed flags something and carries on with what it can. Here it produces nothing at all, and the reason is that a partial offer letter is more dangerous than no offer letter.

Key takeaways

  • An unmatched term produces no document at all, not a document with a gap in it.
  • The request names the term, quotes what was agreed, and asks for wording.
  • Approved wording enters the library as a versioned clause, so it is instant next time.
  • The person who approves clauses is not the person who agrees offers, and that separation matters.
  • Repeatedly requested clauses are the clearest signal that the library is out of date.

Why a hard stop

The soft option is to produce the letter with a placeholder: “[relocation terms to be inserted]”. It seems helpful and it is how offer letters go out with square brackets in them, which happens more often than anybody admits and reads exactly as unserious as it sounds.

The worse version is a letter that simply omits the unmatched term. The candidate agreed a relocation contribution in a conversation, the letter does not mention it, and nobody notices until they ask about it three months in. At that point the written contract does not include a term that was genuinely agreed, and unpicking that is expensive in a way no software saving justifies.

What happens when a term has no approved clauseA vertical chain of five steps entered by a box labelled An unmatched term, with no approved clause. Step one stops the draft and produces nothing. Step two tells the hiring manager which term and why. Step three asks for wording from whoever approves clauses, who is not the hiring manager. Step four adds the approved wording to the library, versioned and dated. Step five resumes the draft automatically. A note says next time this term appears none of these steps happen, which is the compounding bit.AWS ACCOUNTAn unmatched termno approved clauseStop the draftproduce nothingTell the hiring managerwhich term, and whyAsk for wordingfrom whoever approvesClause ownernot the hiring managerAdd to the libraryversioned, datedDraft resumesautomaticallyNext time this term appears, none of these steps happen. That is the compounding bit.
Fig 1. What an unmatched term triggers. The value is in the last box: a clause approved once makes every subsequent offer with that term instant.
  • Database
  • App integration
  • Machine learning
  • Security & identity
  • Management
  • People

What the request says

Four lines to the clause owner

  • Line one. The term, as agreed. “Relocation contribution of £2,000, payable after three months.”
  • Line two. Who agreed it and with whom, so there is context rather than an abstract request.
  • Line three. The nearest existing clause, if there is one. “Closest we have is the relocation clause used in 2024, which was a fixed sum payable on the start date.”
  • Line four. What is blocked. “One offer is waiting on this — K. Osei, agreed today, start date 28 August.”
  • One box. Paste the wording. That is the whole interaction.

The third line does most of the work. Somebody being asked to write a clause from nothing will take a week; somebody being shown the closest existing clause and asked whether a variant is acceptable will usually reply the same day, because the task has become a comparison rather than a composition.

Who approves clauses

Deliberately not the hiring manager. The whole safety property of this system rests on the letter containing only approved wording, and if the person who agreed the terms can also approve the wording for them then approval means nothing.

In a small business this is usually the owner or whoever holds the relationship with your employment solicitor. It does not have to be a formal role; it has to be a different person, and the system enforces that by refusing to accept a clause approved by the same address that submitted the terms.

Repeated requests are a signal

What it means when the same clause is requested repeatedlyA horizontal row of five boxes. Requested: a four-day week clause, three times. Approved each time: slightly differently on each occasion. The signal: this arrangement is now standard. Add it properly: as one approved option. Never asked again: and consistent from then on. A note says three ad-hoc approvals is three slightly different clauses in three contracts.THE SAME REQUEST, THREE TIMESRequested4-day week, 3 timesApproved each timeslightly differentlyThe signalthis is now standardAdd it properlyone approved optionNever asked againand consistentThree ad-hoc approvals is three slightly different clauses in three contracts.
Fig 2. What a repeated clause request means. The second box is the real risk: ad-hoc approvals of the same thing produce inconsistent contracts.
  • Machine learning
  • Management
  • Analytics

That inconsistency is the quiet cost of not having a library at all, and it is invisible until somebody compares two employees’ contracts. Counting requests makes it visible the third time rather than the thirtieth.

Next: what a sent offer leaves behind.

All posts