Keep the plan with your team's files or calendar

Free Files and calendars · One-time purchase

Keep a workshop plan in a shared folder, or let its activities appear in a calendar your colleagues already use. Tidigar edits the plan; the file or calendar provider supplies access and synchronization. Reading is free; each writer needs the Files and calendars one-time purchase. You do not need a Tidigar Business organisation for this workflow.

If colleagues only need to follow dates from a Business plan, a screen's calendar subscription publishes a read-only view without moving the plan's storage. Publishing requires Tidigar Business (paid); subscribers need no Tidigar account or Apple purchase. The file/calendar workflow below stores the whole plan in a writable calendar and can read supported calendar edits back into Tidigar.

Read for free or keep an app copy

Use Open roadmap file… or search calendars in the library. Valid external plans open for free reading. To edit without changing the source, choose Keep a copy in the app above the plan. The copy gets a new identity, and the source remains untouched. Purchase Files and calendars to edit the source; Export without Tidigar only controls image and print attribution. These Apple purchases are prepared for an upcoming release; App Store availability still needs verification.

Start with a small workshop

This plan has preparation work, a workshop and a milestone. Open your own copy in the Tidigar app on iPhone, iPad or Mac before trying the storage steps. Open in Tidigar in the frame opens an editable browser copy; the frame demonstrates the plan, without accessing your files or calendars. You can also create a new app roadmap and add these activities yourself.

New app roadmaps start as documents. Open Properties and check Storage before moving one. A Business plan must first move to the app's documents; see Library and storage. The free browser does not open or save roadmap files or calendars.

Save the workshop in a calendar

1. In the app document's Properties → Move to…, choose A calendar. This starts the app's calendar save.
2. Allow full calendar access when asked. Reading is needed as well as writing, so Tidigar can check the plan before saving. If you previously denied access, use the offered Settings or System Settings action to change calendar permission, then try again.
3. Wait for calendar creation, writing and verification to finish. Tidigar creates a new calendar named tidigar - A workshop in your own storage; it does not put the plan into an ordinary calendar you already use.
4. Return to the library and check the workshop's calendar storage label. Open it, change Draft the agenda from 25 to 50 percent, and let saving finish.
5. Open your calendar app and look for the new calendar. Draft the agenda occupies 7–9 June 2027 as an all-day event. Workshop complete appears on 15 June as a short midday event.

To work together, share this new calendar through your calendar provider and give colleagues the access they need. After accepting that provider's invitation and making the calendar available on their Apple device, they open Tidigar's library and choose Plan together → Read from a shared calendar, or use the calendar icon to search. A readable, valid Tidigar plan appears as a card. They open that same calendar plan rather than creating another one with the same name.

A colleague with read-only calendar access can read the plan in Tidigar but cannot save changes to it. A purchase does not grant provider permission. A Business invitation or a copied plan link does not share a calendar; its provider controls that access.

Keep the workshop in a file instead

Use a separate app document for this exercise if you already moved the workshop to a calendar.

1. Open the document's Properties → Move to… → A file.
2. In the system save picker, choose a location you control. For collaboration, choose a folder shared through your file provider, with write access for the people who will edit it. Save the proposed .tidigar file.
3. Wait for Tidigar to read back and verify it. Check the file label on its library card, then reopen that card and edit Invite participants. Subsequent saves go to the chosen file.
4. Ask a colleague with access to that folder to use Plan together → Open roadmap file… in their app library and select this same file. On Mac, opening the roadmap file from Finder also opens it in place.
5. Let both devices' file providers finish syncing before checking the changed title on the colleague's device.

Share file in the library's Plan together sheet is marked Coming later. Use Move to… → A file to create the file, and Open roadmap file… to open an existing one. Sending someone a separate downloaded attachment gives them a separate file; it does not keep both people on the same shared roadmap.

Return from a calendar to an app document

With the calendar plan open, open Properties → Save as document. Tidigar reads the calendar, saves and verifies a document, then makes that document the active storage on this device.

