A work instruction sits in the wiki. Whether it is current, nobody knows exactly. Whether the team has read it, nobody knows either. In an audit that is exactly what gets asked.
The Wiki Guide plugin adds an approval workflow and read confirmation to the Redmine wiki. A page becomes a document with a version and an audience.
How it works day to day
- Write a draft. A page is edited as before. At first it counts as a draft and not as the valid version.
- Review and approve. A responsible person approves the version. From that point it is clear which version applies.
- Request confirmation. For briefings and instructions the plugin requests a read confirmation.
- Keep the record. It stays traceable who approved which version and who took note of it.
What changes
- Draft and valid version are distinguishable, without file names carrying version numbers.
- In an audit you can show who read what and when.
- The wiki stays ordered instead of ending up as a grown list of pages.
How knowledge can be organized in Redmine beyond this is described on the page knowledge management.
Which functions the Redmine Wiki Guide plugin brings along and what it costs is described on the product page.