The challenge
The biggest sustainability decisions happen before the first production order.
Design teams compare materials, performance, cost, compliance, and impact across disconnected tools. CommonShare keeps each design choice tied to the product structure, supplier context, calculation inputs, evidence, and decision history it depends on.
Product workflow in practice
Move from design brief to an evidence-backed specification.
Compare alternatives in context, resolve evidence gaps, and preserve why the selected design moved forward.
- Product developmentFrame the design brief
- R&D and sourcingModel material alternatives
- CommonShare networkResolves records and coordinates the configured workflow
- Sustainability and complianceCompare impact and risk
- Cross-functional design teamApprove the design basis
01 InitiateOpen the exact case02 ResolveConnect identity and evidence03 CoordinateCheck, route, and prepare04 DecideKeep human authority05 ActIssue and reuse the outcome
Frame the design brief
Define intended use, target markets, performance criteria, material constraints, circularity goals, and evidence requirements.
- Input
- Mapping
- Decision or control
- Runs within the configured workflow boundary.
- Handoff
- Model material alternatives · R&D and sourcing
- Frame the design briefProduct development
The design decision remains connected to source records, evidence, approvals, and intended downstream use.
Connected evidence model
Keep the complete design basis connected.
Every object remains connected to the people, evidence, versions, and decisions that give it meaning.
- 01Product concept and intended use
- 02Bill of materials and variants
- 03Material and component specifications
- 04Supplier and facility context
- 05Carbon or PEF calculation versions
- 06Tests, declarations, exceptions, and approvals
Connected capabilities
Configure one platform around the work.
Bring the right capabilities into one accountable flow.
Multi-tier network mapping
Connect products, organizations, facilities, materials, and transactions across tiers.
Supplier collaboration
Request structured data and evidence through shared supplier workflows and portals.
Evidence governance
Extract, version, approve, and preserve documents with a reviewable audit trail.
Risk screening and alerts
Match records to risk and watchlist signals, then keep material changes visible.
Cases and decision workflows
Route exceptions, corrective actions, approvals, and escalations to accountable teams.
Impact calculations and ledgers
Connect carbon and PEF calculations to their methods, inputs, and versions.
Commons Architecture
The shared foundation beneath the workflow.
Architecture keeps identity, data exchange, claims, permissions, automation, and human accountability coherent across organizations.
Where it applies
See the workflow in industry context.
Construction Products & Building Materials
Connect material formulation, technical performance, declarations, and lifecycle evidence.
Requirements and methods
Connect evidence to the right pathway.
ESPR
Product-specific measures define the applicable ecodesign requirements and timing.
Product Environmental Footprint
Apply the voluntary methodology with its goal, scope, data, and review context visible.
CommonShare organizes alternatives, calculations, evidence, and approvals. Product teams retain design decisions, and legal or technical specialists retain their assessments.
Frequently asked
Ecodesign, made clear.
Practical answers about scope, workflow, evidence, and accountable decisions.
No. The workflow can be configured around the product, market, design gates, evidence owners, and applicable product-specific requirements.
Design holistically