Skip to main content

Contractor Onboarding Reading Lists

Overview​

This document maps each role to its required and recommended reading from existing Symphony Core documentation. It complements the Team Member Onboarding Checklist, which handles paperwork, platform access and Day 1 logistics for every engagement path.

How to use this document:

  1. Every new contractor starts with Section 1: All Contractors (universal baseline)
  2. Then proceed to the role-specific section for their position
  3. 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​

#DocumentPathWhy
1Team Ways of WorkingLinkChannels, response times, platform naming, confidentiality, escalation
2Team StructureLinkWho does what, reporting lines
3Timesheet & Invoice Submission SOPLinkHow to submit hours and get paid. Only if you invoice Symphony Core directly; vendor-placed team members skip it
4Google Drive Organization StandardLinkWhere files go, naming conventions
5ClickUp Ways of WorkingLinkHow tickets work. Only if you have ClickUp access
6Partner Engagement FrameworkLinkEngagement model, NDA, IP ownership

Not every universal item applies to every engagement path. Items 3, 4 and 6 are internal operating documents and live in the repository, not on team.symphonycore.com. A vendor-placed team member — employed by an agency, invoicing through it, holding one shared Drive folder and no ClickUp — reads items 1 and 2, and item 5 only with ClickUp access. The onboarding lead covers anything in 3, 4 or 6 that affects them. See Team Member Onboarding Checklist §6 for the rest of what changes on that path.

Week 1: Operations & Processes​

#DocumentPathWhy
1KB-002: Automation EcosystemLinkHow the automation stack fits together
2Client Implementation LifecycleLinkWhere your work fits in the client journey
3GHL Naming StandardLinkNaming conventions for all GHL objects

2. WordPress Developer​

Required Reading (in order)​

#DocumentPathWhy
1SC WordPress Stack StandardLinkApproved plugins/theme, prohibited categories, approval process
2WordPress + GHL Integration GuideLinkArchitecture, design patterns, integration standards
3WordPress Setup SOPLinkStep-by-step new site setup procedure
4GHL WordPress Hosting OverviewLinkHosting environment, server config, access details
5GTM WordPress Plugin SOPLinkGoogle Tag Manager installation on WordPress
6GTM Validation SOPLinkHow to verify GTM is firing correctly
7GitHub Configuration StandardLinkRepo naming, branching, access patterns
8Robots.txt SOPLinkStandard robots.txt configuration
9Production Gate ChecklistLinkWhat must pass before going live
10WordPress Staging-to-Live ChecklistLinkWP-specific staging to production cutover process

Reference Material (consult as needed)​

DocumentPathWhen to Use
GHL-WordPress Custom Object Sync PatternLinkWhen building GHL ↔ WP data sync
Software Dev Project TemplateLinkStarting a new dev project
SC Software Dev GuideLinkGeneral software development standards
Website Testing AutomationLinkAutomated testing tools and approach
Responsively App OverviewLinkCross-device responsive testing
Site Migration Checklist TemplateLinkWhen 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)​

#DocumentPathWhy
1Design & Brand SOP (Brand Board)LinkHow SC handles branding deliverables
2Brand Voice TemplateLinkTemplate for capturing client brand voice
3WordPress + GHL Integration GuideLinkElementor and design-relevant platform sections
4Website Project TemplateLinkStandard folder structure for website projects
5Rebrand Project Plan TemplateLinkHow rebrands are planned and executed
6Content Audit TemplateLinkAuditing existing site content before redesign
7Photopea Platform OverviewLinkBrowser-based design tool used by SC
8Figma Wireframe SOPLinkWhen and how to create Figma wireframes before Elementor build
9Logo Format GuideLinkLogo sourcing, naming convention, GHL Media Storage structure

Reference Material (consult as needed)​

DocumentPathWhen to Use
SC WordPress Stack StandardLinkApproved stack and design constraints
Website Status Tracker TemplateLinkTracking multi-page design progress
Website Copy Review InstructionsLinkWhen reviewing or providing copy for pages
Responsively App OverviewLinkCross-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)​

#DocumentPathWhy
1Rank Math Configuration StandardLinkSEO plugin configuration on client WordPress sites
2Client SEO Foundation Setup SOPLinkWhat gets configured when a client takes SEO
3GTM Integration SOPLinkGoogle Tag Manager setup for tracking
4GTM Validation SOPLinkVerifying GTM is firing correctly
5GHL Manual Review Request SOPLinkRequesting Google reviews through GHL
6GHL AI Review Response SOPLinkAI-assisted review response workflow
7SC Niche Classification SystemLinkHow SC categorizes client industries

Reference Material (consult as needed)​

