Simple, action-oriented guide focused on what users need to DO,
not how the system works internally. Perfect for onboarding and
daily reference.
USER_GUIDE.md (15-minute read):
Target Audience:
- Creative teams creating localized assets
- Agencies doing derivative work
- Campaign managers coordinating uploads
- Anyone who needs to USE the system (not maintain it)
Content Structure:
1. Big Picture (Simple Flowchart):
- 6-step process diagram
- "You do step 3-4, system handles rest"
- Clear role definition
2. 3 Golden Rules:
- Always use naming tool (never type manually)
- Every asset needs CreativeX score (no exceptions)
- Always use SAME tracking ID (for all versions)
3. Step-by-Step Workflow:
- Receive email → Download → Localize → Score → Name → Upload
- Each step explained in plain language
- What to look for in emails
- How to use naming tool (field-by-field)
- Where to upload
- What emails to expect
4. Rejection & Rework Process:
- What rejection means (normal, not failure)
- How to read rejection comments (Legal/IA&CC/Approver)
- How to fix and re-upload
- CRITICAL: Must re-score after fixes
- SAME tracking ID, NEW job number
5. Common Questions (10 FAQs):
- How to find tracking ID
- Do I really need 200 scores? (Yes!)
- What if typo in tracking ID?
- Can I upload before scoring? (Yes but not recommended)
- Wrong folder - what to do?
- How long to process? (5 minutes max)
- Can I edit filename? (NO!)
6. Troubleshooting:
- "File not processed" → Check folder, filename, tracking ID
- "Score=0 but I uploaded PDF" → Check filename match
- "Error: wrong tracking ID" → Copy from email exactly
7. Quick Checklist:
- 15-point checklist before upload
- 7 additional steps for rework
- All checkboxes format
8. What NOT to Do (5 critical don'ts):
- Don't type manually
- Don't skip CreativeX
- Don't reuse tracking IDs across campaigns
- Don't upload to wrong folder
- Don't edit generated filenames
9. Quick Reference Tables:
- Box folders and when to use
- Email types and meanings
- Naming tool field guide
- Contact information
Key Differences from Technical Guide:
❌ No system architecture
❌ No database schemas
❌ No Python code
❌ No technical troubleshooting
❌ No server commands
✅ What to click
✅ Where to upload
✅ How to use naming tool
✅ What emails mean
✅ How to fix common mistakes
✅ Who to contact
Tone:
- Friendly and supportive
- Clear and direct
- Action-oriented ("Do this, not that")
- Visual with tables and checklists
- Assumes no technical knowledge
Examples Are Real-World:
- Actual tracking IDs (pOiJ9s, a7K9mP)
- Actual folder IDs (348526703108)
- Real error messages users will see
- Common typos (pOlJ9s vs pOiJ9s)
Length: ~800 lines (~20 pages when formatted)
Perfect for:
- New agency onboarding
- Quick reference during work
- Sharing with non-technical stakeholders
- Training sessions
Complements COMPLETE_WORKFLOW_GUIDE.md (technical deep-dive)
with practical hands-on instructions.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
DJP