A Guide for GC Students Managers
Welcome back! Building a cadence is the start — the real work is managing it once constituents are moving through the steps and your students are working their tasks. People go quiet, a meeting gets booked, a student graduates, and you need to keep the whole program moving without anyone falling through the cracks.
This guide covers the day-to-day management side: how to complete a cadence, how to pause one when life happens, what the delete button actually does (and when not to use it), how to reassign work between students, and how to use the schoolwide tasks view to see everything your team is doing in one place.
A quick refresher: where cadence management lives
Click Cadences in the left-hand menu to open the cadence management page. Each cadence has two tabs:
- Upcoming — your holding pool. Constituents are queued but the timer hasn’t started.
- Active — constituents are moving through the steps; due dates are live and the clock is running.
Almost everything in this guide happens on the Shared tab, where you’ll see each constituent’s name, when their cadence started, the step they’re on, which student they are assigned to, and any past-due steps. The actions below live next to each constituent’s name.
Complete a cadence
A cadence is “done” for a constituent in one of two ways.
It finishes on its own. When a student completes the final step in the sequence, that constituent has run the full cadence — there are no more steps to come due, and they drop off the active list of in-progress steps.
You complete it early. Sometimes the outcome arrives before the last step — a constituent replies or makes the gift on step two of five. There’s no reason to keep firing follow-ups at someone who already said yes. Mark the cadence complete for that constituent so the remaining steps stop generating tasks.
💡 Why this matters: Completing a cadence keeps your students focused on people who still need a touch. Leaving a “done” constituent active means your team keeps getting tasks for someone who’s already across the finish.
When a cadence is complete, the constituent’s history of completed steps stays intact, so you keep the full record of what outreach happened.
Pause a cadence
Pausing stops the clock without losing anyone’s place. Use it when you want to hold outreach temporarily but fully intend to pick it back up.
Good reasons to pause:
- A break in the calendar — finals, winter break, the gap between phonathon shifts.
- A constituent requests a break— they asked you to follow up “in a week or two”
- You’re re-pacing a segment — you want to slow things down before more steps come due.
While a cadence is paused, due dates stop advancing and no new steps come due, so your students won’t see fresh tasks for that constituent. When you’re ready, resume and the cadence picks up right where it left off.
Pause vs. complete: Pause when you’ll come back to it. Complete when the outreach is genuinely finished.
What the delete button does
This is the one to slow down on, because delete is not the same as complete — and it is not reversible.
Delete completely removes all trace of the constituent from that cadence. It wipes them out of the cadence entirely, including any completed-step history. For that reason, delete should only be used when a constituent was truly added by mistake — the wrong group got loaded, a constituent landed in two cadences by accident, or someone was queued who should never have been there.
Rule of thumb: If real outreach happened, complete the cadence so the record survives. Reserve delete for genuine mistakes — a constituent who was added in error and never should have been in the cadence at all. When in doubt, complete.
Reassign a cadence
Students cycle in and out — they graduate, switch shifts, take on a new segment, or just have too full a plate. Reassigning moves a constituent’s cadence (and the tasks that come with it) from one student to another so nothing stalls when your roster changes.
You can reassign at whatever scale you need:
- One constituent at a time — hand off a single person’s cadence to another student.
- A student’s whole load at once — bulk-reassign all of a departing student’s cadences in one move, so you don’t have to go person by person.
Reach for reassign when:
- A student is leaving or going on break and their in-progress constituents need a new owner.
- You’re rebalancing workload — one student is buried while another has room.
- A segment is changing hands as you reorganize your team.
When you reassign, the upcoming and current steps move to the new student, who’ll start seeing those tasks on their own Tasks page. The cadence itself — its steps, timing, and the constituent’s place in the sequence — doesn’t change; only who’s responsible does. The completed history stays attached to the constituent, so you don’t lose the trail of who did what.
See the schoolwide tasks view
Individual students see their own tasks. As a manager, you need the bird’s-eye view — every task, across every student, in one place. You’ll find it under SchoolWide Data → Tasks.
Use the filters to narrow the view — by student, by cadence, by due date, or by status (upcoming, due, past due) — so you can go from “everything” to exactly the slice you need to coach on.
Comments
0 comments
Article is closed for comments.