Military Rehabilitation and Compensation (Non-warlike Service) Determination 2019

The instrument rests on a small set of drafting and legal concepts deployed throughout the Schedule.

• Authorising provision. The instrument expressly says it is made under paragraph 6(1)(b) of the Military Rehabilitation and Compensation Act 2004 (see s 3). The result is a statutory determination rather than a free‑standing code. The instrument’s legal purpose, therefore, is to implement a power conferred by the MRCA.

• Definitions. The instrument contains three explicit definitions in s 5: "Act" means the Military Rehabilitation and Compensation Act 2004; "ADF" means the Australian Defence Force, referencing the Defence Act 1903; and "NATO" means the North Atlantic Treaty Organization. Those definitions determine the textual scope of the Schedule entries: references to "ADF contribution" or to "NATO Stabilisation Force" are read against those defined terms.

• Classification by Schedule. Section 6 instructs that Schedule 1 specifies service that is non‑warlike service for the purposes of the Act. Schedule 1 is a tabular list in which each item identifies an operation (by name where given), the nature of the operation, the geographic extent of the operation and the period during which service in that geographic area is classified as non‑warlike.

• Spatio‑temporal specificity. The Schedule uses precise spatial language. Some entries use internationally recognised boundaries and plain language territorial descriptions (for example "the total land area, territorial waters and superjacent airspace within the internationally recognised boundaries of Israel, Jordan, Syria, Lebanon and Egypt" in Paladin, item 5). Others use geocoordinates to delimit an exclusion (Paladin 5A), or to describe a quadrilateral area (Quadrant, item 24, using four pairs of coordinates). Maritime operations frequently include the adjacent ports and a ten kilometre radius around each port (see items Manitou 18, 18A, 18B). Temporal limits are either expressed as a closed date range (day‑month‑year start and end) or as "On and after" a start date (open‑ended).

• Operational names and blank name slots. Most items have an operation name (Mazurka, Osier, Joint Guardian, etc.). A small number of rows are presented without a name in the Name of operation column (for example item 15 in the HTML table has no name in that column but describes an ADF contribution to a NATO no‑fly zone and maritime enforcement operation against Libya). The Schedule therefore uses either an operation name or a descriptive nature of operation, or both, to identify a deployment.

• Multiple items for the same operational label. The Schedule contains items that share the same operation name but differ in area or period (for example Paladin appears as items 5, 5A and 5B; Manitou appears as items 18, 18A and 18B; Okra appears as 19, 19A, 19B and 19C). These entries create segmented classifications for phases or adjusted geographic bounds of the same operation name.

• Relationship to other instruments and laws. The instrument expressly cross‑references the Defence Act 1903 by defining "ADF" with that meaning. It also defines NATO; both definitions anchor terms that appear in some nature‑of‑operation descriptions. The instrument itself does not set out how other statutes apply once service is classified, but its sole purpose is to make that classification under the MRCA (s 6).

Understanding these concepts is essential because they determine who, where and when an individual's service is treated as non‑warlike. The Schedule is the operative map: read the operation name, nature, area description and the period together to establish whether a particular deployment falls within a listed item.

The instrument affects three principal, identifiable groups directly and a wider set of administrative actors indirectly.

• Service personnel and former ADF members. Individuals who served with the Australian Defence Force in an operation listed in Schedule 1, within the area of operation and during the period specified for that item, are the primary subjects. For those individuals, service that falls within a Schedule item is formally designated "non‑warlike service for the purposes of the Act" (s 6 and Schedule 1). The instrument therefore determines the classification of particular service episodes for every member or ex‑member whose service location and dates correspond to items in the table. Examples: someone attached to the United Nations Kosovo Force in Albania between 11 June 1999 and 12 December 2011 would fall under Joint Guardian (item 3); a sailor who was part of maritime counter‑piracy operations within the area described in Manitou between 1 July 2014 and 13 May 2015 falls under item 18.

