Marketplace ops
AuraScore 79/100

Civic Marketplace Vendor Vetting and Onboarding Memo

Draft a formal vendor onboarding and verification email for public sector catalog suppliers.

Use this template when onboarding newly approved suppliers onto a municipal or civic procurement marketplace. It outlines compliance mandates, catalog upload requirements, and operational milestones in a structured professional email.

Template

Role: Senior Public Procurement Marketplace Operations Specialist with fifteen years of experience managing government supplier catalogs and compliance workflows.

Context

  • Target Agency: {{agency_name}}
  • Onboarding Vendor: {{vendor_name}}
  • Assigned Tier: {{compliance_tier}}
  • Product/Service Category: {{catalog_category}}
  • Verification Cut-off Date: {{audit_deadline}}
  • Dedicated Supplier Lead: {{primary_contact}}

Task

Draft a comprehensive, professional onboarding email directed to the supplier operations team to guide them through catalog activation, public sector pricing caps, and data validation requirements.

Method

  1. Establish the formal approval status of {{vendor_name}} under {{agency_name}} framework agreements.
  2. State the required catalog standards for {{catalog_category}}, including standardized SKU formats and accessibility tags.
  3. Detail the specific verification prerequisites tied to {{compliance_tier}}.
  4. Explain the transaction settlement timeline and statutory prompt-payment terms.
  5. Define the exact technical requirements for inventory feeds and catalog updates.
  6. Highlight critical escalation pathways managed by {{primary_contact}}.
  7. Specify immediate operational actions required before the {{audit_deadline}}.

Constraints

  • Tone MUST remain formal, regulatory-compliant, and supportive of public sector transparency standards.
  • MUST include explicit instructions for multi-factor authentication setup on the vendor portal.
  • Keep email body between 300 and 450 words total.
  • Do NOT introduce speculative legal terms outside standard civic marketplace frameworks.

Output format

An email message structured as follows:

  • Subject line: Clear, actionable, containing vendor name and agency identifier.
  • Salutation: Formal addressing vendor operations leadership.
  • Body Section 1: Activation confirmation and tier classification.
  • Body Section 2: Catalog integration checklist (4 bulleted items maximum).
  • Body Section 3: Statutory compliance and audit deadlines.
  • Closing & Sign-off: Direct contact info for {{primary_contact}}.

Self-review

  1. Verify all {{agency_name}}, {{vendor_name}}, and {{audit_deadline}} placeholders are correctly applied.
  2. Confirm that public sector vendor requirements are unambiguous and actionable.
  3. Check word count to ensure the communication remains concise and within limits.
AuraScore breakdown
79/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 engineering8/12 · Adequate

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 efficiency7/10 · Adequate

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.

ecommerce-retail
ecom-operations
public-sector-nonprofit
procurement
vendor onboarding
public sector