> ## Documentation Index
> Fetch the complete documentation index at: https://calcs.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Request a Feature

> How to request a new feature, and what to include so the product team can scope it.

Blueprint was where a lot of good feature ideas started. Those requests now go through a route the product team reviews on a schedule, rather than depending on who was reading the forum that week.

## Request a feature

Submit it at [calcs.com/request](https://calcs.com/request).

Include as much detail as you can:

* **What you need to do.** The task or workflow, and the problem the feature would solve.
* **Where it fits.** The part of Calcs.com you would use it in, such as projects, load linking, or reports.
* **How you do it today.** A workaround, a spreadsheet, a manual step, another piece of software.
* **How often it comes up.** Something you hit on every project is treated differently from a one-off.
* **Anything you can share.** A marked-up screenshot or a short example of what you expected tells us more than a paragraph.

The detail matters because it is what lets our team scope the feature properly the first time.

## Found something broken instead?

If a feature exists but is not behaving as you expect, that is a bug rather than a request. See [Reporting a Bug](/docs/get-started/support/report-bug).

## What about my old Blueprint requests?

Previously logged requests have been provided to our engineering team for review. If you had a request open on Blueprint and want to know where it got to, email [support@calcs.com](mailto:support@calcs.com).

To keep a copy of what you posted, see [Exporting your Blueprint posts](/docs/release-notes/blueprint/export-posts) and do it before December 1, 2026.

## Related

* [Requesting a Calculator](/docs/get-started/support/request-calculator)