Commercial disputes for contract non-performance (supply/services): evidence strategy

In B2B disputes, outcomes often depend less on narratives and more on provable facts: the contract chain, notices, acceptance, change requests, and the timeline. We help you build an evidence-first strategy for non-performance, delays, defects, or refusal to pay under supply or services contracts.

Next step for you: send the contract set and a one-page timeline (dates, milestones, notices). We will identify the strongest claim path and the evidence gaps to address early.

Informațiile sunt generale și nu înlocuiesc consultanța juridică. Contează faptele, actele și cronologia.

When you need this

• The other party failed to deliver, delivered late, or delivered non-conforming goods/services.
• You delivered, but the customer refuses to pay (with or without reasons).
• There are disputes over scope changes, specs, milestones, or acceptance.
• You need damages or penalties, but evidence is scattered across teams and systems.
• The contract has multiple addenda and email changes that must be unified into one position.
• The dispute involves technical issues that may require expert evidence.
• You need a structured settlement position without weakening litigation options.
• You must decide whether to seek performance, termination/resolution, price reduction, or damages.

What we do, step by step

• Claim framing: select the legal theory (price, performance, damages, termination/resolution, penalties).
• Chronology building: create a date-based story aligned with contract milestones and notices.
• Evidence plan: map each element to proof (documents, witnesses, technical evidence, expert needs).
• Pre-trial steps: structure notices, cure requests, and defect documentation.
• Settlement track: negotiate with enforceable terms and clear triggers for escalation.
• Filing and procedure: prepare pleadings, annexes, and deadline management under Romanian procedure.
• Hearing strategy: prepare witness topics and expert questions to match the claim map.

Documents & information useful for the first review

Document	Why it matters	Notes
Contract + annexes + change orders	Defines scope, acceptance, remedies, penalties, forum	Include all signed versions
Orders/specifications/SOW	Clarifies what performance means and what changed	Send version history and approvals
Delivery/acceptance records	Shows completion, acceptance, or rejection	Protocols, acceptance emails, tickets
Invoices + payment trail	Fixes amounts and due dates	Include credit notes and allocations
Notices and responses	Shows delay, objections, and opportunities to cure	Include proof of delivery
Loss and impact evidence	Supports damages calculations	Internal logs, additional costs, downtime metrics

Risks & common mistakes

• Filing without a coherent chronology and evidence map.
• Relying on informal understandings when the contract defines strict acceptance/change control.
• Missing notice steps that are contract-relevant to remedies or penalties.
• Overstating damages without a documented calculation method and mitigation trail.
• Leaving technical issues undocumented or unmeasured until late in the case.
• Settling without enforceable terms or clear consequences for non-compliance.
• Ignoring court fees and procedural costs when choosing strategy.

FAQ

What matters most in proving non-performance in B2B contracts?

The contract chain and the timeline: what was promised, what was delivered, what was accepted or rejected, and how objections were raised. We build the case around documents and verifiable milestones.

Do we need expert evidence in technical supply/services disputes?

In many technical disputes, yes. We assess early whether expert evidence is needed and how to prepare the technical file so it is usable in court.

Can penalties and damages be claimed together?

It depends on the contract and the applicable legal rules. We assess how penalty clauses interact with damages and what evidence supports each component.