A desk with scattered papers and a whiteboard

Whatever the inventor gave you, bring it in. The format is the tool's problem.

The check-in counter ... verbatim
Agent
"Sir, this bag does not fit the requirement of the airline."

Imagine hearing that at a check-in counter. Not at some budget carrier you booked at 1am on impulse. At any airline. From any human being working any desk, and I am genuinely not sure what you are supposed to do when the person holding the boarding pass just shrugs at you. You would stare. You would ask them to repeat it. You would look around to see if anyone else was noticing this. Because the bag is packed. The flight is in forty minutes. You are not carrying a surfboard or a cello case or a small horse. You are carrying... your things. The things you need for the trip. And the person at the counter is telling you that the container of your preparation is the problem.

This would be beyond belief. For you or anyone.

So why is it so acceptable when a patent drafting tool throws an error and says: only PDF and Word Doc accepted?

Here is what a patent attorney actually arrives with. Not what the tool expects. What the attorney actually has.

An email chain from seven months ago where the breakthrough was mentioned in paragraph four; almost as an afterthought. The inventor was writing to a colleague about something else entirely. The crucial sentence is buried in the middle of a paragraph about scheduling: "...also tried flipping the process and it worked better; not sure why yet." That is the whole thing. That is the novel claim. In a sentence the inventor themselves had half-forgotten by the time the attorney called.

A photograph of a prototype. Taken on a phone. In a lab. Slightly blurry on one edge because someone's hand was in the frame. The prototype is balanced on a paper cup. There are coffee rings on the workbench behind it. This photograph is irreplaceable because the prototype no longer exists in that configuration; it was disassembled three weeks later and rebuilt differently. The photograph is the only record of the thing that worked.

A WhatsApp voice note. Recorded at 11pm. Three minutes and forty seconds. The inventor explaining the one thing that makes this novel, the way only the person who built it can explain it... not carefully, not for a record, not with the precise vocabulary of a patent claim, but thinking out loud in the way people do when they are finally saying the thing they have been trying to articulate for months.

That is what the attorney arrives with. That is the invention.

The tool says: structured fields only. Maximum 20 MB.

That is not a tool helping an attorney. That is a tool creating work for an attorney so it can then help them; on its own terms.

I spoke to three attorneys about this. Independently. Over two months. All three described the same thing without being prompted to compare notes.

One attorney in Chennai spent four hours trying to upload 42 JPEGs of a prototype built entirely out of duct tape and a broken ceiling fan. He was a senior partner.

They had photographed whiteboards during inventor meetings. Long whiteboards; the kind that are covered in branching diagrams and crossed-out formulas and the kind of shorthand that only makes sense to the people who were in the room for the three hours it took to fill it. And then they had typed out those photographs. By hand. Before uploading. Because the tool would not accept an image.

Three attorneys. Independently. Describing the same workaround. That is not a coincidence or a skill gap or a training issue. That is a design failure with a consistent human cost that nobody who built the tool apparently sat down to calculate.

A hand holding a smartphone, photographing a technical whiteboard covered in patent diagrams, crossed-out equations and inventor shorthand in a lab
The whiteboard. Photographed. Then typed out by hand. Before the work could begin.

Every format restriction a tool imposes tells you something about who it was built for. The PDF-and-Word-only requirement is not a technical limitation. It is a priority statement. It says: we built this for the data we knew how to process. We did not build this for the work you actually do.

This is the failure of experiential architecture; or rather the complete absence of it. The question that should should have been asked at the beginning of every sprint, and was apparently not asked at any of them: what does this person actually walk into this conversation carrying? What does the raw material of their work actually look like before it reaches us?

Because the raw material of patent work does not arrive as a structured PDF. It never did. It arrives as the accumulated record of an idea that someone had; across months of emails and sketches and half-finished thoughts and late-night voice notes and photographs of things that no longer exist. The patent attorney's job is to find the thread inside that material and make it legible to a system that requires extreme precision. That is genuinely hard work. The tool's job is to help with that work. Not to create a preprocessing requirement before the work can begin.

You know why the airline bag thing is so viscerally infuriating? It is not the inconvenience. It is the inversion. You did the work. You packed the trip. You got yourself to the airport on time. And then someone at the last possible moment tells you that the container of your preparation is the problem; not anything inside it.

The attorney did the work. They sat with the inventor for two hours and asked the questions nobody else knew to ask. They found the sentence in paragraph four of a seven-month-old email. They listened to three minutes and forty seconds of a voice note recorded at 11pm to understand what the inventor meant when they said "it worked better; not sure why yet." And then they arrived at the tool and the tool said: wrong format.

The bag is packed. The flight is in forty minutes.

Whatever the inventor gave you... bring it in.

The email chain. The photograph of the prototype on the paper cup. The voice note. The photograph of the whiteboard with the branching diagrams and the crossed-out formulas and the shorthand that only makes sense to the people who were in the room. The WhatsApp message at 11pm where the inventor said the thing they had been trying to say for months in a way that no structured input field would ever have captured.

All of it. That should be enough. The format is the tool's problem to solve. Not the attorney's problem to work around before they can even begin.

The person at the airline check-in counter has a manager they can escalate to. A supervisor who can make an exception. A policy that bends when the situation is clear enough and the flight is close enough.

Legal tech tools do not have supervisors. They have release cycles.

The attorney types out the photograph. The next inventor meeting is on Tuesday. There will be another whiteboard. The attorney will type that one out too. :)

All writing The engine is not the story →