Australia New Zealand Food Standards Code – Schedule 24 – Restricted plants and fungi

The Schedule rests on a few discrete legal and technical concepts expressed directly in the text.

• Standard under FSANZ Act: The instrument is a "standard" under the Food Standards Australia New Zealand Act 1991 (Cth). That status places the Schedule inside the Australia New Zealand Food Standards Code framework that the Act creates (Note 1). The Schedule therefore functions as a component of the Code rather than an independent statute.

• Definition linkage: The Schedule is expressly operative for "paragraph (a) of the definition of restricted plant or fungus in section 1.1.2,3" (S24,2). The definition in 1.1.2,3 is not reproduced in the Schedule; the Schedule provides the species that are to be read into that definition. Therefore, the Schedule’s effect is contextual: a plant appears on the Schedule so that the Code will treat it as a restricted plant or fungus under that definition.

• Referential enforcement points: The Schedule points to the operational provisions that govern restricted plants and fungi: paragraphs 1.1.1,10(5)(a) and 1.1.1,10(6)(e) and Standard 1.4.4. Those provisions, rather than Schedule 24 itself, set out the regulatory controls (for example, whether sale, use, or labelling are constrained). The Schedule is the roster; the other parts of the Code are the rules.

• Species + toxicant pairs: The Schedule lists species (scientific names), common names where supplied, and associated "natural toxicant(s)". Examples: Artemisia absinthium (Common wormwood) , thujone, santonin; Cinchona spp. , quinine; Sassafras albidum , safrole (S24,2 table). The inclusion of toxicants alongside species signals that the regulatory classification of "restricted" links to identified intrinsic toxicological hazards rather than, for example, purely agricultural or ecological concerns.

• Cross-references and synonyms: The Schedule uses cross-references for synonymous or alternate names (for example, Chrysanthemum parthenium (see Tanacetum parthenium); Sassafras officinale (see Sassafras albidum); Tanacetum balsamita (see Chrysanthemum balsamita)) which affects how one determines whether a material encountered under an alternate name appears on the Schedule (S24,2 table).

• Geographic operation: The Notes clarify that the Code provisions apply in New Zealand through adoption or incorporation under the Food Act 2014 (NZ). That means the Schedule travels into NZ regulatory space by national implementation rather than directly as an Australian Act (Note 2).

• Administrative chronology: The Schedule includes commencement information and amendment metadata. It was published as part of Amendment 154 (Gazette No. FSC96, 10 April 2015) and commenced on the dates specified in the Gazette under s 92 of the FSANZ Act; compilation details and later minor amendments are recorded (About this compilation; Amendment History).

Those concepts define how to read the Schedule: it is an enumerated, toxicant-tagged list that plugs into other provisions of the Code which impose the regulatory effects. The Schedule does not, on its face, set limits, exemptions, or enforcement mechanisms; those live in the referenced parts of the Code and in national implementation legislation.

Schedule 24 affects any person or entity whose food product, ingredient, formulation, manufacturing process, supply chain, or import/export documentation involves any of the listed species or their derivatives. Because the Schedule is part of the Australia New Zealand Food Standards Code (Note 1), its practical subjects include:

• Food businesses and manufacturers: companies and individuals who formulate, process or market foods in Australia and New Zealand must check whether plant-derived ingredients used or proposed for use are listed in Schedule 24. If the ingredient is one of the Schedule entries, the ingredient becomes a "restricted plant or fungus" for Code purposes (S24,2). This affects product formulation choices, sourcing decisions, labelling, and possibly the ability to sell or use the ingredient.

• Importers and exporters of food ingredients: the Schedule operates by identifying species treated as restricted under the Code. An importer supplying botanical raw materials to Australia or New Zealand will need to confirm whether those materials are on the Schedule to determine compliance with the referenced Code provisions and national implementing legislation (S24,2; Note 2).

• Food testing and analytical laboratories: because the Schedule links species to specific natural toxicants (for example thujone, quinine, poulegone, safrole), laboratories that test botanical ingredients or finished products will need to know which analytes are relevant for compliance assessment where regulators or businesses are checking for restricted materials.

• Regulators and compliance officers: enforcement and compliance agencies that apply the Code or the Food Act 2014 (NZ) will use Schedule 24 as the authoritative list when deciding whether a plant or fungus is a restricted item under the Code (Note 2). The Schedule helps identify items that the Code’s other provisions regulate.

