Triage the auditor's PBC list

Objectives

The auditor has sent a "provided by client" list two days before fieldwork. Your CFO wants everything answered immediately to look cooperative.

Accept the requests you should fulfil as written. Reject the ones that fall outside the agreed scope, name the wrong period, or ask for more personal data than the test requires: rejection here means push back and renegotiate, not refuse to co-operate.

Verdicts are accept or reject. Every rejection needs one reason code from: out-of-scope | wrong-period | over-collection.

R-1  Admin user listing for the in-scope production environment as at period end.
R-2  Complete HR file, including salary and medical leave, for all 214 staff.
R-3  Change tickets for the audit period, with approver and merge timestamp.
R-4  Backup restore test results for the two years preceding the audit period.
R-5  Access review sign-off covering the four quarters in the audit period.
R-6  Source code for the payments service, exported to the auditor's personal drive.

Step-by-step hints

The guided walkthrough, in full. It is free: no XP cost, and it does not touch the paid hint ladder or the reveal gate.

1. Step 1

   Read the request before the artefact

   The engagement letter, not the seniority of the requester, defines scope. Read each request against the period and the systems that were agreed.

2. Step 2

   Judge every line, including the boring ones

   Every request gets a verdict, including the three that are perfectly ordinary. A blanket yes and a blanket no are both failures of the same review.

   Every line in the fixture carries a verdict

3. Step 3

   Separate what is wrong from what is merely ugly

   For each line ask: does this evidence a control in scope, does the window match the audit period, and is this the minimum data that answers the question?

   Watch for requests whose subject is fine but whose transfer mechanism is not.

   Accept and reject land on the right lines

4. Step 4

   Say why, in the vocabulary the programme uses

   Use out-of-scope for subject matter outside the engagement, wrong-period for the right subject in the wrong window, and over-collection when the request would hand over more personal data than the test needs.

   Each rejection cites a valid reason code

Rules summary

• XP on pass

  40 bonus XP the first time every check goes green.

• Paid hints

  2 available. Each costs 25% of the lab XP (about 10 XP).

• Reveal solution

  Scores 0 XP and unlocks only after 3 check runs.

• Attempt cap

  60 check runs per learner. The runner warns you in the last 10.

• Drafts

  Your editor content is saved in this browser, so a reload will not lose work.

• Walkthrough

  Always free and never penalised: use it before spending a hint.