Shire of Tiaro
former local government area in Queensland, Australia

The Shire of Tiaro was a local government area in the Wide Bay–Burnett region of Queensland, Australia, between the regional cities of Gympie and Hervey Bay about 220 kilometres (137 mi) north of the state capital, Brisbane. The shire covered an area of 2,185.3 square kilometres (843.7 sq mi), and existed as a local government area from 1879 until 2008, when it was dissolved and split between two new local government areas, the Gympie Region and the Fraser Coast Region.
The name "Tiaro" is of Aboriginal origin, meaning withered or dead tree. 43 per cent of the Shire was covered by State forest. The main industries in the shire were sugar, beef and dairy cattle, orchards and timber felling and milling.
History
Tiaro Division was created on 11 November 1879 as one of the initial 74 divisions around Queensland under the Divisional Boards Act 1879 with a population of 1852.
On 9 February 1884, following a petition by the ratepayers of subdivisions Nos. 2 and 3 of Tiaro Division, part of Tiaro Division was excised to establish a separate municipality called the Shire of Tiaro. The Tiaro Divisional Board were opposed to the creation of the shire, and had attempted various legal actions to prevent it. The new shire started life in an immediate dispute with the division over the apportionment of the accounts.
Begin with the source’s own compact description: “Shire of Tiaro” is former local government area in Queensland, Australia. The dossier treats that line as a proposition to test through Shire, Tiaro and former, not as a finished interpretation.
Why this record matters
The phrase “former local government area in Queensland, Australia” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Contemporary correspondence, administrative files and participant testimony can test how later narratives organized the event or institution. The source revision retrieved here is dated Apr 20, 2026. The linked authority identifier is Q7498504. Authority coordinates are -25.727, 152.582. 1 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1879, 2008, 1852 and 1884.
Later summaries often reconcile disputed chronology or motive more neatly than the contemporary record permits. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Compare institutional narratives with records created by participants and affected communities. Dates and formal titles are useful anchors, but not substitutes for context.
- Event chronology
- Institutional context
- Locating named record creators
Contemporary correspondence, government or organizational records, oral histories and cited historical scholarship.
Three-step research path
- Establish the record: confirm the title “Shire of Tiaro”, its source revision and the description used here.
- Expand the search: follow Shire of Tiaro primary sources, Shire of Tiaro archive and Shire research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Shire of Tiaro”?
- What chronology connects this entry to wider political or social change?
- Who created the surviving record, and for what administrative purpose?
Search terms from this dossier
This entry incorporates text from “Shire of Tiaro” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.