DocumentPathWhen to Use
GBP Holiday Hours SOPLinkUpdating Google Business Profile for holidays
Robots.txt SOPLinkConfiguring crawl access
Client Knowledge Graph TemplateLinkStructured 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).

5. Social Media Manager​

Required Reading (in order)​

#DocumentPathWhy
1Kristina Task RestructuringLinkContent autonomy tiers — defines what a SM manager can post independently vs. what needs approval
2Brand Voice TemplateLinkTemplate for capturing client brand voice — essential for writing posts
3GHL User TrainingLinkPlatform basics for social post scheduling and CRM features

Reference Material (consult as needed)​

DocumentPathWhen to Use
Business AI Context TemplateLinkUnderstanding client context for AI-assisted content
Client Profile TemplateLinkQuick lookup of client details (replaces deprecated quick-reference template)
KB-012: Mastering Review AutomationsLinkUnderstanding 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. Client Success Manager​

Supersedes the former Account Manager reading list. The Client Success Manager (India) role replaces the coordination-only Account Manager with a senior, client-relationship owner who runs decision calls and holds the roadmap. The reading below still applies; AM-era documents are flagged where they are being reworked for the CSM.

Required Reading (in order)​

#DocumentPathWhy
1Client Support Process SOPLinkPrimary process -- intake, triage, escalation, SLA targets
2Change Management StandardLinkCR numbering, lifecycle, and storage conventions
3Client Success FrameworkLinkPrimary client KPI (appointments booked) and success definitions
4ClickUp basics(covered during onboarding)Basic task tracking — creating tasks, updating status
5Client Implementation LifecycleLinkWhere the CSM's work fits in the client journey
6Account Manager Operations GuideLinkDaily/weekly/monthly rhythms, templates, escalation tree (deprecated AM-era guide; content still valid and being reworked into a CSM operations guide)
6aHiring & Onboarding LifecycleLinkHow the CSM role fits the full team-member lifecycle
7Client Onboarding Procedure (KB-004)LinkFull onboarding flow -- AM needs to know handoff points
8GHL Sub-Account Architecture (KB-009)LinkUnderstanding client sub-accounts for routing and context

Reference Material (consult as needed)​

DocumentPathWhen to Use
Change Request TemplateLinkWhen creating a new CR document
Client Profile TemplateLinkUnderstanding client data structure
Client Engagement Brief TemplateLinkFor client context during onboarding handoff
Team StructureLinkWho does what -- for routing requests

AI Intake Automation Additional Reading​

Symphony Core uses AI intake automation to support the Client Success Manager (acknowledgment, triage, ClickUp task creation). Where that automation is in use, the following also apply:

DocumentPathWhy
SC Account Manager Agent PersonaLinkAgent-specific constraints, communication rules, never-do list
Per-client profiles09-clients/[client-slug]/client-profile.mdClient-specific context loaded per request

Documentation Gaps​

  • [GAP] Client Success Manager onboarding walkthrough -- No step-by-step "first day as CSM" 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 CSM-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​

#DocumentPathWhy
1Support Operator Onboarding SOPLinkThe front door — sequences the entire onboarding
2Client Support Process SOPLinkThe keystone — state machine and decision points
3Support Authorization Check SOPLinkFirst gate at every inbound
4Gmail Delegation Setup SOPLinkBackground on the mailbox access path
5Gmail Send-as Alias Setup SOPLinkOutbound From: mechanics

Day 2: Templates and in-flight states​

#DocumentPathWhy
6Support Acknowledgment Email TemplateLinkDefault first reply to authorized inbounds
7Support Unauthorized Redirect Email TemplateLinkDefault response to non-clients
8Support Closure Email TemplateLinkDefault closing message
9Support Handoff SOPLinkWhen and how to hand off

Day 3: Context​

#DocumentPathWhy
10How to Get Support (client-facing)LinkWhat the client sees about support — your SLA promises
11KB-014: Shared Email AccountsLinkInventory entry for support@
12ClickUp SC Operations Space Setup SOPLinkHow the support list fits in SC Ops
13Support Weekly Review SOPLinkThe feedback loop

Reference Material (consult as needed)​

DocumentPathWhen to Use
White-label / Branding rulesLinkBefore any client-facing message — never GHL in client emails
SC SOP StandardLinkIf contributing or extending an SOP
Change Confirmation Email TemplateLinkSupport → paid Change Request escalations
Change Request Closure Email TemplateLinkClosing a paid CR (vs. generic closure)
Partner Engagement FrameworkLinkContractor 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.

8. Inside Sales / Prospecting​

