Investigate Cranston

08/21/2026

Thank you for speaking up and standing up child abuse!
Thank you for everything you are doing and your efforts 🙏 💪Let's Be Better

08/20/2026

THROWBACK THURSDAY: FROM LUNCH LINE TO THE COLLECTION LINE

In 2018, Cranston Public Schools decided that a family owing just $20 in school lunch debt could be turned over to a private collection agency after 60 days.
Not $200.
Not $2,000.
$20.

The decision drew backlash, and Cranston later emphasized a softer approach.

But the question remains:
How did chasing families over a child’s lunch balance become the answer in the first place?

This wasn’t just about unpaid meals. It was about judgment, priorities, and how a public school system chose to treat the families it serves.

08/20/2026

THROWBACK THURSDAY: WHEN A CRANSTON SCHOOL POLICY CROSSED THE LINE

In 2020, a Cranston parent challenged a district policy that required a doctor’s note before a Section 504 team would even be convened to consider an accommodation for a student.
The Rhode Island Commissioner of Education ruled that requirement violated Section 504 of the Rehabilitation Act and ordered Cranston to remove it.

That should concern every parent.

Because the real question is bigger than one policy:
How does something that violates federal disability law get written, reviewed, approved and implemented before a family is forced to fight it?

Parents should not have to become legal experts just to make sure their children receive the protections the law already guarantees.
Policies matter. Oversight matters. Accountability matters.


Cranston Public School Department Cranston Patch Cranston Herald

08/19/2026

the Flock stand-out Jefferson Blvd Warwick RI.

WPRI 12
What's going on in Rhode Island
NBC 10 WJAR
BZWatchdog News Network
What's going on in Warwick
The Ocean State Current
NewsNation
Judicial Watch
ThatGuy401

08/19/2026

the Flock stand-out Jefferson Blvd Warwick RI.

WPRI 12
What's going on in Rhode Island
NBC 10 WJAR
BZWatchdog News Network
What's going on in Warwick
The Ocean State Current
NewsNation
Judicial Watch
ThatGuy401

08/19/2026

Why is the Cranston City Council spending time creating a new restriction for something Rhode Island law already addresses?

R.I.G.L. § 11-22-2 is already on the books. So who introduced this proposal — and did anyone actually research the existing law first?

And if driver distraction is really the concern, let’s be consistent. During election season, large political signs blanket Cranston and compete for drivers’ attention far more than a small business sign on a telephone pole.

Before creating more fines and more restrictions, maybe City Council should first ask:

Does a law already exist?

In this case, it does.


Cranston Patch Cranston City Hall Mayor Kenneth J. Hopkins

08/19/2026

When the "Truth" is actual a lie, or two or several. But, Hey, That's just "law enforcement"...
Check the comments for a line by line to this Flock "myth vs fact check" graphic

A Message from Chief Michael J. Winquist

The Cranston Police Department has been using Flock Automated License Plate Reader (ALPR) cameras for approximately five years. During that time, this technology has assisted our officers in solving numerous significant cases throughout Cranston. It has also helped us locate missing and endangered persons and prevent crime by intercepting more than 200 individuals driving stolen vehicles, using stolen license plates, or wanted on criminal warrants.

We use this technology responsibly, with privacy guardrails in place that includes training for all officers, a comprehensive policy on its use, and internal audits conducted to protect against misuse. Access is restricted to authorized law-enforcement purposes, and searches are subject to strict accountability measures.

Unfortunately, there has been a tremendous amount of misinformation recently disseminated about Flock cameras—including inaccurate and exaggerated claims about their capabilities, how information is stored, who has access to the data, and how the technology is used.

Some local elected officials have chosen to discontinue the use of this technology in their communities. In my view, doing so deprives their officers of an invaluable investigative tool depriving their ability to solve crimes, locate missing persons, recover stolen property, and keep their communities safe.

The Cranston Police Department will continue to take advantage of all lawful technology available to us to protect our residents and enhance public safety—including Flock cameras.

We believe the public deserves accurate information, transparency, and an honest discussion about how this technology is actually being used.

Please take a moment to review our “Truth About Flock Cameras” Myth vs. Fact information.

08/18/2026

Investigate Cranston Files — Beyond the $7,500 - The handoff
Status of the work

