Skip to content

Call sheets

A call sheet in CineLog is the per-day production plan: the schedule, the location, the people, the weather, and the message that goes out with the email. It’s tightly coupled to the rest of the project — the schedule is the same data as Production view for that day, and the personnel come straight from Cast & Crew.

This guide assumes The basics and Linear vs Production.

Call sheets are day-based — one per Production Day. They appear automatically as sub-entries under Call Sheets in the sidebar; click a day to open its call sheet.

When you create a new call sheet, CineLog seeds it from your previous days rather than starting blank:

  • If a previous day used the same location, your new call sheet starts with that location’s crew and addresses already filled in.
  • Otherwise, if you have three or more previous call sheets that share the same crew, those crew assignments carry over.
  • Otherwise, the call sheet clones from the immediately preceding day.
  • If none of those apply (first day of the project), you get a blank call sheet.

You can change anything that was seeded; it’s just a starting point.

The header runs across the top and carries the day’s key information at a glance.

The single most important field. Sets the base start time for the day (e.g., 08:00). Click it to edit. This time anchors the schedule’s time cascade (below) and is the default time emailed to each recipient unless they have a personal call time set (see Personnel).

The production date. Optional — it’s pulled from the shot list’s Production Day, but you can set or override it manually. Shown in the header and on the exported PDF.

The left side of the header carries your company profile (name, address, phone) and logo. Upload the logo once at the workspace level via the company profile dialog; it then appears in every call sheet’s header and on emailed PDFs.

Right side of the header. Pulled from the project entity — no separate edit here.

Open the display settings popup from the call sheet’s top menu to toggle:

  • Time format — 12-hour (8:00 AM) or 24-hour (08:00).
  • Temperature unit — °F or °C.

Both choices are per-user and persist across sessions.

A reorderable list of named shooting locations for the day. Each location has these fields:

  • Set name and address. Optional note alongside.
  • Parking. A parking name + detail field (where the trucks go, where the crew parks).
  • Hospital. Nearest hospital name and address — important for safety/emergency logistics.

Add and edit via the location overlay. On desktop you can long-press a location row and drag to reorder; on phone, double-tap a row to open the edit overlay.

Google Places autocomplete is wired into the set-location address field. Start typing and you’ll see suggested places; picking one populates the address and stores the coordinates so the weather lookup (below) has a location to work with.

To hide the whole locations section from the call sheet (e.g., when the location isn’t locked yet), use the section visibility toggle in display settings.

The schedule is the Production view filtered to this day. The shots and banners on the call sheet are the same objects as in Production — reordering or editing them here is the same as reordering or editing them there. The gesture grammar is identical to anywhere else in the app.

Three columns: start time | scene + shot | estimated duration.

Banners are non-shot rows that mark meal breaks, company moves, wraps, or other schedule markers. They exist only in Production view and on the schedule. Add a banner from the toolbar (or Cmd / Ctrl + N in Production); name it (“Lunch”, “Company move”), set its duration.

Inserting a banner mid-scene splits the surrounding scene at the banner — see Linear vs Production for the full split-and-merge behavior.

You don’t enter a start time for every row. The schedule has a cascading time engine: it reads the general call time, then walks down the list adding each row’s estimated duration to compute the next row’s start time.

If a row’s explicit start time lands earlier than the running clock would put it (an overlap), the start time is highlighted red. A yellow highlight flags a row with a zero-length estimate. The row’s own estimated duration is what controls the next row’s start time.

Desktop: long-press a banner or shot row and drag. Mobile: double-tap a row to open the edit overlay (no inline drag). Reorders persist back to the Production view, since these are the same objects.

The schedule section can’t be hidden — it’s always shown.

If the call sheet has a location with coordinates, CineLog fetches the day’s weather automatically when you first open the call sheet. The display shows:

  • Temperature, with the day’s high and low
  • Sunrise and sunset
  • Conditions