• Claimants and dependants under the Military Rehabilitation and Compensation Act 2004. The instrument's classification will affect those who bring claims under the MRCA because the Act uses "non‑warlike service" as a statutory category. While the instrument does not itself specify compensation entitlements, administrative decisions and benefit eligibility under the Act will be taken with reference to whether the applicant’s service is non‑warlike as designated in Schedule 1. The instrument therefore has downstream implications for claim processing, evidence to be supplied and the legal basis on which claims are assessed.

• Administrative decision‑makers and records officers. The Department charged with administering the MRCA, the ADF and related agencies will need to apply this Schedule to personnel records when verifying whether service is non‑warlike. That involves matching individual deployment orders, unit records, movement logs, ship tracks, port visits and dates against the Schedule's geographic and temporal descriptions. For maritime entries that incorporate port radii, mapping of port locations and the 10 kilometre radius is necessary. For entries delimited by coordinates (e.g. Quadrant, item 24, or the Paladin 5A exclusion), geo‑spatial verification will be required.

• Legal advisers, advocates and health/rehabilitation providers. Lawyers and advocates representing veterans, and medical/rehabilitation providers whose services operate through the MRCA framework, will use this instrument to establish the statutory status of service for entitlement claims. Media, journalists and researchers dealing with veterans' cases will also rely on the Schedule to determine if particular deployments are within the non‑warlike classification.

• Indirectly affected foreign forces and multinational partners. Some items describe operations that were multinational or NATO‑led (for example Osier, item 2, "NATO Stabilisation Force"). While the instrument does not confer rights on foreign forces, the classification may be relevant to bilateral/multilateral documentation about who was present where and when; the instrument therefore has indirect informational relevance to allies and coalition partners.

The instrument explicitly defines ADF by reference to the Defence Act 1903 (s 5). That means the ADF concept used in the Schedule is coterminous with the definition in the Defence Act, which is consequential for mixed‑force operations, attachments, secondments and contractor or civilian participation. The instrument does not itself treat civilians or contractors; it applies to "service with the Defence Force" as specified in Schedule 1 and so the primary focus is ADF personnel.

The instrument is not a code of obligations. Instead, it creates a legal classification that produces downstream administrative duties and entitles individuals to have their service treated in a particular statutory way under the Military Rehabilitation and Compensation Act 2004.

Duties created or engaged by the instrument

• Administrative application duty. The immediate administrative duty is on the agency or person responsible for applying the MRCA to correctly classify individual service with reference to Schedule 1. Section 6 makes Schedule 1 determinative: if an individual’s service is in an area of operation mentioned in a Schedule item and occurs during the period mentioned, that service is non‑warlike for Act purposes. The duty, therefore, is to match service records against the Schedule items and apply the classification in claim or decision processes.

• Record‑keeping and verification duty. Because many entries are defined by precise geographic terms and dates, administrative duty extends to establishing evidence sufficient to show where a person was located and on which dates. For maritime operations, the Schedule commonly includes adjacent ports and a 10 kilometre radius, requiring geographic verification, and some entries include coordinates that must be interpreted correctly.

• Interpretation duty where the Schedule segments an operation. The Schedule contains multiple entries for the same operation name with differing bounds and periods (for instance Paladin as items 5, 5A, 5B; Okra as items 19-19C). The duty to interpret these segmented entries correctly falls on decision‑makers: they must select and apply the correct item that corresponds to the servicemember’s actual area and period.

Rights that follow from the classification

• Right to be treated as non‑warlike service for the purposes of the Act. The instrument confers, in legal effect, the right for those whose service meets an item’s spatio‑temporal description to have that service treated as non‑warlike service under the MRCA (s 6; Schedule 1). The instrument does not specify the benefits attached to that classification; entitlements, rehabilitation, and compensation proceed under the MRCA's substantive provisions, which are outside this instrument’s text.

• Right to a clear delineation of service. The Schedule supplies clarity for many operations by giving explicit areas and dates. For service members and their advisers, the right to rely on those schedule entries exists; the Schedule is the authoritative statement for the MRCA on which deployments are non‑warlike for the period specified.

