Overview
Start Date:
End Date:
Description
Due to a miscommunication about content requirements with the keyword audit, we are missing some content requests for Feb.
Why
We need to deliver everything they are paying for.
Expected Impact
Content will have to be submitted late and filled by the content team, although they should have capacity since they can get ahead in March.
đ Milestones / Project Timeline
- Created an audit sheet and communicated the plan to Katie.
- Katie will update the audit sheet with findings
Next Actions
- Katie is going to start with DS and work through the entire monthly sheet to see what weâre missing.
Questions
Questions | Answer | Who | When | Where (Meeting) |
|---|---|---|---|---|
If content is not requested or created in the month of February, should reps still create a line for it in the WD Import to include in reporting that says the work is still in progress? | No, content that is requested late this month will be reported on in the month that the content is published. We want to avoid tons of in-progress WD lines that may lead dealers to believe we are slacking in fulfilling their package requirements. | |||
If content is created in a future month to catch up on the Feb. package requirements and is reported on for that future month, will it need to be moved back to the February work section once reporting is over? | It shouldnât need to be moved as it doesnât affect monthly reporting, but may show up in quarterly reporting that we did more work in one month to catch up for another. | |||
Are there QA issues that could arise by having February content reported on in future months? Will QA call out WD Imports that appear to have more than the package requirements fulfilled in a single month? |
Decisions
Decision | Why | Who | When | Where (Meeting) |
|---|---|---|---|---|
*Primary decision maker in bold.
Add Comment