Industry Research and Development (Industry 4.0 Testlabs for Australia Program) Instrument 2018

This instrument turns on a small set of legal concepts and administrative choices. The concepts below are taken from, and only from, the instrument’s text.

• Prescribed program: The instrument “prescribes” a program for the purposes of the Act, specifically for the purposes of subsection 33(1) (s 5). The prescribed program is the “Industry 4.0 Testlabs for Australia” program and is described in the program table (s 5, Column 2).
• Participating universities: The instrument defines a closed list of named universities that are “participating universities” for the program (s 4). The list is explicit and categorical: Swinburne University of Technology; The University of Queensland; The University of Western Australia; University of South Australia; University of Technology, Sydney; University of Tasmania.
• Funding to establish facilities: The program description states it “provides funding to establish Industry 4.0 Testlabs at each of the participating universities” (s 5, Column 2). The instrument records that funding is to establish infrastructure or facilities at those named universities; it does not record funding quantum, timetable, or contracting arrangements.
• SME focus: The program description identifies small and medium business enterprises (SMEs) as the beneficiaries of innovation support and skills-building (s 5, Column 2). The text frames the SMEs as recipients of access to testlabs and as targets for skills assistance.
• Priority industry growth sectors: The program description links the SME support to “priority industry growth sectors” (s 5, Column 2). The instrument does not define what those sectors are; it asserts that the program will focus on SMEs in such sectors.
• Constitutional basis: For the purposes of subsection 33(3) of the Act, the instrument specifies the Commonwealth’s corporations power under paragraph 51(xx) of the Constitution (s 6). The instrument thereby connects the program to the constitutional head of power that governs laws about trading or financial corporations.
• Eligibility criterion: The instrument prescribes, for the purposes of subsection 33(4) of the Act, that applicants must be trading or financial corporations to which paragraph 51(xx) applies (s 7). That is a categorical eligibility requirement in the instrument.

Operationally, these concepts establish a narrow framework: the Commonwealth, acting under s 33 of the Act, has prescribed a named program that funds testlabs established at six specified universities, with stated aims of SME innovation support and SME skill-building; the instrument confines the program to use of the corporations power and requires applicants to be trading or financial corporations. The instrument does not supply the procedural scaffolding that will implement those aims, such as funding mechanisms, application and selection rules, reporting obligations, or duration.

The instrument creates a small set of directly affected parties and a broader set of intended beneficiaries as described in the instrument.

Directly named or bound parties

• Participating universities (s 4): Six universities are explicitly named as “participating universities”. They are identified as the physical locations at which the Industry 4.0 Testlabs are to be established (s 5). The naming is definitive: only these institutions are described as participating universities in the instrument text.
• Applicants , trading or financial corporations (s 7): The instrument prescribes an eligibility criterion stating “applicants must be trading or financial corporations to which paragraph 51(xx) of the Constitution applies” (s 7). That limits who can apply under the program, at least for the purposes referenced in the Act subsections the instrument addresses.

Intended beneficiaries

• Small and medium enterprises (SMEs) (s 5): The program description identifies SMEs as the recipients of innovation support and skills-building delivered through access to the Testlabs. SMEs are described as the target group in the program’s stated purpose (s 5, Column 2).

Other affected actors and institutions

• Commonwealth agencies and decision-makers: The instrument is made under s 33 of the Act (s 3) and prescribes the program for purposes of subsections 33(1), 33(3) and 33(4) of the Act (ss 5, 6, 7). That situates decision rights and administrative duties (application assessment, funding allocation) within the institutional architecture of the Act, though the instrument does not itself set those processes.
• Entities outside the corporate form: The eligibility criterion (s 7) excludes entities that are not trading or financial corporations as applicants for the program, at least to the extent the Act relies on the instrument’s prescription to define eligibility. That means sole traders, unincorporated partnerships, not-for-profits that are not trading corporations, and individuals are not covered by this eligibility statement.
• SMEs that are not corporate trading or financial corporations: The instrument’s SME focus (s 5) is stated as an objective, but the eligibility criterion (s 7) means that the means by which SMEs access the program (for example, through corporate applicants) will be shaped by that requirement. The instrument does not specify whether SMEs that are unincorporated or otherwise outside paragraph 51(xx) can nonetheless benefit indirectly through corporate applicants.

