Skip to content

Guide · 2026-07-23 · 5 min read

A procedure, that actually gets read.

Most procedures don't fail on content. They fail because they stay in the folder.

In 40 seconds

A procedure describes a recurring process step by step: purpose, scope, who's responsible, the individual steps, and the expected result. It's short, written in the order things actually happen, and only useful if it can be found at the right moment.

A procedure fixes how a given task gets done. The same way every time, no matter who's doing it. Handling a complaint, setting up an order, checking goods in. The point is reliability: same process, same result.

The structure, kept short

A usable procedure fits on one page. Five parts are enough.

  • Purpose: what this process is for, in one sentence.
  • Scope: which cases it covers, and which it explicitly doesn't.
  • Responsibility: who carries it out, who decides, who gets informed.
  • Steps: the action in order, numbered, one step per line, starting with a verb.
  • Result: how you tell the process has gone through cleanly.

Write in the order things happen, not the order they occur to you. And write for the person doing this for the first time, not for yourself. What's obvious to you is exactly the point where someone new gets stuck.

The problem no template solves

Say the procedure is good. Clear, short, in the right order. The same thing still happens as with the quality manual: it gets written once, filed, and never opened again. When the complaint actually comes in, nobody has time to dig through the folder structure first. So they do it from memory, the way they did it last time. And practice quietly drifts from the procedure.

A procedure only controls anything if it's present at the moment of doing. A document in a folder isn't. That's filing, not control.

The instruction you can ask

The difference doesn't come from writing better. It comes from retrieving better. Upload your procedures into Rinqo's knowledge base, and the team asks for them at the moment of doing, instead of searching for them. How does the complaint process work? What are the steps for taking on an order? The personal agent gives back the documented steps in order, with a citation to the procedure it came from.

When the process changes, you replace one document, and from the next query on the new version applies, everywhere. No updating several systems by hand, no stray copy still showing the old steps. The procedure stops being something you're meant to follow and forget, and becomes something that answers at the right moment.

Sven Pflüger

Sven Pflüger

Founder & CEO, Rinqo

Sven builds Rinqo from a simple observation: most AI tools are designed in San Francisco and sold in Berlin. The workshop in the Black Forest, the veterinary practice in Salzburg, the family hotel in Tyrol get software that doesn't speak their language. Rinqo flips that. On European servers, set up in ten minutes, in twenty languages. With templates built by the industries themselves.

LinkedIn

Last updated:

Processes you can ask.

Upload your procedures into the knowledge tree, your team pulls them up at the moment of doing. Ten-minute setup, from 99 euros net a month.

See knowledge management