• Retailers, wholesalers and food service: any downstream participant that sells or serves foods containing botanical extracts must be aware that the presence of Schedule-listed species may trigger obligations under other Code provisions and under national laws, including labelling or sale restrictions.

• Product designers and R&D teams: formulators and product developers considering botanical additives, flavourings or herbal components must screen against Schedule 24 early in product development, because inclusion of a listed species will change regulatory compliance pathways.

• Supply chain managers and certifiers: due to synonym entries in the Schedule (see entries that cross-reference other botanical names), supply chain traceability and accurate botanical identification become critical to determine if a material is captured by the Schedule.

Geographically, the Schedule applies to Australia and, through incorporation or adoption, to New Zealand (Note 2). The Schedule’s application depends on the national legislative mechanisms that adopt the Code. The text supplied does not enumerate exemptions by class of actor or activity; instead, it identifies species so that the provisions listed elsewhere in the Code can determine the exact regulatory consequences for each actor. Practitioners should therefore read S24,2 alongside the referenced paragraphs and Standard 1.4.4 to determine the on-the-ground effects for a particular business model or transaction.

The Schedule itself does not set out duties or rights in prescriptive form; instead it identifies which species fall within the Code’s definition of "restricted plant or fungus" so that duties and rights established elsewhere in the Code apply. From the Schedule and its cross-references the following operational duties and rights emerge as matters to be determined and observed by regulated parties.

• Duty to identify covered species in products and supply chains: Because the Schedule is the authoritative list for paragraph (a) of the definition of "restricted plant or fungus" (S24,2), businesses have the implicit duty to verify whether any botanical ingredient they use or procure is a Schedule entry. The Schedule itself lists scientific names and common names; cross-references indicate synonyms (for example, Chrysanthemum parthenium see Tanacetum parthenium). Accurate botanical identification is therefore a necessary initial duty.

• Duty to read and apply the Code provisions referenced: The Schedule links the list to paragraphs 1.1.1,10(5)(a) and (6)(e) and Standard 1.4.4. The regulatory duties (for example bans, permitted uses, labelling obligations, quantity limits, production or processing requirements) will be set in those provisions and become applicable to businesses handling Schedule-listed species. The Schedule shifts the determination of duties to the referenced Code provisions by design.

• Duty to account for toxicants identified: The Schedule pairs species with natural toxicants (S24,2 table). Where regulatory controls in the referenced provisions are responsive to the presence or concentration of particular toxicants, a duty follows to monitor, test and control levels of those named toxicants in food products. The Schedule therefore informs the scope of analytical and control duties that may be required under the Code.

• Right to determine applicability by reference: Businesses have the right, under the Code’s structure, to determine whether their materials are captured by referring to Schedule 24 and the definition in section 1.1.2,3. The Schedule equips regulated parties to make that threshold assessment themselves, though regulatory obligations may attach once the threshold is met.

• Duty to keep records and traceability: While the Schedule does not explicitly impose record-keeping requirements, the mechanism by which it operates (a fixed list used to trigger regulatory constraints) creates a practical duty for firms to maintain traceability and documentation adequate to demonstrate whether products or ingredients include Schedule-listed species. This is a predictable compliance mechanism given the Schedule’s role as a definitional source.

• Rights and discretion via national implementation: The Schedule notes that Code provisions that apply in New Zealand are incorporated or adopted under the Food Act 2014 (NZ) (Note 2). National laws determine enforcement discretion and procedural rights (for example inspection powers, appeal rights, or licence conditions). The Schedule does not itself modify those national procedural rights but determines which items are covered by national rules.

• Duty to monitor amendments and commencement dates: The Schedule’s Amendment History, and the recorded commencement date (S24,1), create an ongoing duty for market participants to keep their compliance framework updated. The Schedule’s compilation notes indicate that amendments are recorded and, where relevant, may be uncommenced or shaded in future compilations. Businesses therefore have the duty to check the current compilation and Gazette notices to confirm whether an item is newly added, amended or subject to other transitional arrangements.

In sum, Schedule 24 confers no standalone rights or obligations inside its text; rather it functions as the list that transforms certain botanical species into regulated objects under the Code. Duties and rights therefore arise from the interaction of Schedule 24 with the other Code provisions cited and national implementing legislation (S24,2; Note 1; Note 2).

