In this article:
Complete a compliance task to record the work carried out, retain supporting evidence, and identify any issues or improvements that require follow-up. The task remains in the Action stage until it is signed off as complete.
You can also make a progress note when the work is not ready for sign-off. Once completed, Logiqc assigns the task to the Approval officer for review and closure.
You are the Action officer selected for this compliance task. The task instructions, due date, source documents, references, and related context explain what needs to be completed.
If the task is not ready to finish, record a progress note so there is a traceable update.
Q: What is the difference between a progress note and sign-off?
A: A progress note records an update and keeps the task in the Action stage. Sign-off confirms the required work is complete and sends it to the Approval officer.
Q: Can I record a follow-up issue?
A: Yes. Add an identified issue and recommended improvement. Logiqc creates a related item in the Improvement register when the task is submitted.
Q: Can I attach evidence?
A: Yes. Attach files or links before you submit the task.
Before you start
Check the following:
- You have the Action Audit, Compliance and Maintenance tasks permission (minimum licence type required: Action).
- You have reviewed the instructions, due date, source documentation, and reference documents.
- The evidence needed to demonstrate completion is ready to attach.
Step 1: Open the compliance task
Open Tasks, select the compliance task description, then work in the Action stage.
Navigation path
Select the task description to open the assigned compliance task.
Step 2: Review the task and Action history
Confirm the task, assigned officer, instructions, and previous workflow events before recording your work.
Action history shows when the compliance task was added and any later workflow activity.
Step 3: Complete the task or make a progress note
In Task management, choose the action that matches the current state of the work.
Sign off completed work or record a progress update without moving the task to approval.
When signing off, describe the work completed in Action taken. Add optional comments only when they provide useful context.
Use Additional comments if you need more space to record details of the work completed. You can add any number of progress notes while the task is in progress; it remains assigned to you in the Action stage until you select Sign off task as complete.
Summarise the completed work clearly enough for the Approval officer to verify it.
Step 4: Record issues and improvements (optional)
Select Add in Identified issues and improvements when the task identifies a gap, non-conformance, concern, or improvement opportunity.
Describe the issue and a practical recommended improvement, then set ownership and access as required.
Use the related improvement fields to make the follow-up clear and accountable.
| Field | How to complete it |
|---|---|
| Issue type | Select Non-conformance or Improvement opportunity. Classify corrective actions as a Non-conformance. |
| Source and origin | Where the form shows Source of issue, select the source that applies to the compliance task. Select whether the issue was identified internally or externally, and name the external person or organisation where relevant. |
| Description of issue | Describe the gap or issue before proposing its solution. This field accepts up to 2,000 characters. |
| Recommended improvement | Record a practical recommendation for improving the process or activity. |
| Related meeting | Select the meeting responsible for monitoring the improvement, or the meeting that should be kept informed. |
| Report this issue to | Select the person responsible for managing the related improvement. |
| Viewing permissions | Set the teams and users authorised to view the related improvement. Add additional users where people outside the selected teams need access. |
Step 5: Attach records and submit
Select Attach to add evidence such as a completed checklist, certificate, report, correspondence, or link. Give each record a meaningful name. Where links are enabled, choose File or Link and use a valid web or SharePoint URL. Only people who can view the compliance task can view its records.
Select Create a related item when you need to create a separate linked item in another register before submitting. The link appears in each item's System event history.
Review any related improvements, then select Submit.
Add supporting evidence and submit when the completion record is ready.
Read the article to find out more:
Other sections
System event history
This section provides a chronological record of changes, assignments, submissions, workflow events, and related items created from the compliance task.
Use System event history to trace changes, assignments, submissions, and related items.
Expand an event when you need to see more information about it.
What happens next
The Action record is saved
Action taken, comments, attachments, and related improvements are retained with the compliance task.
The task moves to the Close stage
The Approval officer receives the completed task for review.
The task is approved or reassigned
The Approval officer can assign another task or approve and close the compliance task.