Active Contributors Report

Overview

The Active Contributors report counts the number of unique developers actively contributing code to your codebase. This foundational metric helps you understand team size, track developer engagement, and provides essential context for analyzing productivity metrics across your organization.

What This Metric Measures

Active Contributors tracks:

• Developer engagement: How many unique developers are actively writing code

• Team capacity: The size of your contributing developer team

• Activity trends: Whether your active developer base is growing, shrinking, or stable

• Resource allocation: How developers are distributed across teams and projects

This metric provides a baseline for understanding your engineering organization's scale and serves as a key input for normalizing other productivity metrics.

What is an "Active Contributor"?

An active contributor is a developer who meets ALL of the following criteria:

1. ✓ Currently employed at the organization

2. ✓ Made code commits within the last 30 days

3. ✓ Not marked as out of office (for certain metric variants)

4. ✓ Designated as a "Contributor" in Span settings (not excluded or marked as non-contributor)

Recommended Practice: Exclude non-coding roles from your contributor list in Span settings to ensure accurate counts.

What Counts as Activity?

Activity is determined by:

• Version control commits (Git/GitLab)

• 30-day rolling window - Any commits in the previous 30 days

• No minimum threshold - A single commit qualifies someone as active

What Does NOT Count?

• Pull request reviews only (without commits)

• Comments or issue activity

• Code that hasn't been committed

• Commits older than 30 days

How It's Calculated

Span uses a 30-day rolling window approach to count active contributors:

Admin Dashboard (For Admins Only)

• Navigation: Settings → People Management > Click "View Active Contributors"

• Month-by-month view (defaults to previous month)

• Shows summary statistics across all organizations

• Includes CSV download for billing/invoicing purposes

• Per-organization breakdown table

Available Breakdowns & Filters

Analyze Active Contributors across multiple dimensions:

Team & People Dimensions

• Individual contributors

• Teams and organizational groups

• Job level or IC level

• Job title or role

• Department or job family

• Location/geography

• Tenure (time at company)

• Custom organizational tags

• Active/inactive employment status

Project Dimensions

• Repositories

• Repository groups

• Project assignments

Time Periods

• Daily: Day-by-day contributor counts

• Weekly: Weekly contributor trends

• Monthly: Month-by-month analysis (most common for capacity tracking)

• Quarterly: Longer-term trend analysis

• Yearly: Annual growth patterns

• Custom ranges: Any date range you specify

The underlying metric always uses a 30-day rolling window for activity detection, but you can analyze how this count changes over any time period.

Key Use Cases

1. Team Capacity Planning

Understand current team size and track growth to inform hiring and resource allocation decisions.

Example: "We have 35 active contributors today. To meet Q3 goals, we need to grow to 45 active contributors, requiring 10 new hires."

2. Resource Allocation Analysis

Compare active developer counts across teams to identify imbalances or optimization opportunities.

Example: "Team A has 12 active contributors while Team B has only 4, but both have similar roadmap commitments."

3. Engagement & Activity Monitoring

Track whether developers remain actively engaged or are becoming inactive over time.

Example: "5 developers who were active last month are now inactive—let's investigate why."

4. Context for Productivity Metrics

Normalize productivity metrics by team size for fair comparisons.

Example: "Team A completed 120 story points with 10 active contributors (12 points per person) while Team B completed 80 points with 4 contributors (20 points per person)."

5. Seasonal Pattern Identification

Understand how holidays, vacation periods, or other seasonal factors affect active contributor counts.

Example: "Active contributors typically drop by 20% in July and December due to summer and holiday vacations."

6. Billing & Invoicing

Track active contributor counts for usage-based billing or budget allocation.

Example: "Our average active contributor count was 42 in Q1, supporting our licensing and tooling budget estimates."

7. AI Tool Adoption Tracking

Measure what percentage of active contributors are using AI coding assistants.

Example: "65% of our 50 active contributors are actively using GitHub Copilot."

How It Relates to Other Metrics

Active Contributors serves as a foundational metric that provides context for many other productivity measurements:

Key Insight: Active Contributors answers "How many people are working?" while other metrics answer "How much are they producing?" Together, they provide a complete picture of team productivity.

Insights You Can Gain

Team Growth Trends

• Is your development team growing or shrinking?

• What's the growth rate? (Month-over-month % change)

• Are you hitting hiring targets?

Developer Engagement Patterns

• What percentage of employed developers are actually active?

• Are developers cycling between active and inactive?

• Do certain teams have lower engagement rates?

Seasonal Variations

• When do contributor counts typically dip? (Holidays, summer)

• How do vacations affect team capacity?

• Should we adjust commitments during low-activity periods?

Team Comparisons

• Which teams have the most active contributors?

• Are teams balanced in size relative to their responsibilities?

• Do smaller teams need additional resources?

Productivity Context

• High commits but few contributors? → High individual productivity or team burnout risk

• Many contributors but low output? → Potential efficiency or coordination issues

• Growing contributor count but flat output? → Onboarding overhead or process bottlenecks

Attrition & Retention Signals

• Are developers who were active becoming inactive? → Potential retention issue

• Is activity concentration increasing? → Fewer people doing more work (burnout risk)

Common Scenarios & Interpretations

Scenario 1: Declining Active Contributors

What you see: Contributor count dropping over time

Possible causes:

• Attrition (people leaving)

• Departures outpacing new hires

• Developers transitioning to non-coding roles

• Seasonal vacation periods

• Inactive periods between projects

Actions:

• Review employment changes and departures

• Check if developers transitioned to management

• Investigate engagement with inactive developers

• Assess impact on team capacity and delivery

Scenario 2: Growing Active Contributors

What you see: Contributor count increasing over time

Possible causes:

• Successful hiring and onboarding

• New team formations

• Increased contribution from existing team members

