Quality Assurance
This page outlines how Quality Assurance works at Accordus and who is responsible at each stage. QA is a required step for all deliverables and exists to ensure accuracy, clarity, and consistency across our work.
No deliverable should be shown to a client, sent, scheduled, published, or printed without completing the appropriate QA steps.
1. Creator Review
Owner | Designer/Writer/Content Creator
Before work is submitted for review, the creator is responsible for:
Reviewing copy for grammar, clarity, and tone
Confirming alignment with brand and strategy
Confirming accuracy of names, dates, links, and details
Checking for obvious errors or missing information in text/graphics
AI tools may be used at this stage to support clarity and consistency, but human judgment remains essential
2. Functional & Technical Review
Emails: Owner | Communications Coordinators
Communication Coordinators provide a critical second set of eyes on email deliverables, reviewing both content and execution.
This review includes:
Checking copy for typos, grammatical errors, and formatting issues
Confirming clarity and readability
Reviewing email builds for layout, spacing, and responsiveness
Verifying links, buttons, images, and tracking
Confirming audience selection and send timing
Sending and reviewing test emails on desktop and mobile
This step ensures emails are clean, clear, and technically sound before senior approval.
Print: Copy Editor Review
Print deliverables receive a dedicated copy edit focused on:
Grammar, spelling, and punctuation
Consistency in language and tone
Accuracy of names, dates, and factual details
Flow and readability within layout constraints
This step ensures print materials are refined and precise before final approval.
3. Senior Level Final Review
Owner | Creative Director/Senior Designer Review for Final Approval
All emails and print materials require Creative Director approval before client delivery.
This review ensures brand alignment, strategic clarity, and readiness for production.
Reminders
QA is not optional
Each step must be completed in order
If you are unsure whether something needs QA, assume it does
Everyone is empowered (and expected) to flag errors or concerns