GoHighLevel Agency TrainingA Dynamic AI HUB training resource
Reporting and Dashboard

Baseline reporting view

Which reports actually matter early on.

Beginner20 min

Purpose

This SOP helps you create a simple baseline reporting view for a new or cleaned CRM account. Early reporting should answer practical business questions: - Where are leads coming from? - Are leads turning into opportunities? - Are appointments being booked? - Are opportunities moving through the pipeline? - Are workflows and campaigns helping or creating noise? - Are emails bouncing or creating complaints? - What should the team review each week? The goal is not to build a complicated dashboard. The goal is to create a simple view that helps the team make better decisions.

When to Use This SOP

  • A new CRM account is being set up
  • The 8-week training path is complete or nearly complete
  • A team needs a weekly review process
  • Reporting feels noisy or unreliable
  • A business wants to understand lead source and pipeline performance
  • Dashboards are full of vanity metrics but not useful decisions

Before You Start

  • Do not build reporting before the underlying system is clean.
  • Reports depend on pipeline stages
  • Source tags
  • Custom fields
  • Calendar bookings
  • Workflow activity
  • Campaign performance
  • Clean contact data
  • Consistent opportunity movement
  • If the underlying data is messy, reporting will be messy too.
  • Before building a reporting view, confirm pipelines are named clearly
  • Lead sources are tagged or stored consistently
  • Appointment stages are defined
  • Workflows are not duplicating leads
  • Campaigns have clear goals
  • Imports are tagged by batch
  • The team understands what should be reviewed weekly

Step-by-Step Procedure

  1. 1
    Choose the reporting questions

    Start with questions, not charts.

    A simple baseline reporting view should answer:

    • How many new leads came in?
    • Where did those leads come from?
    • How many became opportunities?
    • How many booked appointments?
    • How many appointments were completed?
    • How many opportunities are in each stage?
    • How many were won, lost, or marked not a fit?
    • Which sources produce better opportunities?
    • Which workflows or campaigns need review?
    • Are email sends creating bounces or complaints?

    If a metric does not help the team decide what to do, do not make it central.

  2. 2
    Review lead source reporting

    Lead source reporting only works if the CRM captures source consistently.

    Review whether source is tracked by:

    • Source tag
    • Source custom field
    • UTM values
    • Form source
    • QR code source
    • Campaign source
    • Manual entry source

    At minimum, the team should know where a lead came from. Better reporting can later show which sources produce booked appointments, qualified opportunities, and clients.

    Avoid one generic source tag for everything. The source should be specific enough to help the business make decisions.

  3. 3
    Review pipeline stage counts

    Pipeline reporting should show the current state of opportunities.

    Review:

    • New Lead
    • Contact Attempted
    • Appointment Booked
    • Appointment Completed
    • Proposal Sent
    • Won
    • Lost / Not a Fit
    • Follow-Up Later

    Use the stages that match the business. Do not add stages only because a dashboard looks empty.

    Pipeline reports should help the team identify where deals are stuck.

  4. 4
    Review appointment reporting

    For appointment-based businesses, bookings are a key operating metric.

    Track:

    • Appointments booked
    • Appointments completed
    • No-shows
    • Cancellations
    • Reschedules
    • Booking source
    • Appointment owner or assigned user

    If appointments are not being tracked consistently, review calendar setup before trusting the report.

  5. 5
    Review workflow and campaign performance

    Early workflow reporting should focus on whether the system is behaving correctly.

    Review:

    • Which workflows are active
    • Which workflows are triggering
    • Whether contacts are stuck in wait steps
    • Whether duplicate workflows are firing
    • Whether the correct workflow starts from each form or calendar
    • Whether campaign emails are connected to the correct audience
    • Whether stop conditions work

    For campaigns, review: delivery, bounces, clicks, replies, bookings, unsubscribes, complaints.

    Do not judge email only by open rate. Opens can be incomplete or misleading. Replies, clicks, bookings, and complaints are more useful.

  6. 6
    Review email health

    Email reporting should help protect deliverability.

    Watch:

    • Bounce rate
    • Repeated failed sends
    • Spam complaints
    • Unsubscribes
    • Low engagement from old lists
    • Sending to unclear or unverified audiences

    If a campaign creates unusual complaints or bounces, pause and review the audience before sending more.

  7. 7
    Build the baseline view

    Create a simple reporting view or dashboard that includes only the metrics the team will actually review.

    Suggested baseline sections:

    • New leads by source
    • Opportunities by stage
    • Appointment bookings and outcomes
    • Won, lost, and not-a-fit outcomes
    • Campaign or nurture performance
    • Email bounce and complaint awareness
    • Tasks or conversations needing team review

    The dashboard should not become decoration. It should support weekly operating decisions.

  8. 8
    Create a weekly review rhythm

    Schedule a recurring reporting review.

    A simple weekly review should ask:

    • What sources produced leads?
    • Which leads became opportunities?
    • Where are opportunities stuck?
    • Were appointments completed or missed?
    • Did any workflow behave unexpectedly?
    • Did any campaign create bounces, complaints, or useful replies?
    • What needs follow-up this week?
    • What should be fixed before more traffic is sent into the system?

    Keep the review short and practical.

  9. 9
    Document reporting definitions

    Create a reporting definitions note.

    Include:

    • What counts as a new lead
    • What counts as a booked appointment
    • What counts as a completed appointment
    • What counts as a qualified opportunity
    • What counts as won
    • What counts as lost or not a fit
    • Which source field or tag is used
    • Which reports are reviewed weekly
    • Who is responsible for review

    Without definitions, two team members may read the same dashboard differently.

Checks Before You Finish

  • ✓Reporting questions are defined
  • ✓Lead source tracking is reviewed
  • ✓Pipeline stage counts are visible
  • ✓Appointment reporting is reviewed if relevant
  • ✓Workflow behavior is part of reporting review
  • ✓Campaign performance is reviewed beyond open rate
  • ✓Email bounce and complaint awareness is included
  • ✓Dashboard view is simple and useful
  • ✓Weekly review rhythm is defined
  • ✓Reporting definitions are documented

Common Mistakes

Watch for these
  • Building a dashboard before the data is clean
  • Tracking vanity metrics that do not change decisions
  • Counting leads without checking lead quality
  • Treating all sources as equal
  • Trusting pipeline reports when stages are unclear
  • Ignoring no-shows and cancellations
  • Judging campaigns only by open rate
  • Ignoring bounces and complaints
  • Letting dashboards become cluttered
  • Reviewing reports without assigning follow-up actions

Related SOPs

← Back to SOP Library