The Ridge Data - Beyond the $7,500 published documents herein are a defined branch of a much larger public-accountability record discovered. Our technical objective remains to close the item-level evidentiary chain for the payments, reporting, attributed work, public-record custody, meeting activity, and filing history examined in the series. Closing that chain would not, by itself, close the broader findings of our investigation and further discoveries.

Why the grassroots phase pauses:

The grassroots research phase has gathered, preserved, indexed, compared, and tested the records available to it. Some remaining questions require records or powers that a public-interest research team does not possess. Depending on jurisdiction and legal authority, further testing may require certified native records, system audit logs, forensic accounting, sworn interviews or testimony, discovery or subpoena process, payment and banking verification, privilege review, or formal corrective and enforcement mechanisms.

The responsible next step is therefore a controlled handoff—not an evidentiary leap. Our preserved records will be supplied to qualified professionals and institutions, whom are able to authenticate additional records, compel or obtain missing evidence where lawfully authorized, reconcile the systems, test competing explanations, and report defensible findings.

The referral package will preserve and distinguish:

- controlled copies of source documents and images;
- source indexes, hashes, filenames, acquisition information, and version history;
- reproduced calculations and the inputs used to produce them;
- chronologies, custody matrices, and documented role overlaps;
- supported findings, reasonable inferences, hypotheses, and open questions;
- APRA requests, responses, denials, fee estimates, productions, and identified gaps;
- corrections, supersession decisions, quarantined claims, and evidentiary limitations;
- the specific native records required to prove, disprove, or narrow each unresolved issue.

Appropriate professional review:

Our records and findings will be extremely useful and invaluable to independent forensic auditors, qualified legal counsel, oversight and ethics authorities, records and open-government authorities, investigative journalists, and other agencies with applicable jurisdiction.

However, A referral is not an automatic investigation or a verdict of guilt. It is a request for professionals with greater access and applicable authority to test the record. The findings must remain separated from allegations, unresolved inferences, and claims that still require native evidence or independent confirmation.

Our grassroots Investigate Crasnton file pauses here. Preservation and hands off happen. wherefore, Professional review may begin.

Public money, public authority, and public records remain subject to public accountability. Our research and evidence does not disappear at handoff. It's saved and dispersed...

This publication point is a preservation-and-referral checkpoint. It is not a declaration that the Cranston investigation is complete, that every evidentiary branch has been exhausted, or that all unresolved questions have been answered.

Cranston City Hall
Mayor Kenneth J. Hopkins
Paul McAuley for Cranston City Council
(Former) State Representative Christopher Millea
Cranston Herald
GoLocalProv
NBC 10 WJAR
Peter Neronha
Nicole Renzulli

08/18/2026

Investigate Cranston Files — Beyond the $7,500 -The Audit That Can Close the Chain

Four linked ledgers and one reproducible public finding.

The Ridge Data question is no longer just a question about three payments.

The controlled public record presents a connected audit problem involving:

• three Cranston City-reported Ridge Data Consulting payments of $2,500 each;
• all three historical Ridge rows appearing together in a later cumulative legal-expense report after being absent from the earlier acquired report state;
• blank displayed legal-matter fields for all three Ridge rows;
• later attribution of approximately 65 hours to each payment without the complete contemporaneous work chain presently available for public verification;
• an initial reported records response consisting of a finance-system screenshot, followed by the later production of invoices;
• a separate, persistent $63 invoice-versus-paid field discrepancy elsewhere in the same legal-expense reporting system;
• testimony routes crossing a public web form, a named Mayor’s Office mailbox, the City Clerk’s distribution function, committee members, meeting notation, and a filing vote;
• legal-expense questions entering executive-session custody without a public item-level record establishing whether Ridge was discussed;
• clustered and delayed Secretary of State filing patterns that require meeting-by-meeting testing against Rhode Island’s filing rule, approval history, any extension, and any applicable advisory-body exception.

These are not interchangeable allegations. They are distinct, documented control points.

They cannot be resolved by another narrative, another summary, or another isolated PDF.

They require an independent audit that joins four systems:

1. THE TRANSACTION LEDGER — who authorized, coded, approved, paid, cleared, reported, and corrected the money.

2. THE PERFORMANCE LEDGER — what was assigned, when it was performed, what source material was used, what was produced, who reviewed it, and where it was retained.

3. THE PUBLIC-PARTICIPATION LEDGER — what testimony was submitted, where it arrived, who handled it, whether members received it, how it was noted, and where it was filed and retained.

