GCLE common mistakes
GCLE · Understand the traps and how to avoid them.
Treating common-law and civil-law doctrines as interchangeable - for example hunting for consideration in a contract governed by a civil-law system, or assuming a general duty of good faith is implied in an English-law commercial contract.
Most study material is written from a single national perspective, so candidates memorize one doctrinal vocabulary and then apply it to every fact pattern regardless of the stated governing law.
What to do instead
For each core doctrine, keep a three-column note (common law / civil law / treaty or regional overlay) and open every answer by stating which legal family the analysis assumes and what would change under the other.
Answering from general contract doctrine while ignoring the express clauses in the fact pattern - notice periods, limitation of liability, entire-agreement, governing law, and tiered escalation or ADR ladders.
The operative clause is usually one sentence buried in the fact pattern, and the familiar textbook rule is easier to pattern-match than to read the clause carefully.
What to do instead
Read and restate the operative clauses in one line each before applying any default rule, then explicitly ask whether the clause displaces the default and which body decides the dispute.
Confusing internal approval with authority to bind - assuming a board or shareholder resolution makes a named individual an authorized signatory, or that a parent company's approval binds its subsidiary.
Candidates collapse corporate authority (who decides) into agency (who can bind the entity externally), and subsidiary separateness is easy to gloss over in a short fact pattern.
What to do instead
Draw the full chain - entity, organ or resolution, delegation, individual signatory, external representation - and check the constitutional documents and any power of attorney before concluding the entity is bound.
Treating consent as the default lawful basis for every processing activity, including employee data and data received from a business customer.
Consent is the most familiar and most visible concept in privacy training, whereas contract necessity, legal obligation and legitimate interests require a purpose-by-purpose analysis that takes longer.
What to do instead
Run a lawful-basis test per processing purpose before considering consent, test whether consent is genuinely freely given in the relationship, and separately identify the cross-border transfer mechanism as a distinct question.
Treating anti-money-laundering due diligence and anti-bribery due diligence as one exercise - running KYC and list screening on a third party and then declaring the relationship 'cleared' on all compliance fronts.
All three regimes sit in one compliance function and share a vendor-onboarding workflow, so the shared form creates the illusion of a shared test.
What to do instead
Keep three separate workstreams with different questions and different evidence: beneficial ownership and source of funds (AML), public-official status, intermediaries and red flags (bribery), and list, ownership and end-use screening (sanctions); state in the answer which regime creates the obligation.
Importing a home-country employment default into a cross-border fact pattern - assuming at-will termination, no works council or employee-representative body, easy reclassification of contractors, and no statutory severance.
At-will employment is assumed to be the 'normal' baseline, and local mandatory rules that override it are invisible unless specifically looked up.
What to do instead
Trigger a per-jurisdiction checklist whenever headcount, location or entity structure changes: consultation duties, representative bodies, statutory severance, transfer-of-undertaking rules, and the local contractor-classification test.
Assuming a technology licence carries rights the grant clause does not give - modification, sublicensing, affiliate or production use, or ownership of derivative works - or applying US work-made-for-hire doctrine to a contractor based elsewhere.
'We licensed it, so we can use it' is intuitive, while the scope limits in a grant clause (field, territory, term, users, derivatives) are technical and easy to skim.
What to do instead
Parse the grant clause into six dimensions (rights granted, permitted users, territory, term, sublicensing and modification, derivative works) and check default ownership rules under the contractor's actual governing law rather than the US rule.
Running the conflicts screen only against the named client entity, missing affiliates, parent and subsidiary entities, directors acting in a personal capacity, and former clients whose confidential information is relevant to the new matter.
Conflict checks are operationally executed against a matter or client name in a database, but the legal test turns on who the client is and who the adverse party is, which is broader than any single data field.
What to do instead
Map the client group, affiliates, individual officers and former clients on one side and the adverse parties on the other, then test each pairing and state whether the conflict is consentable and what form of consent (written, informed, advanced waiver) is required.
Jumping straight to the outcome of an investigation - discipline, termination, self-report - without first addressing privilege, employee interview warnings, data-transfer or works-council constraints on collecting evidence, and preservation obligations.
The fact pattern ends on a decision point, and candidates answer the last question asked instead of the sequence that makes the answer defensible.
What to do instead
Answer in sequence: scope and legal basis, privilege and interview protocol, evidence preservation and data-transfer limits, factual findings, remediation, and only then disclosure or reporting obligations.
Concluding that a counterparty is not sanctioned because the named entity does not appear on a list, without checking ownership or control by listed persons, sectoral restrictions, the counterparty's jurisdiction, or the end use of the goods.
Screening is automated against names, so the name-match result feels like the complete test; the ownership-aggregation, sectoral and territorial measures are separate analytical steps that no screening tool performs.
What to do instead
For each counterparty record five separate findings: direct list match, aggregated ownership and control by listed persons, sectoral and territorial exposure, goods and end-use classification, and payment-route or intermediary exposure.