10/10/2026
Investigate Cranston - The Nine Cranston City Council Minutes filed in less than 5 Minutes!!
A RI Department of State/Secretary of State records production has exposed a concentrated Cranston filing event that cannot be dismissed as a matter of wording, harmless batching, or an insignificant website issue.
On September 16, 2024, nine records identified as Cranston Development Plan Review Committee meeting minutes were filed through the Secretary of State’s Open Meetings system in approximately four minutes and thirty-seven seconds.
Those records concerned meetings held between December 20, 2023 and July 17, 2024.
The oldest record was filed 271 calendar days after the meeting.
The newest was associated with its meeting 61 days afterward.
Rhode Island law generally requires covered public bodies to file official or approved minutes of open meetings with the Secretary of State within 35 days. This is a deadline, not an optional posting suggestion.
The filing sequence is documented by the Secretary of State’s own database export, its public DPRC dashboard, and nine electronic confirmation messages produced in response to APRA Request 26-84.
THE SEPTEMBER 16 FILING SEQUENCE
According to the Department of State’s records:
• 10:55:20 a.m. — June 5, 2024 minutes
103 days after the meeting and 68 days beyond 35 days
• 10:55:40 a.m. — April 17, 2024 minutes
152 days after the meeting and 117 days beyond 35 days
• 10:55:52 a.m. — April 3, 2024 minutes
166 days after the meeting and 131 days beyond 35 days
• 10:56:15 a.m. — March 20, 2024 minutes
180 days after the meeting and 145 days beyond 35 days
• 10:56:36 a.m. — March 6, 2024 minutes
194 days after the meeting and 159 days beyond 35 days
• 10:57:36 a.m. — February 7, 2024 minutes
222 days after the meeting and 187 days beyond 35 days
• 10:59:03 a.m. — December 20, 2023 minutes
271 days after the meeting and 236 days beyond 35 days
• 10:59:32 a.m. — a file associated with the July 17, 2024 meeting
61 days after the meeting and 26 days beyond 35 days
• 10:59:57 a.m. — January 17, 2024 minutes
243 days after the meeting and 208 days beyond 35 days
The elapsed times are not estimates drawn from screenshots. They come from the timestamps in the Department of State’s own production.
The Department’s public DPRC dashboard independently displays the same September 16 filing cluster.
WHAT THE LAW REQUIRES
R.I. Gen. Laws § 42-46-7 establishes several distinct public-record duties.
Under subsection (b)(1), unofficial minutes must be available at the office of the public body within 35 days of the meeting or at the next regularly scheduled meeting, whichever is earlier. A public body may extend that period by majority vote if it publicly states the reason.
Under subsection (d), covered public bodies must file official or approved minutes of open meetings with the Secretary of State within 35 days. The exception applies to a public body whose responsibilities are solely advisory.
Cranston’s own Development Plan Review ordinance does not describe the DPRC as solely advisory.
Chapter 17.84 authorizes the DPRC to conduct public meetings, vote on development applications, approve applications, impose conditions, require modifications, deny applications, issue written decisions, approve major changes, and extend approvals. A DPRC approval may be required before a building permit or further action before the Plan Commission or Zoning Board.
The DPRC sometimes performs an advisory role on particular applications, but its responsibilities as a body are not limited to advice. On the face of Cranston’s ordinance, the “solely advisory” exception does not fit the DPRC’s full authority.
The active Department of State regulation reinforces this structure. It requires covered public bodies to file minutes within the time prescribed by the Open Meetings Law. It also provides that successful electronic submission generates a confirmation message, which becomes the filer’s proof that the record was filed.
The act of uploading several records in succession is not, by itself, the central problem.
The problem is that the Department’s own records place these minutes outside the 35-day filing period, show no earlier filing in the produced data, and document a wrong attachment being associated with a meeting.
THE JULY RECORD CONTAINED THE JANUARY MINUTES
The most serious record-association problem in the September 16 sequence concerns the July 17, 2024 meeting.
The Secretary of State’s database associated file 502788 with Meeting ID 1060989, the July 17 meeting.
But the file was named:
“1.17.24 DPRC Minutes - DRAFT.pdf”
Our examination found that file 502788 contains the January 17 minutes. Its substantive extracted text is the same as file 502789, which was filed under the January 17 meeting.
The January minutes were therefore placed into the system twice: once under the July meeting and once under the January meeting.
Two days later, on September 18, a different file was added to the July meeting:
File 503122
“7.17.24 DPRC Minutes -APPROVED.pdf”
That later document contains the July proceedings, but it visibly carries the heading “AGENDA,” contains blank speaker identifications, and includes statements that some comments were inaudible.
That is a documented wrong-document association followed by a later corrective filing. It is more substantial than a typographical error in a filename.
The unanswered questions are direct:
Who discovered that the January minutes had been attached to the July meeting?
When was the error discovered?
Was the incorrect document publicly displayed?
Was it removed, archived, hidden, or superseded?
Was a correction notice issued?
Were members of the public who relied on the original record informed?
What audit trail was preserved?
The initial Department of State production did not answer those questions.
THE PRODUCTION ITSELF CONTAINED A GAP
The Department’s spreadsheet lists two files for the March 20, 2024 DPRC meeting:
• Notice file 487320
• Minutes file 502782
Neither file was included in the ZIP archive produced in APRA Request 26-84.
The spreadsheet says the files exist. The production package did not contain them.
That could result from a collection or export error, but the cause cannot be determined without the collection log, export manifest, search parameters, or production checklist.
A follow-up APRA request has now asked the Department to produce both missing files and the records showing why they were omitted.
THE FILER ACCOUNT WAS CREATED TWELVE DAYS BEFORE THE CLUSTER
The Department’s user-role spreadsheet identifies Grace Brownell as the filer associated with the September 16 submissions.
Her DPRC filer role was created on September 4, 2024, twelve days before the filing cluster.
The spreadsheet attributes creation of that role to user ID 453. The same production identifies user ID 453 as Cranston City Clerk and municipal Filing Coordinator Tracy A. Nelson.
This establishes an account and authorization sequence:
September 4 — Brownell’s DPRC filer role was created.
September 16 — the nine-record filing cluster occurred.
September 18 — the July corrective record was added.
It does not, without further records, establish who directed Brownell to clear the backlog, assembled the files, reviewed their accuracy, or decided which versions to submit.
Those are precisely the questions for which the role-creation record, training material, instructions, emails, system logs, and correction history have been requested.
The production also identifies multiple DPRC filers who existed before Brownell’s account was created. The current record therefore does not support a simple explanation that no filer account was available before September 2024.
THE DOCUMENTS APPEAR TO HAVE EXISTED BEFORE THEY WERE FILED
Embedded PDF metadata shows that several documents were created months before the September 16 filings.
Examples include:
• The January 17 minutes carry a January 31, 2024 creation string.
• The February 7 and March 6 files carry April 1, 2024 creation strings.
• The April 3 and April 17 files carry May 31, 2024 creation strings.
• The June 5 file carries a June 26, 2024 creation string.
Metadata does not establish authorship, approval status, or intent. It does establish that several electronic documents appear to have existed well before they entered the Secretary of State filing record.
That narrows the accountability question:
If the documents existed, why were they not transmitted within the statutory filing period?
THE FILES CONTAINED SUBSTANTIVE LAND USE MATTERS
These were not empty administrative sessions.
The delayed records include proceedings involving development approvals, project conditions, jurisdictional decisions, recusals, and property interests.
Two of the batch-filed records concern 1112 Reservoir Avenue:
• The December 20, 2023 meeting included the 1112 Reservoir Avenue cannabis proposal as a pre-application matter.
• The January 17, 2024 meeting included a preliminary-plan vote concerning 1112 Reservoir Avenue and records a recusal by Building Official Stanley Pikul.
The December 20 minutes were filed 271 days after the meeting.
The January 17 minutes were filed 243 days after the meeting.
The April 17, 2024 minutes include the Sharpe Drive Solar proceeding involving Sharpe Solar LLC, the Pawtuxet River Authority, and a representative identified in the minutes as being from Revity Energy.
Those minutes were filed 152 days after the meeting.
The current evidence does not establish that the filing delays were caused by, or intended to benefit, any particular applicant. It establishes that records documenting consequential municipal land-use proceedings were unavailable in the Secretary of State’s centralized filing system for months after the meetings.
That impaired contemporaneous public review regardless of motive.
THE SEPTEMBER 2024 CLUSTER WAS NOT AN ISOLATED EVENT
The DPRC’s current public dashboard displays other records filed well after the corresponding meeting dates.
Representative examples include:
• June 21, 2023 meeting — minutes filed August 4, 2025
• January 15, 2025 meeting — minutes filed June 12, 2025
• February 19, 2025 meeting — minutes filed June 18, 2025
• June 18, 2025 meeting — minutes filed September 17, 2025
• July 2, 2025 meeting — minutes filed September 17, 2025
• November 19, 2025 meeting — minutes filed January 22, 2026
• January 21, 2026 meeting — minutes filed May 20, 2026
• April 1, 2026 meeting — minutes filed May 20, 2026
These entries are visible on the Secretary of State’s public Cranston DPRC dashboard.
The September 2024 event therefore appears within a broader pattern of delayed, clustered, replacement, or catch-up filing activity. The appropriate response is an item-level audit, not an assumption that every delay has the same cause.
A NON-GOVERNMENT GMAIL ADDRESS RECEIVED THE CONFIRMATIONS
The September 16 confirmation messages were sent to Brownell and copied to several City and Department of State recipients.
They were also copied to:
[email protected]
A separately located May 2021 Department of State filing confirmation concerning a North Kingstown public body copied the same address.
That establishes cross-municipality use of the address within the Department’s confirmation workflow. It does not identify the owner.
The outstanding questions include:
Who controlled the account?
Was it a Department test or support account?
Was it controlled by an employee, contractor, vendor, or development team?
Why was a Gmail address receiving official filing confirmations across municipalities?
What access controls and retention rules applied?
Were messages in that account searched when the Department responded to APRA Request 26-84?
What system configuration or distribution rule routed confirmations to it?
Those questions have been included in the follow-up request. The account should not be attributed to any person without the underlying ownership and configuration records.
THE LATER CITY COUNCIL FAILURE MAKES THE CONTROL PROBLEM HARDER TO DISMISS
A separate 2026 Open Meetings Act complaint concerned the Cranston City Council’s June 15, 2026 minutes.
In its September 14 response, counsel for the City Council admitted that the minutes were not filed with the Secretary of State within 35 days.
The City explained that the Clerk’s Office had been disrupted by employee departures and the extended absence of City Clerk Tracy Nelson. The response said Nicole Renzulli, while continuing to serve in the Mayor’s Office as Director of Government Affairs and Communications, assumed additional Council and Clerk-related work.
The City’s response also stated that Renzulli received “no formal transition, training, or institutional handoff” concerning the Clerk’s internal process for tracking and electronically transmitting minutes to the Secretary of State.
That admission does not explain the 2024 DPRC filings. The 2024 cluster predates Renzulli’s later Clerk-related role, and it would be inaccurate to attribute the earlier DPRC backlog to her.
It does, however, document a later failure in the same general City-to-Secretary-of-State records channel.
Taken together, the records show:
• A 2024 DPRC backlog and wrong-document association.
• Additional DPRC delays visible before and after the September 2024 cluster.
• A 2026 City Council filing violation conceded by the City.
• A City explanation acknowledging that Clerk functions were assigned across office lines without a formal transition or training process.
The common accountability issue is not one employee. It is the absence of a reliable, documented municipal control system that ensures each public body’s minutes are prepared, approved, accurately associated, filed on time, confirmed, corrected, and preserved.
THE SEPARATE CRANSTON APRA FAILURE MATTERS AS CONTEXT
Investigate Cranston also has a separate City APRA matter seeking records concerning municipal legal work and governance issues, including Ridge Data, the Broccoli-Hopkins matter, the Mello-Ware matters, the City Solicitor, the Mayor’s Office, the Council, outside legal work, expenses, assignments, recusals, and related municipal records.
That request began on May 21, 2026.
It was later substantially narrowed and restructured in writing. The requester expressly stated that the narrowing was not a withdrawal or a new request.
City counsel Timothy Williamson later wrote that he was awaiting legal records and billing material. A final production or final administrative-appeal determination did not follow.
The Rhode Island Attorney General’s Open Government Unit subsequently directed the City to address the lack of a substantive APRA response, the absence of a final administrative-appeal decision, and the legal sufficiency of the City’s claimed extension.
After the response period passed without a City submission being served on the complainant, the Open Government Unit prompted City counsel on September 14.
On October 8, the Attorney General’s Office again asked City counsel for an update.
This separate APRA dispute does not prove that the DPRC filings were intentionally concealed or that the two matters were coordinated.
It does show why dependable records controls matter.
Cranston’s incomplete, delayed, or inaccessible records do not involve only meeting minutes. Similar access failures have obstructed public examination of consultant payments, legal assignments, municipal expenses, conflicts, recusals, and official decision-making.
WHAT IS NOW ESTABLISHED
The present record establishes all of the following:
Nine DPRC minute records were filed on September 16, 2024 in approximately four minutes and thirty-seven seconds.
The associated meetings occurred between December 20, 2023 and July 17, 2024.
Each filing in that sequence occurred more than 35 days after the meeting date.
Cranston’s DPRC possesses decision-making authority and is not structured as a body whose responsibilities are solely advisory.
The January 17 minutes were associated with both the January 17 and July 17 meeting records.
The correct July record was added two days later.
Several documents appear to have existed before they were filed.
Several files were still named “DRAFT,” while the July corrective document retained an “AGENDA” heading and incomplete speaker information.
Two files listed in the Department’s spreadsheet were omitted from the Department’s produced ZIP archive.
Brownell’s filer role was created twelve days before the cluster through an action attributed to the user ID assigned to Cranston’s Filing Coordinator.
A non-government Gmail address received Cranston and North Kingstown filing confirmations.
The public DPRC dashboard displays additional delayed and clustered filing activity outside the September 2024 event.
Cranston later admitted a separate 2026 City Council 35-day filing violation and acknowledged that Clerk filing responsibilities had shifted without a formal transition or training process.
A separate Cranston APRA request involving legal and financial accountability records remains unresolved despite Attorney General involvement and repeated requests for a City response.
WHAT REMAINS TO BE DETERMINED
The missing evidence concerns mechanism and responsibility:
• Who identified the DPRC backlog?
• Who directed the September 16 filing sequence?
• Who collected and selected the documents?
• Who verified whether each file matched the correct meeting?
• Were the minutes approved before filing, and on what dates?
• Were any public votes taken to extend the availability period for unofficial minutes?
• Did earlier filings exist and later disappear, or was September 16 the first transmission?
• Who discovered the January-to-July attachment error?
• What happened to the incorrect public record after the September 18 correction?
• Why were files listed in the Department’s spreadsheet omitted from its APRA production?
• Who controls [email protected], and why was it embedded in a statewide government filing workflow?
• What written designation, training, supervision, and quality-control process governed Cranston’s filers?
• What corrective action, if any, followed the later City Council violation?
These are answerable questions. The answers should exist in database logs, native confirmation messages, filer-designation records, emails, support tickets, audit records, training materials, retention records, and correction histories.
THE FOLLOW-UP REQUEST
On October 10, 2026, a new targeted APRA request was submitted to the Rhode Island Department of State and assigned Request 26-92.
It seeks:
• The missing March 20 notice and minutes.
• Native electronic confirmations with full headers.
• Audit and version history for the January-to-July attachment error.
• Records showing how and when the corrective July document replaced or superseded the incorrect file.
• Brownell’s filer designation, approval, activation, and training records.
• Communications about the September 2024 backlog.
• Records identifying the owner, purpose, configuration, and retention treatment of [email protected].
• Policies governing late, clustered, backlog-remediation, correction, replacement, and supersession activity.
• System records concerning other specifically identified wrong-document and replacement sequences.
That request is pending.
WHAT CRANSTON AND THE STATE SHOULD DO
Investigate Cranston is calling for an independent, item-level reconciliation of Cranston’s public-body meeting records.
That review should:
Compare every Cranston public-body meeting against the corresponding Secretary of State filing record.
Identify every record filed outside the statutory period.
Determine whether any lawful exception or documented extension applies.
Identify every duplicate, incorrect, missing, replaced, or superseded attachment.
Publish a correction history that does not erase the earlier record.
Confirm the identity, authorization date, and role of each municipal Filing Coordinator and filer.
Produce the written designation and training records required for those roles.
Establish a documented handoff process when Clerk, Council, Planning, or Mayor’s Office personnel assume filing duties.
Require periodic reconciliation between the City’s meeting archive and the Secretary of State’s system.
Preserve the native audit trail rather than relying solely on the current public display.
QUESTIONS FOR THE COMMUNITY
If the government record says nine old minute files entered the system in under five minutes, should the public be expected to treat that as ordinary without asking what triggered it?
If a January document was attached to a July meeting, how many people could have relied on the wrong record before it was corrected?
If the correct record was added two days later, where is the public correction notice?
If official minutes record votes affecting development, permits, property, traffic, drainage, recusals, and public participation, what happens when those records appear months late?
If Cranston later admitted that Council filing responsibilities shifted without training or a formal handoff, what controls existed before that breakdown, and what controls exist now?
Why should residents need multiple APRA requests, Attorney General complaints, spreadsheet reconstruction, PDF comparison, metadata analysis, and system-level follow-up simply to determine when public meeting records were filed and whether they were accurate?
And if Cranston cannot reliably account for the custody and filing of its meeting records, how should the public evaluate its handling of legal expenses, consultant work, conflicts, recusals, sealed sessions, and records requests?
This investigation remains active while Request 26-92 is pending.
We will publish what the next production proves, correct anything the primary evidence disproves, and continue asking the questions that the existing record requires.
This is public-record accountability.
The timestamps are real.
The wrong attachment is real.
The filing delays are real.
The later admitted City Council violation is real.
The unanswered question is what Cranston and the responsible oversight institutions are going to do about them.
Investigate Cranston and LibertyQuahogMedia
Cranston Herald
Mayor Kenneth J. Hopkins
The Ocean State Current
What's going on in Cranston
Steve Stycos for City Council
Paul McAuley for Cranston City Council
Robert Ferri for Cranston