This Schedule lists, by name and by named variants, persons, entities and assets under ten discrete Parts. Its mechanical effect is to identify specific natural persons, organisational bodies, quasi-governmental bodies and commercial enterprises, grouped principally around Taliban leadership and structure (Parts 1-6), individuals associated with Usama bin Laden (Part 7), and a broader compendium of individuals and organisations said to be identified pursuant to United States President Bush’s Executive Order Number 13224 of 23 September 2001 (Part 8). The Schedule includes aliases, alternative dates of birth, locations and, for some entities, addresses and trade names. Examples: Part 1 opens “The Taliban” and then enumerates named officials such as “Mullah Mohammad Rabbani, Chairman of the Ruling Council, Head of the Council of Ministers” and “Mullah Mohammed Omar, Leader of the Faithful (‘Amir ul-Mumineen’), Afghanistan.” Part 7 names “Usama Bin Muhammad Bin Awad Bin Ladin (aka Usama bin Laden; aka Osama bin Laden aka Abu Abdallah Abd Al-Hakim)” and lists multiple close associates. Part 8 is headed “Other Individuals and Entities, as identified pursuant to US President Bush’s Executive Order Number 13224 dated 23 September, 2001” and contains a long roster of terrorist organisations, financial houses, charities, companies and individuals with a variety of identifying details.

Mechanically, the Schedule functions as an explicit catalogue of designated targets: it supplies textual identifiers (names, aliases, alt DOBs, locations, business names) that any statutory or administrative regime attaching consequences to Schedule 1 will use to determine who falls within that regime. The Schedule itself does not in this text set out the consequences, licensing regimes or enforcement apparatus; it supplies the factual list that other provisions of the parent instrument will reference to trigger obligations or prohibitions. Where the Schedule includes parenthetical material , alternate names, alternate spellings, alternative domiciles , it expands the net of identification beyond a single canonical name.

The Schedule also cross-references an external information source: Part 8 contains a parenthetical note directing readers to the US Treasury/OFAC site for further descriptive information. That note signals alignment or reliance on foreign designation sources for supplementary detail. The Schedule therefore functions as a primary identification instrument together with pointers to other lists for context and additional identifiers.

Finally, the Schedule is arranged to make operational checking practicable: grouped parts permit target-focused screening (Taliban leadership vs. bin Laden-associated individuals vs. entities identified under US EO 13224). The inclusion of corporate and trade names, addresses and multiple variants increases match rates for automated name-screening systems but also raises scope for false positives where common names or overlapping trade names exist.

The Schedule is built around several recurring structural concepts that govern how a practitioner should read and use it. Those core concepts are identification by name and variant, grouping by functional or historical association, duplication of identifiers, and cross-reference to foreign designations.

Identification by name and variant. The Schedule supplies primary names and an extensive set of alternative names and aliases in parentheticals. Examples: “Usama Bin Muhammad Bin Awad Bin Ladin (aka Usama bin Laden; aka Osama bin Laden aka Abu Abdallah Abd Al-Hakim)” (Part 7). Individuals and entities frequently have multiple transliterations, alternative romanisations, kunyas (eg Abu X), nom-de-guerre and alternative legal permutations. The Schedule purposefully presents these variants to cover transliteration and identity-masking techniques.

Grouping. The instrument organises entries into Parts that reflect the target’s role or source of designation: (1) “The Taliban” (a long list of Taliban office-holders and officials), (2-5) Taliban diplomatic missions and consulates with named personnel, (6) other Taliban entities (eg Ariana Afghan Airlines; Da Afghanistan Bank), (7) individuals associated with Usama bin Laden, and (8) a broad set of groups and entities “as identified pursuant to US President Bush’s Executive Order Number 13224”. The organisational logic makes clear that this is not an alphabetic register but a thematic compilation: users will often treat different Parts differently in operational policy.

Multiplicity of identifiers. Many entries include additional identifiers beyond names: alt dates of birth, multiple places of birth, passport numbers, addresses and even job titles. Examples in Part 8 include passport numbers and alternative dates of birth for particular individuals (eg “DARKAZANLI, Mamoun ... Passport No: 1310636262 <Germany>”). The presence of such data supports narrower, higher-confidence matches for screening, but not every entry has those fields.

Cross-reference to foreign designations. The Schedule explicitly notes that some entries are identified pursuant to US Executive Order 13224 and points users to the US Treasury/OFAC site for further information (“Note: further descriptive information ... available at http...”). This shows the Schedule’s function as part of an internationalised designation regime: it is not an isolated list but part of a landscape where foreign lists inform and are cross-checked against domestic names.