How parties are affected

• Universities: Named universities are designated sites for infrastructure establishment. The instrument states funding will be provided to “establish Industry 4.0 Testlabs at each of the participating universities” (s 5). That creates a forward-facing expectation that the participating universities will host facilities funded under the program.
• Corporations (applicants): Corporations that qualify under paragraph 51(xx) are the class that may apply under the eligibility criterion (s 7). The instrument does not state application mechanics, but the legal framing indicates program access is mediated through corporations.
• SMEs (beneficiaries): SMEs are the target audience for use of the Testlabs and for skills-building described in the program purpose (s 5), but the instrument does not create a direct statutory entitlement for SMEs; access and modalities will depend on the administrative implementation under the Act.

Practical note drawn from the instrument: the list of participating universities is concentrated and fixed in the instrument; the instrument therefore channels the program’s on-the-ground activity to those six locations (s 4; s 5). The eligibility rule for applicants is confined to trading or financial corporations (s 7), so entities seeking to participate must evaluate whether they meet that constitutional/corporate test.

The instrument itself creates relatively few operative duties and rights. It is a prescription of a program, a specification of authority, a list of participating universities, and an eligibility requirement. The substantive, operational duties and rights that will govern grant-making, contractual obligations, reporting, or sanctions are not contained in the instrument; they will sit in the Act and subordinate administrative instruments or program guidelines. Below are the duties and rights that the instrument does create or imply, strictly as the text states.

Express or direct duties and rights in the instrument

• Duty to recognise the prescribed program under the Act: For the purposes of subsection 33(1) of the Act, the instrument prescribes the “Industry 4.0 Testlabs for Australia” program (s 5). That legal act of prescription matters for the operation of s 33 of the Act; the instrument therefore alters the legal landscape by formally designating this program under the Act. The practical duty this creates arises when agencies exercise powers under the referenced Act provisions, because the program is now a prescribed program for those purposes. The instrument itself does not create specific grantee duties.
• Eligibility limitation on applicants: The instrument prescribes an eligibility criterion , that applicants must be trading or financial corporations to which paragraph 51(xx) of the Constitution applies (s 7). That operates as a legal limitation, for the purposes of the referenced subsection of the Act, on who can be treated as eligible under the program. Entities that do not meet that description will be outside the eligibility class as set out in this instrument.
• Recognition of participating universities: The instrument sets out that testlabs are to be established “at each of the participating universities” (s 5) and defines the participating universities by name (s 4). The universities so named are thereby the geographically specified locations for the funded infrastructure.

Implied rights and administrative consequences (as framed by the instrument)

• Right to funding under the program: The program description states it “provides funding to establish Industry 4.0 Testlabs” (s 5). The instrument does not itself create a statutory entitlement to funding for any particular applicant, but prescribing the program under the Act enables whatever grant-making powers the Act authorises to be exercised in relation to this program. That is a procedural consequence of prescription rather than a freestanding right created by this instrument.
• Right of SMEs to access facilities: The program’s purpose statement says participating universities will “provide innovation support for SMEs … by providing access to Industry 4.0 Testlabs” and “assist SMEs with building the skills required” (s 5). Those are programmatic objectives stated by the instrument; they describe intended uses of the Testlabs rather than precise legal rights of SMEs enforceable under the instrument’s text.

What the instrument does not do (not present in the text)

• The instrument does not confer specific contractual or statutory duties on participating universities (for example, operating, maintenance, access protocols, or reporting). It names them and locates the funded testlabs there, but operational duties are not specified in the instrument.
• The instrument does not set funding amounts, allocation criteria, application processes, selection procedures, reporting obligations, audit powers, or penalties for non-compliance.
• The instrument does not create express enforcement mechanisms or sanctions.

