Send the plan. Keep the context.

Before you export

Check the project name, the intended dates and the view you are sharing. Follow one changed task through the schedule and make sure the export represents the plan you want to discuss. If the conversation is about cast, review the shoot-day assignments and the relevant DOOD view too.

Choose the level of detail the recipient needs. A whole-production timeline can explain the shape of the work; a schedule table can answer an exact-date question. Do not expect a busy collaborator to reconstruct your intent from a file with no explanation.

Choose the format deliberately

Use PDF when a fixed visual reference is the priority. Excel or CSV is useful when the next conversation will happen in a spreadsheet. JSON provides a structured production record. These are different outputs, not interchangeable guarantees about what another tool will understand.

A standard JSON schedule export is not the same as a full native project backup, and this guide does not promise a round-trip import. Check the actual recovery features available in the build you use before relying on a file to restore a project. Keep important records outside browser storage.

Include the context that travels with it

State the revision, the important changes and the specific question for the recipient. If a date is provisional, say so. Keep the file you sent so that a later conversation can refer to the same version instead of two people reading different plans.

Martini stores the working project in the current browser. Exports do not create a live shared workspace or automatically sync edits back from someone else’s spreadsheet. After feedback, update the source plan, review it and send a fresh export when needed.

• Identify the project and revision.
• Summarise the changes and open decisions.
• Confirm that the recipient has the current file.
• Keep a copy before changing devices or clearing browser data.