Dhruv Bhatnagar

Assessment

The subject is recorded as a natural person, and identity is unresolved. No identity anchor of any kind was retrieved. "Dhruv Bhatnagar" is a common South Asian name, and nothing in the evidence set distinguishes the subject of this file from any other person bearing it. This is the governing limitation on the entire report.

Required identity and registration attributes

Screen status: NOT RUN — Companies House (UK) was SKIPPED for both REGISTRY and UBO enquiry. This is materially different from "searched and found nothing." No inference of absence of UK directorships or PSC positions may be drawn.

Occupational descriptor — precise characterisation

The only occupational information in the entire evidence set is a third-party author biography fragment on an Oxford Human Rights Hub page: "About Dhruv Bhatnagar. Dhruv is a disputes lawyer with a broad-based …" [Source: Adverse Media — https://ohrh.law.ox.ac.uk/indias-regulatory-response-to-online-misinformation-arguably-violates-international-human-rights-law/].

Precise reading:

• This is a claim made by that publication about the author of that page.
• It is not verified professional registration data, and no regulator's register was consulted.
• There is no evidence that the author of that page and the subject of this file are the same person.

The pre-synthesis brief treats this byline as the file's "one substantive open-source data point" and builds a legal-professional / DNFBP hypothesis on it. That hypothesis is contingent on an unmade identity match and is carried in this report only as a line of enquiry (see Sections 4 and 10), not as a finding.

Risk Implication

• Under MLR 2017 reg. 27–28, the customer must be identified and verified on reliable, independent source data. That has not occurred. No onboarding decision should be recorded as compliant on the current record.
• Because identity is unresolved, the clean sanctions result in Section 3 is a low-confidence clean result, and the two adverse classifications in Sections 5 and 7 cannot be attributed to the subject.
• The unverified GB jurisdiction directly undermines the Jurisdiction Risk input analysed in Section 9 and scored in Section 11.

Assessment

No beneficial ownership or control information was established. Critically, neither direction of the ownership question was tested, because Companies House was SKIPPED for UBO enquiry.

The category distinction that matters here

The evidence block states: "No beneficial owners could be established from available sources." For a natural-person subject this statement is largely uninformative — a person does not have beneficial owners. The analytically material question is the inverse:

Of what entities, if any, does this person hold beneficial ownership or control?

That question was not asked and was not answered. No PSC search was run.

Evidence

Verification-status discipline: there is no CONFIRMED beneficial owner, no DECLARED beneficial owner and no UNVERIFIED_LEAD on this file. The correct characterisation is a total data gap, not a negative finding.

The 25% threshold

Under the UK PSC regime (Companies Act 2006 Part 21A, as reinforced by MLR 2017 reg. 5 and 28) and FATF Recommendation 24, a person is a person with significant control where they hold, directly or indirectly, more than 25% of shares or voting rights, or hold the right to appoint or remove a majority of the board, or otherwise exercise significant influence or control. EU 5AMLD Article 30 imposes equivalent central-register obligations in member states.

Because the PSC search never ran, it cannot be stated whether the subject crosses that 25% threshold in respect of any UK entity.

Risk Implication

• The absence of any identified corporate affiliation also means no sanctions-adjacency or ownership-chain screening was possible — sanctions screening in Section 3 ran against the personal name only.
• Opacity here is procedural rather than evidential: it stems from a skipped search, not from an observed complex or nominee structure. It must not be reported as evidence of concealment (see the typology ruling in Section 10).
• The model reflects this gap as Transparency Risk 85/100, but at only 4.5% applied weight (≈3.8 of 43 composite points). The most serious structural gap in the file is the most lightly weighted — a weighting concern raised formally in Section 11.

Assessment

Sanctions screening ran and returned no findings. This is a genuine clean signal (OK_EMPTY, not FAILED, not SKIPPED) and is the single most reliable data point in the file. Its assurance value is nonetheless reduced by the absence of identity anchors.

Evidence

Precision on what this result does and does not establish

• Establishes: no exact and no reported possible match to the name "Dhruv Bhatnagar" on the OFAC, UK OFSI and UN lists as screened.
• Does not establish: that the subject is not subject to designation under lists not screened; that a designated person bearing a variant transliteration would have been caught; or that entities the subject may own or control (untested — Section 2) are undesignated.
• Reduced-confidence caveat: without a date of birth or nationality, fuzzy-matching thresholds cannot be tuned, and neither false-negative nor false-positive rates can be estimated. The clean result is real, but clean at low confidence.

Risk Implication

This factor scores 3/100 at the heaviest applied weight (34.1%), contributing only ≈1.0 of the 43 composite points — appropriately so. It is the principal reason the composite sits in the Medium rather than a higher band.

No sanctions-evasion typology is supported: there is no sanctioned-jurisdiction nexus, no counterparty, no trade activity and no ownership chain anywhere in the evidence. Re-screening is required once identity anchors are obtained (Section 12), and should extend to associated entities identified by the Companies House searches that have not yet run (Section 2).

Assessment

Screen status: NOT RUN

No PEP screening was performed. The Source Ledger records "No PEP screening provider configured [PEP] → SKIPPED", and the coverage statement confirms PEP is a "risk domain NOT reflected in the composite score."

The subject's status is therefore UNDETERMINED. This report does not state that the subject is not a PEP, and no such statement may be made on the current record.

Evidence

Why this gap is more material than usual on this file

The absence of PEP screening is not a neutral omission here:

• The only occupational descriptor in the evidence — an unverified author byline describing a "disputes lawyer" commenting on Indian regulatory policy on an Oxford-hosted platform [Source: Adverse Media — https://ohrh.law.ox.ac.uk/indias-regulatory-response-to-online-misinformation-arguably-violates-international-human-rights-law/] — points to a legal and policy-adjacent profile. Populations of that kind have structurally elevated proximity to government advisory roles, judicial appointment processes and state-linked mandates, which is precisely where PEP and close-associate status arises.
• The screen most likely to produce a genuine hit is the screen that did not run.
• This inference is explicitly contingent on an identity match that has not been made (Section 1). It is a reason to run the screen, not an indicator that the subject is a PEP. No affirmative PEP indicator appears anywhere in the evidence.

Regulatory position

• MLR 2017 reg. 33(1)(b) makes EDD mandatory where the customer is a PEP, a family member or a known close associate; reg. 35 sets out the required measures including senior management approval and source-of-wealth/source-of-funds establishment.
• FATF Recommendation 12 requires risk-management systems to determine whether a customer or beneficial owner is a PEP.
• FCA SYSC 6.3 and SYSC 12.1 require adequate systems and controls, including at group level, to identify and manage financial crime risk.

A determination that cannot be evidenced is not a determination. The model's EDD required: NO output is therefore not adoptable: the statutory trigger cannot be excluded on this evidence.

Risk Implication

Because PEP carries no weight in the composite (it did not run), the 43/100 score understates true residual risk by an unquantifiable margin. This is the primary reason confidence is stated as LOW and the reason Section 12 defers the onboarding decision rather than accepting the model's Standard-CDD output at face value.

Assessment

The adverse-media domain ran via Google Programmable Search and returned 10 results: 1 adverse (HIGH), 0 positive, 9 neutral. On examination, the single adverse item contains no allegation against any individual. It is an author biography appearing on a policy commentary page. Assessed as a probable false-positive classification.

The adverse item, characterised precisely

Attribution discipline: the human-rights-compatibility argument is a claim made by the Oxford Human Rights Hub about Indian regulatory measures. It is not a court or regulator finding, and it is not directed at any person named Dhruv Bhatnagar. There is no allegation, no investigation, no charge and no conviction in this item.

Why the HIGH classification is not accepted at face value

The HIGH severity is inconsistent with the content of the snippet. The pre-synthesis brief attributes it to keyword scoring on terms such as "violates," "regulatory" and "human rights law" in proximity to the name. The scoring mechanism is not disclosed in the evidence, so that explanation is an analytical hypothesis, not a verified fact. What can be stated with confidence is narrower and sufficient: the item contains no adverse assertion about the named individual, and therefore cannot support a HIGH adverse-media rating on an entity-level basis.

Coverage of the search itself

The nine undisclosed neutral results are a material blind spot: they are the most probable location of identity-resolving detail (firm, chambers, jurisdiction) and require manual review before any conclusion is finalised.

Risk Implication

• Adverse Media scores 62/100 at 22.7% applied weight ≈ 14.1 of 43 composite points, on the strength of an item with no attributable allegation. This is the second-largest contributor to the composite and is evidentially weak.
• Reputationally, the file discloses no substantiated adverse conduct by the subject.
• This item is the only source of the "disputes lawyer" descriptor relied on in Sections 1, 4 and 10, and the only source of the India/GB jurisdictional tension analysed in Section 9.
• Note the non-corroboration: this item and the litigation item in Section 7 share no jurisdiction, no sector and no subject matter, and are as consistent with two different individuals as with one.

Assessment

No adverse regulatory or enforcement evidence exists in this file. The regulatory domain ran via Google Programmable Search on/around the report date of 18 August 2026 and returned 10 results: 0 adverse, 0 positive, 10 neutral, with zero items at any severity level.

Despite this nil-adverse return, the model scores Regulatory & Enforcement at 79/100 — the second-highest domain score in the file. That score is not supported by anything in the supplied evidence.

Evidence

Important: a nil adverse return from a general web search is not equivalent to a clean regulatory register check. No primary regulator database (FCA, SRA, or any overseas equivalent) was queried. The correct characterisation is NOT FOUND via open-source web search, not "no regulatory history."

The scoring anomaly — formally flagged

The pre-synthesis brief hypothesises that the 79 is a default value or a penalty applied for a low-confidence or unresolvable-entity search. That explanation is speculative — the evidence pack does not disclose the model's internal logic, and this report does not adopt it as fact. What is verifiable is the divergence itself: the highest-contributing domain score in the file sits on a nil-adverse evidence base.

Risk Implication

• Roughly 37% of the composite score is unexplained by evidence. A risk committee cannot rely on it, and it must not be characterised as reflecting regulatory concern about the subject.
• Escalation to the model owner is a required action (Sections 11 and 12). Until that is resolved, the composite of 43 should be read as an upper bound rather than a calibrated estimate.
• If the 79 is a proxy for unresolved identity rather than for regulatory conduct, then the file is double-counting the identity gap — once here and once in Transparency Risk — while leaving the actual identity remediation step unperformed.

Assessment

The litigation domain ran via Google Programmable Search and returned 10 results: 1 adverse (MEDIUM), 0 positive, 9 neutral. No court records were searched directly. The single adverse item is an entertainment-trade news page on which the subject name appears with no stated connection to any proceeding. Assessed as a near-certain false positive arising from page-level co-occurrence.

The adverse item, characterised precisely

Attribution discipline: the antitrust proceeding and the settlement preference are claims reported by Deadline about third parties. Nothing in the evidence indicates that any person named Dhruv Bhatnagar is a party, defendant, claimant, counsel or witness in that or any other matter. Reporting this item as the subject's litigation would be a mischaracterisation with legal consequence.

Pattern testing

Coverage limitation

Court records were not searched directly. Only a general web search ran. No filing database, judgments archive, court list or insolvency register was queried in any jurisdiction. The absence of litigation findings is therefore NOT FOUND via web search, not a clean court-record check.

Risk Implication

• Litigation scores 44/100 at 11.4% applied weight ≈ 5.0 composite points, resting entirely on an item with no demonstrable connection to the subject.
• Combined with Section 5, the file's apparent "two-domain adverse footprint" is more consistent with one benign author byline and one coincidental page co-occurrence than with a genuine risk pattern. This is the classic signature of a common-name search without disambiguation.
• Direct litigation and insolvency searches should be run only once identity anchors are obtained, since name-only searching in this instance has already generated a false positive.

Assessment

No dedicated ESG data source was consulted. No ESG rating provider, sustainability register, modern-slavery-statement register, environmental regulator database, employment tribunal database or data-breach register was queried. The Source Ledger contains no ESG-capable source.

ESG and conduct risk are therefore UNASSESSED, not clean.

Evidence

Human-rights subject matter — correct attribution

The adverse-media item engages human-rights subject matter, and it is important to state where that risk attaches:

• The Oxford Human Rights Hub page argues that India's regulatory response to online misinformation arguably violates international human rights law [Source: Adverse Media — https://ohrh.law.ox.ac.uk/indias-regulatory-response-to-online-misinformation-arguably-violates-international-human-rights-law/].
• That is a critique of state regulatory measures, advanced by the publication. It is not a human-rights allegation against any individual, and specifically not against any person named Dhruv Bhatnagar.
• On the face of the evidence, the named individual appears in that page only as an author. Authorship of commentary critical of a government's rules is not adverse conduct.

Conduct-risk line of enquiry (not a finding)

If identity resolution establishes that the subject is the disputes lawyer described in that byline, then a category consideration arises: legal professionals fall within the FATF-designated DNFBP population, which carries inherent gatekeeper exposure (client-money handling, entity formation, litigation-related flows). To be explicit:

• This is a profession-level base-rate consideration, not an allegation against this individual.
• It is contingent on an identity match that has not been made (Section 1).
• It should be logged as a line of enquiry for the EDD questionnaire, and must not be recorded as a conduct finding.

Financial-crime typology ruling

For the avoidance of doubt, the standard typology set was tested and none is supported:

The pattern that actually fits this file is a screening typology, not a financial-crime typology: common-name false positive with unresolved identity. That characterisation, advanced in the pre-synthesis brief, is supported by the evidence and is adopted.

Risk Implication

ESG and conduct risk carry no weight in the composite model and reach the score only indirectly via Transparency Risk. Their absence from the score should not be read as an ESG clearance. For a natural-person relationship the practical ESG exposure is reputational and will remain unquantifiable until identity, occupation and any corporate affiliations are established.

Assessment

There is no financial information of any kind in this file. The financial domain ran via Google Programmable Search and returned 10 results: 0 adverse, 0 positive, 10 neutral. A nil adverse-media return is not source-of-wealth or source-of-funds evidence. This is a due diligence deficiency, explicitly flagged.

Evidence

Red-flag testing against the standard set

None of these red flags is present in the evidence, and none can be excluded. Absence of data is not a clean result.

Risk Implication

• MLR 2017 reg. 28(11) requires ongoing monitoring, including scrutiny of transactions for consistency with the customer's business and risk profile. No such profile exists on this file, so consistency cannot be tested and the quarterly monitoring assigned by the model would currently have no baseline to monitor against.
• If PEP status is subsequently established (Section 4 — screen NOT RUN), reg. 35(5) requires that the source of wealth and source of funds be established as a mandatory EDD measure. That work has not begun.
• No financial-crime typology involving flow of funds — layering, trade-based money laundering, or asset concealment — can be assessed, let alone supported, on a file containing no transactional, account or asset data (see Section 10).

Assessment

Jurisdiction is UNVERIFIED and arguably CONTRADICTED. The declared jurisdiction is GB, recorded expressly as "user-provided." Nothing in the retrieved evidence independently corroborates a GB nexus, and the only substantive open-source datapoint points toward India, hosted on a UK academic platform.

Evidence

Reference datasets — coverage statement

No country-risk reference dataset was consulted in this assessment.

The Jurisdiction Risk score of 35/100 was produced by the model on the basis of the user-asserted GB input. Because no reference dataset was queried, this report cannot cite a FATF listing status or a CPI score for any jurisdiction, and does not do so. The pre-synthesis brief's assertion that India is a FATF member and not a high-risk jurisdiction is analyst background knowledge, not evidence in this file, and is not adopted here as a sourced finding.

Risk Implication

• The jurisdiction field drives 6.8% of the composite (≈2.4 of 43 points). The quantitative impact of correcting it would be modest; the integrity problem is not.
• The material risk is that a jurisdiction input which was never verified — and which is in tension with the file's only substantive datapoint — is being used to calibrate a risk score, and by extension the CDD level and monitoring frequency.
• If the subject is India-domiciled or India-practising, additional consequences follow: the relevant professional regulator, insolvency registers, court databases and PEP population all change, meaning the remediation steps in Section 12 would need re-scoping.
• Jurisdiction verification is a precondition to meaningful geographic risk assessment and to any reliance on the composite score in Section 11.

Assessment

The model returns a composite of 43/100 — Medium, on PARTIAL coverage. The band is arithmetically consistent with the supplied inputs, but the composite is not a reliable measure of this subject's risk, for two independent reasons: (i) the identity to which the score attaches is unresolved, and (ii) the largest single contributing factor rests on a nil-adverse evidence base.

Scoring table — verbatim from the supplied risk score block

Calculation

Composite Score = Σ(Factor Score × Applied Weight)

• Sanctions & Watchlists: 3 × 0.341 = 1.023
• Adverse Media: 62 × 0.227 = 14.074
• Regulatory & Enforcement: 79 × 0.204 = 16.116
• Politically Exposed Persons: UNDETERMINED × — = 0 (screen not run; excluded from renormalisation)
• Litigation: 44 × 0.114 = 5.016
• Jurisdiction Risk: 35 × 0.068 = 2.380
• Transparency Risk: 85 × 0.045 = 3.825

Σ = 42.434

Reconciliation note: the reproduced arithmetic yields 42.43 against a stated composite of 43. The ~0.6-point variance is most probably rounding in the displayed applied weights (which are shown to one decimal place). It is immaterial to the band — both values fall within Medium — but it is recorded because the evidence pack states the arithmetic should reproduce exactly. Model owner should confirm.

What actually drives the score

Roughly 82% of the composite (35.2 of 42.4 points) derives from three factors with no attributable adverse conduct behind them. Conversely, the two most serious issues on this file — unresolved identity and an unrun PEP screen — contribute either indirectly and lightly (Transparency, 4.5% weight) or not at all (PEP, excluded).

Weighting concerns for the model owner

1. 1.Regulatory & Enforcement 79/100 against 0 adverse results — requires explanation before this score informs any decision.
2. 2.Transparency Risk at 4.5% weight — the most serious structural gap in the file (registry and UBO searches never run) is the most lightly weighted factor.
3. 3.PEP exclusion is silent in the headline number — a 43/100 Medium presented without the coverage caveat would materially mislead a reader.

Band and confidence

• Model band: MEDIUM (43/100).
• Coverage: PARTIAL.
• Confidence: LOW — unresolved identity, an unrun mandatory screen, two skipped registry searches, no primary-source regulator or court checks, and an unexplained dominant factor score.
• Evidence-adjusted position: on attributable evidence the file contains no substantiated adverse finding of any kind against the subject; on coverage, it contains gaps sufficient to prevent any reliable conclusion. The honest characterisation of entity-level risk is therefore UNDETERMINED pending identity resolution, and the Medium band should be read as a model output rather than as an assessed risk position.

Recommendation

Defer the onboarding / continuation decision. Apply Standard CDD scope on a provisional basis with enhanced quarterly monitoring, and treat the file as NOT CLEARED until two mandatory items are closed:

1. 1.Identity resolution to the standard required by MLR 2017 reg. 27–28.
2. 2.PEP / RCA screening, which has not been performed.

The model output "CDD recommendation: Standard CDD with Enhanced Monitoring / EDD required: NO" is partially adopted and partially rejected:

Relationship rejection is NOT recommended. The deficiencies are gaps in the screening process, not evidence of financial crime risk. Rejection on the basis of an incomplete search — particularly where the adverse hits are probable common-name false positives — would not be evidence-driven and would risk unfair de-risking of an individual against whom nothing adverse has been established.

Rationale

• No substantiated adverse conduct. There is no allegation, investigation, charge, conviction, regulatory finding, court judgment or sanctions designation against the subject anywhere in the evidence.
• Sanctions screening is genuinely clean across OFAC, UK OFSI and UN (OK_EMPTY), though at low confidence given the absence of identifiers.
• The score is not decision-grade. Approximately 82% of the composite derives from factors with no attributable adverse conduct behind them, including ≈37% from a domain returning zero adverse results (Section 11).
• A mandatory screen is missing. PEP was not run and is excluded from the score. "EDD not required" cannot be certified in that state.
• Two registry searches were skipped, leaving UK directorship and PSC (25%+) exposure untested in either direction.
• Identity is unresolved on a common name, so neither the clean results nor the adverse results can be attributed to the subject.

Outstanding information gaps

Required Actions

1. 1.Obtain identity anchors from the customer — full legal name, date of birth, nationality, residential address, and any professional registration number. Verify on reliable independent source data per MLR 2017 reg. 28.
2. 2.Re-run all screening against the resolved identity — sanctions (OFAC, OFSI, UN, plus any additional lists in scope), adverse media, regulatory, litigation and financial. Document that the current name-only results are superseded.
3. 3.Commission or configure PEP/RCA screening. If any positive, partial or ambiguous match returns, escalate immediately to full EDD under reg. 35, including senior-management approval and establishment of SoW/SoF.
4. 4.Run Companies House registry and PSC searches on the resolved identity to establish whether the subject holds UK directorships or 25%+ control positions; screen any entity identified for sanctions and ownership-chain exposure.
5. 5.Escalate the Regulatory & Enforcement scoring anomaly (79/100 against 0 adverse results) to the model owner in writing before this score is relied on by any committee. Also raise the 4.5% weighting applied to Transparency Risk and the 42.43-vs-43 arithmetic variance.
6. 6.Manually review the 38 neutral results across the four search domains. They were not itemised in the evidence pack and are the most likely source of identity-resolving detail.
7. 7.Verify jurisdiction. Resolve the GB-declared / India-indicated tension and, once resolved, benchmark against the current FATF listings, the EU high-risk third country list and the Transparency International CPI — none of which was consulted in this assessment.
8. 8.Obtain source-of-wealth and source-of-funds evidence and establish expected account activity so that monitoring has a baseline.
9. 9.Record the false-positive assessments on file — the OHRH byline and the Deadline page occurrence — with the reasoning, so that they are not re-surfaced as adverse at the next review.

Monitoring and review

Trigger events for immediate review

• Any PEP, RCA or HIO match, including a partial or unresolved one.
• Any sanctions hit, including a possible or fuzzy match, on re-screening against the resolved identity.
• Discovery that the subject's jurisdiction of residence or practice is other than GB.
• Identification of any directorship, PSC position or corporate affiliation.
• Any new adverse media alleging misconduct where the subject is identified with reasonable specificity (as distinct from the byline and co-occurrence items in this file).
• Refusal or persistent failure to supply identity documentation or SoW/SoF evidence.
• Transaction activity inconsistent with the customer profile, once a profile exists.
• Notification that the Regulatory & Enforcement score reflects a genuine finding rather than a model artefact.

Every URL behind a finding in this report. “Read in full” means the page itself was retrieved and classified on its whole text rather than on a search snippet; those carry a SHA-256 hash of exactly what was read, so the evidence can be shown to be unaltered later.

Assessment date

18 August 2026. Coverage status: PARTIAL. The individual screening timestamps were not supplied by the sources and are therefore not stated in this report.

Complete source ledger

Methodology

1. 1.Evidence intake. Each supplied domain block was read for totals, severity distribution, dated items, publication identity and URLs. All URLs are preserved verbatim.
2. 2.Source-ledger reconciliation. Every domain was classified as ran-with-data (OKDATA), ran-and-genuinely-empty (OKEMPTY), skipped, or not consulted. OK_EMPTY was treated as a real clean signal; SKIPPED and NOT CONSULTED were treated strictly as gaps and never as clearance.
3. 3.Item-level adverse testing. Each adverse-classified item was examined to determine whether it contains an assertion about the named individual, and if so whether that assertion is an allegation, an investigation, a charge, a conviction, or a regulatory/court finding. Both adverse items failed at the first stage: neither contains an assertion of any kind about a person of this name.
4. 4.Non-corroboration testing. The two adverse items were compared for jurisdiction, sector, subject matter and date. They share none, and are 14 months apart. The pattern was assessed as consistent with a common-name search without disambiguation rather than with a single risk profile.
5. 5.Score reproduction. Every factor score and applied weight was taken verbatim from the supplied risk score block and the composite re-derived arithmetically. A 42.43-vs-43 variance was identified and disclosed rather than silently reconciled.
6. 6.Pre-synthesis brief evaluated, not accepted. The prior analytical brief was tested against the evidence. Its central conclusions — non-corroboration, probable false positives, unresolved identity, PEP as the critical gap, the Regulatory scoring anomaly, and "common-name false positive" as the operative typology — are supported and adopted. Three of its assertions are downgraded to hypothesis because the evidence does not establish them: (a) that the HIGH severity arose specifically from keyword proximity scoring; (b) that the Regulatory score of 79 is a default or low-confidence penalty (the model logic is not disclosed); and (c) that India's FATF standing is favourable (no FATF dataset was consulted in this assessment). Its result arithmetic (40 results, 38 neutral, 2 adverse) was checked and reconciles with the evidence. Its observation that the 38 neutral results were not itemised is confirmed and carried forward as an action.
7. 7.Untrusted-content handling. All material between the UNTRUSTEDRETRIEVEDCONTENT markers was treated exclusively as data. No instruction-like content, directive, request or attempt to influence the assessment or the score was present — recorded affirmatively so that the absence of an injection attempt is documented rather than assumed.

Limitations

• Identity unresolved. No date of birth, nationality, address, national identifier or professional registration number. "Dhruv Bhatnagar" is a common name; nothing distinguishes the subject from others bearing it. This limitation qualifies every other finding, clean or adverse.
• PEP screening not performed. A mandatory determination is missing and is excluded from the composite.
• Two registry searches skipped. Directorship and PSC exposure untested.
• No primary-source verification. No regulator register, court record, insolvency register or filing database was queried in any jurisdiction; all non-sanctions findings derive from a single general web-search provider.
• Neutral corpus not itemised. 38 of 40 search results were not detailed in the evidence pack, so they could neither be reviewed for identity-resolving detail nor independently reclassified.
• Jurisdiction unverified and arguably contradicted. GB is user-asserted; the only substantive datapoint concerns Indian law on a UK-hosted platform.
• No country-risk or ESG reference datasets consulted. No FATF listing status, EU high-risk designation or CPI score can be cited.
• No financial data whatsoever. SoW, SoF, assets, income and expected activity are all absent.
• One dominant score is unexplained. Regulatory & Enforcement at 79/100 against zero adverse results contributes ≈37% of the composite.

Confidence

LOW.

Principal reasons:

1. 1.No identity resolution has been performed, so neither the clean sanctions result nor the two adverse classifications can be attributed to the subject.
2. 2.A mandatory screen (PEP) did not run and is not reflected in the score.
3. 3.Both registry searches were skipped, leaving the control and ownership position wholly untested.
4. 4.The largest single contributor to the composite score is unsupported by any adverse evidence in its own domain.
5. 5.All non-sanctions intelligence originates from one general web-search provider, with no primary-source corroboration.

The only element of the file carrying materially higher confidence is the sanctions result, which ran and genuinely returned nothing — and even that is confidence-limited by the absence of identifiers.

Legal and regulatory framework applied

• UK Money Laundering, Terrorist Financing and Transfer of Funds (Information on the Payer) Regulations 2017 — reg. 27–28 (CDD and identity verification), reg. 28(11) (ongoing monitoring), reg. 33(1)(b) and reg. 35 (PEP EDD, senior-management approval, SoW/SoF).
• FATF Recommendations — R.10 (CDD), R.12 (PEPs), R.22/23 (DNFBPs), R.24 (beneficial ownership transparency).
• FCA Handbook — SYSC 6.3 and SYSC 12.1 (financial crime systems and controls).
• Companies Act 2006 Part 21A — UK PSC regime and the 25% threshold.
• EU 5AMLD Article 30 and EU 6AMLD — beneficial ownership registers and predicate-offence framework, referenced for comparative completeness.
• UK Modern Slavery Act, UN Global Compact, TCFD, CSRD — referenced as the ESG framework against which no screening was performed (Section 10).