Understanding Developer Days and Developer Months in Cost Capitalization Reports

Last updated: October 27, 2026

Your downloadable Cost Capitalization report includes four effort columns. This article explains what each one means, how Span calculates developer-months, and how to reconcile the numbers.

Why it matters

Finance teams often work in developer-months, while Span measures effort in days. Knowing how Span converts one to the other lets you check the report and explain small differences to your auditors or controller.

How it works

Each report row is one person's effort on one container (an epic, initiative, issue, or project) in one month. The four effort columns are:

Column

What it means

fte_developer_days

Total effort for this person and container in the month, in FTE-days

capitalization_developer_days

The capitalized part of that effort, after the Capitalization % and the start and end dates are applied

fte_developer_months

fte_developer_days divided by the month's working days

capitalization_developer_months

capitalization_developer_days divided by the month's working days

Working days depend on your organization's setting How to calculate developer-months:

  • Business days in the month (the default): Monday to Friday in that calendar month. Every person shares the same divisor.

  • Calendar days in the month: every day in the month, weekends included.

  • Business days in the month, plus any days worked outside business days: the business days, plus each weekend or holiday on which that person had activity. The divisor is specific to each person and month.

Each developer-months value is capped at 1.0, since a person can't register more than one developer-month in a month, and is shown rounded to two decimal places.

Setup

An admin with the Manage Cost Capitalization permission picks the option in Settings → DevFinOps → Basic Settings → How to calculate developer-months. The setting changes only the developer-months columns. Developer-days, salary, and cost figures aren't affected.

Things to know

  • Rows below 0.005 show as 0. A row with 0.08 capitalized developer-days in a 22-day month works out to 0.0036 developer-months, which rounds to 0.00. Nothing is dropped: the developer-days columns hold the precise figure, and those rows still count fully toward cost.

  • Small rows are normal. Someone who touches several epics in a month has their time split into many small rows.

  • Summed developer-months can drift. Each row is rounded on its own. Twenty rows that each round up by 0.004 overstate the total by about 0.08, which can make a person-month look slightly above 1.00 when the precise value is at or below it.

  • The per-person divisor only applies to one option. With the "plus any days worked outside business days" setting, you can't reproduce the column by dividing every row by the same number.

To check one person's total for a month

  1. Sum capitalization_developer_days for that person and month.

  2. Divide once by that month's working days under your setting.

That gives the exact figure. The same approach works for epic-level and team-level totals. Reconcile from the developer-days columns and divide once at the level you care about.

Worked example

A month has 22 business days and 31 calendar days. An engineer has 11 capitalized developer-days in it and had activity on two Saturdays.

Setting

Divisor

capitalization_developer_months

Business days in the month (default)

22

11 / 22 = 0.50

Calendar days in the month

31

11 / 31 = 0.35

Business days plus days worked outside them

24

11 / 24 = 0.46

Related articles

Introduction to Cost Capitalization

FTE & FTE-d Calculation

Need help?

Contact your Span account team or reach out to support@span.app.