Variants and corporate webs. The Schedule contains corporate groups with multiple trading names and subsidiaries (eg the extensive AL-BARAKAAT family listings, various Barakaat companies, Al-Baraka Exchange LLC), and trusts or financial intermediaries (eg ASAT TRUST REG.). Those multi-entry corporate webs indicate the Schedule intends to capture not only obvious operators but also financial plumbing and associated trading vehicles.

Directly affected persons and entities. The Schedule names the persons and entities; therefore those listed are the primary subjects of the Schedule. Part 1 enumerates dozens of named Taliban officials (eg “Mullah Hadji Mohammad Hassan, First Deputy, Council of Ministers; Governor of Kandahar”), Part 2-5 list personnel attached to Taliban “Embassy” and “Consulate General” missions in Islamabad, Peshawar, Karachi and Quetta, and Part 6 lists Taliban-linked entities (eg “Ariana Afghan Airlines,” “Da Afghanistan Bank,” “Banke Millie Afghan”). Part 7 lists Usama bin Laden and close associates by name and alias, and Part 8 contains an extensive roster of organisations, charities, financial entities, individuals and trading companies linked to international terrorist designations. Those named are the obvious direct targets.

Entities beyond those named. The Schedule’s composition means a variety of non-listed actors will be affected in practice. Financial institutions, payment service providers, remittance houses, insurers, shipping companies, freight forwarders, trade counterparties, professional firms (lawyers, accountants), telecommunications providers, and any business required to screen counterparties will need to reconcile their customers, suppliers and transaction counterparties against this list to avoid regulatory, reputational and operational risk. For example, Part 8 contains numerous remittance and money-transfer firms (eg AL-BARAKAAT WIRING SERVICE, BARAKAT WIRE TRANSFER COMPANY) whose presence in systems can cause cascading screening alerts for banks and remittance networks.

Diplomatic and quasi-diplomatic contacts. Parts 2-5 list people described using diplomatic ranks and postings for Taliban missions (“Ambassador Extraordinary & Plenipotentiary,” “First Secretary/Deputy Head of Mission,” “Consul General,” “Commercial Attache”). Practitioners dealing with protocols, consular services, or diplomatic clearances will find potential ambiguity: listed names include individuals styled with diplomatic titles that may interact differently with other legal regimes (eg diplomatic immunities under international law) although the Schedule itself does not resolve such questions.

Indirectly affected third parties. Companies and NGOs with historical ties, counterparties in jurisdictions where listed entities operate, shareholders in companies named on the Schedule, and employees or service providers whose identities overlap with listed names face indirect effects. Example risks include frozen business relationships, disrupted contract performance where a supplier is named, and reputational damage where a name match is ambiguous.

The Schedule, as provided, is an identification instrument and does not itself set out duties, rights, exemptions or licensing schemes within this text. It supplies the roster of targets to which duties and rights in the parent Act or instrument will attach. Readers must therefore separate the Schedule’s factual content (the names, aliases, addresses, positions) from the legal obligations that other text imposes when the Schedule is incorporated into law.

Duties that will commonly be triggered by a Schedule of this form (practitioner note). Although the Schedule does not itself prescribe them here, schedules of this nature are typically paired with duties in the parent instrument that include: screening obligations for regulated entities; freezing or restraint obligations in respect of assets; prohibition on providing funds, services or economic resources to listed persons and entities; reporting and disclosure duties; and obligations to seek licences or permits for dealings that would otherwise be prohibited. Because those duties are not quoted in this text, a practitioner must confirm the parent Act’s operative provisions before advising on enforcement or compliance steps.

Rights and procedural safeguards likely to be relevant (but not in this text). The Schedule includes no text on rights of review, removal or administrative remedies. Typical rights that practitioners must check in the parent instrument include: rights to seek administrative review or judicial review of a designation; rights to apply for licences or exemptions; privacy protections during information-sharing; and procedural notification duties. The Schedule as printed does not indicate whether listed persons will be notified, what evidentiary standard underlies listing, or whether de-listing processes exist.

Information rights imposed by the Schedule’s structure. The Schedule does provide rights of identification to users: it gives data elements (alternate names, DOBs, passport numbers, addresses, organisational roles) that enable regulated entities and counsel to better assess whether a person or organisation in their systems is the same as the listed subject. For example, where an entry contains a passport number or alternate DOB (see Part 8 entries such as DARKAZANLI, Mamoun with Passport No: 1310636262), those identifiers narrow the universe of potential matches and reduce the cost of secondary inquiries.

