Pacific Viking Consulting
Executive guide

Behavioral Health Executive Operating System

How to run a leadership team on a weekly rhythm: KPI review, issues list, owner scorecards and follow-through.

Book a free discovery call

Sources checked Nov 18, 2026 · 6 min read

Brass desk clock beside a closed leather planner and a fountain pen on a dark oak table
On this pageWhy treatment programs need one
  1. Why treatment programs need one
  2. The weekly leadership meeting
  3. Owner scorecards
  4. The issues list and how items close
  5. Rolling it out without disrupting operations
  6. Sources

An executive operating system is the fixed weekly rhythm a leadership team runs on: one KPI review, one issues list, named owners with scorecards, and follow-through across clinical, admissions, revenue and compliance. In a treatment program it keeps census, authorizations and survey readiness from being managed in separate silos.

Why treatment programs need one

Treatment programs run on handoffs. Admissions hands a patient to clinical staff, clinicians hand notes to utilization review, reviewers hand authorizations to billing, and compliance depends on all of them. When each leader manages their own area alone, problems surface late and in someone else's numbers: a lapsed authorization shows up weeks later as a denial.

An operating system gives the leadership team one place to see those handoffs each week, one list of what is broken and one way to decide who fixes it. It is a set of routines, not software, and it starts with the reports the program already has.

Signs the program needs one

Look for these signs:

  • The same issues come up meeting after meeting without closing.
  • Leaders bring different numbers for the same measure.
  • Decisions are made in hallway conversations, and nobody writes them down.
  • Survey preparation starts only when a survey is expected.

What it is not

It is not a second layer of department meetings, a reporting exercise or a way for the chief executive to manage every detail. Department heads still run their teams. The leadership meeting handles what crosses between teams and what needs a decision above them.

The weekly leadership meeting

The core of the system is one leadership meeting each week: same day, same time, same agenda. Who attends depends on the program, but usually the chief executive or administrator, the clinical director, the medical director or a delegate, and the leaders for admissions, revenue cycle and compliance.

A simple agenda, in order:

  • Measures: each owner reports their scorecard, and only the measures off track are discussed.
  • Headlines: short updates on patients, staff or payers that leaders need to know, without discussion.
  • Issues: the team works the issues list, starting with the items that carry the most risk.
  • Decisions and actions: each decision is written down with its owner, its due date and who will tell the staff affected.

Running the meeting

Send the measures before the meeting, so time goes to problems rather than reading numbers aloud. Start on time even if someone is late, and end with a read-back of every decision and action. Keep patient names out of the meeting materials: leadership needs counts, trends and the status of fixes, not patient detail.

Who keeps it running

Name one person to keep the system running: preparing the measures, keeping the issues list current and recording decisions. In a smaller program that may be the administrator; in a larger one, an operations or quality lead. Without a named keeper, the routine drifts.

Using the agenda template

Pacific Viking's free executive meeting agenda template sets out a weekly agenda, rules for the measures review, issues list standards and a decision log. The download page asks for your name and email.

Owner scorecards

Each leader owns a short scorecard: a few measures that show whether their part of the program is working, each with a written definition, one data source and a target the team agrees. Measures should show results and risk, not activity counts. Examples:

  • Admissions: inquiries, qualified inquiries and admissions by level of care, and how quickly inquiries are answered.
  • Clinical: notes and treatment plan updates completed on time, and internal chart audit results.
  • Utilization review: reviews completed before their due date, and authorizations still pending.
  • Revenue cycle: denials by reason, and collections beside what was billed.
  • Compliance: open findings and corrective actions by due date, and required training completed.
  • Staffing: open roles, departures and agency or overtime shifts, with roles the license requires on their own line.

Survey readiness on the scorecard

Survey readiness belongs on the weekly scorecard because it cannot be built at the last minute. A Joint Commission resurvey of a behavioral health care setting comes with seven days' notice, hospital-based opioid treatment programs excepted, and a CARF-accredited organization submits an Annual Conformance to Quality Report signed by its leadership.[1][2][3]

