The tasks that keep an organization in good standing, assigned for you
One task, from the schedule in spring to the approval in November
You define the task once
A trigger says what the task asks for: an uploaded financial report, the bylaws questionnaire, an updated board roster. It says which units or councils owe it, when it is created each year, and when it is due.
Every morning, Connect creates what is due to start
At 8am a job reads every trigger. A fixed date, an offset from July 1, or an anniversary of the last approval: whichever the trigger says, today's tasks are created.
The task lands on the unit that owes it
The person responsible at Meadowlark gets an email. The task appears in their My Tasks list beside anything they hold at other organizations.
The treasurer submits in September
They upload the report or fill in the form and submit. If they spot a mistake an hour later, they withdraw it and submit again.
It moves up to the council
The task lands on the council's approver. They approve it or reject it with a comment, and a rejection goes straight back to the unit.
Then the district, then the state
Each approval route with a person assigned gets its turn. An out-of-council unit skips the council and goes to the district. A route with nobody on it is passed automatically.
Monday morning, the past-due list goes out
Every Monday at 8am Pacific, each person holding past-due tasks gets one email listing all of them. Your office sees the same thing as a report, by council, district or state.
Approved, and written down
The task is done and everyone watching it is told. The log holds every action and every comment, and an approver can reopen it if something turns out to be wrong.
The annual filings are a calendar in someone's head
The state sends one email to a thousand units in August. Whether the treasurer at Clover Hill saw it is anyone's guess until the deadline passes.
The unit emails the council, the council forwards to the district, the district to the state. By November nobody can say where a given report is.
Chasing what is late is a job for someone with a spreadsheet and an afternoon, and the list is only right on the day it is made.
How a task knows who owes it, when, and who has to say yes
What the unit sends back travels that route one approver at a time, and comes back down if anyone says no.
See a year of required tasks created before anyone asks
Built for state PTAs and school districts. We set it up with you.
What every unit gets
Every task assigned to them, across every organization they belong to, with its due date and status.
The person responsible is told the day the task is created, not the week it is due.
For triggers that allow it, a unit starts a mid-year update or a Change of Status itself.
A submission can be pulled back until the moment it is approved.
A rejection says why, in the task itself, so the fix is the right one the first time.
Anyone can watch a task and hear when it completes, whether or not it is theirs.
And so much more
Frequently Asked Questions
Keep looking around
Board Rosters
Positions are defined once, at the top. Every unit, council and district fills in its own board each year, copies it forward at turnover, and the whole state or district can be exported in one file.
Compliance Reports
A compliance report for every level: which documents are in, which tasks are past due, what the IRS and the state charity registry say about each organization. Filtered, sorted, exported to Excel.
Documents
You define the document types. Each unit, council and district uploads what it owes, term by term. Everything is reviewable from the level above and searchable from the top, with a report of what is still missing.