Operational duties for compliance officers. The Schedule obliges, in practice, operators to implement reliable name-matching and escalation procedures. Because the list uses numerous aliases and trading names (eg the AL-BARAKAAT family in Part 8), duty-holders must account for corporate chains, alternate spellings and transliteration variants. That imposes practical duties on data hygiene, watchlist updates, and manual review to resolve false positives.

This Schedule does not contain penalty provisions or enforcement mechanisms within the text presented. It is an annexed list of designated persons and entities; the legal sanctions and enforcement instruments that apply to matches against this list are not printed here. Practitioners must therefore consult the operative sections of the parent Act, regulations or secondary instruments to identify criminal offences, civil penalties, administrative sanctions, enforcement agencies and licensing regimes.

What the Schedule enables for enforcement. Because the Schedule provides definitive identifiers, it becomes the reference standard for any enforcement system that the parent instrument creates. Enforcement agencies and regulated institutions will use these identifiers to detect matches, freeze assets, block transactions, refuse services or seek authorisations. The presence of detailed alternate names, addresses and passport numbers increases enforcement agencies’ ability to obtain evidence and to seek restraint orders, where the parent law authorises those remedies.

Administrative enforcement risks. The Schedule’s structure raises specific administrative enforcement challenges. First, the volume of aliases and corporate permutations (eg BARAKAAT/AL-BARAKAAT listings, AL-TAQWA groupings) can generate numerous screening hits that require human review and triage. That produces administrative costs for compliance teams and enforcement bodies. Second, the inclusion of diplomatic titles and consular staff names requires enforcement agencies to consider complex questions about immunities and privilege, even though the Schedule does not resolve immunity questions.

Criminal and civil penalty implications (practitioner note). If the parent legislative instrument attaches criminal or civil liability for dealings with listed persons, then the Schedule’s detailed identifiers can be the factual basis for charges or civil restraint applications. The Schedule itself does not supply mens rea text or available defences. Practitioners should therefore verify whether the parent Act envisages strict liability offences, knowledge-based offences, or offences requiring reasonable suspicion or intent.

Enforcement cooperation and extraterritoriality. The Schedule’s explicit reference to US EO 13224 and the OFAC database indicates a likely intent to coordinate with foreign enforcement lists and to allow mutual assistance or parallel sanctions. That alignment increases the potential for cross-border enforcement action and information-sharing between agencies. However, those cooperative mechanisms and the legal bases for sharing are not included in the schedule and must be located in the parent Act, memoranda of understanding, or international agreements.

The Schedule, standing alone, is an identification annex; its legal interaction with other laws depends on how the parent statutory instrument incorporates the Schedule. Within this text there are two explicit signals of cross‑jurisdictional or cross‑instrument interaction: the inclusion of diplomatic titles and missions, and the express reference to US Executive Order 13224 with a pointer to the US Treasury/OFAC site.

Reference to US EO 13224. Part 8 is headed “Other Individuals and Entities, as identified pursuant to US President Bush’s Executive Order Number 13224 dated 23 September, 2001” and includes the NOTE directing readers to further descriptive information available at the US Treasury/OFAC website. This indicates substantive alignment or reliance on a US designatory framework. Practically, a domestic legal regime that incorporates this Schedule will be synchronised, in part, with US designations. That raises questions about cross-border enforceability, the availability of foreign-sourced intelligence as evidence in domestic proceedings, and reciprocal recognition of asset freezes or licence regimes. The Schedule does not specify whether any foreign designations automatically imported here, or whether domestic administrative processes were used to vet or approve each item.

Diplomatic and consular designations. Parts 2-5 label named individuals with diplomatic titles attached to Taliban missions (eg “Ambassador Extraordinary & Plenipotentiary,” “Consul General,” “First Secretary”). If a parent law imposes sanctions, such listings intersect with international law governing diplomatic status and consular immunity. The Schedule does not resolve whether listing extinguishes diplomatic privileges, whether separate legal processes apply to persons enjoying immunity, or whether host-state obligations (eg Vienna Convention on Diplomatic Relations) constrain enforcement. Practitioners must therefore reconcile domestic statutory obligations with international law obligations in handling listed diplomatic personnel.