4. THE MEETING-AND-FILING LEDGER — what was noticed, created, approved, transmitted, filed, replaced, sealed, reviewed for release, or left unresolved.

The audit succeeds only if those ledgers can be joined by native identifiers, timestamps, approvals, hashes, vouchers, payment IDs, message IDs, meeting IDs, attachment IDs, and version history.

The standard is not another explanation. It is joined native evidence that another qualified reviewer can reproduce.

Why a four-ledger audit is necessary

One record can show a payment. It cannot, by itself, show the Complete public transaction. And that may very-well be the point?

A finance screenshot may establish that an entry exists in a City system. An invoice may establish what a vendor billed. A cumulative report may establish what the City later displayed. A check or electronic-payment record may establish disbursement. A bank record may establish clearing. A time record may support duration. A deliverable may support performance. An approval may identify who accepted the work.

None of those records substitutes for all the others.

The same principle applies to public testimony and meeting records. An agenda may define the promised intake and distribution procedure. It does not prove that a particular submission arrived, was forwarded, reached each member, was noted at the meeting, was voted into the record, was attached to the correct filing, or was retained.

The investigation has therefore reached a precise conclusion:

The public record is fragmented across systems that must be joined at the items level.

The purpose of the four-ledger audit is to determine which explanation the native evidence supports—not to force every issue into a predetermined theory.

Possible outcomes include regular process, incomplete reporting, clerical error, weak controls, inadequate records searches, unsupported attribution, misallocation, a conflict requiring review, or another evidence-supported explanation.

The audit must decide among them and show its work.
Ledger 1: the transaction chain

The first ledger follows the money from authority through public reporting.
For each of the three $2,500 Ridge rows, the audit should identify:

• the request for services;
• the legal and administrative authority for the engagement;
• the vendor-master record and every vendor alias or identifier;
• the contract, engagement letter, purchase authorization, or other controlling instrument;
• the invoice and its native metadata;
• the account, fund, department, and matter coding;
• the voucher or accounts-payable batch;
• each approval and the approving user;
• the payment instrument and payment identifier;
• bank or treasury clearing;
• general-ledger posting and reconciliation;
• the public legal-expense report row; and
• every correction, replacement, or version event.

The public reports display three Ridge rows dated October 10, October 30, and November 21, 2025, each for $2,500.

The controlled December-to-January comparison found that the cumulative report with a December 4 footer displayed no Ridge provider block. The next acquired cumulative state, with a January 13 footer, displayed all three historical Ridge rows together.

Those three Ridge rows were the only additions in that transition whose displayed payment dates all preceded the earlier report footer.

That is a verified report-state exception.

It is not, by itself, proof of when the transactions were entered, approved, posted, paid, settled, or cleared. Those are different clocks, and the native transaction ledger must supply them.

The audit must answer: Why did the public report change. and why does the native accounting history support the displayed sequence?

he report-control test and the separate $63 discrepancy

The legal-expense reporting system has an independently reproducible control problem.

One non-Ridge Marsella row displays:

• Invoice Amount — $4,418.95
• Amount Paid — $4,481.95
• Difference — $63.00

Across seven controlled report states, the displayed grand total follows the invoice-amount column, while the sum of the displayed amount-paid fields is exactly $63 higher.

This is not a Ridge discrepancy.

It is not proof that $63 was improperly disbursed or cleared.

It is direct evidence that the public report can carry two different displayed monetary values for a row while aggregating only one of them. That makes the underlying report definition, source fields, authoritative transaction amount, adjustment history, and reconciliation process material to the Ridge audit.

The native audit should obtain:

• the Marsella invoice;
• voucher and accounts-payable distribution;
• payment instrument;
• adjustment or correction history;
• general-ledger and clearing record;
• the report’s data dictionary and calculated fields; and
• the query or procedure that produces the displayed totals.

The point is not that the Marsella row proves anything about Ridge.

The point is that the same reporting system cannot be treated as self-authenticating when its displayed columns and totals do not fully reconcile.

Ledger 2: the performance chain.

The second ledger follows the publicly funded work.

NBC 10 reported that the three invoices described “data consulting services” but did not state hours. NBC further reported a later explanation attributing approximately 65 hours to each $2,500 payment.

The arithmetic is reproducible:

• approximately 65 hours × 3 = approximately 195 hours;
• $7,500 ÷ 195 hours = approximately $38.46 per hour.

