> For the complete documentation index, see [llms.txt](https://help.aphex.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aphex.co/docs/planner/features/production-measures.md). # Production Measures Production Measures let you define the measurable outputs work is planned against, each created with a name, unit (e.g. ‘Panels, each’), and an optional target rate per day. When a target rate is set, Aphex calculates the implied daily rate and compares it against that target, surfacing the variance as a red, amber, or green indicator in a dedicated Production Measure column on the Gantt.
## Creating Production Resources ***
Creating Production resource lets you build a reusable library of Production to assign to Tasks. #### To create Production: * Click your Project Title in the top left, then select `Project Assets` * Select `Production` from the menu * Click * Create your custom Production resource by entering the `Name`, `Unit` and a `Colour` * Optionally assign a `Unit Name` and toggle Set Daily Target Rate * The Production resource is added to the library of Production the team can assign to their Tasks
Production Measure Resource rules * The Unit is confirmed once a measure is created; name, colour and target rate can be edited. Percentage-based measures have no quantity, target or breakdown. * Choosing Count adds a custom Unit Name e.g. ‘Panels’.
## Assigning Production to tasks ***
#### **To assign the Production Measure to a Task:** * From Gantt view, click ![](https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2FvKmhsEo7KN1cBILxsani%2FColumn%20Picker%20Buttons.svg?alt=media\&token=9c6cc79d-7f88-4492-a6ea-7f2ba6418ffc)Column * Toggle ![](https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2Fi95XyOgpy7hzTLYWhvru%2FControl.svg?alt=media\&token=b4440363-6bc5-4836-8d65-19a701f9a308) on Production * Click on the Task's Production cell * Select the Production Measure from the dropdown * Set the total quantity, review the daily breakdown and alignment, then #### **To change the Task's Production Measure:** You can change or remove a task’s measure at any time by selecting a new Production Measure from the dropdown. Logged updates are never deleted. Each update stays as it was recorded, and the running total is recalculated against the task’s new measure.
Production on Tasks rules * Only one Production Measure can be assigned to a task at a time. * Tasks without a Production Measure show `None`. When the project is set to `Track % Complete`, the `None` option in the dropdown also shows `% Complete by Default`. This is a project default, not a measure, so it doesn’t appear in your Production library.
What happens to progress when the measure changes
ChangeRunning totalPast updates
% → % (including the % Complete by Default)Carries over (40% stays 40%)Unchanged
Units → %Converts (50 of 100 panels becomes 50%)Stay visible
% → UnitsResets to 0Stay visible, but don’t count towards the unit total
One unit → another unitResets to 0Stay visible, but don’t count towards the new total
Measure removed on a Track End Date projectNo % is trackedStay visible
Tasks without a measure track % complete by default. See Progress. If a day shows 50% logged but the task shows 0% overall, the task was most likely switched to a unit-based measure after that update. Log units against the new measure and the total will start moving.
## Editing Planned Production ***
Make changes to the production breakdown where needed and impact the cumulative total needed. * Right-click a Task and select `View Details` * Scroll to `Planned Resources` and click into * Update the value and see the cumulative total impact
Production Impact rules * Unit-based measures (m³, linear metres, items, etc.) take a total quantity, support an optional daily target rate, and show a day-by-day breakdown with on![](https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2F7AUy7m7GtKNnQBcAdALr%2FProduction%20Rates%20Variance.svg?alt=media\&token=a8e733ac-90d0-4ef6-8d0c-9dcd7b5e21b5)/ over![](https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2FBNjqiJb8gwMhdS8DgyNH%2FAtomic%20Tag%20Anatomy.svg?alt=media\&token=347c5eb2-a7c1-4f9b-bc62-5a53dc9a86d2)/ under targetstatus.
## Align your Task Duration with the Target Rate ***
When a task's average production rate is below or in excess of its target, you can extend or shorten the task duration in one click so it lines up with the target rate no manual recalculating needed. * Hover the Target Rate Variance icon on the `Production` Gantt cell, in the Task side panel, or on a Board/List task card * Where the average is off target, an `Align Task Duration` button appears * Click it to extend or shorten the task duration until the daily average production matches the target rate * The quantity breakdown updates automatically to reflect the new duration ## Understanding Planned Production ***
Once a Production Measure with a target rate is assigned to a task, Aphex continuously compares the task's planned daily rate against that target so misalignment is visible before it becomes a problem. #### Understanding Task movement on Planned Production Resizing or dragging a task with a Production Measure assigned updates its plan in real time. * As you stretch or shrink the Task Bar, a Task Resize Indicator tooltip shows a live preview of the new average daily production rate * If the measure has a target rate set, the tooltip also shows whether that new average is aligned, above, or below target * Release the bar to confirm the new duration the daily breakdown recalculates automatically #### Target Rate Variance Summary * On the Gantt, navigate to and toggle on `Production` * Check the visuals of ![](https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2FBNjqiJb8gwMhdS8DgyNH%2FAtomic%20Tag%20Anatomy.svg?alt=media\&token=347c5eb2-a7c1-4f9b-bc62-5a53dc9a86d2), ![](https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2F0eNE4bDxgOF6Ba8YVfDS%2FProduction%20Rates%20Variance%20\(1\).svg?alt=media\&token=e977ce80-48a7-427f-899a-b8c79e001d54)and ![](https://2273109354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLu0mYklsCTm7XQm3ZGqv%2Fuploads%2F7AUy7m7GtKNnQBcAdALr%2FProduction%20Rates%20Variance.svg?alt=media\&token=a8e733ac-90d0-4ef6-8d0c-9dcd7b5e21b5)to check the Target Rate Variance
Target Rate Variance meaning
IconMeaning
Over the current target rate and could mean reforecasting is needed
On the current Target and is in accordance with the daily forecast rate
Under the current target and could mean the duration of the task can be shortened
## Filter by Production ***
#### To filter by Production: * Click and * Select `Production` in the first dropdown * Select from `Is`, `Is Not`, `Is Empty` or `Is Not Empty` in the second dropdown * Select your desired Production measure in the third dropdown See also: create & share Views
Filter Breakdown | Filter | Operator | Value | | ---------- | -------------------------------------------------- | ------------------------------ | | Production |

Is
Is Not
Is Empty
Is Not Empty

|

Multi-Select


|
--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.aphex.co/docs/planner/features/production-measures.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.