Developing lighter, more durable gear can require experiments across materials, mechanical designs and electronics. Cedar works with your product team to identify that development work and carry the claim through reporting, financial preparation and filing coordination.
A product investigation may move between material samples, workshop prototypes, laboratory tests and field trials. We connect those stages so the claim explains the engineering problem and the purpose of each design change.
Field records are most useful when they identify the prototype, conditions and behaviour being tested. We combine them with the controlled comparisons and design records that explain the results, drawing on our engineering, software and outdoor-industry experience.
Illustrative examples
Development problems worth a closer look
These hypothetical examples show how a technical problem can lead to experimental work. We assess your project using its actual starting knowledge, investigation and records.
A lightweight assembly under repeated loading
Development challenge
An equipment assembly needs to remain light while withstanding repeated loads in wet and cold conditions. Known construction methods do not establish how its joints and materials will behave under those combined demands.
Experimental work
Prototype comparisons vary joint geometry, material layup and construction details. Repeated-load tests and field observations identify failure locations and test explanations for the loss of strength or stiffness.
Reliable sensing away from a network
Development challenge
A connected recreation product needs reliable measurements with limited battery capacity, changing environmental conditions and intermittent connectivity. The interaction between sensing accuracy, power management and interrupted data transfer remains unresolved using available approaches.
Experimental work
Bench and field experiments compare sensing, power-management and data-handling strategies. Measurements of error, energy use and recovery after interruptions guide the next hardware and software revisions.
Claim strategy
Define the work and the costs.
We identify the technical investigation within the wider product programme. Styling, market research, routine user testing and commercial production are separated from the experimental design, analysis and testing that support the claim.
Cedar reconciles the project costs with your financial records and documents the allocations used in the claim.
Keep the prototype version with each result. A failure photograph becomes much more useful when it connects to the construction drawing, loading conditions and design change that followed.
Drawings, material specifications and construction versions that identify the designs compared.
Bench and field trials
Test plans, loading or environmental conditions and records of the behaviour observed.
Failures and design changes
Measurements, photographs and development notes that explain revisions between prototypes.
Development costs
Team activity, prototype materials, contractor invoices and external testing costs for reconciliation.
Working with Cedar
A senior preparer leads your whole claim.
We handle the claim strategy, technical reports, financial reconciliation, tax schedules and filing coordination. Our fees are tied to the outcome of your claim, and full CRA audit and provincial review support is included.
1
Set the claim strategy
We speak with the people who did the work, review the development records and identify the projects and costs to assess.
2
Write and reconcile
We write the technical reports, reconcile expenditures to your accounts and prepare the federal and applicable provincial tax schedules. Your team provides the records and reviews the completed claim for approval.
3
Coordinate filing and handle reviews
We coordinate the claim filing with your accountant, who files the corporate T2 return. If the claim is reviewed, we prepare technical and financial responses, attend meetings and coordinate with your team and accountant.
A practical way to connect design notes, test results, project time, and costs using the records your team already creates.
3 min read
Discuss a project
Tell us what you’re developing.
Bring a product lead and a development problem that led to repeated prototypes or experiments. We can start with the gear and its test history, then organize the claim around the work.
