Please enable JavaScript.
Coggle requires JavaScript to display documents.
The RFP Project - Coggle Diagram
The RFP Project
Workflow
P&G system → Coordinator downloads files → Locaria linguistic workflow → Agency QA → Coordinator uploads to P&G → PIM approval
Step 1: The P&G team uploads the local master content to PIM.
:question: Who is the team?
:question: Will they inform us when anything is submitted or should we check proactivelly?
Step 2: Stagwell Media team downloads and prepares the local master content from PIM
:zap: Confirm the access and test downloading (bulk exports).
:question: In which form will the local master content be uploaded to PIM?
:question: In which form will the Locaria team expect the master content to be shared with them?
:question: What are the ways of sharing the materials with the Locaria team?
:warning: Check and confirm how long would it take to prepare the content for Locaria work.
Step 3: The Locaria team carries out the linguistic work and delivers the adapted local content
:question: In which form will the adapted content be delivered by the Locaria team?
:question: What are the Locaria team's timings of delivery (i.e. how much time would it leave us for internal check and content upload)?
:question: Will any side-information be delivered with the content, regarding proofreading, post-editing, corrections, compliance or quality optimisation, to put any changes into context?
Step 4: Quality assurance of the adapted local content
Terminology compliance: target ≥98–99%
Style-guide compliance: target ≥90%
First-time-right: target ≥95% for standard content
Tracking critical / major linguistic errors
:question: Who is responsible for the QA?
:question: How is the criteria measured?
Step 5: Stagwell Media team prepares and uploads the adapted local content to PIM
:question: In which form should the adapted content be uploaded?
:zap: Check how long the upload would take.
Step 6: The P&G team reviews and ultimately approves the adapted local content in PIM
:question: In case of any feedback, how is the feedback shared?
:question: Do we get the information about feedback and approvals, or should we check for them proactively?
Scope of Work
The agreed SOW is essentially a 10-language CE managed linguistic QA service for P&G AI-generated eContent, where Locaria centrally manages post-editing, terminology, QA and project coordination, while the Stagwell Media team handles the PIM system interaction under the 5-working-day SLA.
-
-
-
-
-
Client Expectations
SLA timing: 5 working days from receipt of the local master
:warning: Maximal batch to be established.
Volume and turnaround: 30–40 Local Masters per category during the first three months, with volume expected to decline closer to spring.
:warning: Establish the exact amount of SKUs instead of "masters per category".
-
Using the first three months as a calibration period to establish the quality baseline and subsequent reporting/dashboard.
-