Transactional
AuraScore 81/100

Advisory Onboarding and Artifact Request Matrix

Generate structured document collection matrices and formal kickoff transactional notifications for client engagements.

Deploy this prompt when launching new consulting, tax, or advisory workstreams that require strict document collection. It structures data-request matrices and automated transactional dispatch templates.

Template

Role: Engagement Quality Assurance Principal in an enterprise professional services practice.

Context

  • Delivery Organization: {{firm_name}}
  • Client Contact: {{client_stakeholder}}
  • Focus Domain: {{audit_scope_details}}
  • Required Inputs: {{required_pre_work}}
  • Ingestion Deadline: {{submission_deadline}}
  • Dependent Schedule: {{statutory_milestones}}

Task

Author a comprehensive Information Request Matrix and the corresponding kickoff transactional email instructing the client on exact document submission protocols to avoid project slip.

Method

  1. Deconstruct {{required_pre_work}} into itemized data artifacts categorized by functional domain.
  2. Assign strict confidentiality classifications and ingestion formats for each requested item.
  3. Link each requested item to downstream impacts on {{statutory_milestones}} if delayed.
  4. Build an Information Architecture Matrix establishing ownership, format, and dependency risk.
  5. Draft the formal transactional onboarding email outlining portal upload directions and deadlines.
  6. Highlight {{submission_deadline}} prominently to ensure legal and operational adherence.
  7. Establish governance protocols for handling incomplete or non-compliant artifact submissions.

Constraints

  • MUST structure artifact requirements in a Markdown table matrix before the email body.
  • MUST NOT leave file format specifications open-ended (e.g., must specify CSV, PDF, or secure export).
  • The email tone MUST be definitive, transactional, and authoritative.
  • Do not include conversational filler or unrelated promotional text.

Output format

1. Information Ingestion Matrix

Markdown table with columns: [Artifact Ref ID | Requested Document / Access | Functional Area | Required Format | Criticality (High/Med) | Dependent Milestone]

2. Formal Ingestion Dispatch Email

  • Subject line: [FORMAL NOTICE] Engagement Data Readiness Checklist: {{firm_name}} / {{client_stakeholder}}
  • Opening verification statement citing {{audit_scope_details}}
  • Explicit instructions referencing the matrix artifact IDs
  • Secure portal ingestion instructions and cut-off: {{submission_deadline}}
  • Milestone delay disclaimer referencing {{statutory_milestones}}
  • Delivery team sign-off

Self-review

  • Confirm every item in {{required_pre_work}} is mapped to a specific artifact ID in the matrix.
  • Check that the date {{submission_deadline}} is highlighted clearly as a hard dependency.
  • Verify matrix headers match the exact names specified in the output format.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

emails
emails-transactional
professional-services
client onboarding
document collection
advisory kickoff