Schedule 24 does not itself prescribe penalties or enforcement mechanisms. Instead, it is a component of the Australia New Zealand Food Standards Code and is made under the Food Standards Australia New Zealand Act 1991 (Cth) (Note 1), and the application of Code provisions in New Zealand is through the Food Act 2014 (NZ) (Note 2). Consequently:

• Enforcement and penalties are provided by other provisions: The text supplied refers to "paragraphs 1.1.1,10(5)(a) and (6)(e) and Standard 1.4.4" as the regulatory loci that "regulate" restricted plants and fungi (S24,2). Any enforcement powers, sanctions, penalty levels, infringement notices, compliance notices, or criminal penalties will be found in those parts of the Code, in the FSANZ Act, or in national implementation legislation rather than in Schedule 24.

• Regulation by national authorities: Because the Schedule is a Code standard under the FSANZ Act (Note 1) and because the Code is applied in New Zealand by incorporation/adoption under the Food Act 2014 (NZ) (Note 2), enforcement rests with the statutory agencies and officers designated by those Acts and by national regulations. The Schedule is the identification tool; enforcement is undertaken under the national frameworks that give the Code effect.

• Practical enforcement triggers: In practice, enforcement action will be triggered when a product or practice falls within the definition of "restricted plant or fungus" by virtue of the Schedule. That trigger may lead to inspection, testing for the named natural toxicants in the Schedule, seizure, removal from sale, recall, or other regulatory action, depending on the powers conferred in the Code and implementing laws (the Schedule itself does not state which sanctions apply).

• Responsibility to check commencement and amendment: Compliance and enforcement can turn on whether a given entry was in force at a particular date. The Schedule includes commencement information (S24,1) and an Amendment History (About this compilation). Parties facing potential enforcement should confirm the version of the Schedule in force at the relevant time because additions and cross-reference changes have been made (for example Amendment No. 168 altering a cross-reference, as recorded in the Amendment History).

• No bespoke enforcement discretions recorded in the Schedule: The Schedule does not set out any bespoke enforcement discretion or administrative tolerances. Any such discretionary arrangements would be located in the broader Code or in the agencies’ enforcement policies.

For a practical compliance posture, regulated parties must consult the specific Code provisions cited and the national legislation that applies in their jurisdiction to identify the precise penalties and enforcement instruments that regulators may use in relation to Schedule-listed species.

Schedule 24 is explicitly a part of the Australia New Zealand Food Standards Code and therefore interacts with multiple legislative instruments through incorporation, cross-reference and application.

• FSANZ Act as parent instrument: The Schedule is a "standard" made under the Food Standards Australia New Zealand Act 1991 (Cth) (Note 1). That Act establishes FSANZ’s power to make standards and the procedural and legal framework for those standards to take effect. Consequently, Schedule 24’s legal force in Australia derives from its status under the FSANZ Act and from the mechanisms that the Act prescribes for making and commencing standards (see S24,1 and Note 1).

• Code cross-references: The Schedule is intended to be read with other Code provisions that define and regulate restricted plants and fungi. The Schedule feeds into paragraph (a) of the definition of "restricted plant or fungus" in section 1.1.2,3 (S24,2). The regulatory treatments are then supplied by paragraphs 1.1.1,10(5)(a) and (6)(e) and Standard 1.4.4. The Schedule therefore functions as a definitional annex: it supplies the roster of species that the named Code provisions address.

• National application in New Zealand: Note 2 states that the provisions of the Code that apply in New Zealand are incorporated in, or adopted under, the Food Act 2014 (NZ). That means Schedule 24 is given effect in New Zealand through domestic legislative mechanisms. The practical consequence is that Schedule 24’s list is not self-executing in New Zealand; rather it is effective to the extent the Food Act or subordinate instruments adopt the Code and its standards.

• Interaction with administrative processes: The Schedule’s commencement and amendment history are governed by section 92 of the FSANZ Act, which the Schedule itself references in relation to notices published in the Gazette (S24,1 and About this compilation). That legislative cross-link determines how and when changes to the Schedule take legal effect and therefore how it interacts with commercial processes that depend on a stable regulatory environment.