• Returning from extended leave

Actions:

• Celebrate successful growth

• Monitor onboarding effectiveness

• Ensure infrastructure scales with team size

• Adjust processes for larger team

Scenario 3: Stable Count with Productivity Changes

What you see: Active contributor count steady but productivity metrics changing

Interpretation:

• Team efficiency improving or declining

• Process changes affecting output

• Work complexity changing

• Technical debt impacting velocity

Actions:

• Focus on process and efficiency improvements

• Investigate quality metrics

• Review cycle time and blockers

• Check for technical debt accumulation

Scenario 4: Large Inactive Developer Pool

What you see: Many employed developers not appearing as active contributors

Possible causes:

• Roles misconfigured (should be marked non-contributor)

• Managers or support staff included in reports

• Developers working on non-coding tasks (architecture, planning)

• Extended onboarding periods

• Project transitions or planning phases

Actions:

• Review and update contributor designations in settings

• Exclude non-coding roles (managers, PMs)

• Investigate extended inactive periods

• Consider whether definitions need adjustment

Best Practices

1. Properly Configure Contributor Settings

• Exclude managers, PMs, and other non-coding roles

• Mark support staff as "Non-contributor"

• Regularly review and update contributor designations

• Ensure new hires are properly classified

2. Combine with Employment Data

Calculate the "active contributor ratio":

Active Contributor Ratio = Active Contributors ÷ Total Engineering Headcount

This shows what percentage of your engineering team is actively coding.

3. Track Trends, Not Point Values

• Single-month snapshots can be misleading

• Focus on 3-6 month trends

• Account for seasonal patterns

• Look for sustained changes

4. Use as Context, Not Performance Target

Active contributor count is a descriptive metric, not a performance metric:

• ✓ Use to understand team size and capacity

• ✓ Use to normalize productivity metrics

• ✗ Don't pressure developers to "stay active" during legitimate breaks

• ✗ Don't penalize strategic non-coding work (architecture, mentoring)

5. Investigate Transitions

When developers move from active to inactive:

• Is it planned? (transition to management, extended leave)

• Is it concerning? (disengagement, departure)

• Is support needed? (unblocking, reengagement)

6. Pair with Quality Metrics

High contributor counts don't guarantee high quality:

• Monitor code review thoroughness

• Track incident rates

• Assess technical debt

• Measure customer impact

7. Account for Team Maturity

• New teams may have lower activity during setup phases

• Onboarding periods temporarily reduce team velocity

• Mature teams may have more consistent contributor patterns

Setting Up Your Active Contributors Report

Requirements

To use this metric, ensure you have:

• ✓ Version control system integrated (GitHub, GitLab, Azure DevOps)

• ✓ Employee records configured in Span

• ✓ Contributor vs. non-contributor designations set

• ✓ Calendar integration (for OOO tracking in normalized metrics)

• ✓ Team/group structure defined

Configuration Steps

1. Review Contributor Designations

   • Navigate to Settings → Contributors

   • Mark managers and non-coding roles as "Non-contributor"

   • Verify all IC engineers are marked as "Contributor"

2. Set Up Team Structure

   • Define teams and organizational groups

   • Assign developers to appropriate teams

   • Validate reporting hierarchies

3. Establish Baseline

   • Review current active contributor count

   • Track for 2-3 months to understand normal patterns

   • Note seasonal variations

4. Create Monitoring Practices

   • Schedule monthly review of active contributor trends

   • Set up alerts for significant changes (if available)

   • Include in regular leadership reporting

Frequently Asked Questions

Q: Why is my active contributor count different from my total engineering headcount?
A: Active Contributors only counts people who have committed code in the last 30 days and are marked as contributors. This excludes managers, non-coding roles, people on extended leave, and developers between projects. This is intentional and expected.

Q: Should inactive developers be a concern?
A: It depends. Some legitimate reasons for inactivity include:

• Transitions to management or architecture roles

• Extended planning or design phases

• Onboarding or learning periods

• Parental or medical leave

• Project transitions

Investigate persistent inactivity to ensure it's intentional, not a sign of disengagement or blockers.

Q: How does the 30-day window work exactly?
A: On any given day, Span looks back 30 days and counts anyone who made at least one commit during that window. This creates a rolling window that smooths out short-term variations while capturing recent activity.

Q: Can someone be partially active?
A: No—the metric is binary. A developer either has commits in the last 30 days (active) or doesn't (inactive). There's no "partially active" status.

Q: What if a developer only commits once per month?
A: They'll appear as active. As long as they commit at least once within any 30-day period, they're counted. The metric doesn't assess activity intensity—only presence of activity.

Q: How do I exclude contractors or specific groups?
A: Use the contributor settings in Span to mark specific individuals or roles as "Non-contributor." You can also use filters in the report to exclude specific teams, locations, or custom tags.

Q: Why did my active contributor count suddenly drop?
A: Common causes:

• End of project cycle (developers between projects)

• Extended holiday period

• Team departures or transitions

• Onboarding period for new hires

• Settings changes (people marked as non-contributors)

Review employment changes and activity patterns to understand the cause.

Q: Should I use this metric for performance reviews?
A: No. Being an "active contributor" is a basic threshold (committed code in the last 30 days), not a performance indicator. It doesn't measure quality, impact, complexity, or value delivered. Use it for capacity planning and team structure analysis, not individual performance assessment.

Q: How does this relate to billing?
A: Many engineering tool licenses and platforms (including Span) use active contributor counts for usage-based pricing. The metric helps track your billing footprint and validate invoices.

Need Help?

For additional support with the Active Contributors report:

• Visit the Span Help Center

• Contact your Customer Success Manager

• Email support@span.app

This documentation reflects Span's platform capabilities as of the current version. Features and calculations are subject to updates.