How calendar writeback works for your church team

What is calendar writeback?

When a pastor approves a follow-up reminder in FlockConnect, calendar writeback can place that reminder as an event on the calendar of the person it is assigned to. The point is simple: the person who needs to make a call or a visit sees it where they already look, instead of inside one more tool.

Nothing is written until a person approves it. FlockConnect drafts the reminder, you review it, and only an approved reminder becomes a calendar event. It never writes to a calendar on its own.

• Writes to Google and Microsoft calendars only, no other providers.
• Writes only to the personal calendar of the person a reminder or booking is assigned to, never to a shared church or team calendar.
• Event titles and descriptions are generic and localized, with a secure link back to FlockConnect.
• Sensitive pastoral details, names, notes, and assessment answers never appear in the calendar event.
• Nothing is written until a person reviews and approves the reminder.
• Confirms write access when a destination is added, and shows a calendar that later stops accepting reminders in Integration Health.

Which calendars can it write to?

FlockConnect writes to Google and Microsoft calendars. No other calendar providers are supported for writeback. Within those two, a reminder lands only on the personal calendar of the person it is assigned to, and a booking only on the calendar of the staff member who was booked. FlockConnect does not write to shared church or team calendars. If that person has no calendar set up for FlockConnect, no calendar event is written, and the follow-up stays in FlockConnect.

When a destination is added, FlockConnect confirms it can actually write there. If it cannot, the destination is switched off and never used, and the person adding it sees why. If a saved calendar later stops accepting reminders, an owner or admin sees it in Integration Health.

What does the calendar event actually say?

The event uses generic, localized text. A title reads something like "FlockConnect follow-up" or "Care team reminder," and the description is a short line pointing to a secure link back into FlockConnect, where the real context lives.

Sensitive pastoral details never go into the external calendar copy. No names of who is being cared for, no notes, no prayer details, no assessment answers, and no health information appear in the event. Anyone who can see the calendar sees only that a follow-up is scheduled, not why.

How does approval state work?

Calendar writeback is tied to an approval. FlockConnect can draft a calendar reminder for a follow-up, but a person reviews and approves it before anything is written. The approval is the gate.

If an approved follow-up is later completed or the reason for it goes away, FlockConnect can clear the matching calendar event so a stale reminder is not left sitting on someone's week. The source of truth stays inside FlockConnect.

Why only personal calendars?

A reminder belongs to the person who has to act on it, so it goes on that person's own Google or Microsoft calendar and nowhere else. A shared church or team calendar would show it to everyone who can see that calendar, whatever they are allowed to see in FlockConnect, so FlockConnect does not offer one.

The event text is generic either way, and the secure link is what carries someone into the details; only signed-in FlockConnect users see them. When you set up your own calendar for FlockConnect, choose one only you use, because anyone who can see that calendar sees the reminder titles too.