The arithmetic does not establish its own source.

The audit must join each invoice to:

• the assignment;
• service date;
• contemporaneous time entry or fixed-fee milestone;
• task and legal-matter identifier;
• source data or research materials;
• system-access authorization and activity, where applicable;
• workpapers, notes, drafts, and deliverables;
• transmittal records;
• reviewer comments;
• acceptance or completion decision; and
• final retention location.

If the engagement was hourly, the audit should identify the authorized rate and contemporaneous time support.

If it was fixed-fee, the audit should identify the authorized scope, deliverable, milestone, and acceptance basis for each $2,500 invoice.

If records are properly withheld from public disclosure, the audit should still determine their identity, custody, date, general function, relationship to the payment, withholding basis, segregability decision, and retention status without publishing protected substance.

The audit must answer: What work was substantiated, and what record produced the later hours attributions?

Ledger 3: the public-participation chain

The third ledger follows public testimony as a government record.

The preserved July 9, 2026 Claims and Safety Committee agendas directed written testimony through either the City Council contact form or a named `[email protected]` mailbox.

The agendas then assigned additional steps:

• submissions were to be provided to committee members by the City Clerk before the meeting;
• the record was to be noted; and
• a vote could or would be taken to file written testimony into the record.

The official Mayor’s Office directory identified Nicole Renzulli as Director of Communications and Governmental Affairs. The official Clerk directory separately identified the City Clerk. The published route therefore crossed an administration mailbox, a public web form, and a Clerk-controlled Council distribution and filing process.

That crossover is a custody fact—not proof that testimony was altered, withheld, or mishandled.

The audit should create an item-level ledger for every submission:

SUBMISSION ID → INTAKE ROUTE → RECEIPT TIME → MESSAGE ID → ATTACHMENT HASH → CLERK HANDOFF → MEMBER DISTRIBUTION → MEMBER RECEIPT → MEETING NOTATION → FILING VOTE → EXHIBIT ID → RETENTION LOCATION

A search of only one mailbox would not be complete if the public web form stored submissions in a database, routed them through another mailbox, retried failed delivery, or preserved them through a vendor platform.

The audit must test both routes and the handoff between them.

The public should be able to determine whether each submission completed the procedure publicly promised in the agenda.

Ledger 4: meetings, sealed records, and filing

The fourth ledger follows a public record from meeting notice through state filing and retention.

The January 20, 2026 Council minutes record entry into executive session for “Discussion of Legal Bills from Law Department.” The public record establishes a legal-expense custody event involving administration and Council participants.

It does not establish that Ridge was discussed.

That distinction must remain intact.

The audit should obtain and join:

• the public notice and docket;
• the report or packet distributed for the meeting;
• document-creation and modification history;
• the motion and recorded vote to enter executive session;
• attendance;
• the sealed-minutes index;
• exhibits or materials taken into the session;
• the return-to-open-session record;
• any disclosed votes;
• the sealing vote;
• later review for continued sealing or release; and
• any unsealed record or public report-back.

Sealing can be lawful. It does not eliminate the need to identify what records exist, who holds them, what legal basis applies, whether a release review occurred, and how the sealed records connect to the public report.

The same ledger must distinguish four separate clocks:

1. the meeting occurred;
2. testimony or another record was received;
3. minutes or attachments were created or approved; and
4. the record was transmitted to and displayed by the Secretary of State.

Those dates are not interchangeable. Batching and Rhode Island’s filing rule.

Batching is not just a visual pattern when a filing deadline applies.

Rhode Island General Laws § 42-46-7 requires meeting minutes and includes electronic filing with the Secretary of State. Subsection (d) provides a 35-day filing rule, subject to an exception for public bodies whose responsibilities are solely advisory.

That means each apparent delay must be tested body by body. The audit must determine:

• whether the body was subject to the 35-day requirement;
• whether it was solely advisory;
• whether an extension was approved;
• what version was filed;
• whether the filing was a draft, approved record, correction, or replacement;
• who transmitted it;
• which filer account was used;
• the electronic confirmation time;
• the MeetingID and attachment ID;
• whether a later version replaced it; and
• whether the City’s copy matches the State-filed attachment.

The official dashboard displays genuine clusters, including multiple DPRC meeting records filed within minutes of one another and Council records sharing or nearly sharing filing times.

