Macros
AuraScore 81/100

Assurance Evidence Request Macro Workflow Specification

Develop a comprehensive technical specification for audit workpaper and document request macro sequences.

Use this template when designing automated macro workflows for audit, assurance, or tax evidence collection. It details notification templates, evidence validation checks, non-compliance escalation paths, and portal integration rules.

Template

Role: Practice Operations & Quality Assurance Lead across multi-partner accounting and audit firms.

Context

  • Audit and compliance standard: {{audit_standard}}
  • Engagement cadence and deadlines: {{engagement_cadence}}
  • Client document portal infrastructure: {{portal_infrastructure}}
  • Evidence non-compliance escalation rules: {{evidence_escalation_rules}}
  • PBC (Prepared By Client) remediation thresholds: {{remediation_thresholds}}
  • Partner sign-off protocol: {{partner_signoff_protocol}}

Task

Author an end-to-end Macro Workflow and Template Specification for {{portal_infrastructure}} that governs PBC evidence requests, deficiency notices, and hard-deadline escalations in accordance with {{audit_standard}}.

Method

  1. Define the stages of evidence acquisition across {{engagement_cadence}} (Initial Request, Clarification, Deficiency Warning, Statutory Stop-Work).
  2. Construct standardized macro templates for each acquisition stage targeting specific client roles.
  3. Integrate precise validation parameters for file formats, secure upload links, and checksum verification supported by {{portal_infrastructure}}.
  4. Embed escalation logic reflecting {{evidence_escalation_rules}} when PBC items breach {{remediation_thresholds}}.
  5. Draft explicit warning notifications detailing consequences of non-delivery on statutory audit opinion dates.
  6. Detail automated metadata tagging (workpaper reference ID, testing cycle, PBC status) applied by each macro.
  7. Map required partner notifications adhering to {{partner_signoff_protocol}} before issuing final delinquency notices.

Constraints

  • MUST cite specific compliance provisions of {{audit_standard}} within the deficiency notice macro specs.
  • MUST NOT generate macros that permit client evidence transmission via unsecured email attachments.
  • All templates must mandate explicit secure hyperlink variables tied to {{portal_infrastructure}}.
  • Clear escalation tiers must directly match {{remediation_thresholds}}.

Output format

  1. Macro Workflow Topology (Flow diagram syntax or step-by-step state machine mapping)
  2. Macro Specification Sheets (Stage Name, Recipient Persona, Macro Body with Workpaper Placeholders, Associated Metadata Mutations)
  3. Portal Action & Security Rules (Payload validation, access token expiration, logging)
  4. Partner Intervention & Stop-Work Protocol (Governance rules matching {{partner_signoff_protocol}})

Self-review

  • Ensure every macro forces uploads exclusively through {{portal_infrastructure}}.
  • Verify alignment between {{remediation_thresholds}} and escalation macro trigger points.
  • Confirm mandatory partner sign-off steps are unskippable in final warning templates.
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.

support-success
support-macros
professional-services
audit-macros
assurance
pbc-workflows