Practical consequences for duties and rights

• Precise dates and spatial language are legally consequential. Closed date ranges, "On and after" open‑ended starts, coordinate‑based exclusions and port radii are not descriptive flourishes in administrative application; they are determinative legal markers for whether service is in scope. For example, someone who was in East Timor on 27 June 2008 may or may not fall within Citadel (item 7, ending 26 June 2008) or Astute/Spire (which end 26 June 2008), depending on the precise date and attachment; the scheduling of overlapping East Timor entries illustrates the necessity of accurate date verification.

• No duties to private parties beyond classification. The instrument does not impose remedial duties on private entities, create offences, or specify compensatory rates; it simply supplies a legally binding categorisation that triggers application of MRCA mechanisms.

This instrument contains no penalty, offence, or enforcement regime. Its operative mechanism is declaratory: it prescribes which Defence Force service is to be regarded as non‑warlike service for the purposes of the Military Rehabilitation and Compensation Act 2004 (see s 6 and Schedule 1). It does not create sanctions, criminal offences or civil penalties; there are no enforcement provisions within the text.

Enforcement in practice therefore occurs indirectly, by reference to the MRCA's administrative and review processes:

• Administrative application. The instrument’s implementation will be enforced through administrative procedures under the MRCA. That is, when a claim or decision under the MRCA requires a determination of the nature of service, decision‑makers will refer to Schedule 1. The instrument itself does not prescribe the mechanisms for contesting or enforcing a classification , those processes, if any, will be found in the MRCA and in general administrative law frameworks.

• Correct application and judicial or merits review (practical note). The instrument does not speak to review routes. It does not create offences for non‑compliance with its terms; nevertheless, an individual or representative who believes an administrative decision misapplied Schedule 1 (for example by treating qualifying service as not non‑warlike) would, in practical terms, pursue remedies and review avenues available under the MRCA and the general administrative law framework. The instrument, however, contains no guidance on procedural protest, review time limits, or internal review rights.

• No internal enforcement agency named. The instrument does not identify which official or body is responsible for ensuring compliance with the determination beyond the implied obligations under the MRCA. The Act’s administrative architecture and delegated powers, not this instrument, will handle claim processing and dispute resolution.

In short, the instrument is a classificatory determination. It produces legal consequences only as those consequences are enacted through the MRCA and the administrative systems that implement that Act. It does not itself contain enforcement mechanics or penalties.

This determination is explicitly anchored to and interacts with at least two external legislative texts by reference, and it has consequential interactions with the administrative machinery of the MRCA.

• Military Rehabilitation and Compensation Act 2004. The instrument is made under paragraph 6(1)(b) of the MRCA (s 3 Authority), and s 6 of the instrument states its operable purpose: Schedule 1 specifies service with the Defence Force that is non‑warlike service for the purposes of the Act. That is the primary legal interaction: the instrument defines the scope of the statutory category "non‑warlike service" used throughout the MRCA. Any MRCA provision which distinguishes between warlike and non‑warlike service will take its input from this instrument’s Schedule.

• Defence Act 1903. The instrument defines "ADF" by reference to the Defence Act 1903 (s 5 Definitions). That means the concept of who is within the ADF, and thus whose service is capable of being classified under this instrument, is determined by the Defence Act’s definition. Where service involves joint, seconded, or embedded personnel, the Defence Act's definition of ADF will be the operative lens for whether the Schedule’s entries apply.

• International organisations and multilateral operations. The instrument defines NATO in s 5, and several items reference NATO or United Nations missions (for example Osier, item 2, NATO Stabilisation Force; multiple items reference United Nations Missions). The instrument therefore operates alongside international operational frameworks; it records ADF contributions to multinational missions and maps those deployments into the MRCA classification scheme. The instrument does not, however, alter any international law obligations or entitlements of coalition partners.

