Most internal procedures are not written down anywhere. They live in one person’s head, a spreadsheet, and a habit. The ones that are written down are usually written into software, which means changing them requires a ticket, a developer, and a release.
In Praxis the procedure is something you edit.
The flow
A procedure is a set of stages and the moves between them. You draw it: this is where a case starts, these are the ways out of each stage, and this is where it ends. Each move is named as what it actually is — submit, return for corrections, approve, cancel — because “status changed” tells nobody anything six months later.
For each move you decide who is allowed to make it, and what has to be ready first: a comment, a document, a form, a signature. “We need the invoice number before Legal sees this” becomes a rule of the procedure, not an email asking for the missing number.
Publishing a change does not rewrite the past. Cases already open keep the rules they started under. The next one follows the new ones.
The forms
The other half of a procedure is the information you need before someone can act. In Praxis that is built in the same place as the flow, at the stage where it is due.
Some fill themselves in. Somebody uploads an ARCA invoice, a VEP, or a DNI, and most of the form is already there.
If the submission was wrong, you ask for a correction. The original does not vanish.
The rest
The same idea covers the parts people notice: your logo, your colors, your domain, and each person reading the interface in Spanish or English.
None of this is a software release. The person who owns the process makes the change.
If this looks like a problem you have, write to us.