Set capacity assumptions

Use this guide to set the capacity assumptions CodeTogether AI reports read when they describe delivered output against a team's schedule. You'll update the current values, choose when the change takes effect, and confirm how it reaches your reports.

• Deployment: SaaS, On-premises
• Role: Owner, Admin

Before you begin

To set capacity assumptions, you need:

• Owner or Admin on the organization: Editing tenant settings requires one of these roles. See Roles reference.

About capacity assumptions

At Settings > General > Cost Policies, set:

Setting	What it sets
Target hours per week	The active engineering hours per week a report compares delivered output against.
Healthy range	The lower and upper weekly hours that reports treat as a healthy level of activity.
Work week hours	The full scheduled work week, used as the base for capacity and utilization figures.
Effective from	The date this version starts applying to reports.
Effective until	The date this version stops applying. Set automatically when a later version starts, or reads Open for the current version.

Settings > General, reached from the left navigation, with the Cost Policies tab active.

The Work schedule section of the current cost policy card, showing target hours, healthy range, work week hours, and the effective window.

1. Update capacity assumptions

1. Go to Settings > General > Cost Policies.
2. Select Update policy. If no policy is configured yet, select Create policy instead.
3. Set Target hours per week, the healthy range, and Work week hours.
4. Choose when the change takes effect: Immediately, or On a specific date.
5. Select Create version.

The Update cost policy dialog, with the work schedule fields and the effective-date choice.

2. Understand what changes

Editing does not overwrite the current values. It creates a new, immutable version and keeps every earlier version in the Policy versions history, so past reports stay traceable to the assumptions that produced them.

A version you create to take effect immediately or on a future date leaves reports for earlier dates untouched — they keep reading the version that was effective at the time.

A version you backdate to a past date is different: reports for the days between that date and the present recalculate under the new assumptions after analytics data refreshes. The dialog warns you when your chosen date falls before the current version's start, since that is the case that rewrites recent history rather than only steering it forward.

The Policy versions history at Settings > General > Cost Policies, showing the current version's effective window.

Reports select whichever version was effective for each date they cover. A report spanning several versions blends them by date rather than retroactively restating earlier days under the newest values.

After you create a version, CodeTogether AI refreshes the analytics data reports read from. Reports keep showing the prior version's figures for their dates until that refresh finishes — including for a backdated version, so a reader never sees a partially-recalculated blend: the numbers are either the old version's or, once the refresh completes, the new one's.

Troubleshooting

The analytics refresh needs attention

The refresh that applies a new or edited version did not complete. Reports keep reading the last successfully refreshed version until it does. Contact support if it does not recover.

If this doesn't fix it

Contact support with all of the following. Tickets missing these take longer to resolve:

• The policy version you created or edited, and its effective date.
• Whether the analytics refresh for that version completed, is in progress, or needs attention.
• The report and date range where the numbers look wrong, and the value you expected.
• Your deployment kind and server version.

Related

• Is the investment paying off? — what these assumptions feed.
• Tune value points — aligning scoring to your priorities.
• Roles reference — who can edit tenant settings.