Building the page behind the scorecards

Every scorecard draws on the same weekly page, so leaders argue about what the numbers mean rather than which numbers are right. The KPI dashboard guide covers how to define each measure and build that page.

The issues list and how items close

The issues list is one shared list of problems the leadership team has agreed to solve. Anyone on the team can add an item. Each item gets one owner, a due date and a plain statement of what closed will look like.

  • Name the problem, not the symptom: continued-stay reviews are missed because notes are late, rather than denials are up.
  • Work the highest-risk items first: anything touching a license, patient safety, a payer relationship or cash.
  • Close an item only when the fix is in place and the measure shows it, not when someone has talked about it.
  • Turn items that need more than one meeting into a short project with its own owner, and keep it on the list until it closes.

When items stay open

Items that stay open week after week are a signal in themselves. Either the owner lacks the authority to fix them, or the team has not agreed who decides. The leadership alignment guide covers decision rights and how disagreements between clinical and business leaders are escalated.

Recording decisions

Keep a running decision log: the date, the decision, who made it, who owns the follow-up and who needed to be told. Read the open items at the start of each meeting. The log settles later arguments about what was agreed, and it gives new leaders a record of how the program got where it is.

Rolling it out without disrupting operations

Start small and use what you already have. A rollout that waits for perfect data or new software stalls. A workable order:

  • Begin with the weekly meeting and the issues list, using the reports the program already runs.
  • Add one scorecard at a time, starting with the areas that carry the most risk.
  • Fix data definitions as they cause arguments, and write each fix down.
  • Bring department heads in through short team meetings that feed issues up to the leadership list.
  • Review the system itself every few months: which measures earned their place, and which meetings ran long.

Monthly and quarterly reviews

The weekly meeting handles the operation. Add a longer monthly or quarterly session for strategy, budgets, the quality program and the scorecards themselves, so the weekly meeting does not fill up with topics it cannot settle in the time it has.

Keeping it going

Keep the routine during busy weeks. The weeks when a survey, a staffing gap or a fall in census crowds the calendar are the weeks the meeting matters most. When a leader joins or leaves, walk them through the scorecards, the issues list and the decision log before their first meeting.

Pacific Viking's healthcare management consulting works with owners and executive teams nationwide on leadership structure, accountability and management systems. For the roles a leadership team needs, see the leadership team guide.

This guide is general information, not legal, billing or financial advice. Confirm current requirements with the agency and your counsel.

Sources

  1. [1]Unannounced survey process · The Joint Commission · jointcommission.org/en-us/knowledge-library/support-center/survey-or-review-preparation/unannounced-survey-process
    Last checked Nov 18, 2026
  2. [2]Steps to accreditation · CARF International · carf.org/accreditation/steps-accreditation
    Last checked Nov 18, 2026
  3. [3]Answering Your Questions About CARF (brochure) · CARF International · carf.org/wp-content/uploads/2025/12/Answering-Your-Questions-About-CARF-brochure.pdf
    Last checked Nov 18, 2026
FAQ

Frequently asked questions

What is an executive operating system?

It is the fixed set of routines a leadership team runs on: a weekly meeting with one review of measures, one list of open issues, named owners with scorecards, and written decisions that are followed up. It is a way of working, not a piece of software.

What should a weekly leadership meeting cover in a treatment center?

Each owner's scorecard, with discussion only for measures off track; short headlines; the issues list, highest risk first; and decisions with owners and due dates. In a treatment program the measures usually cover census and admissions, authorizations, documentation, collections, staffing and compliance.

How is this different from EOS?

EOS is one branded operating system. Pacific Viking is not affiliated with EOS Worldwide, and this guide does not describe or use its method. It sets out a general weekly leadership rhythm built around the handoffs of a treatment program.

Next step

Want a steadier leadership rhythm?

Book a free discovery call to talk through how your leadership team runs today and where the handoffs break down.

(417) 221-6175ConfidentialResponse within 24 hours