Use case 1, document management: This basically just means that you need to implement the capability to “publish” a document version, permanently view that document version (think tag), and auto generate a document “identifier” using the companies naming convention (and allow this to be embedded automatically in the document so the client can use it too). The document ID might look something like SOP-2401001.
Once a document is published it should be read-only, and you should be able to put artifacts a long with published documents … ie exported PDF copies, or signed copies or something.
Use case 2, document siloing: One of the most difficult parts of document management is creating forms for procedures, and then teaching everyone how to not ruin the document management of these forms once they are filled. I have always wanted a silo that automatically copies a form when you start to fill it out, allocates it a brand new document ID, and collects it together with all the other forms of the same kind.
This could be integrated with an automation platform so that ie if you fill out a form it sends someone an email or something like that. Or if you wanted to get really fancy, you could allow people to define “workflows” for documents and actually visually show a business process alongside a document.