Risk Management Platform Ideas

Serialize Audit ID

User's have to type in a unique Audit ID every time an audit is assigned. Beyond audit name, audit type, audit location, and audit due date, what other information needs to be conveyed? Suggest to automate the serialization of Audit ID's, similar to Incident ID's in IT

  • Guest
  • Jun 27 2016
  • Shipped
  • Attach files
  • Guest commented
    July 11, 2016 19:07

    Maybe pre-populate it with an abbreviation of [Audit Name] – [Audit Location] – [Counter]. For example, Fire Extinguisher Check audit for Warehouse location would be ID’ed as FIR-WAR-01. Incident Track is a bit more simple. It uses [Year]+[Counter] of incident type in each site. For instance, the third WR incident in 2016 in a given site would be ID’ed as 2016003. So would the third auto incident in that site.

     

    If we display the audit name, audit location, audit assignee, and assignment/completion dates, I am not sure what additional use the Audit ID conveys. Maybe we don’t need it at all. If we do keep it, I suggest to pre-populate it and not wait for user input (they can overwrite, if desired).