1 / 4
Finding
The audit finds no current supplier assessment. The auditor records what is missing and which requirement needs to be met. That gives the team a starting point.
Open this area of the appAn audit leaves a finding. What happens next?
Interactive example with fictional data. This is not a screenshot of a live account.
One item. Two distinct responsibilities.
One person carries out the action. Another checks whether it solved the problem. The example below shows what each person sees and records in Pulsar.
2 / 4
Action
Anna updates the supplier assessment by the due date. The action includes the audit finding and the expected result, so she does not have to reconstruct the context from emails.
Open this area of the app3 / 4
Evidence
Anna attaches the supplier assessment and identifies its version. The document awaits review. Adding it confirms that the material was submitted, not that the action was effective.
Open this area of the app4 / 4
Decision
Mark reviews the document and assesses whether the action worked. He records the decision and its rationale. Missing evidence or an inadequate result sends the item back for correction.
Open this area of the app
See where this workflow helps.
Audit preparation
Review material is missing. Assign its collection, then check the documents and open findings.
Cross-team action
An action moved from quality to purchasing. Keep the finding, due date and reviewer with it.
Risk assessment
A risk is described but awaits a decision. Review the assessment and evidence before deciding what to do next.
Management review
A summary needs support. Open the records behind its figures and statuses.
Open a specific view.
Interface views with sample data. Open an image to see the details.
Is there an issue your team struggles to close?
Describe it in the form. We’ll establish who does the work, where you record the result and what holds up the decision. Then we’ll show a relevant Pulsar example. Keep confidential documents with you.