How Overseas Headquarters Can Preserve Evidence and Coordinate Sri Lanka Teams in Cross-Border Contract Disputes

When signs of a cross-border contract dispute emerge, the immediate priority for overseas headquarters is not to assign blame or cut off communication. It is to prevent key records from being deleted, altered, scattered across different people, or described inconsistently.

Headquarters should quickly establish a traceable process for evidence preservation and communication coordination. The Sri Lanka team should focus on collecting facts and on-site materials, rather than making legal assessments, admitting liability, or committing the company to a solution.

In this article, “signs of a dispute” may include delayed delivery, quality concerns, payment disagreements, unconfirmed scope changes, a supplier refusing to perform, a customer making a claim, a service provider not progressing as agreed, or either party issuing a formal complaint or reservation-of-rights notice. Even if no formal dispute process has started, these situations should trigger evidence preservation.

1. First determine whether this is an operational issue or a potential contract dispute

Overseas headquarters does not need to decide immediately who is right or wrong. It does need to decide whether to activate a dispute-record preservation process. A practical test is whether a fact could later affect payment, delivery, allocation of responsibility, termination of the relationship, or calculation of losses.

A project lead can use the following questions for an initial review:

• Has the other party clearly indicated that it cannot perform as originally agreed?
• Are the scope of work, pricing, delivery standards, or timing still unconfirmed?
• Has a payment been suspended, has a refund been requested, or has the basis for payment been challenged?
• Are there records of site defects, damaged goods, incomplete services, or failed acceptance?
• Is anyone preparing to delete chat records, overwrite file versions, recall emails, or replace a project contact?
• Are employees, consultants, or suppliers communicating important facts only verbally?

If any of these issues could affect a later claim or defence, headquarters should instruct the project team to stop non-essential deletion and overwriting activities. Record collection should move from ordinary project management to a reviewable factual record. This does not mean legal action must follow; it helps avoid discovering that the record is incomplete only when the company needs to explain what happened.

2. Define the preservation scope early instead of collecting only favourable evidence

The purpose of evidence preservation is to retain a complete chain of facts, not merely to select helpful screenshots. Keeping only selected materials, asking staff to privately align their accounts, or changing project records after the event can make internal assessment more difficult and may undermine the credibility of the materials.

Headquarters may appoint one cross-functional coordinator to maintain a dispute materials register, classified by source. The register should record who provided each item, when it was obtained, where the original is stored, whether copies exist, and whether the record is still being updated.

Material category	Priority materials to preserve	Main action for the local team
Contract documents	Signed contracts, schedules, quotations, orders, supplemental agreements, change confirmations	Check that versions, signature pages, and attachments are complete
Communications	Emails, meeting minutes, instant-message records, formal letters	Export the full context and identify participants and dates
Delivery records	Acceptance documents, work outputs, shipment or receipt records, site reports	Collect original records and site photos or videos
Financial records	Invoices, payment requests, payment evidence, reconciliation materials, refund requests	Confirm the source and related matter with finance
Project records	Task allocations, schedules, meeting minutes, issue lists, risk reports	Preserve version history and explanations from responsible personnel
Site materials	Premises condition, equipment status, goods labels, construction or service-site conditions	Organise original materials by time, location, and photographer

For electronic records, retain original files, original email chains, and complete export records where possible, rather than screenshots alone. Screenshots can help provide a quick understanding, but often do not show the full sending time, attachments, participants, context, or version information.

3. Divide responsibilities: the local team collects facts, while headquarters controls messaging and escalation

A common issue in cross-border projects is not a lack of activity, but that too many people are replying to the other party. This can lead to inconsistent descriptions of the facts. Where local employees, supplier managers, and overseas headquarters are all communicating with the counterparty, an unapproved statement such as “we will take responsibility,” “we accept this arrangement,” or “we can issue a refund” may affect the company’s negotiating position.

The following allocation of responsibilities should be clarified once a dispute arises.

Responsibilities of overseas headquarters

• Appoint one business decision-maker and one approver for external communications.
• Confirm whether the immediate objective is continued performance, remediation, negotiation, payment suspension, or fact verification.
• Review drafts that concern admissions of responsibility, payment commitments, termination, settlement, or claims.
• Coordinate internal documents from legal, finance, procurement, and project-management functions.
• Decide when to instruct appropriately qualified local legal or other professional advisers.

Responsibilities of the Sri Lanka local team

• Collect site conditions, original records, personnel accounts, and copies of documents.
• Coordinate factual confirmation with suppliers, customers, landlords, service providers, or site personnel.
• Record the date, participants, discussion points, and follow-up actions for each meeting, call, and site inspection.
• Promptly alert headquarters to local risks involving goods, equipment, documents, access rights, or personnel changes.
• Send approved communications only after receiving headquarters’ authority, and retain proof of sending.

Matters the local team should not handle independently

• It should not admit breach, agree to a loss amount, or accept the other party’s attribution of responsibility on behalf of the company.
• It should not verbally agree to refunds, discounts, extensions, termination, or substitute performance arrangements.
• It should not delete, amend, or ask others to amend potentially relevant project materials.
• It should not make private arrangements in its own name to “sort it out first.”
• It should not present unverified on-site observations as settled conclusions.