The outbound caller. Dials prospects, works the audit report as the reason for the call, and books discovery calls. This role talks to strangers on a recorded line in a regulated channel, which is why the order below is not negotiable and why one item is a gate rather than a reading.

The rule that orders this list​

Compliance comes before any script, and the offer comes before both. A caller who learns the opener first will say it before they know which states are closed, who is allowed to hear the call, or what to do when someone asks to stop. Every other role's reading list can be read in any order and lose little. This one cannot.

The offer sits ahead of the compliance block for a different reason: it is short, and without it the rest of day 1 is a list of prohibitions attached to a business nobody has described. Twenty minutes on what Symphony Core sells makes the remaining six hours make sense.

Day 1, first: What Symphony Core is and what it sells​

Twenty minutes, before anything else. You cannot describe an offer you have not been told about, and the very first thing you do on a call is say why you are ringing.

#DocumentPathWhy
1Inside Sales Day One MapLinkStart here. The whole job in four diagrams: where a lead comes from, the shape of a block, what follows a dial, and the three hard boundaries. Ten minutes, and it makes the rest of this list readable
2Symphony Core at a GlanceLinkWhat the company is, what it sells, what it is trying to do, and which system holds what. Twenty minutes
3Symphony Core Company InfoLinkWhat we sell, to whom, and at what price. The quick-reference, not the deck
4Prospecting Bucket TaxonomyLinkThe five problems every call opens on. The audit has already picked one for you

Day 1, then: What you may and may not do​

Read in this order. Nothing else on day 1, and no dialling on day 1.

#DocumentPathWhy
5Inside Sales Caller Operating GuideLinkThe spine — what the job is, which list, what order, what to do with each outcome
6Inside Sales Caller Rule SheetLinkOne page, and the only one you keep open during every block. The rules first, then an index of every activity and the document that covers it — once you have read this list once, that index replaces it
7SC Outbound Calling Compliance StandardLinkThe reasoning behind every line of the rule sheet. Read it once properly; you will not read it again
8Sales Development Onboarding SOPLinkHow the ramp works and what the gates are

Day 2: What you say​

#DocumentPathWhy
9Prospecting Cold Call ScriptsLinkThe openers, the beats, the finding-to-spoken-line table
10Prospecting Objection HandlingLinkValidate / label / secondary ask. Includes "how did you get my number?"
11Prospect Qualification StandardLinkWhich gate is answered at which point, and by whom. Keeps you from disqualifying too early
12SC Ideal Customer ProfileLinkWho we are for, and the disqualifiers

🚪 Gate — before any dial, live or mock. Answer these four from memory, no notes. From the SDR onboarding SOP:

  1. Which three states are never called, and why is New York not one of them?
  2. What is the calling window, and whose clock is it?
  3. Who tells the prospect the call is recorded, and when must you say it yourself?
  4. What do you do the moment someone asks to be taken off the list?

A wrong answer is not a failure, it is a re-read. Nobody dials until all four are right.

Day 3: How the machine works​

#DocumentPathWhy
13Prospect Phone and Call Execution SOPLinkBlock mechanics, the thirteen dispositions, the CALL | note format
14Symphony Core Sales PipelineLinkWhat each stage means and who moves it
15Marketing audit report — a real one(the Implementation Lead sends two examples)You will reference this on every call. Read two before you talk about one

Week 1: Reference, as needed​

#DocumentPathWhy
16Prospecting Review Response PlayLinkThe reviews-led variant of the call
17TCPA SMS Consent and Suppression StandardLinkWhen you may text a prospect and when you may not. You have a line of your own, so this is a rule you apply rather than a restriction applied to you
18SC Brand VoiceLinkHow we sound, for when you write a follow-up email
19Prospect Bucket Slotting ChecklistLinkHow the buckets are decided, when you want the reasoning behind a tick
20Prospect Reply Handling SOPLinkAnswering a reply to the audit email: the eleven reply shapes, and what escalates

Not on this list, on purpose​

Not readWhy
The lead research and CRM import SOPHow the list is built is not how the list is worked
The C-021 and C-024 workflow specsNode-level automation design. The caller needs the behaviour, which the operating guide gives
KB platform trainingWritten for delivery roles on the platform's build surface, not for Contacts and Conversations

This list is read once, in order. After that, work from Where everything lives on the rule sheet — it maps each activity to the document, and nobody should be re-reading an eighteen-item path to find out where a disposition is defined.

The universal Day-1 list in §1 still applies, minus the items that assume a delivery role. The timesheet SOP applies only if the caller invoices Symphony Core directly; a vendor-placed caller skips it.

Documentation Gaps​

  • None. The operating guide closes the spine gap that this role had before 2026-10-26.

