Help Docs

How to write briefs, scripts and production notes where the whole team can find them in Clipflow

Write content briefs, scripts, hooks, and production notes inside the project where the team can review and approve them.

Updated

Write with your whole team using project pages

A page is a live document that lives where the work happens. Outlines, scripts, hooks and production notes no longer sit in a Google Doc nobody can find; they stay attached to the project, asset or task they describe.

Work together in the same page in real time. Your team can see who else is editing, changes sync live, and comments stay on the relevant paragraph instead of disappearing into a message thread. Pages also carry the same review states as media, so a script can be approved the same way a cut is.

Why keep writing in the project?

Common problems solved:

  • Scripts in one tool, footage in another, feedback in a third
  • Editors working from an outdated document
  • No record of what changed between drafts
  • Notes that vanish when whoever wrote them leaves

What you get:

  • The script sits beside the footage it produced
  • Comments land on the paragraph in question
  • Revisions you can go back to
  • A review state, so “is the script approved?” has an answer

Choose the page type that belongs with the work

Pages are typed so Clipflow can put each document in the context where someone will need it. Choose the type based on the work it supports, not just the words you are writing.

Project documents

Use these to shape the content before and during production:

Page type Used for
Outline The structure before scripting
Script The script itself
Hook Hook options for the opening
Production notes Shot lists, locations, gear and shoot direction
Idea outline Notes on an idea before it becomes a project

Asset documents

Record notes against in-progress project assets, so every note is where you need it when you need it.

Page type Used for
Packaging Set the rules, structure and design for every video
Publishing Keep captions and publishing direction against posts
Thumbnail Give designers instructions or a thumbnail brief

Working documents

Use these where the work is being done or referenced:

Page type Used for
Tasks Detail and instructions attached to a specific task
External links Notes against a linked reference or resource

Team documents

Page type Used for
Organization procedures and SOPs Reusable instructions available wherever the team needs to follow the same process

Organization procedures are worth calling out. Write an SOP once and attach it where the task needs it, so an editor gets the instructions inside the task rather than searching through an onboarding document.

Step 1: Create a page

  1. Open a project and go to Pages.
  2. Choose Add page.
  3. Pick the type.
  4. Give it a title and start writing.

Pages autosave. There is no save button to forget.

Step 2: Write and format

The editor handles the usual: headings, bold, italic, lists, links, quotes, and code. Paste from a doc and formatting comes across.

Keep one page per job. An outline and a script in the same page means neither can be approved on its own.

When more than one person is working, stay in the same page. Clipflow shows who is present and syncs edits live, so a producer, writer and reviewer can work from one current version instead of passing document copies back and forth.

Step 3: Get feedback

Comment on a page the way you would on a media file. Mention a teammate to pull them in, or mention an agent to get a draft or a critique. See AI Agents.

Comment notifications follow your normal settings. See Notifications.

Step 4: Move it through review

Pages carry the same five states as media:

State Meaning
Pending Waiting to be looked at
Changes required Feedback left, back to the writer
Reviewed Looked at, not final
Approved Cleared to be produced from
Declined Not proceeding

Approving the script before the shoot is what stops an editor cutting from a version somebody changed on Tuesday.

Step 5: Use revisions

Create a revision before a significant rewrite. You keep the earlier version, which matters when a client decides the third draft was better than the fifth.

Duplicating a page is the other move worth knowing. It is how a strong outline becomes the starting point for the next project in a series.

Sharing pages externally

A page can be added to a share link, so a client reviews a script without an account. See Share Links and External Feedback.

Tips and best practices

  • Write the hook page first. A weak opening is cheaper to fix before the shoot than after the edit.
  • Put SOPs in organization procedures, not in a project. A procedure copied into fifteen projects is fifteen things to update.
  • Approve the script before production starts. It is the single largest source of rework.
  • Revision before a rewrite, not after. Nobody remembers to snapshot a draft they already replaced.
  • Templates carry pages. A project template can include an empty outline and script so every project starts with the same shape. See Creating Project Templates.

Frequently asked questions

Can two people edit a page at once?

Yes. Edits sync live and everyone sees who else is in the page.

Can I see what changed between drafts?

Revisions let you go back to an earlier version. Create one before a large rewrite.

Can a client see a page?

Only if you add it to a share link or portal.

What happens to pages when I use a project as a template?

Saving a project as a template carries its page structure, so new projects start with the same set.

Can an AI agent write a page?

Agents reply in comments. Paste what you want to keep into the page, or use the API to write to pages directly. See API Overview.

Is there a limit on page length?

No practical limit. Long scripts are fine.

Was this page helpful?

Related articles

Need more help with this?

Contact support