The dashboard also displays Council examples beyond the 35-day reference point, including the November 17, 2025 minutes displayed as filed 42 calendar days after the meeting and the December 15, 2025 minutes displayed as filed 37 calendar days after the meeting.

Those displayed intervals create compliance questions. They do not, without the approval history, extension record, submission receipt, applicable-body analysis, and version history, establish the complete legal conclusion.

The audit must publish the meeting-by-meeting determination rather than dismiss the clusters as mere semantics or declare every cluster unlawful without testing the statutory conditions.

The native keys that make the audit reproducible

Names, Dates, and PDF pages are not enough to join four government systems reliably.

The audit must preserve and use the native keys:

• vendor ID;
• invoice ID;
• voucher and accounts-payable batch ID;
• payment and instrument ID;
• account, fund, department, and matter codes;
• user and approval IDs;
• native creation, modification, posting, approval, and clearing timestamps;
• message and submission IDs;
• attachment hashes;
• recipient and distribution logs;
• meeting and agenda-item IDs;
• Secretary of State MeetingID, attachment ID, filer account, and electronic confirmation;
• sealed-record index identifiers;
• filenames, storage paths, and retention labels; and
• complete version and correction history.

These keys are what allow an auditor to answer whether two records describe the same payment, assignment, testimony item, meeting attachment, or document version.

Without them, similar dollar amounts, names, dates, and filenames can be mistaken for proof of identity when they are only possible associations.

With them, the audit becomes testable.

The findings the independent audit must publish

The public does not need another untestable assurance, The public needs and deserves answers.

For each material issue, the audit should publish:

1. What Happened?

2. Which explanation is supported by the native record?

3. Did the money reconcile from from authority through clearing and public reporting?

4. What work was substantiated, By which records, and under what compensation structure?

5. Did each testimony item compete the promised intake, distribution, meeting, filing, and retention chain?

6. Did each meetings record comply with the applicable notice, minutes, approval, extensions, filings, corrections, sealing and retention requirements?

7. Which controls functioned?

8. Which test control failed, Were incomplete, Or could not be tested?

9. What corrective action is required?

10. What remains unsolved, And which exact record or authority is needed to resolve it?

Every conclusion should cite the native record, reproducible calculation, or documented limitation supporting it.

The audit should distinguish:

• verified fact;
• reproduced calculation;
• supported conclusion;
• reasonable inference;
• unresolved conflict;
• allegation not adopted as fact;
• negative search result; and
• evidence not acquired.

That is how an investigation becomes defensible rather than merely forceful. The finite preservation and production demand!

Transactions:

• Engagement and selection records
• Contract, scope, rate, and authority
• Vendor master and aliases
• Native invoices
• Account, fund, department, and matter codes
• Vouchers and AP batches
• Approvals and user logs
• Payment instruments, GL postings, clearing, and bank reconciliation
• Report-source tables, queries, and correction history

Performance

• Assignments and matter IDs
• Service dates and contemporaneous time records
• Source of the approximately 65-hour figures
• Data-access authorizations and logs
• Workpapers, drafts, deliverables, transmittals, reviews, and acceptance
• Custodian, repository, retention, and disposition history

Public Participation

• Contact-form configuration and submission database
• Mailbox registration, delegates, forwarding, message trace, and audit
• Attachment hashes and receipt times
• Clerk handoff and member-distribution manifests
• Member delivery or receipt evidence
• Meeting notation, filing vote, exhibit index, and retention location

Meeting and Filing

• Notices, agendas, packets, and native source documents
• Creation and revision history
• Approval and extension votes
• Clerk transmittals
• Secretary of State receipts, filer-account audit, MeetingIDs, and attachment IDs
• Replacement and correction history
• Executive-session entry and return votes
• Sealed-minutes indexes, exhibits, release reviews, and later unsealing

This is a finite audit design.

It is broad because the public systems intersect. It is precise because every demand is tied to a specific proposition the records can prove, disprove, or narrow.
EVIDENTIARY BOUNDARY

This thread does not declare fraud, theft, criminality, civil liability, an ethics violation, nonperformance, intentional concealment, improper testimony handling, or an Open Meetings Act violation.

It does establish a documented basis for an independent audit: the presently public record does not provide an item-level, native, reproducible chain joining the Ridge transactions, attributed performance, public-record handling, meeting custody, and state filing history.

It also identifies exactly what can resolve the material questions.

No predetermined verdict, In-fact, A reproducible one.

