Overview
Each project in Dash360 has an extensive configuration form organized into tabs. These settings control everything about how the project behaves — which code files it uses, how cost classes are structured, how signatures work, and which features are enabled.
Open a project’s settings by clicking its row on the Projects page.
Properties Tab
Core identity and status fields for the project.
| Field | Description | Required |
|---|
| Name | The project name shown throughout Dash360 | Yes |
| Description | Optional longer description | No |
| Status | Active or Inactive | Yes |
| Default Project | Make this the project that loads by default for users | No |
| Fiscal Year Start Month | The month your fiscal year begins (e.g., October = FY start in Q1) | Yes |
General Tab
Contract and organizational information.
| Field | Description |
|---|
| Contract Number | The contract identifier for this project |
| Client Name | The client or customer for this project |
| Project Manager | Name of the PM responsible |
| Contract Type | The type of contract (e.g., Cost Plus, Fixed Price) |
| Start Date | Project start date |
| End Date | Project end date |
| Probability | Probability of award or execution (percentage) |
Cost Classes Tab
Define the cost classes available for this project. Cost classes represent different estimate scenarios — for example, Budget, Baseline, Earned Value, and Actual Cost.
Each cost class has:
| Field | Description |
|---|
| Name | The display name (e.g., “Budget”, “Baseline”) |
| Type | The class type (Budget, Earned, Actual) — controls which calculations apply |
| Order | Display sequence in cost class selectors |
| Locked | When enabled, users cannot edit resource assignments in this cost class |
Cost class locking is a registry-controlled feature. If locking is not enabled in the registry settings for this project, the Locked field has no effect.
Code Files Tab
Assign the supporting files that define the project’s data structure. These files must be created in the Codes admin page before they can be assigned here.
| File | Description |
|---|
| WBS Code File | The Work Breakdown Structure hierarchy for this project |
| Work Package Code File | The work package numbering codes |
| Resource File | The resource codes available for resource assignments |
| Basis Code File | The estimating basis codes (e.g., Analogy, Engineering, Parametric) |
| Activity Code File | Activity codes for schedule integration |
| Contingency Table | The contingency source file used for risk factor calculations |
| Registry Set | The registry configuration that controls feature flags and system settings |
Code files can be shared across multiple projects. If you select a code file that is already used by another project, changes to that file (adding, editing, or deleting codes) will affect all projects sharing it. Use the sharing indicators on the project list to monitor which files are shared.
Thresholds Tab
Define performance thresholds used for color-coding and alerting in earned value reports. Set upper and lower bounds for cost variance, schedule variance, CPI, and SPI. Values outside the threshold range are highlighted in reports.
Variance Fields Tab
Configure the fields that appear on the Variance Narrative Report for this project. Each variance narrative field maps to a specific cost class and appears as a column in the variance grid. This tab controls which fields are shown and their display order.
Signatures Tab
Configure the sequential signature workflow for cost estimate approvals on this project. Each signature step represents one approval level.
| Field | Description |
|---|
| Step Name | Label for this approval step (e.g., “CAM Approval”, “PM Review”) |
| User | The user responsible for this signature step |
| Order | The sequence — signatures must be completed in order |
Risk Register Setup Tab
Assign the risk categories and risk types available for this project’s Risk Register. Only categories and types assigned here will appear when users add risks in the Risk Register.
Risk categories and types are defined globally in the Risks admin page and then assigned to individual projects here.
Uncertainty Classes Tab
Define uncertainty classes for this project. Uncertainty classes are used in conjunction with risk factors to calculate contingency bands. Each class has a name and an associated contingency percentage range.
Calendar Tab
Create and manage project-specific fiscal calendars. By default, projects use the system calendar aligned to the fiscal year start month set in Properties. Custom calendars allow non-standard period structures.
Each calendar entry has:
| Field | Description |
|---|
| Name | Calendar name |
| Type | Calendar type (e.g., Fiscal Year) |
| Periods | The fiscal periods and their date ranges |
MTDC Tab
Configure Modified Total Direct Cost (MTDC) settings for this project. MTDC controls how indirect costs are applied to resource assignments. Set the MTDC rate structure and the applicable cost categories.
Premium Pay Tab
Configure premium pay rates that may apply to labor resource assignments on this project. Define the pay classification, months of service thresholds, and the applicable premium rate.
Resource Code Security Tab
Control which users can see and use specific resource codes on this project. By default, all users with access to the project can use all resource codes. Enable resource code security to restrict individual users to a subset of codes — useful when different CAMs own different resources and should only see their own.
Quick Status Settings Tab
Configure the Quick Status workflow rules for this project. Quick Status is the page where CAMs submit activity progress updates. Settings here control:
- Which activities appear in Quick Status
- Submission rules and constraints
- Approval requirements before data flows to earned value
