Ranking in Connections

Connections Online uses a ranking system to organize Metrics, Projects, and Tasks into logical hierarchies. This system helps users visualize relationships, group related items, and maintain clarity across organizational goals and initiatives.

Why Ranking Matters

• Clarity: Makes it easy to see how detailed metrics roll up into strategic objectives.
• Reporting: Enables structured dashboards and roll-up views.
• Flexibility: You can reorganize metrics easily by adjusting their rank.

What Is Ranking?

Ranking is a manual, decimal-based system that reflects the relationship between items. It’s used to:

• Group related items together
• Indicate parent-child relationships
• Organize dashboards and reports

Ranking is set in the Rank field when editing an item.

By default if no rank is chosen, (auto), the new metric/task/project will be placed at the end/bottom of the list.

Ranking for Metrics

Metrics are the most structurally dynamic item in Connections Online. They can be ranked to reflect strategic goals and sub-goals, and they support value roll-ups from child metrics to parent metrics when the parent is configured as a rolled-up metric. A metric must have all three of its thresholds set for it to be considered an active metric for performance management purposes. You can have a metric with just a name as a category to group.

For more on rolled-up and linked metrics, see this article.

How Metric Ranking Works

• Parent Metrics: Assigned whole numbers (e.g., 1.) to represent high-level goals.
• Child Metrics: Use decimals (e.g., 1.1, 1.2) to show contributing subcategories.
• Sub-child Metrics: Extend further (e.g., 1.1.1) for deeper breakdowns.

Example

In the above example 1.1 Net Aspiring Member Growth is a rolled-up metric and it will automatically calculate values from its children as either a sum or average of their combined current values.

Ranking for Projects

Projects are arranged in groups by status in dedicated lists on either the Organization page or within a Department. There are no dependencies between projects in Connections. Ranking is purely for organizational clarity. Each status will have its own separate numbered ranks.

Project Structure

• Projects: Assigned whole numbers (e.g., 2.).
• Sub-projects: Can be added using decimals (e.g., 2.1).
• Tasks: Exist only within the context of a specific project and are not shared across projects.

Example

Sub-projects are useful for breaking down large initiatives but are not commonly used.

Ranking for Tasks

Tasks are tied to a specific project and follow a similar ranking logic within that project’s task list.

• Parent Tasks: Assigned whole numbers (e.g., 1.).
• Subtasks: Use decimals (e.g., 1.1, 1.2) to show dependencies or workflow steps.

Note: Tasks and subtasks are not functionally linked. Ranking is for visual grouping only. There are no task dependencies.

Example

Summary of Ranking by Item Type

Metrics

• Used for strategic grouping and goal alignment
• Supports parent-child relationships through ranking
• Can roll up values from child metrics when configured as rolled-up
• Most dynamic and functional use of ranking in the system

Projects

• Used for organizing initiatives within departments or the organization
• Projects are standalone objects with their own task lists
• Sub-projects can be created but are rarely used
• Ranking is for visual grouping only—no functional linking between projects

Tasks

• Exist within a specific project and are not shared across projects
• Ranking helps organize workflow steps or dependencies
• Subtasks are visually grouped but not functionally linked
• No roll-up or cross-task functionality—ranking is purely organizational