These boundaries are directly connected to authority management before contracts are signed. Companies may also review the related article, “How to Confirm Local Signing Authority and Approval Boundaries Before a Sri Lanka Company Signs a Contract,” to check who can sign, who may issue formal notices, and who is limited to coordination and record-keeping in the current project.

4. Maintain a fact timeline so headquarters can understand events remotely

When a dispute continues for several weeks, the main source of confusion is often not the contract text but the sequence of events. Headquarters should ask the local team to maintain an ongoing fact timeline, rather than relying on different people to reconstruct events from memory in separate meetings.

The timeline should not be written as an advocacy document. It should use the format: date — fact — source — item to be confirmed. For example:

• On a certain date: the other party raised a delivery issue by email; source: original email.
• On a certain date: the local team inspected the site and took photographs; source: original photos and site record.
• On a certain date: the parties held a meeting and the other party requested remedial action; source: meeting minutes and confirmation from attendees.
• On a certain date: the company internally decided to pause a subsequent arrangement; source: internal approval record.

Information that has not been verified should be clearly marked as “to be confirmed” rather than recorded as an established fact. For example, “site personnel stated that the equipment stopped operating on a certain date” is different from “the equipment stopped operating on that date.” The first records the source of information; the second requires further supporting evidence.

5. Follow three communication principles: facts, authority, and records

External communications during a dispute should be concise, professional, and based on verified facts. If the company cannot yet respond to questions about liability, amounts, or deadlines, it can state that the relevant materials are under review and that it will respond after internal confirmation. Do not make rushed commitments simply to ease the relationship.

Before each external communication, check:

1. Does the email or message accurately describe verified facts?
2. Does it include language that could be understood as admitting responsibility, accepting losses, or waiving rights?
3. Does the sender have the appropriate authority?
4. Have the final sent version, attachments, and recipient details been preserved?
5. If there is a call or site meeting, will written minutes be prepared afterwards?

If the other party insists on discussing key matters by phone, voice message, or instant messaging, the local team may send a brief written follow-up after the discussion. It can record the company’s understanding of what was discussed and identify any matters still to be confirmed. The purpose is not to resolve the disagreement immediately, but to reduce the risk that verbal communications are later interpreted differently.

6. Do not overlook site and system-access risks

Cross-border disputes do not exist only in contracts and emails. Businesses with offices, warehouses, equipment, project sites, or local system accounts in Sri Lanka should also consider which records and assets could become unavailable because of personnel changes or a breakdown in cooperation.

The local team can assist in checking whether:

• Site documents, paper delivery acknowledgements, access-control records, and equipment-use records have been retained properly;
• Access to project email accounts, shared drives, cloud folders, procurement systems, and finance systems remains under company control;
• Departing employees, contractors, or external consultants hold the only account, device, or copy of a key document;
• Surveillance footage, access logs, system logs, or project-platform records may soon be overwritten; and
• Site photos and videos can be linked to a specific location, date, photographer, and matter.

Where personal information, employee records, customer information, system data, or cross-border transfers are involved, the company should first confirm applicable data-handling requirements and seek advice from appropriately qualified professional advisers where needed. Evidence preservation does not mean that all data can be copied, forwarded, or disclosed without limits.

7. Make record updates a regular process, not a one-off exercise

New materials will continue to emerge during a dispute: new emails, site inspections, payment records, delivery versions, and meeting minutes. Headquarters should establish a regular update cycle under which the local team submits new materials, unresolved issues, and risk alerts for the next steps.

Each update can focus on four areas:

• New facts: what occurred during the reporting period;
• New materials: which documents, photos, and records have been archived;
• Items to be confirmed: which statements still require verification; and
• Decisions required: which issues need clear authority or an option selection from headquarters.

This process is also useful for projects that have not yet developed into a formal dispute but are already experiencing performance friction. The earlier the company brings order to its materials, authority structure, and communication rhythm, the less likely it is that separate teams will retain separate files, repeatedly explain the same facts, or miss critical points in the process.

8. When to escalate for professional advice

Where a dispute involves contract interpretation, allocation of responsibility, payment withholding, loss calculations, termination arrangements, formal notices, regulatory matters, employment relationships, data handling, or possible litigation or arbitration, the company should not rely only on the experience of the project team. Headquarters may provide the organised contract documents, timeline, and evidence register to an instructed and appropriately qualified professional adviser for review before deciding on next steps.

MMD Business Support may assist enterprise setup projects by helping clarify requirements, coordinate materials lists, connect local resources, accompany communications, and follow project progress. Professional work relating to company registration, legal services, tax, audit, immigration, and specific licences should be handled by professional institutions that hold the qualifications required by law. Whether to take any legal or commercial action should be decided by the company based on its own contract, facts, and professional advice.

This content is provided for general information only and does not constitute legal, tax, or immigration advice. Specific requirements should be confirmed against the latest guidance from the relevant Sri Lankan authorities and instructed licensed professional advisers.