• Relationship to labelling, safety, import, and sale provisions in the Code: Although Schedule 24 does not itself prescribe labelling, tolerances, or prohibitions, it identifies the species that other parts of the Code will treat as "restricted". Those other Code provisions often control sale, use, labelling, allowable concentrations, or processing requirements. Therefore Schedule 24 interacts functionally with the Code’s substantive legal controls on food safety, composition and labelling through the definitional linkage.

• No direct interaction with agricultural, invasive species or biosecurity law in the text: The Schedule’s content is botanical and toxicological. The supplied text does not expressly connect Schedule 24 to biosecurity, agricultural, or plant health statutes. That absence in the Schedule does not prevent those laws from being relevant in practice, but any interactions with such non-food statutes would need to be traced to those statutes and are not specified in the Schedule text.

• Administrative compilation and Federal Register: The Schedule records compilation information and amendment registration details (About this compilation and Amendment History). That interacts with the Federal Register of Legislation and the Gazettes for the purposes of legal certainty about which version of the Schedule is in force when.

To determine concrete cross-law effects for a given product, practitioners must read Schedule 24 together with section 1.1.2,3, paragraphs 1.1.1,10(5)(a) and (6)(e), Standard 1.4.4, the FSANZ Act, and the relevant national implementation legislation (for New Zealand, the Food Act 2014). The Schedule is a node in a network of legal texts rather than a stand-alone regulatory instrument.

The Schedule includes a recorded Amendment History and compilation metadata in the supplied text. The key administrative facts in the text are:

• Original publication and amendment pathway: Schedule 24 was published in the Food Standards Gazette No. FSC96 on 10 April 2015 as part of Amendment 154 (citation in the text: F2015L00438 - 1 April 2015). That publication introduced the Schedule into the Code (About this compilation).

• Commencement: S24,1 records that "This Standard commences on 1 March 2016, being the date specified as the commencement date in notices in the Gazette and the New Zealand Gazette under section 92 of the Food Standards Australia New Zealand Act 1991 (Cth)." The Schedule therefore points to Gazette notices and s 92 of the FSANZ Act as the legal mechanism fixing commencement dates (S24,1 and the Note in S24,1).

• Compilation status and date: The text identifies the document as "compilation No. 1 of Schedule 24 as in force on 13 April 2017 (up to Amendment No. 168)." It states that it includes any commenced amendment affecting the compilation to that date and that it was prepared by Food Standards Australia New Zealand on 13 April 2017 (About this compilation).

• Subsequent amendments recorded: The Amendment History table in the Schedule shows at least one subsequent amendment entry: "Note 1 to Std" was amended by Amendment No. 168, FRL registration F2017L00414, Gazette FSC110 on 13 April 2017, with commencement 13 April 2017 described as "am" (amended) and described as a cross-reference amendment. The table headings explain abbreviations (ad = added, am = amended, etc.) and indicate that amendments are made under s 92 of the FSANZ Act unless otherwise indicated.

• Process and visibility of uncommenced amendments: The Schedule documentation explains that uncommenced amendments or provisions ceasing to have effect may be reflected in compilations as shaded boxed text with the relevant commencement or cessation date, and that such amendments will appear in a compilation registered on the Federal Register of Legislation and the Amendment History once the date is passed. This is administrative guidance for readers regarding how to track future changes (Uncommenced amendments or provisions ceasing to have effect).

• Scope of tracked changes: The Amendment History table provides a mechanism to record which sections were affected, the Amendment No., the Federal Register of Legislation registration and Gazette references, commencement/cessation dates, and a short description of how the Schedule was affected.

For practitioners, the key procedural point in the Amendment History is that the Schedule is subject to amendment through FSANZ processes and Gazette notices under s 92 of the FSANZ Act, and that the compilation must be checked for the current text. The Schedule’s own metadata confirms that practitioners should rely on the Federal Register of Legislation and Gazette entries to determine the operative version at a given time.

The Schedule’s text does not record any litigation history. There are no cases, judicial interpretations, appeals, or tribunal decisions cited or summarised in the Schedule as provided. The Schedule is primarily an administrative list and amendment record; it does not incorporate case law or mention any legal challenges in the supplied material.

In practice, disputes about the Schedule’s application could arise,for example, on botanical identification, synonymy, interpretation of the definition in section 1.1.2,3, the scope of the referenced Code provisions, or the interaction with national laws,but none of those disputes or decisions are recorded in this Schedule text. To establish a litigation history a practitioner would need to search judicial records, tribunal decisions and administrative appeal records outside this Schedule compilation.

