FILE 01Organisation and outcome
Identify the contracting legal party, relevant owners, operating locations, intended users, current system, pain point, desired outcome, deadline, budget range, and person who can accept the work.
- Do not send credentials in the first message
- Disclose regulated or high-risk activity early
- Name the actual decision owner
FILE 02Language, data, and transactions
List required languages/scripts, human reviewers, forms and records, sensitive data, vendors, hosting, payment route, currency, tax adviser, retention, and deletion expectations.
- Include the expected cities and devices
- Identify any AI use and data boundary
- Flag uncertain providers or payment participants
FILE 03Screening and access
Provide enough counterparty and transaction context for current US screening. After fit is confirmed, agree on secure access, backup, staging, validation, rollback, and acceptance evidence.
- Unresolved screening pauses work
- Access remains least privilege
- Scope changes require a recorded decision