The temperature unit follows the display setting (°F / °C). To override or manually enter weather (forecast wasn’t fetched, or you want to use a different source), tap the weather block and edit. The override is stored on the call sheet and reused on every reload.

Five distinct sections, each with its own role and layout. People come from the project’s Cast & Crew; the call sheet references them, not copies them.

A quick-reference list in the header’s second row showing the day’s key roles (Director, DP, 1st AD, Producer, etc.) with names and phone numbers. Up to about six slots. Click the edit button to pick which roles appear.

Three-column table — avatar, name, role. Add talent from the project’s contacts. Click any row to add notes or set a call time. Long-press a row to reorder.

The largest section, grouped by department. On desktop, a multi-column grid; on phone, a vertical card list. Each crew member shows avatar, name, role, and (if set) call time and phone. Same edit pattern as Talent.

Three-column table for client reps, agency producers, executives — anyone outside the production team who needs to be on the sheet. Same edit pattern as Talent.

Grid or expandable list of background performers. No avatars in this section (intentional — keeps the layout tight when there are many extras).

Every person row in Talent, Crew, or Clients can carry notes. They show on the call sheet and on the exported and emailed PDF, visible to everyone who receives that sheet — so use them for shared instructions (“park at side entrance,” “wardrobe fitting before call”), not private messages.

Each person can also have a personal call time that overrides the general call time. When you send the call sheet, each recipient’s email and PDF highlight their personal time. People without a personal time get the general call time.

Each person controls their own profile picture from their Account screen — the project owner can’t upload one on behalf of a contact. Until someone uploads their own picture, they’re shown with a color-coded initials avatar (deterministic from their user ID, so the same person always gets the same colour across every call sheet).

For contacts who haven’t joined CineLog yet (you’ve added them to Cast & Crew but they haven’t accepted the invite), the initials avatar is the only option. Once they sign in and upload their own picture, it propagates everywhere they’re referenced — including past call sheets they were on.

Toggle “Profile Pictures” off in display settings if you want all-initials avatars regardless.

Each section (Locations, Clients, Talent, Crew, Extras) can be hidden from the call sheet via the display settings popup. The toggle hides the section from both the UI and the exported PDF.

A rich-text block for the message that goes out alongside the call sheet PDF. Same message for all recipients — for individual instructions use per-person notes above.

The editor toolbar supports:

  • Bold, italic, underline.
  • Color. Eight curated swatches (White, Gold, Copper, Rose, Lavender, Sea Glass, Sage, Parchment).
  • Image embed. Click the image button, pick an image. Uploads to CineLog’s CDN, up to 2 MB, JPEG / PNG / WebP only. The image URL is embedded in the message and appears in the email body.
  • Clear formatting.

The rendered email applies the same formatting on the recipient side. The server sanitizes the message before sending — only the allowlisted formatting tags pass through.

A footer field for production-wide notes, safety reminders, COVID protocols, or anything you want at the bottom of every recipient’s PDF. Appears centered, uppercased.

When the call sheet is ready, Send in the top menu bar opens the send dialog.

Two steps:

  1. Recipients. A list grouped by section (Talent, Crew, Extras, Clients), sorted by department and role. Everyone with a call time on the sheet is preselected by default. Bulk toggles let you select or deselect a whole section at once.
  2. Message. Optional additional message specific to this send, layered on top of the crew message.

Each recipient gets:

  • A personalised PDF with their call time highlighted.
  • The crew message (rich text) plus any optional message you added.
  • Any per-person notes on the sheet, which print on the call sheet PDF itself (they are part of the sheet everyone on that call time receives).
  • A confirmation link — a unique token-protected URL at links.cinelog.com/confirm-call-sheet/<token>. Clicking the link opens a CineLog-branded portal where they tap “Confirm” to acknowledge receipt.

Open the Sendouts page from the call sheet’s top menu (or navigate to …/call-sheets/<day>/sendouts) to see who’s been sent the call sheet. Recipients are grouped by send batch — each press of Send creates a new batch, so re-sending after edits preserves the full history. Each batch header shows an “N / M confirmed” tally.

