Stages, conditional transitions and automations on the item itself. No more chasing a manager by email for a review.
The Workflow tab of a model: stages, transitions, and the open transition's panel.
Properties of the example workflow shown, not measured outcomes.
nothing prevents falsification after approval
« We need control over revisions and releases — the kind PDM gives you. SharePoint does not. »Approval locks the item and signs it. Changing it needs a new revision.
to change one document revision
« If it is complicated, people do not do it. »Revising is one action on the item, so it actually gets done.
on documentation, in a typical design team
« The administrative load of design control took five people for a team of twenty to thirty. »Evidence is a by-product of the work, not a second job.
| Today | With a Koddex workflow | |
|---|---|---|
| Get a review | Chased by email or in a meeting | One button, the reviewer notified |
| Approve above a threshold | Whoever is around signs | Condition on the amount and the actor |
| Release a validated item | Still editable after sign-off | Locked at release, PDF to sign |
| Send it back | A new file, a new thread | Request changes, back to In progress |
| Prove who approved what | Rebuilt from inboxes | Every step recorded on the item |
What the workflow does as configured in the example, not a measured figure.
Yes. A transition checks conditions on data values (an amount above a threshold, a status, a required field) and on rights (the actor is the manager, or belongs to a group) before it runs.
The transition's automations run: request an approval, notify a group, update data, lock the item, generate the PDF to sign. Every step is recorded on the item.
We build a Koddex workspace with your models and your vocabulary, on approval workflows, then walk your team through it live. Free, 30 minutes.
Book my custom demo →Verbatims: what hardware teams say about Koddex.