Skip to main content

SC Operations Task Template

Purpose: Standard format for Symphony Core internal operations tasks (non-client work). Platform-agnostic -- use this structure regardless of where the task is tracked.

When to use: Agency platform configuration, internal tools work, documentation projects, infrastructure tasks.

Not for: Client deliverables (use the client implementation checklist), software development (use GitHub Issues).

Template​

Title:       [verb]-[component]-[item]
Type:        SC Operations
Sub-account: [GHL location ID or "N/A"]
Priority:    [Low | Medium | High | Critical]

Business Context:
  [1-3 sentences explaining WHY this task matters. Focus on the
  outcome or business benefit, not the technical steps.]

Scope:
  - [ ] [First verifiable deliverable]
  - [ ] [Second verifiable deliverable]
  - [ ] [Additional deliverables as needed]
  - [ ] [End-to-end verification step]

Reference Documents:
  - [Document title](https://team.symphonycore.com/path/to/document)
  - [Additional references as needed]

Notes:
  [Optional. Constraints, dependencies, follow-up tasks, or
  additional context. Remove this section if not needed.]

Field Guidance​

Title​

Use the naming pattern [verb]-[component]-[item]:

  • verb: What action is being taken (configure, migrate, document, build, test)
  • component: What system or area is affected (agency, dns, email, pipeline)
  • item: What specific thing is being acted on (prospecting-pipeline, forwarding-setup)

Examples:

  • configure-agency-prospecting-pipeline
  • migrate-dns-records-to-cloudflare
  • document-email-forwarding-setup
  • build-discovery-scanner-mvp

Business Context​

Write for someone who has no background on the task. Explain:

  • What business outcome does this enable?
  • Why is this being done now?

Avoid listing technical steps here -- that belongs in Scope.

Scope​

Each item should be independently verifiable. Write deliverables as checkable items, not process steps. Good scope items answer "how will we know this is done?"

GoodBad
Configure prospecting pipeline with 5 stagesWork on the pipeline
Verify booking link returns HTTP 200Check the link
Load 6 email templates into the platformSet up emails

Reference Documents​

Link to SOPs, guides, or standards on team.symphonycore.com that provide context or step-by-step instructions for completing the work.

Notes​

Use for anything that doesn't fit the other sections:

  • Hard dependencies (e.g., "requires DNS propagation before testing")
  • Explicit exclusions (e.g., "does not include Google Workspace configuration")
  • Follow-up work that may become its own task