Because the instrument is narrow, the practical duties and rights that will govern behaviour , for example, how a corporate applicant secures funding, how the grant is contracted, or how SMEs gain access to testlab facilities , will depend on the Act and on administrative instruments, grant guidelines or contracts that implement the program. The instrument performs a legal classification function (it prescribes the program) and sets definitional anchors (participating universities; applicants must be trading or financial corporations) that will materially constrain implementation choices by agencies when exercising powers under the Act.

The instrument contains no express penalty provisions, enforcement mechanisms, or sanctioning regime. Its content is limited to prescribing the program, naming participating universities, specifying commencement, stating its authority, identifying the constitutional head of power relied on, and prescribing an eligibility criterion for applicants (ss 1-7). None of those sections sets out offences, administrative sanctions, pecuniary penalties, compliance obligations with stated remedies, or inspectors’ powers.

What the instrument does tell us about enforcement context

• The instrument is made under s 33 of the Industry Research and Development Act 1986 (s 3). Any enforcement, penalty, or compliance regime that applies to actions taken under the Act in the exercise of powers conferred by s 33 would be found in the Act itself or in other authorised subordinate instruments, not in this instrument. The instrument does not reproduce or modify any such enforcement provisions.
• The instrument prescribes an eligibility requirement that applicants must be trading or financial corporations (s 7). The instrument does not state how that eligibility will be verified, who reviews eligibility, what evidence will be required, or what happens if an applicant is later found not to meet that criterion.

Consequences for practitioners

• If enforcement provisions are relevant (for example, false statements in applications, misapplication of grant funds, or breach of grant conditions), those will be enforced under the Act or any relevant contracts or guidelines established under the Act’s powers. The instrument itself does not supply those enforcement rules.
• Administrative discretion: Because the instrument leaves procedural matters (applications, assessments, contracting, reporting, and sanctions) unspecified, significant implementation discretion will fall to the administering agency under the Act. That discretion is not constrained by this instrument beyond the declared program description and the eligibility criterion.

Practical steps for assessing enforcement exposure

• Consult the Industry Research and Development Act 1986 to identify statutory offences, offences in associated criminal or financial penalties federal legislation, and administrative sanctioning powers that apply to programs prescribed under s 33.
• Obtain the program’s implementing guidelines, grant agreements, or contract documents to identify the operative compliance and enforcement terms that an applicant or grantee will face in practice.
• For eligibility disputes, determine the evidentiary standard the administering agency applies to the “trading or financial corporation” test; the instrument establishes the criterion but not the process for proof.

In short, the instrument prescribes the program and ties it to the Act and to the corporations power, but it does not include enforcement mechanics or penalties; those must be located in the Act and in the program’s implementation instruments.

The instrument situates the prescribed program within a narrow legal framework by explicit reference to the Act and to the Constitution. The text provides the legal connectors; it does not itself amend or reproduce the Act but instead operates as a delegated instrument under the Act.

Primary interactions stated in the instrument

• Industry Research and Development Act 1986: The instrument is made under s 33 of the Act (s 3) and explicitly prescribes the program “for the purposes of subsection 33(1) of the Act” (s 5). It also invokes subsection 33(3) when specifying the constitutional power relied on (s 6) and subsection 33(4) when setting the eligibility criterion (s 7). The instrument therefore functions as an exercise of delegated legislative power under the Act to prescribe a particular program and to attach an eligibility rule to it. Any legal effect that flows from this prescription is conditioned by the operation of s 33 and the broader statutory scheme of the Act; the instrument does not displace or re-write other provisions of the Act.
• Constitutional power (paragraph 51(xx)): The instrument specifies, for the purposes of subsection 33(3) of the Act, that the relevant constitutional head of power is the corporations power under paragraph 51(xx) (s 6). That matters as a jurisdictional foundation: the instrument ties the legal basis of the program to Commonwealth legislative power over trading or financial corporations.
• Eligibility requirement tied to constitutional test: The instrument prescribes that applicants must be trading or financial corporations “to which paragraph 51(xx) of the Constitution applies” (s 7). This expressly links statutory eligibility to the constitutional reach of the corporations power. That linkage can affect which legal entities are eligible and how the administering agency interprets corporate status and trading or financial activity.