Intersection with domestic AML/CFT and criminal laws. While the Schedule itself does not state how it interacts with domestic anti‑money laundering/combating the financing of terrorism (AML/CFT) regimes or criminal statutes, the inclusion of banks, remittance houses and other financial institutions (eg Da Afghanistan Bank; AL-BARAKAAT group) means that domestic AML/CFT reporting regimes will have an operational interest. Regulated entities typically must conduct enhanced due diligence and file suspicious matter reports where transactions touch listed entities. The Schedule’s entries can trigger AML obligations only if the parent law or domestic AML regime references the Schedule or adopts it as a sanctions source.

The Schedule text provided contains no explicit amendment history metadata: there are no dates of adoption for each entry, no marginal notes indicating additions or deletions, and no notation of which government or instrument appended it. The only temporal marker in the text is the reference in Part 8 to “US President Bush’s Executive Order Number 13224 dated 23 September, 2001.” That reference suggests that at least some entries derive from designations made in or after that date, but it does not provide domestic timeline information or show when particular entries were incorporated into this Schedule.

Practical consequences of the absence of an amendment trail. For users, the lack of embedded amendment metadata means that a practitioner cannot, from this Schedule alone, tell when a given individual or entity was designated, whether the listing is current, or whether an entry has been historically contested or judicially varied. That omission increases the need to consult supplementary sources: government gazettes, official consolidated lists, regulatory guidance notes, or agency websites where designations and delistings are typically recorded.

Where to look for authoritative amendment records. Practitioners must consult the parent Act’s register (if one exists), the official government consolidated list maintained by the sanctioning agency, legislative instruments (gazettes) that formally add or remove entries, and any public notices from enforcement bodies. The Schedule’s inclusion of the OFAC pointer in Part 8 indicates that a foreign source may hold detailed designation histories for those entries, so cross-checking foreign lists may supply dates and explanatory narratives for those items.

Common amendment mechanisms (contextual note). Sanctions or designation regimes frequently amend schedules via subordinate instruments, ministerial determinations, or orders. Those instruments normally carry statutory serial numbers and dates and appear in an official gazette. The absence of such markers in this Schedule means the schedule must be validated against official consolidated lists to ensure currency.

Impacts on legal certainty. Without amendment history within the Schedule text, affected persons face uncertainty about the length and recency of their listing, and counterparty firms lack internal evidence to justify actions unless they maintain external contemporaneous records. This increases litigation risk and operational friction for banks and advisers who must show reliance on an up‑to‑date authoritative source.

Recommendations for practitioners given the missing history. Always check the parent legislative instrument or the administering agency’s publicly available consolidated list for up-to-date entries and amendment timelines. Maintain records of the version of the Schedule relied upon in any compliance decision. Where a client seeks de‑listing or challenges an entry, obtain the administrative record or the designating instrument that formalised the entry; that will typically include dates and reasons not present in this annex.

The Schedule text contains no references to litigation, court decisions, judicial review outcomes or administrative appeals. It presents a catalogue of names and aliases without any appended judicial determinations or notes on prior challenges. There are no citations of cases, tribunal decisions, or administrative rulings within this text to indicate whether any entries have been subject to successful delisting, partial de‑designation, or judicial remediation.

Implications of the text’s silence on litigation. Because this Schedule does not record litigation history, counsel and compliance teams cannot use it to determine whether an individual or entity has previously contested their designation, succeeded in a challenge, or obtained interim relief. The absence of litigation indicators means that due diligence must extend beyond the Schedule to open-source legal research and administrative records to identify prior challenges or judgments that might affect enforcement risk.

How to research litigation history in practice. To establish whether any listed person has been litigiously challenged, practitioners should consult: (a) judicial databases for domestic courts and tribunals, (b) administrative review bodies’ records, (c) consolidated sanction lists and their annexed notes (some lists annotate entries with “subject to review” or “de-listed on X date”), (d) foreign court decisions (noting the Schedule’s reliance on US EO 13224 entries may entail US litigation records), and (e) media and NGO reporting that often track de‑listing campaigns. The Schedule itself does not link these resources.

Potential legal issues recurring in challenges (contextual note). Challenges to designation commonly raise administrative law points (procedural fairness, disclosure of reasons), substantive evidence questions (insufficient nexus to terrorism or wrongdoing), proportionality and human rights claims, and separation‑of‑powers arguments. Where a Schedule offers no statement of reasons, applicants often press for disclosure or for an open materials test. The absence of explanatory text in this Schedule foreshadows precisely those potential challenges, but again, the Schedule contains no litigation record to show whether such arguments were tried and how courts responded.

Evidence preservation and necessity for administrative record. If litigation arises, the enforceable record will be the parent instrument and the administrative determination or intelligence assessment underpinning the listing. Practitioners should note that the Schedule does not reproduce that record, so a litigator seeking relief must subpoena or request the administrative record or seek discovery through public record processes.