Each recipient row shows:

  • Delivery status — one of:
    • queued — handed to the mail provider, not yet sent.
    • delivered — accepted by the recipient’s mail server.
    • opened — the recipient’s mail client opened the message.
    • bounced — the recipient’s mail server rejected it (bad address, full mailbox).
    • failed — the mail provider couldn’t send.
  • Confirmation timestamp — once they click their link.

Delivery and confirmation are independent: an email can be delivered without being confirmed (the recipient hasn’t opened or hasn’t clicked yet), or confirmed quickly (they were on email when it arrived).

To prevent runaway sends, CineLog enforces two ceilings:

  • Per call sheet: up to 10 sends per hour.
  • Per workspace: up to 1000 emails per month.

These are generous for normal use; you’ll only hit them if something’s looping or you’re running an unusually large operation.

You can re-send the same call sheet after editing it (a script change, a crew swap, a wardrobe note). The new send creates a fresh batch on the Sendouts page; previous batches stay intact for the audit trail.

Two ways to get a PDF, depending on the use case:

Cmd / Ctrl + P or the export button in the top menu opens the export dialog. You can set page margins (top, bottom, left, right in points), then export. Rendering is local — no upload, no server-side render — so it works offline. Useful when you want a PDF to distribute outside the email flow (Slack, WhatsApp, hand-off in person).

When you press Send, the server generates a personalised PDF for each recipient with their call time highlighted and their per-person notes attached. You don’t trigger these directly — they’re a side effect of sending.

Both export paths respect display settings: hidden sections stay hidden, the temperature unit and time format are applied. Large media is downsampled.

International scripts (Arabic, Hebrew, Devanagari, CJK, Thai) render correctly via font fallbacks.

Editing and sending call sheets are gated by the project’s call_sheets ACL resource. Viewers can see call sheets they have access to; only roles with edit permission can modify the schedule, people, or message; sending requires the same edit permission.

Editing call sheets works offline — changes save to the local database and sync when you reconnect, like everything else in CineLog. Sending requires connectivity (it’s an outbound email flow). Local PDF export works offline.

“My new call sheet pre-filled itself with stuff I didn’t ask for.” That’s the smart-seeding behavior. CineLog copies from a matching previous call sheet (same location → same crew + locations, otherwise the immediately preceding day) so you don’t start from a blank sheet every day. Edit or clear whatever you don’t want.

“My schedule order doesn’t match Production view.” It should — they’re the same data. If they differ, the sync indicator probably has pending changes. Wait for it to flush.

“How do I change a crew member’s profile photo?” You can’t — profile pictures are controlled by each user from their own Account screen. As a project owner you can’t upload one on their behalf. People who haven’t joined CineLog yet show the initials avatar; once they sign in and upload, their picture appears across every call sheet they’re on.

“The schedule time is highlighted red / yellow.” Red means the row’s start time lands before the previous row finishes (an overlap). Yellow flags a row with a zero-length estimate. Adjust the durations or the start time to reconcile.

“Weather didn’t load.” The auto-fetch needs a location with coordinates. Set a location via Google Places autocomplete (so the lat/lng is captured), then reload the call sheet. You can also enter weather manually.

“A crew member says they didn’t get the call sheet.” Open the Sendouts page for that day and find their row. delivered or opened means it left CineLog and was accepted by their mail provider — the issue is downstream (spam folder, mailbox rules, deleted by accident). bounced or failed means the email never reached them; check the address in Cast & Crew and re-send. queued means it’s still on the way; give it a minute.

“The confirmed count isn’t going up.” Confirmation requires the recipient to click the link in the email. Delivery alone isn’t enough.

“I hit a send limit.” You’ve exceeded 10 sends in the past hour for this call sheet, or 1000 emails in the past month for the workspace. Wait it out or get in touch if you need a higher limit.

“My crew message image didn’t upload.” Check the file: under 2 MB, JPEG / PNG / WebP. Other formats and oversize files are rejected.