Secondary or implied interactions

• Administrative law and contract law: The instrument does not set application procedures or contractual terms, so the customary Commonwealth administrative law framework (decision-making procedural fairness, merits review mechanisms where available, delegation and administrative discretion rules) and contract law will govern the implementing arrangements. Those legal regimes will interact with the instrument’s prescription once implementing instruments are issued under the Act.
• Competition law and procurement: The instrument specifies a closed list of participating universities. Where funding or contracting follows, procurement law, Commonwealth Grants Rules and Guidelines, and competition law may apply to the implementation. The instrument itself does not address those interactions.
• Corporations law: Because eligibility is expressly tied to corporate status and the constitutional corporations power (s 7), questions about a prospective applicant’s status under the Corporations Act 2001 or related corporate law concepts could become determinative in practice. The instrument does not define “trading” or “financial” within its text.

Limitations of the instrument’s reach

• The instrument does not override or replace requirements in other statutes. For example, environmental approvals, planning laws, state-based land use rules, and university governance requirements that apply to establishing physical testlabs remain in force independently of this instrument.
• The instrument’s note about its commencement table clarifies that the table “relates only to the provisions of this instrument as originally made” and will not be amended to deal with later amendments (s 2 table note). That is an administrative point about the instrument’s published history and does not affect substantive interaction with other laws but does affect how one reads the instrument’s commencement history against later changes.

Practical implication: to understand the full legal framework that will govern parties’ obligations, rights and exposures under the program, a reader must consult the Industry Research and Development Act 1986 (the parent statute), any program guidelines or grant instruments issued under the Act in relation to this prescribed program, and relevant federal, state and local laws that touch on facility establishment and funding. The instrument supplies the classification and constitutional anchor; operational legal relations will be specified elsewhere.

The instrument includes limited, explicit history relating only to its commencement and a caution about the commencement table. The instrument does not record any statutory amendments, revocations, variations, or historical versions beyond its original making. The available text establishes the following points.

• Original commencement: The instrument provides a commencement table that states “The whole of this instrument” commences “The day after this instrument is registered,” and it records a date in the table information column as 15 November 2018 (s 2 commencement table). That sets the instrument’s initial operative date as the day following registration in 2018.
• Commencement table scope limitation: The instrument explicitly states the commencement table “relates only to the provisions of this instrument as originally made. It will not be amended to deal with any later amendments of this instrument” (s 2 note). That means the commencement table is a historical record of the instrument’s original commencement and will not be updated within the instrument text to track subsequent changes.
• Publishing note: The instrument also contains a publishing caveat stating that any information in column 3 of the commencement table is not part of the instrument and that such information may be edited or inserted in published versions (s 2(2)). Practically, that means the date annotation in the published table is an informative note rather than a binding operative clause.

No recorded amendments in the instrument text

• The instrument as provided contains no later amending provisions, disallowances, schedules, or explicit subsequent variation entries. There is no schedule attached that lists any replacements or modifications.
• The instrument does not list any revocations of earlier instruments or refer to prior versions. It stands as the single instrument prescribing the program in its original form.

What to check for an up-to-date history

• Because the instrument’s commencement table will not be amended to reflect later changes (s 2), one must consult the Federal Register of Legislation or the authorised legislative database to identify later instruments that may have amended, varied or repealed this instrument. The instrument itself cautions that the published column 3 information is not part of the instrument (s 2(2)), so published annotations should be treated as editorial rather than legislative.
• Any change to the program’s substantive elements (participating universities, eligibility criteria, program description, or authority) would require either an amending instrument under the Act or replacement by a later instrument. The text provided contains none of those changes.

