How to Turn a Read-Only Calendar Feed into Busy Time on Your Work Calendar

To make a read-only timetable block work availability, create separate busy events in the work calendar people check. The timetable remains controlled by its publisher. A scheduling tool that can check the feed directly may not need those extra copies.

The scheduling tool's conflict calendars

First inspect the scheduling tool. Some booking services let you select additional calendars for conflict checking. If your feed is available there and the plan supports it, selecting it may be enough.

Google's appointment schedules, for example, have a calendar-selection setting and plan requirements for secondary-calendar checks. Its availability guide describes those options. A colleague using another provider's free/busy view may still see something different, so test the actual scheduling route.

For your own reference view, use a calendar subscription without creating additional events.

Manual busy blocks for occasional commitments

Open the work calendar that colleagues or the booking service check. Create an appointment covering the time you are unavailable, give it a neutral title, and set its availability to Busy.

Keep the real class or shift in its original calendar. The work block only communicates availability. Avoid adding guests, forwarding confidential descriptions, or including private meeting links.

Manual blocks work for a handful of events, but you must keep them current. Move the work block when a shift moves. For urgent changes, check the employer's schedule directly.

For regular changes, use a copying workflow

An automation needs more than “when an event appears, create another event.” It also needs to recognize changes, cancellations, and existing copies. Otherwise the schedule can accumulate stale blocks.

If you already use an automation platform, check whether its calendar connectors support your feed, update detection, and deletion handling. An account-based connector may be more suitable than ICS when the source service offers one. Always inspect what data the workflow sends to the destination.

Avum supports ICS links as read-only sources for Sync Rules. A sensible first arrangement is:

Add the authorized feed link as a source connection.
Connect the Google, Microsoft, iCloud, or CalDAV account that should receive copies.
Select the relevant feed and writable destination calendar.
Set a neutral copied title and omit personal descriptions and locations.
Check the copied availability setting.
Start with a recognizable set of appointments. Compare start, end, status, and exposed details on their work copies. Ask a colleague to inspect free/busy or open the booking page.

The destination must allow event creation. The source feed remains read-only: a change to a destination copy does not reschedule the publisher's appointment.

Choose what deserves to block time

Not every event in a feed represents a commitment. A school feed may include deadlines and optional performances; a sports feed may contain matches you simply follow.

If the publisher offers separate feeds or filtered exports, choose the relevant one at the source. For more selective copying, use only filters you understand and test their results. Select school commitments separately from informational notices so an all-day announcement does not close every work slot.

A privacy-safe copy can still be too broad. Check dates and durations as carefully as titles.

Feed delays and stopping copies

When the publisher changes an event, check that the work copy follows. The feed must first be published and fetched, so no copying service can promise an immediate ICS update. Microsoft documents possible native-subscription delays in its subscription instructions.

Include recurring events and cancellations in the sync checks. When you stop copying, review cleanup while the service still has access and inspect the work calendar for stale blocks.

Ready to try feed-to-work-calendar copies? Start your free 30-day trial with Avum today.