Gap Summary​

RoleGapPriority
WordPress DeveloperWordPress code review standardsHigh
WordPress DeveloperWP-specific staging → production checklistMedium Resolved
WordPress DesignerSC visual identity / design system referenceHigh
WordPress DesignerElementor design conventionsMedium
SEO SpecialistSEO reporting template / standardHigh
SEO SpecialistLocal SEO playbookHigh
Social Media ManagerSocial media content calendar templateMedium
Social Media ManagerSocial media brand guidelines per clientMedium
Client Success ManagerCSM onboarding walkthrough (first-day setup)Low
Client Success ManagerCSM operations guide (rework of the deprecated AM Operations Guide)Medium
Inside Sales / ProspectingNo reading path for the outbound calling roleHigh Resolved


Revision History​

VersionDateAuthorChanges
2026-09-011.6Retitled the role from Client Delivery Manager to Client Success Manager. "Client Delivery Manager" reads as an IT-services programme role in the Indian market and was repeatedly re-mapped by the recruiting partner to titles she could source and price; Client Success Manager is the searchable market-standard title and sits one word from the band already benchmarked. Scope of the role is unchanged.Symphony Core Systems Team
1.112026-11-02Symphony Core Systems Team§8 reconciled with five days of live calling. Three rows had gone false: item 17 said texting "is not available to you" before the caller had a line of her own, item 13 said twelve dispositions where there are thirteen, and the exclusion list said a different seat runs the email motion, which stopped being true when prospect communication moved to the caller. The email-outreach exclusion is removed, the bucket slotting checklist and reply handling SOP are added as week-1 references now that both are on the wiki, and the list now hands off to the rule sheet's activity index instead of expecting itself to be re-read
1.82026-10-27Symphony Core Systems Team§1 Day 1 now opens with Team Ways of Working instead of the founder's context guide, which left this repo. Timesheet SOP marked as applying only to people who invoice SC directly. ClickUp item links ClickUp Ways of Working. Removed retired tools: KB-001 (Extendly) from Week 1, SearchAtlas from the SEO list (replaced by the Rank Math Configuration Standard).
1.102026-10-27Symphony Core Systems TeamMakes the list reachable for the people it is written for. Thirteen of the twenty-three items across Sections 1 and 8 carried no publish_to, so they existed only in the repository — and a contractor has wiki access, not repository access. Eight are now published: the company-info quick reference, team structure, the bucket taxonomy, the ICP, the qualification standard, the review-response play, the TCPA standard and brand voice. Section 8 item 1 moves from sc-goals.md, which stays internal because it carries revenue targets, to a new Symphony Core at a Glance page that gives the orientation without them. Section 1 gains engagement-path scoping: three of its items are internal operating documents a vendor-placed team member does not read, which the list had left to inference
1.92026-10-27Symphony Core Systems TeamSection 8 gains a company introduction, which it did not have. Day 1 went from the operating guide straight into the compliance standard, and the universal Day-1 list in Section 1 is entirely admin — ways of working, timesheets, Drive — so a cold caller could reach mock calls having never been told what Symphony Core sells or to whom. The first company context arrived on Day 2 through the ICP. Three items now sit ahead of the limits: SC Goals, the company-info quick reference, and the bucket taxonomy, which carries the five problems every call actually opens on. The compliance-before-any-script rule is unchanged; the offer is not a script
1.72026-10-26Symphony Core Systems TeamAdd Section 8: Inside Sales / Prospecting. The first reading list ordered by legal exposure rather than by topic — the compliance standard is read before any script, and a four-question gate stands between reading and the first dial, because a caller who learns the opener first will say it before they know which states are closed. Also the first list with an explicit not-read table: the email motion belongs to a different seat and reading it invites scope the role does not have. Gap Summary records the sales path as resolved
1.52026-06-07Symphony Core Systems TeamRealign Section 6 Account Manager → Client Delivery Manager (role superseded); link CDM role + lifecycle map; flag deprecated AM Operations Guide; reframe AI-agent reading as AI intake automation; update doc-gap entries
1.42026-05-18Symphony Core Systems TeamAdd Section 7: Support Operator reading list (Phase 1 manual support process)
1.32026-03-18Symphony Core Systems TeamAdd 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.22026-03-01Symphony Core Systems TeamUpdate ClickUp references — replace deprecated clickup-config-standard link, simplify AM ClickUp reading to basic task tracking
1.12026-02-24Symphony Core Systems TeamAdd Section 6: Account Manager reading list
1.02026-02-17Symphony Core Systems TeamInitial release covering WordPress Developer, WordPress Designer, SEO Specialist, Social Media Manager