In short, the instrument records a single, original instrument dated for commencement in November 2018 and contains a note that its commencement record will not be amended within the instrument. No subsequent amendment history is recorded in the supplied text.

The instrument itself contains no references to litigation, judicial review, cases, or dispute outcomes. It does not cite any court decisions, nor does it record challenges to its validity, scope, or implementation. The instrument is a short, administrative prescription and includes no litigation history section.

Implications from the instrument’s text

• No litigation recorded in instrument: Because the text contains no litigation history, there is nothing in the instrument to ground any claim about disputes arising directly under this instrument.
• Potential for review in general: The instrument is a statutory instrument made under s 33 of the Industry Research and Development Act 1986 (s 3). In general administrative practice, decisions made under the delegated authority of an Act can be subject to judicial review, merits review, or contract dispute, but such possibilities are not recorded or described in the instrument itself. Any contested decisions arising from implementation would be addressed under the general rules of administrative law and the Act’s provisions.

What a practitioner should do to evaluate litigation risk

• Search the Federal Court, Full Court, or High Court databases, and administrative review tribunal records for any cases that reference this instrument by name or program title. The instrument provided here contains no such references.
• Examine program implementation documents, grant contracts and administrative decisions issued under the Act in relation to this prescribed program to identify any decisions that have been challenged. The instrument itself does not supply that material.

Because the instrument contains no litigation record, a reader must consult external case law databases and the implementing agency’s public records to determine whether disputes have arisen in relation to the program.

The instrument is short, but several concrete legal and practical risks, ambiguities and operational gaps flow directly from its text. The following items are drawn from what the instrument states and what it omits, with references to the relevant sections.

1. Participating universities are fixed and limited (s 4; s 5)

   • The instrument names exactly six universities as “participating universities” (s 4). That creates a narrow locus for funded facilities. Expect that any physical infrastructure funded under the program will be located at those institutions. If you are a university not on the list, the instrument provides no basis to claim participation.
   • Practical risk: parties should not assume regional expansion or additional university participation without a separate instrument or other authorised change.

2. Ambiguity about who holds funding and how SMEs access Testlabs (s 5; s 7)

   • The program description says it “provides funding to establish Industry 4.0 Testlabs at each of the participating universities” and that participating universities will “provide innovation support for SMEs … by providing access to Industry 4.0 Testlabs” (s 5). The eligibility criterion separately states applicants must be trading or financial corporations (s 7).
   • Two distinct, plausible operational models could follow, and the instrument does not pick one explicitly: (a) the Commonwealth grants funds to universities to establish and operate the testlabs, with universities then providing access to SMEs; or (b) the Commonwealth funds corporate applicants (trading or financial corporations) which then contract with universities to establish or operate the labs, with SMEs accessing services via those corporations. The instrument’s text is consistent with either reading, because it both names participating universities and restricts applicants to corporations. This creates implementation ambiguity that matters for procurement, tax, audit and governance.

3. Eligibility limited to trading or financial corporations (s 7)

   • The instrument prescribes that applicants must be trading or financial corporations “to which paragraph 51(xx) of the Constitution applies” (s 7). That excludes non-corporate entities from being applicants for the purposes invoked. If you are an SME that is an unincorporated partnership, sole trader, cooperative or an incorporated non-trading not-for-profit, the instrument does not treat you as an eligible applicant.
   • Practical consequence: SMEs that are not corporations will need to rely on corporate partners, intermediaries or the participating universities themselves to access the program’s resources.

4. “Priority industry growth sectors” are undefined (s 5)

   • The program description ties SME support to “priority industry growth sectors” but gives no definition, list, or criteria in the instrument (s 5). That creates a substantive unknown that will be determined in implementation documents or internal agency policy.
   • Practical consequence: Applicants must seek out implementing guidelines or agency statements to determine which sectors qualify and how to align projects to them.

