Shift Schedule

Help

How this app works.

Add your aliases first

In Settings, add every way you appear on the schedule sheet (last name, initials, a nickname). Uploads use this list to find your shifts — without it, nothing will match.

Bring your own API key

This app has no shared key. In Settings, pick Claude, OpenAI, or Gemini and paste a key from that provider's console. It's stored only in this browser and used to call that provider directly. Claude is the best-tested option; the others should work too.

Upload a PDF, screenshot, or photo

Your AI provider reads the schedule and pulls out just your shifts. You always get to review and fix the results before anything is saved — a self-check also flags anything that doesn't match your aliases.

Everything stays on this device

There are no accounts. Your name, aliases, key, and shifts live only in this browser's storage. A coworker using the same app on their own phone has their own separate, private copy.

Connect Google Calendar (optional, one-time setup)

This also has no shared key — it uses your own Google sign-in, set up once in your own free Google Cloud project. Takes about five minutes.

  1. Go to console.cloud.google.com and create a new project (or pick one you already have).
  2. APIs & Services → Library — search “Google Calendar API” and enable it.
  3. APIs & Services → OAuth consent screen — choose “External,” fill in an app name and your email, add the scope calendar.events, and add your own Google account as a test user.
  4. APIs & Services → Credentials → Create Credentials → OAuth client ID — application type “Web application.” Paste the redirect URI shown in Settings under Google Calendar sync into “Authorized redirect URIs,” then create it.
  5. Copy the Client ID (ends in .apps.googleusercontent.com) and paste it into Settings → Google Calendar sync, then tap Connect.
  6. If Google says the sign-in failed rather than showing a consent screen, come back and add the Client Secret Google also generated — the field for it is right below Connect.

While the consent screen is in “Testing” mode, only accounts added as test users can connect, and Google may expire the connection after 7 days. Switch it to “In production” (same OAuth consent screen page) once it's working to avoid that — for this narrow scope it shouldn't require Google's review.

Connect Outlook Calendar (optional, one-time setup)

Same idea as Google Calendar sync, using your own free Microsoft app registration instead. Takes about five minutes.

  1. Go to portal.azure.com → App registrations → New registration.
  2. Name it anything. Under “Supported account types” choose “Accounts in any organizational directory and personal Microsoft accounts” — the broadest option, so both work Microsoft 365 accounts and personal Outlook/Hotmail accounts can connect. Leave the redirect URI blank here → Register.
  3. Authentication → Add a platform → Single-page application — paste the redirect URI shown in Settings under Outlook Calendar sync, then Configure.
  4. API permissions → Add a permission → Microsoft Graph → Delegated permissions — search “Calendars” and check Calendars.ReadWrite → Add permissions.
  5. On the app's Overview page, copy the Application (client) ID and paste it into Settings → Outlook Calendar sync, then tap Connect.

No client secret is needed or used — “Single-page application” is Microsoft's own no-secret client type. Personal Outlook/Hotmail accounts should connect with no extra approval; a coworker on a company-managed Microsoft 365 account might occasionally need their own IT admin to approve a new app the first time, depending on that organization's policy — nothing that can be changed from here.

✦

Add to your home screen

On iPhone: tap the Share icon in Safari, then “Add to Home Screen.” It opens full-screen with its own icon, like a native app.