Project currency
Select the ISO currency used across every case, chart, CSV, and PDF in the project. Existing projects default to EUR.
A ValueTrace project is a collection of related business value cases plus their shared currency, catalogs, definitions, and calculators. Each case represents a defined initiative or process and connects solution enablers to changed behavior, measurable indicators, and financial value.
.valuetrace.json file. Opening replaces the project currently stored in the browser.A project groups related cases and shared setup. Implementation and recurring costs belong to each case. Leading indicators, value formulas, timing, overlap, evidence, and finance ownership belong to each benefit.
Open Configure structures from the gear icon. Setup opens with every section collapsed; choose Currency, Catalogs, or Benefit calculators for the task you need. Setup controls reusable project choices and does not change existing case numbers automatically.
Select the ISO currency used across every case, chart, CSV, and PDF in the project. Existing projects default to EUR.
Maintain value chain, process, and sub-process entries used by the Business process field.
Maintain P&L and balance-sheet paths used by the Financial line field.
Add a concise definition so users can distinguish similar processes or financial lines.
Add organization-specific calculators with custom labels and a controlled change treatment. The six built-in calculators remain available and cannot be edited or deleted.
Changing the project currency updates symbols and labels but does not apply an exchange rate or change numeric amounts. Convert values separately before changing currency when the project needs true FX conversion.
Open Catalogs, choose the catalog to manage, and review its current entries. To add entries, download the CSV template, complete its Level 1, Level 2, Level 3, and Definition columns, select whether to add or replace entries, then import the completed file.
Open Benefit calculators to review the methods available in Step 3. In Create a custom calculator, name the method, choose how indicator change is interpreted, label the annual-volume and unit-value inputs, explain the formula, then choose Create calculator.
Use the i beside How to interpret indicator change for examples. Automatic from unit recognizes percentages; Percentage ÷ 100 always normalizes a percentage-point change; Absolute change keeps the baseline-to-target difference; Days ÷ 365 annualizes a timing change.
Custom calculators support normalized change × annual volume × unit value × realization. They do not evaluate Excel-style operators, parentheses, cell references, or arbitrary formulas.
Prompt buttons create contextual text for Copilot or another AI assistant. ValueTrace does not call an AI service and does not send case data anywhere.
| Prompt | Use it for | What to verify |
|---|---|---|
| Process | Recommend a three-level process hierarchy. | Scope, terminology, and organizational ownership. |
| Indicator | Propose measurable leading indicators with units and source systems. | Availability, baseline quality, and causal relevance. |
| Financial | Suggest the likely P&L or balance-sheet treatment. | Direct versus capacity value and finance ownership. |
| Suggest value paths | Generate candidate capability-to-indicator hypotheses from the qualified case. | Causal relevance, measurability, ownership, and whether each indicator is distinct. |
Never treat generated wording or numbers as validated facts. Record measured sources and named owners in the model.
Step 2 creates a value path from solution enabler to changed capability and leading indicator. Step 3 turns that path into a modeled benefit by adding transparent measurement and financial ownership.
Add the value mechanism, eligible volume, unit value, realization, classification, financial line, and finance owner. Only then is the value path treated as a modeled benefit.
Create separate benefits when value has a different indicator, calculator, timing profile, evidence source, finance owner, or financial line. Do not split merely to make the same value appear more than once.
The process and financial catalogs provide consistent hierarchies across cases. Users can still enter a more specific value when needed.
When you choose Save project, the selected currency, configured processes, financial lines, definitions, and calculators are included with the cases.
Each calculator follows the same transparent structure while changing labels and indicator treatment for its value mechanism.
Indicator change × annual volume × unit value × realization × overlap adjustmentPercentage changes are divided by 100, day changes by 365, and direct-unit changes are used as entered. The annual run rate is the full modeled value before the case-level adoption schedule.
| Change treatment | Behavior | Example use |
|---|---|---|
| Automatic from unit | Divides by 100 when the measurement unit contains %; otherwise uses the direct change. | A reusable calculator that may receive percentage or absolute indicators. |
| Percentage ÷ 100 | Always converts the baseline-to-target difference to a decimal percentage. | Conversion, error, adoption, or retention rates. |
| Absolute change | Uses the direct numeric difference without normalization. | Transactions, incidents, hours, or other units. |
| Days ÷ 365 | Converts a day difference to a share of a year. | Working-capital cycle time. |
Custom calculators change the name, treatment, input labels, and explanation. They do not run custom code or replace the transparent calculation engine. Built-in calculators cannot be modified.
Custom calculator definitions travel with the project. Save project includes them in the .valuetrace.json file together with cases and catalogs. Open project validates, restores, and stores them in the receiving browser, so benefits continue to use the same calculator definitions.
You can delete a custom calculator from Setup; built-ins cannot be deleted. After confirmation, every benefit using the deleted calculator switches to Quality or automation. Save a project backup first when the definition may be needed later.
| Calculator family | Typical use |
|---|---|
| Labor capacity | Time released from employee work; confirm whether it is capacity or cashable cost. |
| Quality or automation | Defects, rework, exceptions, or avoidable transactions. |
| External spend | Vendor, contractor, service, or purchased-cost reductions. |
| Revenue or margin | Conversion, volume, retention, price, or margin improvement. |
| Working capital | Cash tied up in receivables, inventory, or payables. |
| Downtime | Production or service availability and avoided interruption. |
A project can contain up to 100 calculator definitions. Calculator names, labels, treatments, and explanations are validated when a project file is opened.
Set the evaluation horizon, discount rate, Year 0 implementation investment, and ongoing costs once for the case. Ongoing costs can grow by an annual percentage or be entered separately for each year.
For each benefit, set the first benefit year and ramp for the first, second, and later benefit years. Values are decimal shares: 0.4 means 40% realization in that year.
Use dependencies to show that one benefit relies on another. Use overlap adjustment to reduce value when benefits affect the same population or financial line. An adjustment of 0.75 retains 75% of the calculated value.
Draft means finance has not yet validated the selected benefit. Completing fields improves readiness but does not automatically change this status.
After review, choose Mark finance validated. Choose Reopen validation if assumptions or treatment need to change. A case is Validated only when every benefit is finance validated.
Tier 1 is measured organizational data. Tier 5 is a named assumption. Use the lowest defensible tier and retain the source and owner needed to reproduce the estimate.
The Review step combines benefit validation with case-level outputs: NPV, ROI, payback, total investment, cumulative net cash flow, benefit contribution, and annual cash flow.
From the project portfolio, choose Project summary to review Annual Potential Value, modeled NPV, portfolio ROI, total investment, and aggregate time to value across all cases.
Confirm the case status, evidence tiers, discount rate, overlap adjustments, and whether capacity benefits are described accurately.
ValueTrace saves working data in this browser. There is no account and no server synchronization.
Creates a named empty portfolio with no cases and restores the built-in EUR currency, catalogs, definitions, and calculators.
Downloads a portable .valuetrace.json file containing cases, the active case, currency, catalogs, definitions, and calculators.
Validates and replaces the current local portfolio with data from a compatible project file.
The initial six cross-functional demo cases belong to one example enterprise transformation project. Start a new project when you are ready to build your own portfolio.
Changes are retained in browser storage on the current device and browser profile.
Use Save project regularly and store the downloaded file in an approved organizational location.
Save the current portfolio first when you may need it later. Only open project files from a trusted source.
| Annual run rate | Full annual benefit at steady-state realization, after the benefit overlap adjustment. |
|---|---|
| NPV | Discounted value of modeled net cash flows across the evaluation horizon. |
| ROI | Total modeled benefits less total investment, divided by total investment. |
| Payback | Interpolated time when cumulative net cash flow reaches zero. |
| Realization | Share of theoretical indicator value expected to become economic value. |
| Ramp | Share of the annual run rate achieved in a specific benefit year. |
| Overlap adjustment | Reduction applied to avoid double counting related benefits. |