Glivent answers
What records can a Glivent workflow keep for review and audit?
Direct Answer
A Glivent workflow can record the inputs used, the steps completed, staff approvals, unusual cases and final outcomes when the business needs evidence of how work was handled. What should be recorded depends on the process, the sensitivity of the information and how long the business needs to keep it.
Record the decisions that matter
Useful records show who or what handled the work, when it happened, what required approval and how an exception was resolved. Logging everything without purpose makes review harder and can create unnecessary data retention.
Match the record to the workflow
A document intake flow may need the source file, validation result and reviewer decision. A staff knowledge query may need a lighter record or no retained conversation at all. The business should decide what evidence it needs before the system is configured.
Retention is part of the design
Records need an owner, an access rule and a retention period. Glivent can implement the agreed technical behaviour, while the business remains responsible for deciding what its legal, professional and operational requirements demand.