Contractor Onboarding Reading Lists
Overview
This document maps each contractor role to its required and recommended reading from existing Symphony Core documentation. It complements the Team Member Onboarding Checklist, which handles platform access and Day 1 logistics.
How to use this document:
- Every new contractor starts with Section 1: All Contractors (universal baseline)
- Then proceed to the role-specific section for their position
- Items marked [GAP] are documentation that needs to be created — skip these during onboarding until they exist
1. All Contractors (Universal Reading List)
Every contractor reads these regardless of role.
Day 1: Essentials
| # | Document | Path | Why |
|---|
| 1 | Working with Rohit Context Guide | Link | CEO working style, communication preferences, expectations |
| 2 | Team Structure | Link | Who does what, reporting lines |
| 3 | Timesheet & Invoice Submission SOP | Link | How to submit hours and get paid |
| 4 | Google Drive Organization Standard | Link | Where files go, naming conventions |
| 5 | ClickUp basics | (covered during onboarding) | Basic task tracking — creating tasks, updating status |
| 6 | Partner Engagement Framework | Link | Engagement model, NDA, IP ownership |
Week 1: Operations & Processes
| # | Document | Path | Why |
|---|
| 1 | KB-001: Extendly Quick Start | Link | Platform fundamentals |
| 2 | KB-002: Automation Ecosystem | Link | How the automation stack fits together |
| 3 | Client Implementation Lifecycle | Link | Where your work fits in the client journey |
| 4 | GHL Naming Standard | Link | Naming conventions for all GHL objects |
2. WordPress Developer
Required Reading (in order)
| # | Document | Path | Why |
|---|
| 1 | SC WordPress Stack Standard | Link | Approved plugins/theme, prohibited categories, approval process |
| 2 | WordPress + GHL Integration Guide | Link | Architecture, design patterns, integration standards |
| 3 | WordPress Setup SOP | Link | Step-by-step new site setup procedure |
| 4 | GHL WordPress Hosting Overview | Link | Hosting environment, server config, access details |
| 5 | GTM WordPress Plugin SOP | Link | Google Tag Manager installation on WordPress |
| 6 | GTM Validation SOP | Link | How to verify GTM is firing correctly |
| 7 | GitHub Configuration Standard | Link | Repo naming, branching, access patterns |
| 8 | Robots.txt SOP | Link | Standard robots.txt configuration |
| 9 | Production Gate Checklist | Link | What must pass before going live |
| 10 | WordPress Staging-to-Live Checklist | Link | WP-specific staging to production cutover process |
Reference Material (consult as needed)
| Document | Path | When to Use |
|---|
| GHL-WordPress Custom Object Sync Pattern | Link | When building GHL ↔ WP data sync |
| Software Dev Project Template | Link | Starting a new dev project |
| SC Software Dev Guide | Link | General software development standards |
| Website Testing Automation | Link | Automated testing tools and approach |
| Responsively App Overview | Link | Cross-device responsive testing |
| Site Migration Checklist Template | Link | When migrating an existing site |
Documentation Gaps
- [GAP] WordPress code review standards — No document defining what "clean code" means for SC WordPress projects (naming conventions, file structure, prohibited patterns like direct DB queries, inline styles in PHP). The role definition says "no unnecessary code creeping into the codebase" but there's no reference doc to point to.
3. WordPress Designer
Required Reading (in order)
| # | Document | Path | Why |
|---|
| 1 | Design & Brand SOP (Brand Board) | Link | How SC handles branding deliverables |
| 2 | Brand Voice Template | Link | Template for capturing client brand voice |
| 3 | WordPress + GHL Integration Guide | Link | Elementor and design-relevant platform sections |
| 4 | Website Project Template | Link | Standard folder structure for website projects |
| 5 | Rebrand Project Plan Template | Link | How rebrands are planned and executed |
| 6 | Content Audit Template | Link | Auditing existing site content before redesign |
| 7 | Photopea Platform Overview | Link | Browser-based design tool used by SC |
| 8 | Figma Wireframe SOP | Link | When and how to create Figma wireframes before Elementor build |
| 9 | Logo Format Guide | Link | Logo sourcing, naming convention, GHL Media Storage structure |
Reference Material (consult as needed)
| Document | Path | When to Use |
|---|
| SC WordPress Stack Standard | Link | Approved stack and design constraints |
| Website Status Tracker Template | Link | Tracking multi-page design progress |
| Website Copy Review Instructions | Link | When reviewing or providing copy for pages |
| Responsively App Overview | Link | Cross-device responsive testing |
Documentation Gaps
- [GAP] SC visual identity / design system reference — No document captures SC's visual identity standards (primary blue
#3682AE, typography choices, spacing conventions, component patterns). Partially addressed by the Figma Wireframe SOP (brand integration section) and Elementor Best Practices Guide (global design system setup). Still needs a dedicated design system reference.
- [GAP] Elementor design conventions — No doc standardizing Elementor-specific patterns: global color names, global font names, section padding defaults, mobile breakpoint behavior. The development primer covers some of this but is developer-focused.
4. SEO Specialist
Required Reading (in order)
| # | Document | Path | Why |
|---|
| 1 | SearchAtlas Configuration Standard | Link | Primary SEO platform setup and usage |
| 2 | One-Time SEO Setup SOP | Link | What gets configured for every new client |
| 3 | GTM Integration SOP | Link | Google Tag Manager setup for tracking |
| 4 | GTM Validation SOP | Link | Verifying GTM is firing correctly |
| 5 | GHL Manual Review Request SOP | Link | Requesting Google reviews through GHL |
| 6 | GHL AI Review Response SOP | Link | AI-assisted review response workflow |
| 7 | SC Niche Classification System | Link | How SC categorizes client industries |
Reference Material (consult as needed)
| Document | Path | When to Use |
|---|
| GBP Holiday Hours SOP | Link | Updating Google Business Profile for holidays |
| Robots.txt SOP | Link | Configuring crawl access |
| SearchAtlas Training Materials | Link | Deep-dive SearchAtlas training |
| Client Knowledge Graph Template | Link | Structured client data for SEO |
Documentation Gaps
- [GAP] SEO reporting template / standard — No document defining what a monthly SEO report should contain, formatting, or delivery process. The role definition says "client-ready reports" but no template exists.
- [GAP] Local SEO playbook — No document capturing SC's local SEO methodology (GBP optimization steps, citation sources, NAP audit process). This is the #1 SEO use case for SC's client base (local service businesses).
Required Reading (in order)
| # | Document | Path | Why |
|---|
| 1 | Kristina Task Restructuring | Link | Content autonomy tiers — defines what a SM manager can post independently vs. what needs approval |
| 2 | Brand Voice Template | Link | Template for capturing client brand voice — essential for writing posts |
| 3 | GHL User Training | Link | Platform basics for social post scheduling and CRM features |
Reference Material (consult as needed)
| Document | Path | When to Use |
|---|
| Business AI Context Template | Link | Understanding client context for AI-assisted content |
| Client Profile Template | Link | Quick lookup of client details (replaces deprecated quick-reference template) |
| KB-012: Mastering Review Automations | Link | Understanding automated review workflows |
Documentation Gaps
- [GAP] Social media content calendar template — No standardized content calendar or posting schedule template.
- [GAP] Social media brand guidelines per client — No document capturing platform-specific guidelines (LinkedIn tone vs Facebook tone, image sizing, hashtag strategy). The brand voice template covers general tone but not social-specific conventions.
6. Account Manager
Required Reading (in order)
| # | Document | Path | Why |
|---|
| 1 | Client Support Process SOP | Link | Primary process -- intake, triage, escalation, SLA targets |
| 2 | Change Management Standard | Link | CR numbering, lifecycle, and storage conventions |
| 3 | Client Success Framework | Link | Primary client KPI (appointments booked) and success definitions |
| 4 | ClickUp basics | (covered during onboarding) | Basic task tracking — creating tasks, updating status |
| 5 | Client Implementation Lifecycle | Link | Where AM's work fits in the client journey |
| 6 | Account Manager Operations Guide | Link | Daily/weekly/monthly rhythms, templates, escalation tree |
| 7 | Client Onboarding Procedure (KB-004) | Link | Full onboarding flow -- AM needs to know handoff points |
| 8 | GHL Sub-Account Architecture (KB-009) | Link | Understanding client sub-accounts for routing and context |
Reference Material (consult as needed)
| Document | Path | When to Use |
|---|
| Change Request Template | Link | When creating a new CR document |
| Client Profile Template | Link | Understanding client data structure |
| Client Engagement Brief Template | Link | For client context during onboarding handoff |
| Team Structure | Link | Who does what -- for routing requests |
AI Agent Additional Reading
If the Account Manager role is filled by an AI agent, the following are also required:
| Document | Path | Why |
|---|
| SC Account Manager Agent Persona | Link | Agent-specific constraints, communication rules, never-do list |
| Working with Rohit Context Guide | Link | CEO preferences and escalation style |
| Per-client profiles | 09-clients/[client-slug]/client-profile.md | Client-specific context loaded per request |
Documentation Gaps
- [GAP] Account Manager onboarding walkthrough -- No step-by-step "first day as AM" guide covering how to gain access to the support inbox, ClickUp spaces, and Slack channels. The Team Member Onboarding Checklist covers generic access but not AM-specific setup.
7. Support Operator
Operators running the inbound support process (intake at support@symphonycore.com, authorization check, acknowledgment, triage, in-progress work, handoff, closure). This role can be filled internally or by a contractor; the reading list is the same. Contractor-specific access constraints are handled separately by the Support Operator Onboarding SOP § Phase 1.
Required Reading (in order)
Day 1: Foundation
| # | Document | Path | Why |
|---|
| 1 | Support Operator Onboarding SOP | Link | The front door — sequences the entire onboarding |
| 2 | Client Support Process SOP | Link | The keystone — state machine and decision points |
| 3 | Support Authorization Check SOP | Link | First gate at every inbound |
| 4 | Gmail Delegation Setup SOP | Link | Background on the mailbox access path |
| 5 | Gmail Send-as Alias Setup SOP | Link | Outbound From: mechanics |
Day 2: Templates and in-flight states
| # | Document | Path | Why |
|---|
| 6 | Support Acknowledgment Email Template | Link | Default first reply to authorized inbounds |
| 7 | Support Unauthorized Redirect Email Template | Link | Default response to non-clients |
| 8 | Support Closure Email Template | Link | Default closing message |
| 9 | Support Handoff SOP | Link | When and how to hand off |
Day 3: Context
| # | Document | Path | Why |
|---|
| 10 | How to Get Support (client-facing) | Link | What the client sees about support — your SLA promises |
| 11 | KB-014: Shared Email Accounts | Link | Inventory entry for support@ |
| 12 | ClickUp SC Operations Space Setup SOP | Link | How the support list fits in SC Ops |
| 13 | Support Weekly Review SOP | Link | The feedback loop |
Reference Material (consult as needed)
| Document | Path | When to Use |
|---|
| White-label / Branding rules | Link | Before any client-facing message — never GHL in client emails |
| SC SOP Standard | Link | If contributing or extending an SOP |
| Change Confirmation Email Template | Link | Support → paid Change Request escalations |
| Change Request Closure Email Template | Link | Closing a paid CR (vs. generic closure) |
| Partner Engagement Framework | Link | Contractor operators — engagement rules |
Documentation Gaps
- None at v1.0 of the Phase 1 support documentation set. Gaps will surface through the Support Weekly Review SOP and be recorded here as they're identified.
Gap Summary
| Role | Gap | Priority |
|---|
| WordPress Developer | WordPress code review standards | High |
| WordPress Developer | WP-specific staging → production checklist | Medium Resolved |
| WordPress Designer | SC visual identity / design system reference | High |
| WordPress Designer | Elementor design conventions | Medium |
| SEO Specialist | SEO reporting template / standard | High |
| SEO Specialist | Local SEO playbook | High |
| Social Media Manager | Social media content calendar template | Medium |
| Social Media Manager | Social media brand guidelines per client | Medium |
| Account Manager | AM onboarding walkthrough (first-day setup) | Low |
Revision History
| Version | Date | Author | Changes |
|---|
| 1.4 | 2026-05-18 | Symphony Core Systems Team | Add Section 7: Support Operator reading list (Phase 1 manual support process) |
| 1.3 | 2026-03-18 | Symphony Core Systems Team | Add WP Staging-to-Live Checklist to WP Developer required reading (resolves GAP), add Figma Wireframe SOP and Logo Format Guide to WP Designer required reading, add publish_to tag |
| 1.2 | 2026-03-01 | Symphony Core Systems Team | Update ClickUp references — replace deprecated clickup-config-standard link, simplify AM ClickUp reading to basic task tracking |
| 1.1 | 2026-02-24 | Symphony Core Systems Team | Add Section 6: Account Manager reading list |
| 1.0 | 2026-02-17 | Symphony Core Systems Team | Initial release covering WordPress Developer, WordPress Designer, SEO Specialist, Social Media Manager |