Clients can see what is expected next
Preparing documentation for ISO certification involves requirements at different stages. Some documents still need to be submitted, others await review, and some require revisions. We organised the portal around these tasks so that each status has a clear meaning and points to the next step.
The overview separates client tasks, documents under review and completed items. Individual standards have their own views. A requirement page explains the document and presents information relevant to its status. The demonstration also shows preparation for a scheduled audit.
Document status guides the collaboration
Statuses distinguish documents that have not been submitted, items under review, revision requests and approved documentation. Items approaching expiry or considered not applicable are marked separately. A revision comment explains what the client should address in the next submission.
The public demo’s consultant view presents several fictional clients and a queue of documents awaiting review. The same process can therefore be explored from both perspectives: clients follow their tasks, while consultants see the work awaiting their attention.
Separate access for document submission
Alongside the demonstration interface, we developed a sign-in area. An assigned account receives a view of its requirements and can submit the corresponding document. A new submission changes its status to “under review”. Approved and non-applicable items cannot have their documents replaced through this workflow.
Submission checks the permitted file type and size, and document access is connected with the user account. Account creation and consultant processing are organised separately. The public demo is not an open administration area for actual clients or a place to submit business documents.
B2B collaboration can start with documents
This project presents a B2B portal built around requirements and documentation. A store and shopping basket are unnecessary when the business process involves submission, review and revisions. The interface follows Certiwa’s visual identity, with Swedish labels and guidance.
The companies, people and statuses shown in the demo are fictional. For a similar web application, we first define the roles, required information and responsibility for status changes. Access scope, support and document handling procedures are then agreed around that workflow.