Operations · by 30 September
- Freeze active and legacy HIT/workflow inventory.
- Separate submitted, unsubmitted and intentionally retired states.
- Name qualification, approval and bonus logic without copying restricted records.
Close MTurk deliberately—not with a last-day folder dump.
A printable 12-control close-out board for small research teams and legacy requesters. Assign owners, preserve evidence pointers, expose unknowns and stop before a replacement-platform claim.
Download editable CSVRequest free three-observation triageSee fixed-scope paid packs
12bounded close-out controls
3official closure clocks
4owner roles in the template
0real records or platform-equivalence claims
Evidence boundary: Amazon’s public Closure FAQ establishes the three dates used here: 30 September 2026 for permanent closure and HIT submission stop, 30 October 2026 for requester approval/rejection and bonus actions, and 28 January 2027 for transaction-history access. This board is an operational template—not IRB/ethics, legal, privacy, labour, tax, procurement or research-methods advice. It does not establish that another platform is available, suitable or equivalent.
Three clocks, four owners
Research owner · before route testing
- Retain consent/ethics artifact pointers under the team’s own rules.
- Mark participant-pool, screening and method questions as unknown.
- Approve any step beyond synthetic/no-recruitment mapping separately.
Finance · by 30 October / 28 January
- Confirm pending approval, rejection and intended bonus ownership.
- Export transaction-history evidence to authorised storage.
- Record completion evidence as a pointer; do not paste payment details here.
Engineering · before decommission
- Pin code, launcher, callback, dependency and export-format versions.
- Exclude secrets and credentials from the board.
- Keep candidate-route field gaps separate from compatibility claims.
12-control close-out board
| Control | Deadline | Owner | Minimum evidence | Safe state | Stop / hold condition |
|---|---|---|---|---|---|
| C01 · Workflow inventory | 30 Sep | Operations | HIT/workflow row ID and purpose | known / retired / unknown | Unowned legacy workflow |
| C02 · Submission state | 30 Sep | Operations | Submitted/unsubmitted state pointer | frozen | Do not infer from old screenshots |
| C03 · Qualification logic | 30 Sep | Research | Plain-language rule; IDs may be redacted | documented / partial | Semantic meaning unsettled |
| C04 · Batch and response target | 30 Sep | Operations | Target/actual counts or restricted pointer | recorded / restricted | No participant rows in this board |
| C05 · Approval/rejection owner | 30 Oct | Operations | Named role and due date | owner assigned | Pending count not verified |
| C06 · Bonus owner | 30 Oct | Finance | Intended-action status and owner | closed / action due | No payment details copied |
| C07 · Transaction history | 28 Jan | Finance | Authorised-storage pointer and export date | exported / verify | Completeness not confirmed |
| C08 · Consent/ethics artifacts | Team date | Research | Pointer only | retained / restricted | No ethics determination here |
| C09 · Worker/participant data | Team date | Data owner | Retention state only | retained / deleted / restricted | No raw data transfer |
| C10 · Code/API dependencies | Before decommission | Engineering | Repository/version pointer; no secrets | pinned / unknown | Unreproducible dependency |
| C11 · Candidate-route questions | After archive | Research + engineering | Field, access and procurement questions | candidate only | no_equivalence_claim |
| C12 · Synthetic pilot gate | After owner review | Named approvers | Synthetic test and explicit stop rule | hold / approved separately | Stop before recruitment or data transfer |
A clean handoff has three states
Ready · evidence is pointed to
Each operational row has an owner, state, observed date, storage pointer or deliberate unknown. Restricted materials remain with the authorised team.
Hold · the decision is not ready
Named-team access, qualification semantics, participant-pool fit, API/export shape, price, procurement and ethics suitability remain explicit questions.
Stop · scope crosses the boundary
Do not place participant responses, worker identities, payment details, credentials, private ethics records or secrets into a public/shared close-out board.
Paid handoff only after acceptance
The US$250 Archive Readiness Pack covers up to three workflow rows. The US$750 Assisted Mapping Sprint adds one workflow mapped to up to two candidate routes. Prices are validation hypotheses, not proven market rates.
Download the fictional template CSVInspect fictional completed deliveryAsk a scope question
Template status: all rows in the downloadable CSV are fictional placeholders. There is no customer, requester, university, study, worker, participant, account, payment, migration, live pilot or external contact represented. Replace bracketed values only inside your team’s authorised environment and retain restricted evidence under your own policy.