5. No operational rules, funding quantum or timelines (s 5)

   • The instrument states the program “provides funding” but does not specify amounts, funding rounds, duration, milestone requirements, or conditions precedent. None of that detail is present in the instrument.
   • Practical consequence: Applicants cannot rely on the instrument alone to determine monetary exposure, matching fund requirements, or reporting obligations. Look for program guidelines and grant agreements.

6. Enforcement and verification omitted (s 3; s 7)

   • The instrument prescribes an eligibility test but does not provide verification mechanisms, documentary requirements, or consequences for misrepresentation (s 7). Similarly, the instrument contains no sanctions for misuse of funds or breach of program rules.
   • Practical consequence: the administering agency will need to establish verification, audit and sanction mechanisms under the Act or separate instruments; applicants should anticipate those in practice and gather corporate-status evidence.

7. Constitutional anchor may limit scope (s 6)

   • The instrument explicitly ties the program to the corporations power (s 6). That constitutional anchor signals that the program is to be implemented in ways that rely on the Commonwealth’s power over trading or financial corporations. This choice may limit the legal reach of direct Commonwealth action toward entities that are not corporations.
   • Practical consequence: Plaintiffs, auditors or challengers may scrutinise whether particular funding arrangements fall within the constitutional power relied on; the instrument’s text is explicit about the chosen power, but the instrument itself does not explain how that power will be operationalised in contractual arrangements.

8. Commencement table is a historical note, not a running ledger (s 2)

   • The instrument warns that the commencement table will not be updated to reflect later amendments (s 2). If you are seeking amendment history or current operative text, do not rely on the embedded commencement table; instead consult the legislative database for consolidated instruments.
   • Practical consequence: always verify you are looking at the current, consolidated version of the instrument on the authorised register.

9. No express rights for SMEs (s 5)

   • While SMEs are stated beneficiaries, the instrument does not create enforceable rights for SMEs to access facilities or services. Any access rights will derive from grant agreements, university policies, or commercial contracts.
   • Practical consequence: SMEs should secure contractual arrangements or service agreements if access certainty is required.

10. Concentration of benefits to named universities (s 4; s 5)

    • Naming six universities centralises the program’s on-the-ground infrastructure. That concentrates practical benefits (facilities, research capacity) at those institutions rather than distributing them broadly.
    • Practical consequence: regional or non-participating universities and local SMEs outside host regions should expect indirect access only.

These “gotchas” arise directly from what the instrument says or does not say. Parties seeking to act under the program must therefore search for implementing guidelines, grant contracts, and the relevant sections of the Industry Research and Development Act 1986 to fill the instrument’s operational gaps.

The instrument is brief and leaves most operational obligations to implementing documents under the Act. Nevertheless, a compliance checklist that flows directly from the instrument can be drafted. The checklist below outlines concrete steps and documentary items parties should assemble to engage with the prescribed program and to manage legal and administrative risk, each item traceable to the instrument’s text.

1. Confirm corporate status and trading/financial character (s 7)

   • The instrument prescribes that applicants must be trading or financial corporations to which paragraph 51(xx) applies (s 7). Before preparing an application or bid, confirm that your entity is a corporation and that its activities fall within the ordinary meaning of “trading” or “financial” for the purposes of the Corporations Act and constitutional tests. Gather corporate registration details, ASIC extracts, financial statements, and evidence of trading activity.
   • Evidence: ASIC company extract; ABN registration; audited financial statements; evidence of market transactions or contracts demonstrating trading activity.

2. Align project scope with the program description (s 5)

   • The program’s stated purpose is to establish Industry 4.0 Testlabs at the participating universities and to provide innovation support to SMEs in “priority industry growth sectors” and skills-building opportunities (s 5). Design proposals that clearly show how the project: will make use of testlab facilities at one of the participating universities; deliver access to SMEs; and include skills-building elements.
   • Action: map project deliverables to the two stated program aims in s 5, and be prepared to explain how SMEs will be permitted access, what skills training will be provided, and how the project advances priority sector objectives.