The old calendar remains. This device's later document edits no longer go there, and colleagues still using the calendar will not receive them. Tell your team which place to continue using. A calendar or document kept under Previous storage is an earlier location, not a second autosave destination.

How files and calendars work in detail

The provider carries the changes

A shared folder synchronizes whole files; a calendar provider synchronizes events. Tidigar saving successfully means it has written and checked its storage, rather than proving that another device has received it. A slow, offline or unavailable provider can delay what colleagues see.

Open a plan on the other device and check a recognizable edit after synchronization. A library thumbnail or an old card alone does not prove that current provider content can be read. Files that moved, disappeared or lost permission may fail to open; read the error before assuming the last displayed plan has been saved there.

The Apple apps use calendars available through the device's calendar accounts. An account appearing there does not establish that every provider preserves Tidigar's data correctly. Microsoft 365/Exchange and Google/CalDAV have not been verified for this workflow. Provider transport and signed-app calendar links need their own verification; a locally saved plan alone cannot establish them.

A calendar contains a whole plan

One Tidigar calendar holds one project, including its activities, milestones, periods, dimensions and saved views. Some supporting events are metadata placed on 1 January 2000. Leave those events and Tidigar event URLs intact: the name of an event or calendar does not identify the stored plan.

Activity events are all-day and non-recurring. Their title, description and all-day dates can be edited in a calendar client and read back into Tidigar. An ordinary event you add without Tidigar's identity is left alone; it does not become a new activity. A milestone uses a short midday event but represents a date in the plan, rather than an appointment time.

Making an activity timed or recurring, damaging metadata or introducing duplicate project records can stop the calendar loading or saving. Tidigar keeps the latest valid plan rather than treating unreadable data as an empty roadmap. Renaming the roadmap does not rename its calendar. Unrelated events remain outside Tidigar's edits, and deleting a roadmap removes only its verified project events, never the calendar itself.

Changes can arrive separately or conflict

A calendar provider may deliver a save event by event. Tidigar can wait for more data during a partial reload. When settled content has broken references, it repairs supported cases, such as dropping a dependency on a deleted activity or moving dependent work later. It reports repaired records and waits for a quiet period before writing those repairs back.

File changes can be combined with your edits when a known shared starting version exists. Otherwise, conflict handling can preserve a separate copy. Calendar providers settle individual event versions before Tidigar reads them; Tidigar cannot recover versions the provider has already discarded. See Changes made elsewhere for merge choices and conflict copies.

Personal reading state, such as your selected view, scroll position and folded summary rows, stays on your device. Saved view definitions belong to the plan and travel with it; see Timeline views.

Check errors before restoring or retrying

Open a storage warning to read its reason. The library's Storage log also records failures; for a calendar, Refresh now reads again. Revoked permission, a read-only provider, an invalid event or a conflicting external edit can prevent saving even while a plan remains visible.

For a blocked writable calendar, Restore calendar from Tidigar can replace this project's calendar records with the open plan. Read the proposed counts of created, updated and deleted records before confirming. This discards the calendar edits being replaced and leaves unrelated events alone. It is a deliberate recovery action, rather than an automatic retry.

A move becomes active only after the destination has been read back and verified. Cancelling the file picker leaves the document active. If a move created a destination but verification failed, Tidigar retains that unfinished transfer and can block another attempt instead of silently creating a second calendar or file. Keep the source and read the error; a failed transfer is not a completed move.

Removing a card and purchase access

For a linked file, Remove from library… forgets its card and leaves the file where it is. This differs from deleting a calendar roadmap's project events. Neither action changes the provider's sharing permissions.

Reading files and calendars is free. Choose Keep a copy in the app in the editor to edit an independent copy without touching the original. Writing the source requires the Files and calendars one-time purchase and provider write permission. A refund or revocation stops external writes and retains pending content for a local copy. Restore purchases uses the same Apple Account on iPhone, iPad and Mac.