From Evidence to System: Your Business Needs to Remember Without You

Over the last three modules, we’ve been building this one piece at a time.

First, we looked at the difference between doing something sustainable and being able to make a claim about it. Then we went looking for the evidence your business is already producing.

Last week, we started reading that evidence differently: what does it actually tell us, what doesn’t it tell us, and where could that information be useful?

So now you have evidence.

Maybe you have invoices, proofs of payment, supplier information, production records, patterns, photographs, repair messages and agreements. That’s a good start, but having evidence and having an evidence system are two different things. A folder full of documents is not necessarily a system, especially if the only reason anyone can find anything in it is that you remember where you put it.

I have a rule about records: if I ask you for something, you should be able to produce it within 48 hours. Honestly, in most situations I would hope it takes considerably less time than that, but 48 hours is generous enough to account for real life while still asking a useful question: does your business actually know where its information is?

I’ve experienced both sides of this inside OneThread. There was once a disagreement between Liam and me about whether something had been included in an earlier product document. I knew I had written it, but more importantly, I knew roughly when I had written it and how I had sent it. While we were still on the phone, I searched my email, found the original message, found the document attached to it, screenshotted the email, resent the document on WhatsApp and pointed him to the relevant sections.

I didn’t remember every sentence of a roughly 30-page document, and I didn’t need to. The information had been preserved somewhere I could retrieve it. The business had a memory outside of my brain.

I’ve also experienced the opposite. Someone was sure they had sent me a document. I was sure I hadn’t received it. We checked the inbox and the outbox, and it turned out it hadn’t actually been sent. The document existed. The intention to send it existed. But the transfer we thought had happened had not happened, and there was no record showing otherwise.

Those examples sound incredibly ordinary because they are. Evidence systems are built around ordinary moments like these.

Your Notebook Can Still Be a System

This is usually the point where talking about “systems” starts to sound like I’m about to tell a small business to buy expensive software. I’m not.

A notebook can be part of a system. Google Drive can be part of a system. A spreadsheet can be part of a system. Physical folders can work. Dropbox can work. Airtable can work. There are also entire platforms, including ours, designed to help businesses structure and manage this kind of information. The technology is not what magically turns information into a system.

What matters is whether there is a repeatable process around it.

Imagine that every time your business purchases fabric, the person making the purchase saves the invoice on the same day. It goes into a folder called Sourcing, then into the relevant year, then under the supplier. The supplier, material, quantity, price and purchase date are also added to a sourcing sheet.

Now we know what is being captured, who is responsible for capturing it, when they should do it, where the information lives and how we can retrieve it later.

That is a system.

It doesn’t have to be technologically impressive. It has to work consistently enough that the information is there when you need it.

Your Business Cannot Depend on Your Memory

This can be particularly difficult for founders because, in the beginning, we often genuinely do know where everything is. The supplier’s number is somewhere in the WhatsApp conversation from April. The correct pattern is the file called FINAL FINAL 2.

You remember which invoice belongs to which collection, and you remember what was agreed during the phone call because you were the person on the phone.

For a while, that can work. Then you get sick, you travel, someone joins the business, six months pass, or the company simply grows to the point where remembering every conversation, payment, supplier, document, and decision becomes impossible. Even if you remain a solo founder, Future You still needs to understand what Present You was doing.

This is why I keep coming back to the idea that a business cannot scale if one person’s memory is its operating system.

The goal isn’t to remove people from the business or document every human interaction until running a creative company feels like filling out government forms. It’s to identify the information that the business genuinely needs to remember and make sure that information doesn’t disappear when the person who knows it is unavailable.

Start With Three Things, Not Thirty

Once you realise that your business needs better systems, there is a temptation to fix everything at once. Suddenly every folder needs reorganising, every old invoice needs renaming and you’ve somehow spent an entire weekend designing a database instead of running your company.

You do not need to do that.

Go back to the Evidence-to-Opportunity Map you completed in Module 3 and look at the records you discovered were genuinely useful. Choose three.

Maybe your fabric invoices turned out to be useful for costing, supplier history and material traceability. Start there. Maybe customer repair requests are giving you useful information about product quality, so you decide to create a simple repair log. Maybe your payment records are scattered between your email, WhatsApp and banking app, and you need one consistent place where the relevant records are preserved.

For each of those three records, you only need to answer five questions: What are we keeping? Who captures it? When? Where does it live? How do we find it again?

Your answers do not need to sound impressive. “After every repair, I record the product, the problem, what we did to fix it and the date in this spreadsheet” is a perfectly good system. What makes it useful is that the next repair gets recorded too, and the one after that. Eventually, you have information you can actually learn from instead of three repair conversations buried somewhere in your WhatsApp history.

That is how information stops being accidental.

Now Give Your System to Someone Else

Once you’ve designed your first evidence system, I want you to do something slightly uncomfortable: give it to somebody else.

Choose one record and ask another person to find it. If you have a team, ask someone who doesn’t normally manage that information. If you don’t have a team, ask a friend, your partner or someone who has absolutely nothing to do with your business.

Tell them what they are looking for, but don’t tell them where it is.

Then let them try.

If they have to ask which folder you mean, write that down. If they don’t understand one of your abbreviations, write that down too. If they find four documents with almost identical names and have no idea which version is current, that is useful information. If they eventually turn to you and ask, “Okay, but where do you actually keep these?” then your system is still relying on something that only exists in your head.

The real test of a system isn’t whether you can use it. You built it. Of course it makes sense to you. The test is whether someone else can.

And if they can’t, that doesn’t mean you’ve failed the exercise. It means the exercise worked. You’ve found the part of the system that needs to become clearer. Fix it and test it again.

You Are Teaching the Business How to Remember

There is a reason we didn’t start this learning series by telling you to build a sustainability evidence system. If we had, you could have ended up creating folders for documents you didn’t understand, collecting information because somebody told you it was important and building a beautifully organised archive without knowing what any of it was actually for.

Instead, we started with the business you already have.

We looked at what you are actually doing and what you can reasonably say about it. We identified the evidence your business already produces. Then we looked at what that evidence actually tells you, what it cannot tell you on its own and where the information might be useful.

Only now are we asking which of those records are important enough that your business should make sure they exist every time.

That is what your First Evidence System is for. Choose three records and decide what gets captured, who captures it, when it happens, where it lives and how somebody finds it again. Then put your system through the 48-hour retrieval test.

Documentation isn’t about making a small creative business behave like a giant corporation. It isn’t about creating paperwork for the sake of paperwork. It is about making sure the knowledge your business creates doesn’t disappear.

Your business should be able to remember what it bought, what it made, who it worked with, what went wrong, what changed and what it learned. As that record grows, so does your ability to understand what happened and, when necessary, prove it.

A good evidence system is simply a way of making sure your business can remember without you having to remember everything for it.

That is the foundation we’re building.