Introducing Owarelin Records

Hello, my name is Oumar Dicko, and I am the founder of Owarelin.

Before talking directly about Owarelin Records, I think it is important to explain where Owarelin comes from.

Technology is now part of everyday life. We use it to communicate, work, store documents, share information, and make decisions.

Inside an organization, almost every action eventually creates or moves information: a message, a document, an approval, a comment, a decision.

Little by little, that information ends up in several places, between several people, with several levels of context.

At that point, a question starts to appear: do we still know where the right information is, whether it is up to date, and in what context it was used?

That is often where things become complicated.

The observation behind Owarelin

This gap interested me a lot: we have more and more tools, but information can still be difficult to follow, understand, or use correctly.

Owarelin was born from that observation.

Because at the core, the problem is not always the technology itself.

Very often, what slows adoption is the way people are able to work with information: finding it, understanding it, trusting it, and knowing how it has evolved.

At that point, the subject is no longer only about storing a file somewhere.

The real subject is understanding what that information represents, where it comes from, what happened around it, and why it matters.

This is the idea behind Owarelin: reducing the distance between people and the tools they use.

Not to replace people with machines, but to give the machine its real role: helping organize, retrieve, track, and clarify information.

People remain at the center, because people understand context, make decisions, and give meaning.

The problem we want to solve

This is the logic that leads to Owarelin Records.

The word “records” comes from records management. Behind that term, the idea is simple enough: managing information from the moment it appears until the moment it is no longer used.

But before talking about management, we need to ask a simpler question: what truly defines a piece of information?

When we receive information, we often start with simple questions:

• What is its nature?
• Is it true?
• Is it reliable?

Those questions matter, but they are not enough.

In an organization, information is almost never isolated data. It comes from somewhere. It moves through several hands. It can carry value, sensitivity, and responsibility.

And that is often the part we forget.

We look at the content, but forget the journey:

• Where does this information come from?
• Who had access to it?
• Which steps did it go through?
• Who modified it?
• Who approved it?
• Can we easily recover its history?

Take a simple example: a piece of information can begin as a draft, move into review, be corrected, then approved and archived.

At every step, something happens. A person intervenes. A decision is made. The status of the information changes.

Why context matters

This is where context becomes essential.

If we find a document without knowing who produced it, when it was approved, and whether it is still current, we hesitate to use it.

We do not only lose time. We also lose trust in the information.

That is the problem Owarelin Records is designed to address: helping organizations keep information clear, traceable, and usable.

Starting from each organization’s reality

The first idea behind Owarelin Records is not to impose a single way of defining what information is.

Every structure has its own reality, its own files, its own rules, and its own responsibilities.

So Owarelin Records first allows an organization to define its own information types.

That happens through schemas and metadata.

For example:

• for a municipality, information can be connected to a citizen, a request, a department, a status, a deadline;
• for a hospital, it can be connected to a patient, a file, a procedure, a unit, a sensitivity level;
• for a company, it can be connected to a contract, a customer, a decision, a deadline, a responsibility.

Once that definition exists, everything else can be built around it.

We can follow its journey, control access, keep its history, automate certain steps, and above all recover the context needed to understand it.

In other words, Owarelin Records does not start from the file.

It starts from the way the organization understands and uses its information.

Building the journey of information

Concretely, we first start from how the organization works.

We define what it handles, the metadata that matters, the relationships between elements, and the rules that must accompany them.

From there, Owarelin Records can build the journey:

• where information is created and what it is attached to;
• who can access it;
• which steps it goes through and which actions can be performed;
• how long it must be retained;
• how it can be found later.

The goal is not only to classify information.

The goal is to make sure information remains understandable throughout its lifecycle.

From here, we can now look at how this logic is translated concretely into the platform.