This SOP is a work in progress. If you notice anything that is out of date, could be more clear, or could be more efficient please update the SOP or add a comment to start a conversation.
Purpose
Quality Assurance (QA) corrections are done to ensure that we are delivering high-value, errorless work to our clients. Doing so creates credibility and a good user experience for our sites.
Procedure
Inputs:
You’ve done a daily check for outstanding QA corrections.
You see a “.5” or a “1” in the QA Completed column.
Expand | ||
---|---|---|
| ||
First, we need to open our QA Trello board! ARI
Dealer Spike
|
Expand | ||
---|---|---|
| ||
Here are the scenarios you’ll see on your cards, and what to do when you see them: 1. QA Complete label and a Due Date
2. QA Complete label and All Good label
3. Re-Submit label and a Due Date
4. Juniper label and a QA Complete or Re-Submit label
|
Expand | ||
---|---|---|
| ||
Now we’re going to mark this task as complete. ARI
Dealer Spike
|
Outputs:
QA corrections are complete.
The monthly sheet is marked off with a “1” for this customer.
FAQs
Expand | ||
---|---|---|
| ||
|
...