Audit fields

The following fields are available for audits:

Name

Description

Data type

Audit id

Unique id for the audit

String

Status

Can be Planned, Ongoing or Report

String

Planned date

If chosen, this will show the planned date of the audit

Date

Audit start time

The time when the first action was taken by the auditor (this could be taking a photo, writing a comment, or choosing an answer in multiple choice, etc. ). It does not reflect the time of download.

DateTime

Audit end time

The time when the auditor submitted the audit. Qarma supports off line operations, so there can be a difference between the Audit end time and the time that the report is available in the system: if the auditor was offline for two hours, the app keeps track of the time when the audit was submitted, and this time will be the Audit end time, even if the Qarma server did not receive the data until two hours later.

DateTime

Supplier name

The name of the supplier

String

Supplier number

The number of the supplier

String

Auditor name

The name of the auditor

 String

Auditor email

The auditor’s email

String

Production unit name

The name of the production unit (if any)

String

Production unit number

The number of the production unit (if any)

String

Production unit address

The address of the production unit (if any)

String

Latitude

Tracking based on the last photo taken in this inspection

Float

Longitude

Tracking based on the last photo taken in this inspection

Float

Accuracy

For the GPS coordinates, this is the accuracy

Number

Auditor comment

This will show the comment given by the auditor when submitting the audit (if any)

String

Checklist id

The id of the checklist used for the audit

String

Checklist name

The name of the checklist used for the audit

String

Checklist revision

The revision number of the checklist used at the point of time the audit was downloaded

Integer

Link to report

http-link to the online audit report

String

Audit type

The type of audit

String

Auditor conclusion

The conclusion which the auditor selected when submitting the audit

String

Final conclusion

The final conclusion chosen. This can differ from auditor conclusion if for example there is an approval flow or the conclusion was revised after submitting the report. In most cases this is the conclusion to use for downstream analysis.

String

Checkpoints fields

The following fields are available for audit checkpoints:

Name

Description

Data type

Checkpoint id

The id of the audit’s checkpoint. It's unique to the audit, meaning that the same checkpoint on another audit will have a different Checkpoint id even though the same checklist has been used.

String

Checkpoint type

The type of checkpoint (Multiple choice, Standard, Text, Text Table, Measurements, Production Unit Custom Fields*, Supplier Custom Fields*)

String

Audit id

Unique id of the audit. Can be used for mapping the Checkpoints-data with the Audits-data

String

Checkpoint header

Name of the checkpoint header

String

Checkpoint

The checkpoint text

String

Status

Status of the checkpoint type “Standard” if the status-buttons was enabled. Status' include the following: “Checked Not OK”, “Checked OK”, “Not Applicable”, and “Pending”.

String

Comment

Comments written on the checkpoint by the Auditor during the audit

 String

Multiple choice

The auditor’s chosen answer on a multiple choice checkpoint. If multi-selection is allowed and the Auditor selected multiple choices, the answers will show as comma-separated strings

String

Score

The score (if applicable) of the auditor’s chosen answer on a multiple choice checkpoint. Note that scores on multiple choice checkpoints is not mandatory and can therefore be blank.

Integer

Max score

The maximum possible score that a multiple choice checkpoint can result in, no matter what the auditor chose.

Integer

Raw data

The raw checkpoint data as JSON format. 

JSON


  • * The Checkpoint type of “Production Unit Custom Fields” and “Supplier Custom Fields” needs to be enabled by a Qarma employee.

 

Corrective Actions fields

The following fields are available for corrective actions:

Name

Description

Data type

Corrective action id

Unique id of the corrective action

String

Audit id

Unique id of the audit. Can be used for mapping the Corrective Actions-data with the Audits-data

String

Status

The status of corrective action. Can be one of the following: “Finding”, “In progress”, “Review”, and “Closed”

String

Finding

The finding of the corrective action

String

Requires evidence from app

Is “true” if evidence is required from the app and “false” if not.

Boolean

Description

The description of the corrective action

String

Approver comment

The comment made by the Approver when setting the status of the corrective action

String

Created

Time of which the corrective action was created

DateTime

Due

The selected due date of the corrective action

Date

Resolved

The time of when the corrective action was resolved

String

Checkpoint id

If the corrective action was created from a checkpoint of an audit this field will show the unique id of the checkpoint. The id is unique to the audit, meaning that the same checkpoint on another audit will have a different Checkpoint id even though the same checklist has been used.

String

Supplier id

The unique id of the supplier

String

Supplier name

The name of the supplier

String

Supplier number

The number of the supplier

String

Production unit id

The unique id of the production unit (if any)

String

Production unit name

The name of the production unit (if any)

String

Production unit number

The number of the production unit (if any)

String

Responsible name

The name of the user responsible for resolving the corrective action

String

Responsible email

The email of the user responsible for resolving the corrective action

String

Approver name

The name of the user responsible for approving the corrective action

String

Approver email

The email of the user responsible for approving the corrective action

String