Scale B.O.S.S. Goals Guide

How supervisors create, publish, and manage individual goals inside the Team area

What this page is for
The Goals page is where a supervisor turns development and performance expectations into clear, reviewable commitments for a specific team member. It works best when goals are specific, time-boxed, and written with the Historical Summary panel open for context.

Goals workspace with employee selector on the left, goal cards in the center, and Historical Summary on the right.

How Goals fit into the system

Goals sit alongside Evaluations, CFOs, and Approvals as part of the same supervisory operating rhythm, but serve a distinct purpose.

Evaluations reflect how someone is performing. CFOs identify the operational work they own. Goals capture what that individual should develop, complete, or achieve over a quarter or year.

That distinction matters. A page full of vague goals becomes noise. A small number of clear, meaningful goals becomes a real management tool.

Use Goals for development, certification, capability-building, role-readiness, or measurable individual outcomes.
Do not convert every project, coaching note, or passing idea into a goal.
Keep the number of live goals tight and the wording specific.

Screen anatomy

The page is organized into four working areas.

1. Top context bar

The month selector and scope filter set the review context for the page. The top bar controls which team members appear in the left-hand selector and anchors the page to a real operating period, even when individual goals are quarterly or annual.

2. Left-hand employee selector

The left rail includes a search box and the supervisor's list of team members. Clicking a name updates both the center workspace and the Historical Summary to that individual. The highlighted row makes it immediately clear whose goals are being edited — an important safeguard in a supervisory workflow.

Employee selector with search and active employee highlight.

3. Center goal workspace

The center panel is where new goals are written and existing goals are maintained. Its broad, readable layout allows supervisors to work through each goal without opening a separate modal for routine edits. Titles, descriptions, goal periods, status, progress, notes, and the Draft → Ready → Published flow are all managed here.

Existing goal cards in the center workspace.

4. Historical Summary

The right panel provides context instead of relying on memory. It keeps recent performance, resource context, capacity, workload counts, tracked weaknesses, and evaluation history visible while goals are being created or updated. Supervisors can write or revise a goal without losing sight of what the employee is already carrying or how they have recently performed.

Historical Summary used as live context while goals are created or updated.

Creating a new goal

Clicking + New Goal opens the creation form in place at the top of the center workspace — not in a separate screen. It inserts above existing goals so the employee selector, current goals, and Historical Summary all remain visible. Good goal-setting is comparative; the full context should be accessible while building a new goal.

In-place goal creation form.

Field-by-field guide

Title: Required. Describe the outcome clearly enough that both supervisor and team member would interpret it the same way.

Description: Optional, but strongly recommended. Define what the goal means and what completion looks like.

Goal Type: Quarterly or Annual. Use Quarterly when the work should land within a specific quarter; use Annual when the commitment spans a full year.

Quarter / Year: These fields anchor the goal to a real time box. Time-boxing turns a good intention into a managed commitment.

Target Value / Unit: Use when a numeric outcome exists. Measurable targets make the goal easier to review honestly.

Good practice
Keep the Create button disabled until the goal is truly ready. A saved goal should not be a first rough thought. Use the in-place form to finalize the wording, period, and measurement before the goal becomes part of the employee's live record.

What strong goals look like

The best goals are outcome-based, time-bound, and reviewable. They tell the employee exactly what needs to happen and give the supervisor a clear standard for judging success.

One clear outcome
One owner
One defined period
A description that removes ambiguity
A measurable completion standard where applicable
Language that can be reviewed objectively

Goal writing examples

Weak goal	Stronger Scale B.O.S.S. goal
Improve marketing	Complete HubSpot Inbound Certification and submit a 1-page lifecycle-stage outline by end of Q1 2026.
Get more organized	Build and maintain a weekly client follow-up tracker for 8 consecutive weeks with no overdue follow-up older than 2 business days.
Learn more about onboarding	Publish a reusable onboarding checklist and train the client success team on its use before quarter-end.

The stage flow: Draft, Ready, Published

