About 240entries in the disclosure log dated 11 November 2026, decided from July 2010 to 10 November 2026
0links to a released document anywhere in the log’s 37 pages
2entries added between the 2 June and 11 November versions of the log
Feb 2027when the council’s response suggests a report on the idea, if councillors support it
When someone uses the Government Information (Public Access) Act, usually called GIPA, to get documents out of Central Coast Council, and the council thinks the rest of us might be interested too, it records the release in a public disclosure log. The log tells you the reference number, the date the application was decided, what was asked for and whether it was released in full or in part. It does not give you the documents. For every entry the access column says the same thing: contact the Customer Service Centre on 02 4306 7900 and quote the reference number.A
Exhibit A · from the source
Cr Corinne Lamont wants that changed. Her notice of motion, item 7.4 on the 17 November Ordinary Council agenda, asks that the council
Improves the accessibility and transparency of its GIPA Disclosure Log by providing direct hyperlinks to the actual documents and records released in response to GIPA access applications, wherever those documents are assessed as suitable for public release.
Notice of motion, item 7.4, Ordinary Council meeting agenda, 17 November 2026, page 80
The motion also asks for redacted versions where some content cannot be published, for the approach to
apply to future releases, and for earlier releases to be added progressively
where practicable
. Her note
to the motion puts the problem plainly:
This creates an unnecessary additional step for the community members who would like to examine information that has already been released by Council.
She asked about it at the 27 October meeting, too. The written answer, printed in the 17 November agenda,
confirms the arrangement:
Members of the public can request copies of disclosed information by contacting Customer Service and quoting the relevant reference number.
What the log actually holds
We read the current log, dated 11 November 2026, end to end. It runs to 37 pages. The oldest entry was decided on 27 July 2010 and the newest on 10 November 2026, a request about investigations of a road over rail crossing at Ourimbah, released in part. Many entries are about development applications, trees, roads and specific sites; some are about larger council matters. By our count there are about 240 entries, and the access column of every one points to Customer Service and the reference number. There is no web link in the document. Nine entries were decided in 2026 and 24 in 2025. Thirty-seven entries record the release type as “Access is granted for 6 months”, which the log does not explain.
The previous version, dated 2 June 2026 and the one the motion links to, said
Council will review and update this disclosure log monthly.
The November version no longer carries that sentence. Between the two versions two entries were added:
one decided on 17 July and the one decided on 10 November.
The council’s “How to access information” web page, last updated on 11 November, gives a slightly different route from the log itself: it says to contact the Governance Team on the same number, or to email ask@centralcoast.nsw.gov.au. Either way, the documents come to you on request, not from the page.
What the council’s response says
The chief executive’s response to the motion, printed under it, does not oppose the idea outright.
It says governance officers have had preliminary discussions with other councils, and
None of the councils contacted currently provide direct links to GIPA documents in the manner proposed.
It raises legal, privacy and administrative questions, possible IT limits given the volume of some
releases, and one more concern:
A large volume of material accessible via Council’s website may also be vulnerable to data mining.
If councillors support the motion, the response recommends further investigation and a report to the
February 2027 meeting covering what other councils do, the Information and Privacy Commission’s
guidance, and the IT, governance, legal, privacy and cyber security questions.
We checked the response’s comparison in a small way. The City of Sydney and Camden logs we looked at are single PDFs or lists of entries, with no per-document links that we could see. The NSW Department of Climate Change, Energy, the Environment and Water, a state agency, asks people to email its GIPA unit with the reference number. So on what we saw, the Central Coast log is ordinary, not an outlier. The motion would make it unusual.
What the rules and the watchdog say
Section 25 of the GIPA Act requires every agency to keep a disclosure log, and section 26 sets what each entry must record: the date the application was decided, a description of what was released, and whether the information is available to other people and how. The NSW Information and Privacy Commission, the law’s regulator, sets out good practice in a fact sheet updated in August 2020. The Act does not prescribe a format, it says, and ideally a log should
provide a link for people to access the information online; or
Information and Privacy Commission NSW, Fact Sheet: Good Practice for Disclosure Logs, updated August 2020
or include a statement explaining how the information can otherwise be accessed. The council’s log
does the second, so it meets the guidance as written. Among the benefits the fact sheet lists for a log is
that
it removes the need for agencies to process multiple applications for access to the same information.
It also says agencies should not put personal information about the applicant or anyone else in a log,
and that an agency linking documents has an ongoing duty to keep the links working.
What you can do now
- Find the entry in the current disclosure log and note its reference number, which starts with F and a year for recent entries.
- Phone 02 4306 7900, as the log says, or email ask@centralcoast.nsw.gov.au, as the council’s access information page says, and quote the number.
- The council already publishes some documents without a request on its authorised proactive release page, including redacted returns of interest for councillors and senior staff.
Our view
Cr Lamont’s motion is right, and it is modest. These are documents the council has already decided to release and has already judged to be of interest to the public. Making each reader ring a call centre for them adds a step for residents and, as the regulator’s own fact sheet points out, work for the council every time the same file is asked for twice.
The response’s worries deserve an answer rather than a dismissal. Privacy is the serious one, and the motion already allows for redaction and for documents that cannot be published. The data mining point is weaker. A log that only lists what the council considers of public interest, published by a council that already posts redacted returns of interest on its own website, is not obviously a new risk. The comparison with other councils tells us the practice is uncommon. It does not tell us it is wrong.
The sensible version is the one the motion already leaves room for: link new releases from now on, and add older ones where practicable, rather than scanning every file back to 2010 before anything changes. Two cheap steps need no report at all. Put the email address on the log itself, so it matches the council’s own web page. And restore the promise to update it monthly, or say how often it will be updated, since two new entries between the June and November versions is hard to read either way.
We will read the minutes of the 17 November meeting when they are published and report what Council decided on item 7.4, and we will report the February 2027 report if Council asks for one.