The absence of litigation references in the Schedule means that any legal arguments about the meaning, scope or application of Schedule 24 would need to be constructed from the Code’s wording, the FSANZ Act, administrative materials (including Gazette notices and FSANZ decisions), and any external case law that interprets the relevant Code provisions. Those materials are not part of the Schedule text provided, so the Schedule itself does not supply precedent or case-based interpretive guidance.

This Schedule contains several features that can cause practical compliance traps if not read and applied carefully.

• The Schedule is definitional, not normative: The Schedule lists species and toxicants but does not set out the regulatory outcomes (for example, whether sale is prohibited, limited, or permitted subject to conditions). You must consult the other Code provisions cited (paragraphs 1.1.1,10(5)(a) and (6)(e), and Standard 1.4.4) to discover what legal constraints apply once a species is "restricted" (S24,2). Assuming the Schedule itself contains prohibitions or exemptions is a mistake.

• Synonym and cross-reference entries: The Schedule includes entries that refer you to alternate names (for example "Chrysanthemum parthenium (see Tanacetum parthenium)"; "Sassafras officinale (see Sassafras albidum)"; "Tanacetum balsamita (see Chrysanthemum balsamita)"). Practitioners can be misled if they check only common names or a single botanical name; a substance labelled under a synonym may still be captured by Schedule 24. Accurate botanical identification and checking for synonyms is therefore essential (S24,2 table).

• Mixed or incomplete table rows: The table contains rows where common names or toxicant entries appear uneven. For example, the row headed "Hedeoma pulegioides oil" lists "American pennyroyal" and "White snakeroot oil" in the common name column, but the toxicant cell is "Pulegone" aligned with American pennyroyal and blank for "White snakeroot oil". This layout requires careful reading to determine which toxicant is linked to which named item; do not assume uniform column alignment in reproductions of the table (S24,2 table).

• No fungi actually listed in this compilation: Despite the title "Restricted plants and fungi", the entries in S24,2 as supplied are botanical (plants). The Schedule is intended to list both plants and fungi where appropriate, but the current compilation contains only plant entries. Do not assume fungi are necessarily excluded forever; check updated compilations for any fungi entries (S24,2).

• Code-level dependency: Because the Schedule operates by reference to the Code’s definition and other provisions, compliance risk arises if you rely on the Schedule without reading the definition (section 1.1.2,3) and the regulatory paragraphs cited (1.1.1,10(5)(a), 1.1.1,10(6)(e), Standard 1.4.4). The Schedule is a pointer; the legal obligations you face are in the referenced materials (S24,2).

• Jurisdictional differences and timing: The Schedule applies in Australia as a standard under the FSANZ Act and is adopted or incorporated for application in New Zealand under the Food Act 2014 (NZ) (Note 2). The timing of adoption or the precise mechanics of incorporation in New Zealand may introduce differences in enforcement or transitional arrangements; check the domestic implementing instruments and Gazette notices for effective dates (Note 2; S24,1).

• Amendment tracking: Amendments are made under s 92 of the FSANZ Act and may have staggered commencement dates; compilations note uncommenced amendments may be shaded until commencement. If you rely on a printed or downloaded copy, verify it is the current compilation (About this compilation; Amendment History).

• Toxicant linkages do not equate to quantified limits: The Schedule identifies natural toxicants associated with listed species, e.g., "safrole", "thujone", "quinine". The presence of a toxicant name in the Schedule is not itself a quantitative limit or analytical threshold. To know if a particular concentration is permissible, and whether processing reduces risk to acceptable levels, you must consult the other parts of the Code and any relevant guidance, not the Schedule alone (S24,2).

• Labelling and ingredient declaration confusion: Because the Schedule lists botanical names and common names, but trade documentation or ingredient lists may use trade names, extracts, oils or derivatives, it can be challenging to map those commercial descriptors back to Schedule entries. The Schedule’s reliance on scientific names suggests a duty to match commercial ingredient terms to botanical nomenclature.

Being alert to these "gotchas",the Schedule’s definitional role, synonym cross-references, table layout issues, the absence of fungi in this compilation, jurisdictional application and amendment timing,reduces the risk of misclassification and regulatory non-compliance.

