Auditing the supply chain

The Customer Contractor asks its whole chain, downwards only, and reads what came back.

For: System Admin · Customer Administrator · WorkerLast checked: 2026-10-03
  1. 1
    Customer record: Settings System Admin

    Switches Auditing on for the Customer.

  2. 2
    Audits Customer Administrator

    Creates the audit (the whole Customer, a Country or a Project, with its dates), then runs a pulse survey, a Worker data audit or interviews within it.

  3. 3
    Survey link Worker

    Answers from the emailed link, without signing in.

  4. 4
    Audit survey responses Customer Administrator

    Reads the answers as they arrive; reminders go to whoever has not replied.

  5. 5
    Audit interview Customer Administrator

    Records an interview within the same audit.

  6. 6
    Audit report Customer Administrator

    Issues the written report as a PDF kept in Obtempera; an email with a link to it goes to the Customer's Administrators, the audit team, and the Contractor Administrators of each Contractor with a finding.

How it fits together

Only the Customer audits, and it audits everything beneath it. A Contractor never audits sideways or upwards.

  • Obtempera switches Auditing on for the Customer.
  • The Customer Administrator opens an audit under Audits, for the whole Customer, a Country or a Project. It starts in Draft with them as lead auditor; other Customer Administrators can join the audit team. Every audit holds all five parts: pulse surveys, the Worker data audit, interviews, findings and follow-ups, and the report.
  • They create a pulse survey from a template (Obtempera's, or one of their own) and choose the Workers in the audit's scope. Nothing is sent until the audit is started (Start audit); then Send to N Workers emails each Worker a link of their own.
  • Workers answer from the email link, without signing in, or in the Worker Portal. Reminders go to whoever has not answered and stop once they have.
  • The administrator reads the results as they arrive, draws a sample of Workers to check what the system holds, interviews Workers in person, and raises findings: red and amber ones carry follow-up actions.
  • An external Contractor with an action is emailed, answers it in its Contractor Portal, and the administrator marks it done.
  • They write and issue the audit report. The recipients are emailed a link to it with the red, amber and green counts; a Contractor sees only its own findings and actions, in its Contractor Portal or from that link.

What to watch for

  • A Draft audit sends no survey. Start the audit first; Workers can be chosen meanwhile.
  • An anonymous survey needs 10. It must go to at least 10 Workers and shows its answers only once 10 have responded; if it closes with fewer, only the totals for each option.
  • The Wellbeing Survey starts anonymous, because people answer more openly when not named; it can still be made attributed before it is sent.
  • A sent answer cannot be changed. On an attributed survey the Worker sees what they sent in the Worker Portal, or from the link only after signing in; an anonymous answer is never shown back.
  • Survey, interview and finding forms are templates under Fields & Forms. Build the questionnaire before you send it.
  • Repeated surveys can be grouped into a survey series to compare their results.
  • Closing with findings open needs a reason. The follow-up actions stay open and can still be marked done after the audit closes. Closing the audit also closes any survey still open.