3. Engage the participating universities early (s 4; s 5)

   • The instrument names six participating universities by which the testlabs are to be established (s 4; s 5). If your proposal contemplates using or establishing facilities at a named university, secure formal letters of support, memoranda of understanding, or partnering agreements with the relevant university to demonstrate cooperation and site access.
   • Documents: signed MOUs; facility use agreements; host university governance approvals.

4. Seek and review implementing guidelines and grant agreements (s 3; s 5)

   • The instrument does not set procedural or contractual terms. To understand application windows, assessment criteria, funding amounts, reporting obligations, milestones, audit rights and sanction mechanisms, obtain the program’s implementing guidelines, grant opportunity documents, and draft grant agreement templates published by the administering agency under the Act.
   • Action: request or download program guidelines from the administering agency; flag key compliance items (reporting cadence, eligible expenditures, record-keeping, audit rights, intellectual property clauses).

5. Prepare documentation to demonstrate SME access and priority-sector focus (s 5)

   • Because the program is targeted at SMEs in “priority industry growth sectors” (s 5), proposals should include: a definition of which SMEs will be served, selection criteria for SME participants, training curricula or skills development programs, measures of impact, and evidence of how activities support priority sector growth objectives.
   • Documents: SME selection criteria, training outlines, KPIs, monitoring and evaluation plans.

6. Build contractual and procurement strategy consistent with the corporations power framing (s 6; s 7)

   • The instrument ties the program to the corporations power (s 6) and restricts applicants to trading or financial corporations (s 7). Where contracting occurs, structure agreements to reflect corporate parties, appropriate procurement rules, and compliance with Commonwealth grants rules. If a university is to be a recipient or service provider, ensure that contractual form and legal basis align with the eligibility framework prescribed in the instrument.
   • Action: legal review of proposed contracting structures to verify that the roles and legal status of contracting parties match the instrument’s eligibility and constitutional framing.

7. Maintain thorough records to support eligibility and compliance (ss 5, 7)

   • Keep contemporaneous records that evidence corporate status, use of funds, SME engagement, training delivery, and adherence to any priority sector criteria. Because the instrument itself does not specify verification procedures, an administering agency may require documentary proof.
   • Documents to retain: copies of grant applications, correspondence, financial records evidencing expenditure, SME participant registers, training attendance logs, outcome measurement reports.

8. Check the authoritative consolidated instrument and program updates (s 2)

   • The instrument warns that the commencement table is not amended to reflect later instrument changes (s 2). Confirm whether the instrument has been amended, superseded, or supplemented by later instruments or program guidelines on the Federal Register of Legislation or the administering agency’s website.
   • Action: check for consolidated versions and notice of variation on the official legislative register.

9. Anticipate audits and procure insurance and indemnities

   • While this instrument does not specify audits or insurance, typical Commonwealth funding arrangements include audit rights and require recipients to carry appropriate insurances. Ensure financial controls and insurance are in place.
   • Action: set up internal finance controls and confirm insurance coverage for project activity and facility operation.

10. If in doubt, seek clarifying correspondence from the administering agency

    • Because the instrument leaves essential operational matters unspecified, obtain administrative clarification in writing where necessary: for example, about whether universities will be direct recipients, whether corporate applicants are expected to subcontract to universities, or how “priority industry growth sectors” are defined.
    • Action: lodge formal queries with the administering agency and retain responses for due diligence and audit trails.

These steps follow directly from the instrument’s requirements and omissions: establish corporate eligibility (s 7), align proposals with the program purpose (s 5), partner with the named universities (s 4), and seek implementing documentation issued under the Act (s 3). Because the instrument is declaratory and skeletal on operational detail, compliance in practice depends on reading and adhering to the Act and the implementing materials referenced or produced under it.