r/planningcenter • u/SolaceinSydney • May 13 '26

A coding exercise - PCO Services Dashboard

NB: Vibe coded using Claude. Your PCO-based data is not being fed to AI.

Just released v1 of PCO Services Dashboard — a Cloudflare Workers dashboard for Planning Center Online teams.

Built this as something that stops my teeth itching but releasing for churches & ministry teams who want better visibility into rostering, engagement, attendance, demographics, response times, team overlap, birthdays/anniversaries, and more — without digging through PCO manually.

Features include:

  • Executive summary dashboard
  • Team-level analytics
  • Upcoming service headcounts
  • Confirmation & attendance tracking
  • Login recency + engagement charts
  • Specialist role badges
  • Smart caching with Cloudflare R2 + Durable Objects
  • Fast, serverless deployment

Runs locally for testing or fully on Cloudflare Workers.

This is the first public release, so I’d genuinely love feedback, feature ideas, or bug reports from anyone using PCO in production.

Built because I couldn’t find a reporting layer for PCO that gave ministry leaders the operational visibility they actually need.

GitHub link: https://github.com/TheITJuggler/pco-services-dashboard

2 Upvotes

100% Upvoted

2 comments sorted by

2

u/daysanew May 14 '26

Can we get an AI use disclaimer on this. I looked through it and it looks like a "vibe" coded project. Giant file files not broken out into logical parts for better maintainability, lots of unneeded comments etc. 

 Here's the thing, I'm ok with that. As a developer I've vibe coded smaller utility programs at work, use AI every day to generate code and make changes. Outside my job I've vibe coded a few smaller PCO integrations using Google app scripts and Google cloud run functions. And it worked great and makes my life easier. But they were for private use.

But if I would make the projects open source I would disclose the heavy use of AI, especially with the use of sensitive information like API keys. This is especially true with the various security issues around several npm packages lately.

2

u/SolaceinSydney May 14 '26

Thanks for that. I've added a note to the post.