• Territorial and maritime law references. The Schedule frequently uses geographic terms such as "territorial waters", "exclusive economic zone", and "superjacent airspace". Those terms have specialist meanings under public international law and domestic maritime law. The determination adopts those phrases to describe areas of operation; the instrument does not define those technical terms further, so their ordinary legal meanings will be required when applying the Schedule. For example, the Quickstep item (item 12) includes the "exclusive economic zone of Fiji", while several items include territorial waters and superjacent airspace.

• Interaction with administrative law. The instrument itself does not describe review mechanisms or remedies. In practice, any dispute about whether a person’s service falls within the Schedule will be resolved within the MRCA’s administrative scheme and ultimately by the general administrative law framework (judicial review of decisions, merits review where provided). The instrument does not purport to oust review rights, but it does provide the authoritative classification that decision‑makers must apply.

• International or historical state designations. The instrument includes a clarifying note about Serbia and Montenegro being united as the Federal Republic of Yugoslavia between 1992 and 2006. This demonstrates the instrument’s interaction with historical questions of state nomenclature and territory; where a Schedule item lists historical state names, the note is authoritatively appended for interpretation.

Overall, the instrument is an implementing instrument for the MRCA, using terms and definitions that link to the Defence Act and to international mission frameworks. It does not, on its face, create rights or obligations under other statutes beyond providing classification that other laws reference.

The instrument itself is titled as a 2019 Determination (s 1 Name) and is made under paragraph 6(1)(b) of the MRCA (s 3). The text of the instrument contains no internal narrative or schedule of prior amendments; it does not include a defined "amendment history" section. What the instrument does include, however, is a Schedule that reflects a set of operations spanning multiple decades and exhibiting differing temporal statuses: closed ranges, fixed start and end dates, and open‑ended "On and after" commencements. These temporal markers amount to an operational history embedded within the Schedule.

Key features that operate like an amendment trace, inside the Schedule

• Temporal reach across decades. The Schedule contains items dating back to the 1990s (Mazurka, item 1, "On and after 28 January 1993"; Quadrant, item 24, 13 May 1997-30 June 2006) and extends to entries with commencement dates in the 2020s (for example Fortitude, item 26, "On and after 30 April 2019"; Kudu 28A, "On and after 25 April 2024"; Beech, item 29, "On and after 13 October 2023"; Hydranth, item 30, "On and after 15 February 2024"). This distribution shows that the Schedule aggregates many historical operational classifications and some more recent or current classifications.

• Multiple entries for the same operation across different periods. The presence of items such as Paladin (items 5, 5A, 5B) and Okra (items 19, 19A, 19B, 19C) indicate the Schedule captures operational phases or changes. These segmented entries implicitly record that geographic scope or period for an operation has altered over time; for example Paladin had a period (21 April 2003-11 July 2006), a brief 5A exclusion period (12 July 2006-14 August 2006) with a specified exclusion of southern Lebanon coordinates, and then 5B "On and after 15 August 2006". Similarly, Manitou has different geographic bounds across items 18, 18A and 18B with differing date ranges and latitude/longitude limits. The Schedule therefore reflects temporal amendments or the sequencing of distinct operational phases.

• Open‑ended versus closed dates. Several entries are open‑ended (start date with "On and after"), which functions as an ongoing designation until a further instrument or amendment changes that status. The presence of open‑ended items signals that the instrument as enacted in 2019 and published contains live classifications that remain in force unless superseded.

• Post‑2019 entries included. Although the instrument bears the 2019 date in its title, the Schedule as presented includes items with commencement dates beyond 2019 and into 2024 and 2023 (for example items 26-30). The instrument’s Schedule therefore appears to aggregate items that may have been added in subsequent legislative instruments or consolidated into this 2019 instrument text. The instrument text as provided, however, does not include a recorded list of amendment instruments, dates of amendment, or explanatory notes specifying when each item was added to the Schedule. It simply presents the Schedule as a current list.

Practical consequence for practitioners seeking amendment history