Public records. Reproduced calculations. Testable questions.
PRESERVE • PRODUCE • RECONCILE • TEST • PUBLISH

Mayor Kenneth J. Hopkins
(Former) State Representative Christopher Millea
Paul McAuley for Cranston City Council
Allan Fung
The Ocean State Current
Peter Neronha
FBI


Source, method, and evidentiary section.

Principal public sources:

NBC 10 WJAR I-Team, “Campaign consultant for Cranston mayor got city work,” May 6, 2026:
https://turnto10.com/i-team/cranston-mayor-ken-hopkins-campaign-consultant-city-work-ridge-data-consulting-michael-cotugno-law-department-may-6-2026

Cranston Finance Department:
https://www.cranstonri.gov/departments/finance/finance-department/default.aspx

Cranston Finance Committee minutes, February 5, 2024:
https://web.cranstonri.org/clerkdocs/FinanceMinutesDrafts/2024/2024_02_05.pdf

Cranston City Council minutes, January 20, 2026:
https://web.cranstonri.org/clerkdocs/CouncilMinutes/2026/2026_01_20.pdf

Rhode Island General Laws § 42-46-7:
https://webserver.rilegislature.gov/Statutes/TITLE42/42-46/42-46-7.htm

Rhode Island Department of State electronic-filing regulation:
https://rules.sos.ri.gov/Regulations/part/100-70-00-2

Cranston City Council Secretary of State dashboard:
https://opengov.sos.ri.gov/OpenMeetingsPublic/OpenMeetingDashboard?EntityID=715&subtopmenuId=201

Cranston Mayor’s Office directory:
https://www.cranstonri.gov/about/mayors-office-directory/

Cranston City Clerk directory:
https://www.cranstonri.gov/departments/city-clerk-records-and-licenses/city-clerk-directory/

Cranston City Council contact form:
https://www.cranstonri.gov/city-council-contact-form/

Rhode Island General Laws § 42-46-7:
https://webserver.rilegislature.gov/Statutes/TITLE42/42-46/42-46-7.htm

Rhode Island Department of State electronic-filing regulation:
https://rules.sos.ri.gov/Regulations/part/100-70-00-2

Cranston City Council Secretary of State dashboard:
https://opengov.sos.ri.gov/OpenMeetingsPublic/OpenMeetingDashboard?EntityID=715&subtopmenuId=201

CONTROLLED INVESTIGATIVE MATERIALS

• Cranston December-to-January Legal Expense Row Field Diff v0.84
• Cranston December-to-January Legal Expense Subtotal and Total Reconciliation v0.84
• Cranston Ridge NBC 10 February Legal Report Population Reconciliation v1.06
• Cranston Ridge APRA Invoice and Explanation Custody Reconstruction v0.56
• Cranston Renzulli-Clerk Testimony Intake and Distribution Chain v0.59
• Cranston Clerk-SOS Batch Typology and Renzulli Attribution Control v1.37
• Cranston SOS Meeting-Minutes Filing Cluster and Four-Clock Audit v0.59
• Cranston July 9 Testimony and June 15 Ridge Minutes Current Status v1.37

08/18/2026

Investigate Crasnton Files - Beyond the $7,500 - The hours where attributed, The work chain was never produced.

Our previous post mapped the Ridge Data question across multiple public control systems: authority, finance, legal-expense reporting, records response, testimony, Clerk distribution, Council custody, meetings, sealed records, and state filing.

This installment tests the performance claim itself.

NBC 10 WJAR reported that Cranston City eventually produced three Ridge Data Consulting invoices for $2,500 each. The invoices reportedly described “data consulting services” but did not state hours. NBC 10 further reported that a later explanation attributed approximately 65 hours to each $2,500 payment.

The arithmetic is straightforward:

• 3 invoices × $2,500 = $7,500• Approximately 65 hours × 3 invoices = approximately 195 hours• $7,500 ÷ 195 hours = approximately $38.46 per hour

That calculation can be reproduced.

It does not, by itself, prove performance.

A defensible work chain should connect:

AUTHORITY → ASSIGNMENT → TIME → TASK → SOURCE MATERIAL → WORK PRODUCT → REVIEW → ACCEPTANCE → RETENTION

The public materials reviewed in this investigation do not presently supply that complete chain.

They do not identify the contemporaneous time entries supporting the approximately 195 hours.

They do not show how the time was divided by:

• Date
• Assignment
• Task
• Legal matter
• Data source
• Research subject
• Deliverable
• Reviewer
• Acceptance decision

They do not identify the record from which the approximately 65-hour figures were later obtained.

This is not a declaration that no work occurred.

It is not a declaration that the attributed hours are false.

It is a finding that the reported invoices and later arithmetic do not allow the public to independently verify what was authorized, performed, reviewed, accepted, and preserved.

The City can resolve that question with finite records:

• Engagement and retaining authority
• Assignment records
• Exact service dates
• Contemporaneous time entries
• Task and matter descriptions
• Source-file and system-access records
• Research notes and workpapers
• Drafts and final deliverables
• Review comments
• Acceptance or approval
• Disposition and retention
• The source of the 65-hour figures

If Ridge was retained on an hourly basis, the audit should identify the authorized rate, time entries, task allocation, invoice calculations, and approval.

If Ridge was retained on a fixed-fee basis, the audit should identify the authorized scope, deliverables or milestones, completion criteria, evidence of delivery, and the basis for approving each $2,500 invoice. The public explanation currently joins a fixed $2,500 invoice amount to hours attributed later. The native engagement and payment records can establish which compensation structure actually governed.

The public does not need protected legal advice to know whether public work was authorized, documented, reviewed, paid, and retained. NBC 10 reported a City position that all Ridge work for the Law Department was privileged. The investigation does not demand the publication of properly privileged legal advice.

But a category-wide privilege statement does not identify:

• Which records exist
• When they were created
• Who created or received them
• Where they are retained
• Which invoice or assignment they support
• What withholding basis applies to each record
• Whether reasonably segregable information can be released

A record-level index can identify those facts without revealing protected substance.

Rhode Island’s Access to Public Records Act excludes certain attorney-client and litigation-related records from public status. It also provides that reasonably segregable portions of an otherwise excluded public record are to be made available after protected information is removed. If an entire record is treated as nonpublic, the public body must state in writing that no reasonably segregable portion is releasable.

Privilege may affect public disclosure.

It does not answer whether the records exist, who holds them, how they relate to the payments, how long they must be retained, or whether the City preserved the evidence supporting a public expenditure.

The performance audit should therefore determine:

Who requested, selected, retained, assigned, and supervised Ridge?

What compensation structure governed the engagement?

What record supplied the approximately 65-hour figures?

Were the hours recorded contemporaneously or reconstructed later?

What tasks, matters, source files, and systems correspond to the attributed time?

What work product was created?

Who reviewed and accepted it?

Which invoice did each assignment or deliverable support?

What records were retained, where, and by which custodian?

What information can be produced, logged, described, or segregated without disclosing properly protected legal substance?

The audit should test competing explanations.

Possible evidence-supported outcomes include:

• Contemporaneous records fully substantiate the approximately 195 hours.

• Work was performed and accepted under a fixed-fee arrangement, while the later hour figures were estimates rather than the original payment basis.

• Work product exists, but timekeeping, approval, or retention controls were incomplete.

• Records exist but were missed or inadequately searched during the initial records response.

• Records are lawfully withheld in whole or in part, but their identity, custody, and relationship to the payments can still be logged and audited.

• The public description, invoices, attributed time, and native records require correction or clarification.

• Another explanation is supported by the evidence.

The audit’s responsibility is to determine which explanation the records support.

Showing the rate is not showing the work.

PRESERVE • PRODUCE • RECONCILE • VERIFY

The Ocean State Current
Mayor Kenneth J. Hopkins
Nicole Renzulli
Paul McAuley for Cranston City Council
(Former) State Representative Christopher Millea
Allan Fung
GoLocalProv
What's going on in Cranston




Principal source — NBC 10 I-Team, May 6, 2026:

https://turnto10.com/i-team/cranston-mayor-ken-hopkins-campaign-consultant-city-work-ridge-data-consulting-michael-cotugno-law-department-may-6-2026

Rhode Island APRA definitions and exemptions:

https://webserver.rilegislature.gov/statutes/title38/38-2/38-2-2.HTM

Rhode Island APRA access and segregability provisions:

https://webserver.rilegislature.gov/Statutes/TITLE38/38-2/38-2-3.htm

Read the comments for the published source chronology, the exact calculation, authority and assignment controls, contemporaneous-time test, work-product chain, data-access evidence, review and acceptance, privilege and segregability, retention, competing explanations, and the precise audit demand.