Arabic Linguist Hub
Your single source of truth for everything Arabic localization at Pixelogic.
Style rules, QC guidelines, terminology, dispute procedures, performance benchmarks, and industry resources — all in one place, built for you and maintained by your Training Manager.
Style Guide — Client Call-Outs
Select a client to see rules that differ from the Pixelogic default. Select Pixelogic Default to see all baseline rules.
Linguistic Newsletter
We are introducing a monthly linguistic newsletter shared at the beginning of each month. Its purpose is to document agreed linguistic practices, recurring discussions, and resolved points that emerge through day-to-day production work. This is not a static rulebook — it is a living reference that captures consensus reached through discussion and real examples. Click any month to expand it.
Linguistic Instructions
General guidance, terminology decisions, and language rules for the Arabic Linguist Team.
Linguistic Dispute Process
Formalized guidelines for raising, reviewing, and resolving linguistic disputes — for both linguists and QCers.
Download the blank Excel file, fill it offline, and send by email.
Workflow
The four phases
- If you agree with the content change but disagree with the error category, submit the assignment first, then raise a dispute. While this may not immediately remove the error weight, it ensures internal alignment and helps prevent similar issues in future titles.
- If you disagree with the content change, raise the dispute in a new email thread — subject:
[Original Title_Episode Number_Linguistic Dispute]. - Copy the assigned QCer and the Training Manager from the start.
- Review the dispute and respond as swiftly as possible.
- QCer returns the dispute form with agreement.
- Linguist overturns or adjusts the flag accordingly.
- Training Manager aligns the outcome internally for future consistency, if needed.
- QCer returns the form with disagreement.
- Training Manager reviews the case privately with the QCer for further discussion.
- A unified decision is reached.
- Training Manager communicates the final decision to the Linguist.
- Linguist proceeds accordingly.
- The decision communicated by the Training Manager is final for delivery purposes.
Once overturned-flag weight is lifted from metrics and overturned flags are subject to review, any flag not raised through this process will count toward finalized linguist metrics. Objective flags should not be overturned without formally going through the dispute process.
Operational rules
Edge cases & deadlines
- Further discussion may take place at a later stage for learning purposes — it should not block submission.
- Linguists are encouraged to send disputes once the changelog is received from RR.
- 6 PM deadline — disputes submitted after 6 PM are handled by the Training Manager directly; the QCer is considered unavailable.
- Same-day urgency — if delivery is urgent and standard process is not feasible, create a Teams group chat with Territory, Training Manager, and the QCer.
Dispute handling rubric
| Role | Step | Action | What & why |
|---|---|---|---|
| Translator (Disputing) |
1 | Identify decision | Clearly state whether you believe the QC flag is valid or invalid. Getting this wrong undermines the entire dispute. |
| 2 | Provide evidence | Provide rationale with linguistic, stylistic, or contextual evidence. Reference style guides or client instructions where relevant. References make disputes and replies stronger. | |
| 3 | Write professionally | Write your dispute in a clear, professional, and respectful tone. Avoid emotional or vague language. Both sides must avoid casual or argumentative phrasing. | |
| 4 | Ensure consistency | Ensure your reasoning is consistent and persuasive — anticipate possible counterarguments. Repeated rubric application builds fairness over time. | |
| QCer (Replying) |
1 | Identify decision | Confirm the translator's claim as valid or invalid based on evidence. |
| 2 | Provide evidence | If invalid, provide a clear rationale with supporting evidence (guidelines, rules, examples). | |
| 3 | Write professionally | Write the reply in a professional, neutral, and concise manner. | |
| 4 | Ensure consistency | Ensure reasoning is consistent with previous QC decisions and persuasive enough to withstand scrutiny. |
KPI & Baseline Thresholds
Internal performance metrics for the Arabic Linguist Team — 2026 baselines.
Baseline KPI Metrics 2026
| Performance Level | On-time Delivery (OTD) | Quality % (Creation) | Quality % (QC) |
|---|---|---|---|
| Below Expectations | Below 98% | Below 92% | Below 98% |
| Meets Expectations | 98.1% – 99.9% | 92.1% – 96.9% | 98.1% – 99.4% |
| Exceeds Expectations | 100% | 97% and above | 99.5% – 100% |
Baseline Competency by Role 2026
| Competency | Baseline Score |
|---|---|
| Stress Management | 2 |
| Focus on Quality | 3 |
| Customer Orientation | 1 |
| Self Development | 2 |
| Integrity | 2 |
| Accountability | 2 |
| Cooperation | 1 |
| Initiative | 1 |
| Result Orientation | 2 |
| Adaptability | 2 |
| Know-how | 2 |
Score Legend
| Score | Level |
|---|---|
| 1 | Beginner |
| 2 | Intermediate |
| 3 | Advanced |
| 4 | Expert |
Competency Bank — Definitions & Examples
| Competency | How-To | Examples |
|---|---|---|
| Stress Management | Staying calm, composed, and professional under pressure, especially when juggling tight deadlines, overlapping projects, or client rejections. |
|
| Focus on Quality | Ensuring accuracy, natural flow, and compliance with style guides, not just meeting the quota. |
|
| Customer Orientation | Understanding what the client and viewer need, and tailoring output accordingly. |
|
| Self Development | Continuously improving language, tools, and industry awareness. |
|
| Integrity | Being honest, transparent, and ethical in all work aspects. |
|
| Accountability | Taking ownership of your work, decisions, and outcomes. |
|
| Cooperation | Working effectively with peers, QCers, and managers to achieve shared goals. |
|
| Initiative | Acting without waiting for instructions when you can add value or solve a problem. |
|
| Result Orientation | Aiming for both quality and delivery efficiency, focusing on outcomes, not excuses. |
|
| Adaptability | Staying flexible with changing client specs, tools, or team setups. |
|
| Know-how | Demonstrating solid command of tools, techniques, and linguistic judgment relevant to your role. |
|
Netflix Spot QC Calculator
Calculate Netflix minimum and Pixelogic extended spot timecodes from program start TC, TRT, and frame rate.
QCer Quality Monitor
Internal tools for the QC team — spot generators, checklists, and monthly QA workflows.
This framework defines how the Arabic Linguistic Team conducts internal quality assurance on its QCers' work each month. Rather than manually and subjectively selecting files for review, this system uses a structured, data-driven approach to identify the files most likely to reveal quality risks — ensuring fair, consistent, and meaningful QA across the team.
The framework operates on a three-month cycle:
- April: 1 Full QA + 30% Spot QA per QCer
- May: 1 Full QA + 20% Spot QA per QCer
- June: 1 Full QA + 10% Spot QA per QCer
Full QA means a complete linear quality check of the entire file — every subtitle reviewed against the source. Spot QA means a targeted review of selected time segments within the file, focusing on areas most likely to contain errors or missed flags.
Files are selected using a risk matrix that scores each file across four factors: PXL-SQM Score, Difficulty, Dialogue Density, and Content Type. The goal is to prioritize files where a QCer is statistically most likely to have bypassed errors or flagged inaccurately.
- Difficulty — Rate each file as Low, Medium, or High based on linguistic complexity:
- Low: straightforward dialogue, minimal technical or cultural content, familiar genre (e.g. simple reality TV, children's content)
- Medium: moderate complexity, some cultural references or technical terminology, standard drama or comedy
- High: dense dialogue, heavy cultural references, specialized terminology, complex narrative structure (e.g. legal/medical dramas, period pieces, high-density episodic productions)
- Exclude List — Type Yes for any file to exclude from QA selection entirely (known technical issues, files reviewed outside this framework, or QCer acting in a different capacity). Leave blank if eligible.
Once you have your QA Selection file, use this tool to generate randomized spot check windows for each Spot QA file. Enter the program start timecode and TRT, select the frame rate, and hit Generate Spots — the tool will produce a different set of randomized QA windows each time, based on the program runtime and dialogue structure. Re-run as many times as needed until you have a distribution that works for your session.
| Spot # | TC In | TC Out | Duration |
|---|
Resources
Curated reference links for the Arabic Linguist Team.
My Dashboard
Your personal QC performance dashboard. Sign in with your QCer code to view your metrics.
Admin Panel
Manage newsletter entries, linguistic instructions, and resources. After adding content, copy the generated data block and paste it into the HTML file, then re-upload to Netlify.
resourcesData array in the HTML file.TEAM_PASSWORD and ADMIN_PASSWORD constants near the top of the <script> section, update the values, save, and re-upload to Netlify.Current team password:
Current admin password:
— no output yet —
Tracker
Daily work log. Add tasks and hours per day. Monthly totals are used for payroll reporting.