• Check instrument register and Federal Register of Legislation. Because the instrument as presented does not contain an annotated amendment record, practitioners should consult the official legislative instrument register and the Federal Register of Legislation to obtain the formal amendment history and the dates on which particular items were introduced or modified. The Schedule’s items and their dates provide substantive content, but do not stand in for a formal gazette chronology.

• Beware embedded historical notes. The Schedule’s note about Serbia and Montenegro is an example of the instrument acknowledging historical state changes. Where interpretation requires historical context, practitioners should track legislative instruments and explanatory materials that accompanied amendments.

In sum, the Schedule itself contains a substantive picture of operational classifications across time, but it does not include a formal amendment history in its text. For authoritative amendment tracing, consult the instrument’s legislative registry entries and consolidated versions available through official sources.

The instrument contains no litigation history, case citations, or references to judicial decisions. There are no judicial or tribunal decisions cited in the text. The Schedule and the body of the instrument are purely declaratory and do not narrate legal disputes or challenge outcomes. Consequently, within the instrument itself there is no record of litigation, appeals, or judicial interpretations of its content.

For practitioners, relevant observations and next steps

• No cases named in the instrument. The instrument names no cases and does not purport to report any litigation concerning the classification of any operation listed in Schedule 1. The instrument does not record judicial construction of any of its items.

• External litigation may exist. Absence of litigation references in the instrument does not imply that no disputes have arisen in practice about the classification of particular service episodes under the MRCA. Where a claimant disputes an administrative decision that applied (or failed to apply) a Schedule item, litigation or merits review may have occurred under the MRCA, administrative law, or social security/compensation appeals channels. Those decisions are not recorded in the instrument and must be located in case databases and administrative tribunals' records.

• Practical approach for legal research. If a practitioner needs the litigation history concerning a particular Schedule item or question (for example disputes over whether a particular deployment fell within the 10 kilometre port radius used in multiple maritime items, or whether a coordinate‑based exclusion applies), the appropriate research path is to:

  • Search relevant tribunal and court databases for judicial review or merits review decisions arising from MRCA applications that reference the specific Schedule item by item number or operation name.

  • Review administrative decision records and appeals to specialist veterans' review bodies or general tribunals if those bodies have published reasons.

  • Check consolidated versions of the instrument and any explanatory memoranda or departmental guidance accompanying particular amendments, because such materials sometimes discuss contested applications that prompted the creation or amendment of a Schedule entry.

• Anticipate interpretive disputes. Given the Schedule’s reliance on geographic descriptions (coordinates, territorial definitions, port radii) and the multiple segmented items for some operations, disputes about scope and temporal boundaries are predictable. Such disputes typically turn on precise service dates, the record of location, and whether particular activities took place inside or outside designated areas. That means litigated issues are likely to be fact‑sensitive, rather than purely legal questions of statutory construction.

Because the instrument itself does not provide litigation records, the instrument functions as the starting point for research rather than as a repository of adjudicative history.

The Schedule contains several drafting and structural features that commonly produce interpretive or operational complications for administrators, claimants and advisers. These "gotchas" are practical traps that can affect entitlement determination if not anticipated.

• Precision of spatial language. Many items use specific geographic phrases: "land area, territorial waters and superjacent airspace", "exclusive economic zone", "ports adjacent to the area … and the area within a 10 kilometre radius of each port", and explicit coordinates. Practitioners must not read such phrases loosely. For example, maritime entries that include a 10km port radius make the status of a port visit determinative only if the ship or personnel were within that radius. Similarly, entries that include "superjacent airspace" extend coverage to aircraft over the area; service that was in transit above the area at a particular altitude is legally relevant.

• Multiple items with the same operation name but different areas/dates. Operations such as Paladin, Manitou and Okra appear in multiple items with differing bounds and dates. The relevant entitlement depends on matching the precise item that corresponds to the service episode. For instance, Paladin is split into 5, 5A and 5B with overlapping territorial descriptions and a coordinate‑based exclusion in 5A. Mis‑matching an individual's service to the wrong Paladin item can change whether it falls within the Schedule.

