How to scope due diligence for an overseas business project
Editorial illustration
GURI Journal · Published 31 October 2026
A request to “check the whole project” can produce a substantial report without answering the buyer’s actual question. The accountant reviews historical accounts, the lawyer examines corporate documents, and the technical adviser assesses equipment. Meanwhile, the proposed investment depends on a customer contract that nobody was asked to investigate.
A useful due diligence brief connects the proposed transaction to evidence. It tells the team what decision is approaching, what could change that decision, and which questions require specialist work. GURI’s approach starts with those connections before selecting a standard checklist or agreeing a page count.
Describe the transaction before describing the service
State what the investor expects to acquire or fund. An equity purchase, a loan, an asset purchase and participation in a new joint venture involve different rights and evidence. Identify the relevant legal entities, jurisdictions, assets and proposed counterparties. If the structure is still being negotiated, record the alternatives rather than silently choosing one for the analysis.
Explain the immediate decision. A preliminary decision to continue negotiations requires a different level of work from a review intended to support signing. The brief should say which stage it serves. A limited review becomes misleading when its title suggests a comprehensive conclusion that the agreed methods cannot support.
Also identify who will use the findings. The commercial lead may need evidence about customer dependence; the finance team needs to understand funding requirements; the decision maker needs to see how unresolved issues affect the proposal. These needs should meet in a coordinated result, rather than three unrelated reports.
Turn broad disciplines into answerable questions
For financial work, specify the relationships to examine. What supports reported revenue? How does it connect to delivery and cash collection? Which liabilities, recurring costs and funding assumptions are included in the model? “Review the finances” does not establish whether the work covers historical figures, forecasts or both.
Legal work should identify the rights and jurisdictions being considered. Depending on the transaction, this may include ownership, material contracts, permissions, restrictions or rights to particular assets. The appropriate professional must define the relevant scope. A company registration search cannot silently stand in for a legal assessment of the transaction.
Commercial questions may concern customers, pricing, sales channels and the evidence behind expected demand. Technical questions may concern asset condition, process capability or the basis of claimed output. The brief should include the disciplines the decision requires and explicitly identify material areas that remain outside the assignment.
Fix the entities, periods and versions
Consider environmental, social and other material issues for the particular operation. The EBRD’s description of its own due diligence includes environmental and social assessment alongside other disciplines. This illustrates the breadth a project review may need; the Bank’s requirements are not automatically the rules for every private transaction.
Choose an information cut-off date and the periods to be analysed. A group presentation, a subsidiary’s accounts and a forecast for a proposed new operation do not describe the same reporting perimeter. Require the team to reconcile those differences before comparing headline numbers.
Provide an initial document index with dates, owners and version status. Distinguish information that has been requested, received, reviewed and corroborated. A populated data room can still contain substantial gaps; the number of files is not a measure of the questions answered.
Agree what happens when new information arrives. A replacement financial model can change earlier calculations and conclusions. The team should identify affected work, preserve the previous version and explain any impact on timing or cost. Otherwise a final report may combine individually careful analyses of incompatible versions.
Match methods to the claims being tested
List the proposed methods: document review, public records, authorised interviews, third-party confirmations, site work or technical testing. State who will arrange access and who may contact customers, employees or other parties. Having a commercial reason to ask a question does not remove confidentiality or access requirements.
The International Trade Administration’s background-check guidance distinguishes a preliminary company check from deeper in-country work. That distinction is useful when commissioning a review. It does not mean a particular US government service is available to every investor or covers every transaction.
For example, a video call may show equipment operating at a particular moment. It does not, by itself, establish ownership, sustained capacity or performance under the conditions assumed in the investment model. If the assignment excludes the work needed to answer those questions, the report must preserve that limitation.
Set priorities without hiding inconvenient questions
Agree how the team will assess significance. A single monetary threshold may be inappropriate for issues such as access to an essential technology or permission to use a site. Ask the reviewer to explain how each important finding affects the proposed transaction, rather than relying entirely on a numerical score.
Require early notice of findings that could change the scope or make part of the work unproductive. If a key asset is outside the proposed transaction, it may be sensible to clarify that point before spending heavily on a detailed operating forecast. Sequencing the work should improve decisions, not remove difficult questions from the final review.
Specify how specialists exchange findings. A legal restriction can alter an operating assumption; a technical limitation can change the cash requirement. The coordinator should ensure those consequences reach the relevant reviewer and appear consistently in the overall assessment.
Agree deliverables that can be checked
Ask for a concise decision summary supported by detailed findings, identifiable sources, calculations where relevant, limitations and unresolved questions. Each significant conclusion should explain what was examined and what the evidence supports. A reassuring adjective is not a substitute for that chain.
Include an action register where further work is necessary. It should identify the missing evidence, the person responsible and the decision or stage affected. A recommendation to obtain a document must not be presented as though the document has already been obtained and assessed.
Discuss who may rely on or receive the report and for what purpose. Sharing it with another investor or lender may differ from the agreed assignment. Resolve that with the adviser alongside confidentiality, ownership of working materials and any intended use of supporting files.
Test the brief against one important claim
Choose a claim from the project proposal, such as the expected output from a production line. Can the brief show who checks technical capability, who tests the sales assumption and who reflects the findings in the financial model? If a necessary part has no owner, the scope is incomplete.
Before appointment, also ask about relationships between the review team and the project’s owners or other participants. Agree how relevant conflicts will be disclosed and managed. The reviewer must be able to report an unwelcome finding without the assignment being treated as a request to endorse a predetermined conclusion.
A strong brief does not promise that every uncertainty will disappear. It creates a disciplined way to determine what is supported, what remains conditional and what must happen before the next decision. That is a more useful acceptance standard than a favourable verdict or an impressive volume of documents.