Editorial Guide: Define Wolfia's Voice for Your Org

​

What the Editorial Guide controls

• Tone and voice: Professional vs casual, first-person vs third-person
• Formatting preferences: Bullet points vs paragraphs, headers, response length
• Terminology standards: Company name usage, abbreviation preferences
• Brand consistency: Ensuring all AI answers sound like they come from your organization

​

What it doesn’t control

The Editorial Guide only affects how answers are written. It won’t change:

• Which facts are included in answers
• The compliance framework focus (use Questionnaire Instructions for that)
• The technical depth of responses (use Questionnaire Instructions for that)

​

Setting up your Editorial Guide

Your guide applies to all AI-generated answers across questionnaires and conversations.

​

Examples

​

Tech startup wanting approachable answers

Editorial Guide:

Be conversational and direct. Use “we” and “you.” Avoid jargon. Keep answers under 150 words when possible.

Before (default AI answer):

Access controls are implemented using role-based access control (RBAC) with multi-factor authentication required for all users.

After (with Editorial Guide):

We use role-based access so you only see what you need. Everyone on the team logs in with multi-factor authentication.

---

​

Enterprise with strict brand guidelines

Editorial Guide:

Always use “Acme Corporation” instead of “we” or “the company.” Use formal, third-person voice. Lead with customer benefits.

Before (default AI answer):

We conduct quarterly security assessments and penetration testing.

After (with Editorial Guide):

To protect customer data, Acme Corporation conducts quarterly security assessments and annual penetration testing.

---

​

Fast-growing startup wanting technical credibility

Editorial Guide:

Use precise technical language. Include specific product names and standards. Write for a technical audience.

Before (default AI answer):

Data is encrypted both at rest and in transit using industry-standard encryption.

After (with Editorial Guide):

All data is encrypted at rest using AES-256-GCM via AWS KMS. Data in transit uses TLS 1.3 with ECDHE key exchange.

​

Best practices

• Start simple: Begin with 2-3 core preferences and refine over time
• Be specific: “Use formal tone” is vague; “Use third-person voice and avoid contractions” is actionable
• Test with examples: Upload a questionnaire and review how answers change

​

Common questions