• "On and after" entries versus closed date ranges. Some items start "On and after" a given date (open‑ended), while others have a defined end date. The legal consequence is that the Schedule both records historical finite deployments and creates ongoing classifications. Practitioners must pay attention to inclusive language: "On and after 28 January 1993" is inclusive of that date; the Schedule uses specific day, month and year markers that should be interpreted literally.

• Blank name entries. A few rows have an empty Name of operation column while still specifying a nature of operation and area (for example item 15 in the HTML table describing the NATO no‑fly zone and maritime enforcement operation against Libya). Do not rely solely on operation name to locate a deployment; read the "Nature of operation" and area fields to confirm whether service falls within an unnamed item.

• Coordinate‑based exclusions and quadrilateral areas. Several items give coordinates or an exclusion polygon (Paladin 5A; Quadrant, item 24). Accurate interpretation requires mapping those coordinates precisely. Sloppy rounding or incorrect datum use could misclassify service. The Schedule does not specify the geodetic datum (for example WGS84), so practitioners should confirm standard practice within the administering agency to ensure consistent interpretation of coordinates.

• Historical state names and changing international borders. The Schedule contains an explanatory note about Serbia and Montenegro to clarify historical nomenclature for items Osier (item 2) and Joint Guardian (item 3). Where state boundaries, names or control have changed over time (for example Ukraine items and "Ukrainian land and territories continuously controlled by Ukraine" in items 28 and 28A), careful factual analysis of whether the servicemember was present in territory continuously controlled by a state at the relevant time is required.

• Overlap and adjacency issues. Several items describe areas that border or overlap other entries (for example multiple entries concern East Timor under different operation names and date ranges). Practitioners must check whether a service episode falls into more than one item, and if so, whether the MRCA has internal rules about precedence or whether either classification suffices. The instrument itself does not prescribe how overlapping items are to be reconciled.

• No procedural guidance for contested classifications. The instrument supplies the Schedule but contains no procedural guidance for dispute resolution. Where there is ambiguity , for example in the exact point of entry to a 10km port radius , it is a "gotcha" that the instrument provides no tie‑breaking mechanism. Instead, institutional practice and the MRCA's decision frameworks will fill that gap.

• Post‑2019 items present without amendment record. The Schedule includes items with commencement dates after 2019. The instrument itself contains no consolidated amendment trail. Practitioners should verify which legislative instruments or determinations added those later items, and whether any later instrument superseded earlier language.

• Different descriptive terms for the same concept. The Schedule alternates between "territorial waters", "territorial sea", "exclusive economic zone" and "superjacent airspace". These are distinct legal concepts; confusing them can produce misclassification. For example, being within an EEZ is not the same as being within territorial waters, and the instrument uses those distinctions intentionally.

If you are advising a claimant or deciding an application, treat the Schedule as the definitive legal map but verify the technical geographies, the precise dates of service, and whether any supporting or subsequent instruments alter the Schedule entries.

Compliance with this determination is a matter of correctly applying the Schedule’s spatio‑temporal entries to individual service records. Compliance responsibilities sit primarily with the agencies and officials who administer the Military Rehabilitation and Compensation Act 2004 and with ADF records officers. For practitioners representing claimants, compliance means assembling the documentary evidence required to show the service fell within a listed item. Practical steps and a checklist follow.

For administrators and decision‑makers

1. Establish the legal question. Determine whether the individual’s service is to be treated as non‑warlike under the MRCA by reference to s 6 and Schedule 1. The legal test in the instrument is conjunctive: service is non‑warlike for the purposes of the Act if it (a) is in an area of operation mentioned in the relevant item of the Schedule and (b) occurs during the period mentioned in that item (Schedule 1,Non‑warlike service, first paragraph).

2. Locate the correct Schedule item. Search Schedule 1 for an item whose area, nature of operation and period correspond to the service episode. Do not rely on operation name alone; some entries have blank name columns and rely on the "Nature of operation" description for identification (see item 15 in the HTML table). Also be alert to multiple entries for the same operation name that differ in area and period (e.g. Paladin 5/5A/5B; Okra 19-19C).