Aliases and transliteration traps. The Schedule contains extensive aliases, multiple transliterations and alternate name forms. Example: Part 7’s “Usama Bin Muhammad Bin Awad Bin Ladin (aka Usama bin Laden; aka Osama bin Laden aka Abu Abdallah Abd Al-Hakim).” Part 8 is replete with alternate romanisations and kunyas. Screening systems that rely on exact-string matching will both miss genuine matches (false negatives) when names are spelled differently, and will generate false positives when common elements overlap. The multiplicity of aliases increases both over‑ and under‑inclusion risk.

Duplicate and similar corporate names. The AL‑BARAKAAT/BARAKAAT and AL-TAQWA families in Part 8 show many near-identical trading names, subsidiaries and branches across jurisdictions. A compliance team that sees a match for “AL-BARAKAAT” must distinguish between distinct legal persons with similar trading names. Without corporate identifiers (eg registration numbers), there is a real risk of misattributing liability or freezing legitimate firms.

Entries with diplomatic styling. Parts 2-5 list individuals attached to “Taliban ‘Embassy’ Islamabad” and consulates, with titles such as “Ambassador Extraordinary & Plenipotentiary” and “Consul General.” Practitioners must not assume that the presence of a diplomatic title absolves or negates the consequences that rest of the parent instrument imposes. The Schedule does not indicate how diplomatic status is to be treated. That ambivalence is a practical gotcha when operational staff attempt to reconcile diplomatic functions with sanctions‑related prohibitions.

Incomplete biographical data. Some entries provide passport numbers, DOBs and addresses (eg DARKAZANLI, Mamoun), whereas many Taliban entries provide only names and positions. The unevenness of identifiers means matching confidence will vary across entries. Less-detailed entries produce higher operational friction because more manual validation is needed.

Legacy names and removed nationals. The Schedule notes for Usama bin Laden that Saudi citizenship is “withdrawn, now officially an Afghan national.” Such status statements may be out of date or contested. Compliance personnel must avoid treating the Schedule’s parenthetical narrative as legally conclusive about nationality or legal status without cross-checking more authoritative government records.

Cross‑listing and foreign reliance risk. The explicit reference to US EO 13224 suggests cross-listing, which creates the following trap: a firm relying solely on domestic lists could miss foreign-designated subsidiary entities or alternate aliases present only on foreign lists. Conversely, foreign list alignment may produce capture of domestic firms that are legitimately operating under foreign licences elsewhere. Always cross-verify.

Treat the Schedule as an authoritative identification source that must be validated against the parent instrument and the administering agency’s consolidated list. Because the Schedule in isolation lacks operative provisions and amendment history, the first compliance step is statutory reconciliation.

1. Confirm legal force and the operative parent instrument. Obtain the parent Act, regulation or notice that incorporates this Schedule and read the operative offences, prohibitions, licensing regimes and defences. Do not act solely on the Schedule text. Record the instrument number, gazette reference and the date of the current consolidated list.

2. Maintain up‑to‑date master lists. Subscribe to the official consolidated list maintained by the administering agency and to relevant foreign lists referenced in the Schedule (eg US OFAC list for EO 13224 items). Implement automated daily or real‑time updates to your screening databases to ensure you are comparing against the most current authoritative set rather than the static Schedule text.

3. Implement layered screening logic. Use multi-field matching, not exact-string matching. Where available, match on combinations of name + DOB + passport number + address + role. Prioritise high-confidence matches (eg matches including passport numbers or multiple identical identifiers) for immediate escalation.

4. Robust false‑positive resolution workflow. Build a documented escalation path for matches that includes: (a) human review by a trained investigator, (b) comparison with internal KYC records, (c) targeted requests for identity verification documents, and (d) legal review before any adverse action is taken (eg freezing assets, terminating contracts). Keep auditable logs of decisions and the sources consulted.

5. Sensitive handling of diplomatic and consular entries. For listed individuals with diplomatic styling, obtain legal advice on the intersection between domestic prohibition regimes and international immunities. Do not assume immunity; but also do not assume sanctions override diplomatic conventions without checking the parent instrument and seeking legal clearance.

6. Records and reporting. Maintain transaction logs, screening output, escalation notes and legal advice. If the parent instrument requires reporting to an enforcement agency (eg suspicious activity reports or notifications on matches with listed persons), ensure timely filing within statutory windows. Preserve a complete audit trail to show reliance on the consolidated list and the decision-making process.