LocalPRO Leadership OS

v8.39 1:1 Voice + Formatting Freeze
Filters apply across Cockpit, Scorecards, Projects, Meeting, Reports, and Print Packet.

Performance Cockpit

A Performance First command deck: People, Systems, Standards, and measurable execution.
Peopleleaders, agents, coaching
Systemsoperating rhythm and repeatability
Standardsdiscipline, quality, accountability
Performanceoutcomes over activity
Leadership AttentionRisks, red metrics, stale updates, and overdue work
Decisions NeededOnly true leadership decisions appear here
Department Flight DeckExecutive scan by department: health, owner, priorities, projects, operating risks, and decisions
Project RadarStrategic initiatives only

Department Blueprints

Clear line of sight for every business unit: purpose, responsibilities, KPIs, projects, decisions, risks, and trend direction over time.
Blueprint + Trends
Weekly Metric Entry
Metric IntelligenceDefinition, why it matters, red action, history
Strategic Project
Feeds Leadership Attention.
Feeds Decisions Needed and Meeting Mode.
Project RadarClick any project to edit

Leadership 1:1s

A guided weekly leadership conversation built around wins, blockers, priorities, support needed, a short pulse check, and commitments.
Leadership Conversation
Leadership 1:1Five-question rhythm
—

Run the conversation, not the software.

Start with context, then ask the same five questions every week. Keep the discussion practical: what changed, what is stuck, what matters next, what leadership owes them, and how they are doing.
01WinsMomentum and repeatable progress.
02ChallengesFriction, blockers, frustration.
03Priorities2–3 outcomes before next meeting.
04SupportDecisions, resources, obstacles.
05Pulse CheckCatch anything important before it builds.

Metrics to Discuss

Read-only context from the selected leader's department. Use this to ground the conversation in facts.

Projects to Discuss

Active projects owned by this leader or tied to the department. Use this to surface risks and decisions.
Role Profile / Responsibilities
Update only when the role changes. This is not the weekly meeting record.
Profile fields do not archive 1:1 history.

What were your biggest wins since we last met?

Question 1
  • What are you most proud of?
  • What worked particularly well?
  • What should we repeat?

What challenges or frustrations are slowing you down?

Question 2
  • What's getting in your way?
  • Where are you stuck?
  • What's harder than it should be?

What are your top priorities before our next meeting?

Question 3
  • What are the 2–3 most important outcomes?
  • What absolutely must get done?
  • How will success be measured?

What support do you need from me?

Question 4
  • What decisions need to be made?
  • What resources are missing?
  • Where can I help remove obstacles?

How are you feeling about your role right now?

Question 5
  • What feels clear or unclear?
  • What would make the role easier to execute?
  • Anything I should know that I do not know?

Commitments & Archive

Turn the conversation into accountability. Add one commitment per line, then archive the weekly session before leaving the page.

Open Commitments

1:1 History

No archived sessions yet.
Show / Hide

Weekly Performance Meeting

Presentation mode. Advance one step at a time. No wandering.

Reports

Monthly, quarterly, and annual leadership reporting from the same metric entries.
Monthly Report

Operating Manual

Adoption-first operating manual: what to update weekly, where each item shows up, and how leadership should use the OS.
Performance First Rhythm

Weekly Fill-Out Order

  1. Metrics first. Enter this period’s actual results. This makes the Cockpit trustworthy.
  2. Projects second. Update health, next milestone, risk, decision needed, owner, and due date.
  3. Department Blueprints third. Review purpose, responsibilities, KPIs, monthly/quarterly/annual trends, projects, risks, and decisions. Use Control Center only when the structure itself needs editing.
  4. 1:1s fourth. Select the person, review role clarity, metric snapshot, and active projects, then discuss wins, blockers, outcomes, and commitments. Archive the weekly session before leaving the page.
  5. Meeting fifth. Run Meeting Mode. Do not wander. Every issue becomes a decision, owner, or commitment.
  6. Reports and backup last. Review the report packet, then export JSON as the source-of-truth backup.

1:1 Consistency Standard

Every leadership 1:1 should use the same rhythm so notes stay comparable over time.

  • Wins: evidence of progress, not general encouragement.
  • Challenges: constraints, blockers, or leadership help needed.
  • Current Focus: the one or two outcomes that matter most before the next 1:1.
  • Commitments: specific owner-owned actions with due dates. If it has no owner or due date, it is not a commitment.

Profile vs 1:1 vs Commitments

  • Save Profile stores responsibilities, expected outcomes, and current focus.
  • Archive 1:1 stores the five-question weekly conversation and history.
  • Add Commitments creates accountability items that feed Cockpit, Meeting Mode, and reporting.

Editable Descriptions

Department purpose statements are editable in Control Center. They should be one clear sentence explaining why the department exists and what business outcome it owns.

  • Good: “Owns agent attraction, conversion, and net agent growth.”
  • Weak: “Handles recruiting.”
  • Use the defaults as the starting point; tighten them once LocalPRO’s language is final.

What Populates the Cockpit

  • Metric entries populate Performance Index, momentum, reports, and attention.
  • Project risks and standing department risks populate Leadership Attention.
  • Project and department decisions populate Decisions Needed.
  • Commitments populate accountability, Meeting Mode, and commitment aging.
  • 1:1 current focus populates the People step in Meeting Mode.

Voice Capture

Voice dictation can reduce typing for 1:1 notes and long descriptions. It uses the browser’s built-in speech recognition when available.

  • Best in Chrome or Edge.
  • May not work in every browser or local-file security setting.
  • Use voice for rough capture, then tighten the wording before saving.

Risk Language Standard

  • 1:1 Blockers / Risks: individual obstacles surfaced in coaching conversations.
  • Operating Risks: current department-level risks discussed in Scorecards and Meeting Mode.
  • Standing Department Risks: structural or ongoing risks maintained in Control Center.

Meeting Standard

No storytelling unless it creates a decision, assignment, owner, or commitment. The OS should drive action, not record conversation.

Backup Standard

Export JSON every Friday. CSV is for review only; JSON is the source of truth and safest upgrade path until the OS is online.

Control Center

Configuration only. Weekly operators should use Metrics, Projects, Scorecards, and 1:1s before touching Control Center.
Select Department
Supports bold and bullets for cleaner Department Blueprint documentation.
Structural or ongoing risks that affect department performance. These are not weekly coaching blockers.
Metric format: Name | Cadence | Unit | Goal | Direction | Score Weight | Definition | Why it matters | Red action. Score Weight is the 1–10 weighting used in the Performance Index; it is not a target and not the red/yellow/green threshold. Example: Avg Transactions / Agent | Monthly | annualized | 18 | Higher | 10 | Annualized average transactions per agent | Shows production density | Review at-risk agents.

Audit Log

Retains the most recent 500 meaningful events.
0 EventsNo history
Saved