Each goal card follows the same stage logic used elsewhere in the Team area. Draft is for shaping the goal. Ready is for review. Published means the goal is live. This flow prevents the system from treating every saved thought as a real expectation.

Stage meanings

Stage	What it means on the Goals page
Draft	The supervisor is still building the goal. Keep it here while wording, scope, and time box are being refined.
Ready	The goal is well-formed enough for discussion or a final check. Use this stage when the goal is review-ready but not yet fully live.
Published	The goal is active and should be treated as a real management commitment, with live status, progress, and note updates.

Working with existing goal cards

Once created, a goal appears as a full card in the center workspace. Each card includes the title, period chip, status badge, description, goal type, period tags, status control, progress control, stage flow, notes area, and a copy control for reusing structure — everything needed for routine management without extra clicks.

Status and progress: the honesty test

This page only works if status and progress are updated truthfully. A polished interface does not create management value on its own — honest updates do.

Progress should reflect real movement, not good intentions. Not Started should sit near 0%. In Progress should reflect actual work completed. Completed should only be used when the description and completion standard have genuinely been satisfied.

Three common failure patterns

Inflated progress: The percentage moves because the person has been thinking about the goal, not because meaningful work has been done.
Status/progress mismatch: A goal is marked Completed when the deliverable is still missing, or In Progress when no real work has started.
Comment-free updates: The percentage changes but notes do not explain what actually happened.

What a strong update sounds like
Weak: "Making progress."
Strong: "Completed certification coursework and scheduled the exam. Lifecycle-stage outline is drafted and awaiting final review."

Using Notes effectively

The Notes area is where the story of a goal should live. A clear note trail makes end-of-period review far easier by showing what happened between the goal's creation and the close of the period.

Good notes record milestone updates, blockers, changed assumptions, completion evidence, next steps, and brief supervisor coaching points.

Record evidence, not just sentiment.
Do not restate the goal description in the notes each month.
Do not let the progress bar serve as the only record of movement.
When status changes materially, notes should explain why.

Using the Historical Summary while writing goals

The Historical Summary is decision support, not decoration. Before publishing a goal, the supervisor should scan the right-hand panel and confirm the goal fits the employee's recent reality.

Trait Average, Resource Average, and Capacity Average help judge readiness. Workload tiles indicate whether the employee is already stretched. Tracked weaknesses and recent evaluation periods connect the goal to real performance patterns rather than general impressions.

If recent performance is only meeting expectations, the goal may need to be narrower or more developmental.
If resources are weak, that context should shape how the goal is written.
If capacity is already tight, an ambitious new goal may create more noise than value.
If weaknesses are being tracked, consider whether the goal should directly support one of those improvement areas.

Judging whether a goal is appropriate

Before moving a goal to Published, pressure-test it. A reliable check: could the employee read only the title and description and know exactly what to do? If not, the goal is not ready.

At the due date, could I determine objectively whether it was completed?
Is it focused enough to be carried well and important enough to matter?
Does it fit the employee's current workload and capacity?
Is the wording precise enough to prevent disagreement later about what it meant?

What a good review looks like

A strong review:

The supervisor selected the right employee intentionally and consulted the Historical Summary before writing.
The title is outcome-based and the description removes ambiguity.
The period matches the real operating window.
The stage was not advanced prematurely.
Status and progress reflect the actual state of the work.
Notes explain movement rather than hiding behind a percentage.

A weak review:

The title is vague or motivational rather than operational.
The description is thin or absent.
The goal is too large for the period.
The goal was published before it was fully shaped.
Progress is optimistic rather than evidenced.
Notes are missing or provide little substance.

Recommended operating rhythm

The Goals page works best as part of a repeating management rhythm, not a once-a-quarter exercise. Create or refresh goals at the start of each period. Review them during regular check-ins. Update status only when real movement occurs. Add notes when milestones or blockers arise. Close the period honestly, even when the result is incomplete.

Keep goals specific, publish only when they are truly ready, and update only when evidence supports it.

Supervisor Guide To Creating And Managing Team Goals