How our tracker works

One picture: how a neighborhood push stays on track

Every initiative pulls together two streams — the problems we’re fixing, and the actions we’re taking (planned, then done). Here’s how they fit, and how they keep the status honest without anyone hand-typing it.

Anatomy of an initiative

The status up top is computed from the two streams below it — never typed by hand.

Initiative Active
Pond Health
At risk ⚠ Overdue 3 of 5 issues resolved
Next up Get a 2nd treatment quote · Johnny · overdue Jun 15 Working with Arbor
▲  computed from  ▲
resolved issues fill the bar
Issues
the problems we’re fixing
ResolvedStanding water
ActiveAlgae & odor
OpenTrash in the ponds
open due dates drive Overdue & Next up
Actions
the work — ours to do, and theirs to deliver
Open
Call: get a 2nd quote · overdue
Commitment: Arbor re-treats · ⚠ broken promise
Done
Email Arbor re: cattails

Resolve an issue and the bar moves. Let an open action slip past its by-date and the initiative turns Overdue — and an overdue Commitment reads as a broken promise. Tick an action done and it moves to Done — the history, no separate log. Nobody maintains the headline; the streams do.

The two streams, and how they differ

IssueWhat’s wrong — one concrete problem a neighbor can point at. Resolving issues is what moves the progress bar.
ActionA piece of work — a call, email, visit, task, or a commitment the other side made. Each has an owner on our side, the party on the hook, and a by-date. Open while it’s ahead of us (the dates the tracker watches), Done once it’s history. One stream, not two.

How an issue moves

Every issue carries one status — the state of that specific problem.

Open Scheduled Active Resolved then Monitoring or set aside as Cancelled
Open Reported. Nobody is on it yet.
Scheduled Work is booked for a date.
Active Someone is working it right now.
Resolved Fixed.
Monitoring Fixed — we are watching to be sure it holds.
Cancelled We decided not to act on it.

How an initiative moves

An initiative has its own forward lifecycle — the Stage.

Open Under Review Active Resolved or Declined
Open Raised. On the list, not started.
Under Review We are scoping it — what to do, who to ask.
Active We are driving it — doing the work or pressing the responsible party.
Resolved The goal is met.
Declined We looked and decided not to pursue it.

When every issue is done, the tracker suggests advancing the Stage to Resolved — a person always confirms; it never decides on its own.

Every signal — and where it comes from

Each answers a different question, so nothing gets muddled into one vague “status.” The italic note says whether you set it, or the streams do.

Stage Where is it in its life? — set by the community.
Health How is it going? InvestigatingOn trackAt riskStalled ⚠ Overdue — you set the dot; Overdue auto-flags from a past-due action.
Progress How much is done? — counted from the issues.
Next up The very next thing, and who owns it. — the soonest open action item.
Current status What’s happening right now, in plain words. — written for neighbors.
Lead Who on our side is steering the whole push. — picked from the roster.
Working with Which outside groups are involved. — rolled up from the actions.

The basics

What this isA shared, community-maintained record of neighborhood issues for Carramore in Westfield, Indiana — one calm place to see what’s been reported, what’s being worked on, and what’s resolved.
ViewingAnyone with the community password can browse everything and follow status — no personal account needed just to look around.
ReportingResidents can report a new issue any time — it posts right away, flagged Pending review until a moderator confirms it. Nothing’s blocked; the flag just keeps the shared record trustworthy.
AccountsContributing (adding or editing entries) uses a personal account so we know who made each change. It’s run by neighbors, not a company.