Triage the intake queue

Objectives

Eight requests are waiting for next quarter's planning. Raise the ones that must not be scheduled in their current form, worst first.

A request qualifies if accepting it as written would damage the operating model, not merely because it is large, awkward or unpopular.

List only the lines that qualify, worst first. Severity is one of: critical | high | medium | low. Add or delete rows as needed.

T-1  Automate the vendor review control; no business owner named, and the requester asks the GRC team to run it and answer the auditor.
T-2  Build a bespoke collector for a system the platform collector already supports, because the requester prefers their own output format.
T-3  "A nice dashboard for compliance"; no control, no obligation and no evidence output identified.
T-4  A four-week integration that would consume the platform capacity reserved for the shared evidence store.
T-5  Automate the quarterly access review: control id, owner, evidence artefact and current manual cost all supplied.
T-6  A request the team estimates will take longer than the requester expects.
T-7  A request submitted by a junior engineer rather than through their manager.
T-8  A request written bluntly enough that two people commented on the tone.

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 fixture as a population, not a list

   Intake exists to ask four questions of every request: which control, whose control, what evidence, and what does it cost manually today. Read each line against those.

2. Step 2

   Decide what actually qualifies

   Four requests fail as written: one transfers accountability, one duplicates shared machinery, one names no control at all, and one spends capacity that was ring-fenced for the platform.

   The right findings are raised

3. Step 3

   Resist the loud lines

   A complete request, an optimistic estimate, an unusual submitter and a blunt tone are not intake failures. Rejecting on tone is how a queue becomes political.

   Benign lines are left out

4. Step 4

   Grade the exposure, not the wording

   Accountability transfer leads: it is the failure that compounds, because every control accepted on those terms becomes the platform team's finding.

   Duplication is next because it bends the cost curve the wrong way, then the request with no control behind it, then the capacity conflict which is a scheduling decision.

   Severity matches the actual exposure

5. Step 5

   Rank so the first line is the one you act on

   Rank by what would be hardest to reverse a year from now.

   Ranked worst first

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.