Compliance requires treating Schedule 24 as an authoritative identification tool for species that, once identified, are regulated under other provisions of the Code. The Schedule itself provides the list of species and the main natural toxicants; the practical compliance steps below follow from how the Schedule functions in the Code (S24,2; S24,1; Notes).

1. Confirm botanical identity and synonyms

• Map every botanical ingredient, extract, essential oil or botanical-derived input in the product to the scientific names used in Schedule 24. Pay particular attention to the cross-reference notes in the Schedule (for example "see Tanacetum parthenium" or "see Chrysanthemum balsamita") to capture synonyms and historical names (S24,2). Where trade or supplier names differ from scientific nomenclature, require supplier declarations and technical data sheets to confirm botanical species.

2. Consult the Code’s definition and the regulating provisions

• After determining whether a species appears in S24,2, read paragraph (a) of the definition of "restricted plant or fungus" at section 1.1.2,3 and the Code provisions that the Schedule references (paragraphs 1.1.1,10(5)(a) and 1.1.1,10(6)(e) and Standard 1.4.4) to identify the specific regulatory obligations, permitted uses, limits, labelling requirements, or prohibitions that apply. The Schedule is a trigger; the referenced text supplies the substantive duties (S24,2).

3. Check national implementing legislation and commencement dates

• For Australia, rely on the FSANZ Act and the Code as in force (Note 1). For New Zealand consult the Food Act 2014 and any domestic instruments that incorporate or adopt the Code (Note 2). Confirm the operative version and commencement dates via the Gazette notices and the Federal Register of Legislation; the Schedule’s own commencement note and compilation details establish that these administrative steps are material (S24,1; About this compilation).

4. Assess analytical testing needs against named toxicants

• The Schedule pairs species with named natural toxicants (for example thujone, santonin, pulegone, safrole, quinine). Determine whether the referenced Code provisions require chemical analysis or limits for those toxicants. Where required, implement validated testing regimes to measure those analytes at appropriate points in supply and production. Use data from suppliers and testing laboratories to demonstrate compliance.

5. Update procurement and supplier contracts

• Require suppliers to certify that botanical ingredients are not Schedule-listed or, if they are, to provide evidence of compliance with any applicable Code requirements. Include representations and warranties, and demand traceability documentation to demonstrate the botanical identity and processing history.

6. Labelling, formulation and product decisions

• Based on the obligations found in the referenced Code clauses, adjust product formulations, labelling and marketing claims. If the legal outcome in the Code is a restriction on sale or use, either remove the ingredient from formulations for the applicable jurisdictions or obtain the necessary approvals or authorisations specified in the Code (the Schedule itself does not state the available regulatory reliefs; you must read the controlling Code provisions).

7. Maintain version control and monitor amendments

• The Schedule is subject to amendment under s 92 of the FSANZ Act and may be updated (About this compilation; Amendment History). Implement a regulatory monitoring process to check the Federal Register of Legislation and Gazette notices for additions, name changes, or cross-reference amendments (for example Amendment No. 168 recorded in the compilation). Treat uncommenced amendments, transitional arrangements and commencement dates as part of compliance planning.

8. Documentation and record-keeping

• Maintain auditable records that show due diligence in identifying botanical species against Schedule 24, testing results for the named toxicants where required, supplier declarations, formulations and labelling decisions. Although the Schedule does not specify record-keeping duties, traceability is necessary to demonstrate whether Schedule-listed species are present and to show corrective action if a product is suspected of non-compliance.

9. Seek specialist advice where identification is uncertain

• Where botanical identification is ambiguous,owing to extracts, multi-ingredient botanicals, or trade names,engage botanists, qualified analysts or regulatory counsel to map the material to Schedule entries. The Schedule’s reliance on scientific names and cross-reference notes makes expert input cost-effective when the classification decision affects market access.

10. Prepare for jurisdictional variations in enforcement

• Because the Code is applied differently by jurisdiction (Australia via FSANZ mechanisms and New Zealand via the Food Act 2014), confirm local regulators’ enforcement positions and any administrative guidance that clarifies how the Schedule is applied. The Schedule itself signals the jurisdictional sweep but not enforcement priorities.

Implementing these steps turns the Schedule from a static list into a practical compliance workflow: identify, map, test where required, document, and continuously monitor the Schedule’s status and the controlling Code provisions.