3. Verify exact dates. Use unit movement orders, personnel administration records, ship logs, air mission reports, time and date stamps on attachments, and other official records to establish the precise dates of deployment. If the Schedule uses "On and after" that start date is inclusive; closed ranges are inclusive of the listed start and end dates as presented.

4. Verify geographic location. Map the servicemember’s location data against the Schedule’s area description. For entries using coordinates or port radii, use accurate geospatial tools and confirm the coordinate datum used in administrative systems. For maritime operations, confirm whether the ship or personnel were within the port 10 km radius where that language is used (see Manitou items 18-18B for port radius language).

5. Document the match. Prepare a concise administrative note that identifies the Schedule item number, quotes the area and period as printed in the Schedule, attaches supporting records showing the servicemember’s presence, and records any interpretation steps taken (for example how coordinates were plotted). This record will be necessary for audit trail and for any subsequent review.

6. Resolve overlaps thoughtfully. If multiple Schedule items arguably cover the same service episode, set out the factual basis for selecting the most appropriate item (date and area). Where overlap is genuine and leads to different characterisations, follow the MRCA’s administrative guidance (if available) about precedence or seek internal legal advice.

7. Maintain a mapping of Schedule amendments. Keep an administrative register that tracks which Schedule items have been added, amended or repealed and the legislative instrument that effected the change. The instrument text provided does not contain an amendment log; compliance systems must therefore maintain this separately.

For claimants and their advisers

1. Assemble deployment proof. Collect primary documents that show location and dates: service records, posting orders, travel orders, mission logs, ship or aircraft logs, port entry/exit records, unit situation reports. For aircrew, sortie logs and Air Tasking Order entries are useful. For maritime personnel, bridge logs and GPS tracks are particularly probative.

2. Match to the Schedule item. Identify the Schedule item whose area and period best fit the service. Quote the item number and text in any claim communication. Do not simply quote the operation name; some Schedule rows have empty name fields or similar names with different bounds.

3. Address geographic challenges. If the service took place near a boundary (a port radius or coordinate line), provide precise geospatial evidence where possible. Photographs, GPS tracks, ship tracking databases and contemporaneous mission notes help.

4. Anticipate disputes over classification. If an administrative decision denies that the service falls within Schedule 1, prepare to request internal review or provide further evidence showing location and dates. Keep the administrative record clear about how the applicant’s presence matches the Schedule text.

5. Use the instrument pragmatically. Remember that the instrument defines only the classification. Rights under the MRCA flow from that classification, but the instrument does not itself set entitlements. Plan claims on the basis that classification is step one; the substantive claim will then proceed under the MRCA.

Technical and process tips

• Geocoordinate interpretation. Use consistent mapping software and confirm datum. Where the Schedule lists coordinates without specifying datum, use the standard datum the administering agency uses for operational maps.

• Port radius calculations. For entries that include a 10 kilometre radius, calculate radial distances from the official port centre point used by the Navy or port authority, and document the port centre chosen.

• Historical state control issues. For items concerning territories with contested control or changing control over time (for example the items concerning Ukrainian territory), confirm contemporaneous control status and map the claimant’s presence against areas described in the Schedule (the Kudu items, 28 and 28A, use the phrase "Ukrainian land and territories continuously controlled by Ukraine" which makes continuous control a factual element).

• Coordinate exclusions. Where an item contains an exclusion polygon (as in Paladin 5A), check whether service was within that exclusion. If a servicemember was in the exclusion area, they cannot rely on that item even if they were otherwise attached to the named operation.

• Record retention. Preserve contemporaneous objective records (logs, GPS, orders). Administrative reliance on Schedule 1 requires proof of where and when.

Following these procedures will align administrative decision‑making and claim preparation with the instrument’s text and the Schedule’s precise requirements. The instrument does not contemplate discretionary reinterpretation; compliance is a matter of matching facts to the Schedule’s descriptions and recording the rationale for classification decisions.