Mooiev
PricingResourcesBlogGet started

MOOIEV BLOG

Film Production Notes: Comments, Tasks and Canvas in Mooiev

Keep project notes, scene discussions, assigned tasks, Canvas ideas and activity in the right context, with a practical production handoff example.

In this article 6 sections

Give each kind of note a clear home

A production note may describe the whole project, question a line of dialogue or ask somebody to prepare a prop. Those are different jobs. Put the shared approach in project notes, discuss a particular scene or section in contextual comments, and create a task when somebody needs to complete an action.

In Mooiev, these tools sit alongside the production material. The purpose is to make a decision findable later. A conversation is only useful to the production if the relevant people can tell what it concerns and what happens next.

Use project notes for the brief and shared constraints

Project notes belong with Overview. Write the concept, important references and constraints that apply across the film. A short brief might explain that AFTER THE TIDE should favour harbour ambience, practical workshop light and close observation of physical work.

Keep this brief readable. When a constraint becomes a specific job, such as confirming access to the pier, move the action into an assigned task and keep the resulting decision in the appropriate place. A general note should not become a hidden list of work nobody owns.

Discuss the scene or section in context

The collaboration panel provides Comments, Tasks and Activity for the current work. A comment can include a reply so the team can follow the discussion. Scene-linked screenplay comments add a more precise anchor when the issue concerns a particular scene.

Write the observation and the proposed change: “The recorder insert should happen before Mara sees the notice, so the audience understands why she came.” That gives the director something concrete to accept, revise or reject. “Make it more cinematic” leaves both the location and the action unclear.

Turn a request into an assigned task

Create a task for an action with an intended owner. “Photograph the recorder controls for continuity” is a task; “the recorder must look worn” is a reference note. Use status changes to distinguish work still needed from work completed or approved.

The task controls respect project roles. Check who can assign or approve work rather than assuming every member has the owner’s controls. After completion, record the useful result where the next person needs it: a prop image in World, an updated shot note or a checked production document.

Production needUseUseful result
Agree the film’s approachProject notesA short shared brief
Discuss a scene changeContextual comment and repliesA recorded decision
Ask for preparationAssigned taskAn owner and visible progress
Arrange visual ideasCanvas sticky noteA spatial connection to shots

Use Canvas when relationships matter

Canvas lets you arrange shots and sticky notes in space and connect ideas. Place a note beside the relevant shot or sequence to explain an insert, transition or relationship between frames. Keep the text short enough to read while reviewing the board.

A Canvas note is not automatically a booked item, approved expense or completed task. If a visual idea adds a setup or prop, update the actual shot plan and production records after the team agrees to it. Use the board to make a relationship visible, then finish the handoff.

Use messages for the conversation and the project for the decision

Direct messages make it easier to talk to a collaborator. Return the agreed production decision to the relevant project context so the rest of the team can find it. Activity can help the team review changes, but a log entry does not explain the reason for every creative choice.

Before a handoff, ask three questions: can the intended person open the material, can they identify the affected scene or shot, and can they tell what they must do? Clear notes and access permissions answer those questions more reliably than a long conversation detached from the work.

Use direct messages and connections

Review crew roles and permissions

Explore the shared project context