Who it is for

Three people who want different things from the same drawing.

Today each of them keeps a private version of that drawing in their head, and the versions do not agree. That is the problem underneath most of the others.

Each section below is the same shape: what this person is actually trying to do, where it goes wrong, what changes, and what it does not solve. The last part is there because a page that only lists wins is a page nobody trusts.

  • 3roles, one record
  • 1question all of them ask
  • 0accounts to create
01Resident architect
What moved under Northern Water since March?

Holds the same estate for years, and is the person everyone asks.

You know this customer better than anyone. You also have four others, and IBM has been changing things underneath all five since the last time you looked properly.

Where it goes wrong

Nothing announces itself. A support line closes on a published date nobody re-reads after the design phase. A product you drew as standalone becomes an add-on inside another one, and the licensing position quietly stops adding up. The diagram on the wall looks exactly as correct as it did the day it was approved.

So the checking happens by hand, under time pressure, before a meeting — by whoever is free, from whatever they can find. And it happens again next quarter, from scratch, because nothing recorded what was checked or when.

What changes

  • Monday starts with a list.Open the estate and Atlas reports what is expiring, what was deprecated or renamed underneath them, which constraints bite, and what cannot be evidenced — ranked worst first, no destination required.
  • The second visit is worth more than the first.Because the estate carries the date you recorded it, Atlas can cross that against the evidence archive and tell you what moved in between, with the excerpt as it read on both dates.
  • Five customers, one question.The portfolio ranks every estate you hold by nearest date, with what has already passed held apart from what is coming.
  • The record survives you.An estate exports as a file with its full history. When the engagement moves to someone else, they inherit what you knew rather than starting the discovery again.

What it does not solve. Atlas cannot tell you what the customer actually runs — only what somebody recorded. If the estate is wrong, every reading built on it is confidently wrong, and it will still be marked as your word rather than IBM's. The record is only as good as the half-hour you spend on it.

02Bid team
Discovery call at ten. Sourced draft by four.

Has one afternoon to turn a call into something a client will read.

The facts exist. They are in three people's heads, two old proposals and a documentation site nobody has time to re-read before five o'clock.

Where it goes wrong

Claims go in unsourced, because sourcing each one costs twenty minutes you do not have. Most of them are right. The review meeting finds the ones that are not, and the cost is not the correction — it is that every other claim in the document now has to be re-checked too, because nobody can tell which ones were verified.

The other failure is quieter: the draft describes the product line rather than the customer. It lists capabilities they will never license, because it was assembled from the catalogue rather than from what they actually run.

What changes

  • The draft comes out of the record.Every fact arrives already carrying the page it came from and the date it was read. Nothing has to be sourced afterwards because nothing entered unsourced.
  • Scoped to them, not to IBM.The move is calculated against the elements they actually run: what carries, what changed underneath them, what leaves. What the release merely offers is held apart, so Maximo Aviation does not appear in a transport operator's upgrade.
  • Judgements are marked, not hidden.Atlas marks every place a human has to decide and refuses to write the recommendation, so the reviewer's attention lands where it is actually needed.
  • Six formats, one record.Proposal draft, Mermaid, draw.io, PlantUML, element register, structured export — each carrying the evidence marks, because the diagram is what ends up in a deck stripped of the tool that made it.

What it does not solve. It will not write your proposal. It produces a draft that opens by saying it is a draft, and the argument, the commercial shape and the recommendation are still yours — they depend on appetite, timeline and budget, and none of those are in a catalogue.

03Design authority
How do you know that?

Signs off other people's architecture and carries the risk when it is wrong.

You ask one question all day long. Most of the time the answer is a reassuring tone of voice, which is exactly why nobody notices the times it should not have been.

Where it goes wrong

A box on a diagram carries the same authority whether it came from IBM's documentation or from somebody's memory of a project in 2019. The drawing gives you no way to tell them apart, so either you trust all of it or you re-verify all of it, and there is never time for the second.

The worse failure is the silent one. An element that was considered and could not be established simply does not appear, and an absence on a diagram reads to every reviewer as a decision rather than a gap.

What changes

  • The question gets an answer.Not an assurance — the sentence IBM wrote, the page it is on, and the date it was read. Quoted rather than summarised, because a paraphrase is an opinion wearing a quotation's clothes.
  • You can see what is judgement.Inferred records say so on the drawing, and carry what was searched, so you can check the same pages and disagree with the specific call rather than with the tool in general.
  • Gaps are drawn.Where nobody has established something, it appears on the diagram marked as unknown rather than being quietly left off.
  • The sheet leaves the room.It prints with its key, so the notation is legible to people who will never open the application — which is most of the room.

What it does not solve. Atlas can tell you a claim is unsourced. It cannot tell you whether the architecture is any good. The judgement you are paid for is untouched by this, and deliberately so.

04Where to start

All three of them are reading the same record.

That is the part that is easy to miss. The architect's Monday list, the bid team's draft and the reviewer's answer are three readings of one estate, recorded once.

So the useful first move is the same whoever you are: record one customer properly, and let the rest fall out of it. It takes about five minutes, it stays in your browser, and there is nothing to sign up for.

Record an estate → What it does today →