> For the complete documentation index, see [llms.txt](https://help.swarmia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.swarmia.com/definitions/developer-effort-ftes/daily-effort-model.md).
# Daily effort model (beta)
{% hint style="info" %}
This is a beta feature that we're rolling out gradually. It changes how developer effort is calculated, so the numbers it produces can differ from the [current effort model](/definitions/developer-effort-ftes.md). It isn't available to everyone yet. Reach out to us if you'd like early access.
{% endhint %}
Swarmia is rolling out a new way of calculating [developer effort](/definitions/developer-effort-ftes.md) by moving the calculation from a monthly to a daily basis. On the current monthly model, a single busy stretch of just a few days can define a large share of the whole month. The new daily model calculates effort one working day at a time. Every working day counts equally, no matter how much activity happened on it, so a single busy day can't dominate the month.
{% columns %}
{% column %}
Monthly model
{% endcolumn %}
{% column %}
Daily model
{% endcolumn %}
{% endcolumns %}
The new model is also more flexible. The current model only calculates across a whole month, so a calendar month is the smallest period it can report on. The new daily model produces a value for each working day, so you can look at effort by day or by week, not just by month.
We keep refining the effort model based on the data we gather and real usage, making the model more accurate and easier to understand. The new daily model is part of that work.
## How it compares to the current model
| | Current effort model | Daily effort model (beta) |
| ------------------------------------------------------- | --------------------------------------------------------------- | --------------------------------------------------- |
| How effort is calculated | From a whole month's activity in one calculation | Each working day separately, then added together |
| Inactivity | Only stretches longer than 5 business days are deducted | Every working day without activity lowers effort |
| Minimum activity | Contributors with fewer than 10 activities a month are excluded | No minimum, even a single event counts |
| Contributors with only issue-tracker activity (no code) | Excluded, below the minimum | Receive effort from their assigned in-progress days |
| Activity on pull requests not linked to an issue | Counted at half weight | Counted at full weight |
| Assigned in-progress issues | Counted | Counted, with more weight |
| Time-off adjustments and current-month proration | Applied | Applied, unchanged |
Two of these changes pull in opposite directions. Dropping the half-weight penalty on unlinked pull requests raises that code work, while giving assigned in-progress issue days more weight raises issue-tracker work. The two roughly cancel out, so the balance between code and issue-tracker work stays close to the current model.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.swarmia.com/definitions/developer-effort-ftes/daily-effort-model.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.