Help · 180Connect

What keeps 180Connect running through the year, and who does it. Most of it happens on its own; the parts that need a person are the ones below.

Happens on its own — nothing to do

180Connect does these without anyone pressing a button:

Every night: backs up the database, fills in more detail on clients from the charity and company registers, and moves clients who have gone quiet to No response.
Every few minutes: sends scheduled emails and collects replies.
Every week: checks whether any client charity or company has closed or changed on its register, and emails a summary to the project's alert inbox.
Every month: downloads a fresh copy of the charity register (on the 1st) and the company register (on the 8th).

You only need to act if one of these stops, and the dashboard's System health card is where you would see it.

Admins clear the queues in Approvals & data quality. See the admin guide.
Someone reads the alert inbox of the project's Google account: a failed backup is reported there, and nowhere else a person is likely to look.

Whenever the branch starts a new round of outreach — a term, say:

Create an outreach cycle — Settings → Platform → Outreach cycles: a name ("Spring 27") and two dates. Team analytics then compares this round with the last; without one it can only show figures across all time.
Import new prospects if the list is running thin — see Importing charities.
CAMs check their outreach preferences and claim the clients they will work, as in the CAM guide.

180Connect's database goes to sleep if nobody uses the app for about a week — over the summer, for example — and does not wake by itself.

Before term starts, open 180Connect. If it will not load, follow The site will not load at all a few days before anyone needs it, not on the morning of the first send.
The nightly backup cannot run while the database sleeps, so its failure email is often the first sign.

Once a year, or whenever the people running the branch change:

Work through Handing 180Connect to a new committee together, before the outgoing committee loses its 180DC accounts.
Invite the new CAMs and admins, hand over leavers' clients, and suspend them.
Check Settings → Platform → Who can join still matches the people you invite.

Contact information review (in Approvals & data quality): personal contact details that have had no reply for two years collect here. Look at it at least once a term.
Feedback: an admin can ask the team for a new round of feedback on 180Connect whenever it would help.
The branch's data policies are documents, not settings. The data handling policy is reviewed every six months (next: 16 February 2027) and the data lifecycle policy once a year (next: August 2027). Ask a developer to update them if the branch's practice has changed.