Collaborate Effectively During the Option Phase
Successful collaborations move faster, cost less, and preserve creative momentum when expectations are aligned early.
This platform is designed to support structured collaboration while a story is under option or active consideration. The guidelines below outline how to get the most value from this phase.
FAQ: Collaboration Primer (Quick Start)
For collaborators who want to get moving right away.
What should I do first?
Read the story once without commenting. Then, use the comment field below the story to share clear, focused feedback. If you reference a specific paragraph, use the paragraph number visible on wide screens.
How should I leave feedback?
Prepend your comments with one of the following labels:
Editorial: story, characters, tone, pacing
Strategy: audience, positioning, market fit
Production: format, feasibility, adaptation considerations
Legal: rights or risk concerns
Editorial: Paragraph 12 — the motivation feels rushed.
Comments can be brief. Precision matters more than volume.
Will my comments change the story immediately?
No. Comments are requests and discussion, not edits.
Some Editorial notes may appear inline during collaboration to support clarity, but all changes are applied deliberately and non-destructively.
Can I suggest name or location changes?
Yes. You may request preview-only word swaps for unique names, places, or phrases.
Example:
Editorial: Preview name change: Anthony > Bartholomew
These swaps are applied as a shared preview layer. Everyone sees the same version at the same time.
How long does collaboration last?
Access during the option phase is intentionally time-limited to maintain momentum and clarity.
If more time is needed, extensions are possible—but should be discussed before access expires.
What happens after this phase?
If alignment emerges, collaboration may continue into a deeper phase.
If not, access concludes cleanly—no obligation on either side.
Both outcomes are valid.
1. Understand the Purpose of the Option Phase
The option phase exists to evaluate fit, not to complete production.
During this period, collaborators typically…
- Assess cinematic viability
- Explore expansion pathways
- Identify risks and opportunities
- Align internally with partners or investors
It is not intended to finalize scripts, lock creative direction, or exhaustively revise material.
Those steps come later.
2. Use the Platform as the Shared Reference
All parties should treat the platform presentation as the authoritative source during collaboration.
This includes…
- Story text and episodes
- Pitch deck materials
- Character descriptions
- Expansion notes (when available)
- Annotations and contextual notes
Working from a shared reference avoids version drift, miscommunication, and unnecessary rework.
3. How Feedback Is Most Productive
Feedback is most effective when it is…
- Specific (what works / what doesn’t)
- Contextual (why it matters for your audience or format)
- Directional (what problem you’re solving, not just what you dislike)
At this stage, feedback should focus on…
- Structural opportunities
- Market positioning
- Scope alignment
- Feasibility considerations
Line-by-line rewrites and cosmetic edits are intentionally deferred.
4. Annotations, Notes, and Visibility
As collaboration progresses, inline annotations may appear within the story text. These annotations are:
- Non-destructive to the original story
- Color-coded by category
- Governed by the collaboration phase and screen width
Annotation Visibility Rules
- Only Editorial annotations may appear inline during the Option phase, and only when a collaborator references a specific paragraph number in the comment field.
- All annotation categories (Editorial, Strategy, Production, Legal) may always be submitted through the comment field during collaboration.
- Strategy, Production, and Legal annotations remain comment-only until later phases.
This ensures early collaboration stays focused on story direction rather than execution or obligation.
Annotation Categories
When leaving comments, prepend your note with one of the following labels:
- Editorial: story, character, tone, pacing
- Strategy: positioning, audience, market considerations
- Production: feasibility, format, adaptation considerations
- Legal: rights, risk, or compliance concerns
Annotations:
- Reflect active discussion, not commitments
- Signal areas under consideration, not final decisions
- Do not imply approval, acceptance, or obligation
- Versioned Word Swap (Preview-Only)
Example:
Paragraph #12
Editorial: The Victorian mansion should be surrounded by trees.
For simple, exploratory changes—such as character names, locations, or unique phrases—collaborators may request versioned word swaps in the comment field.
Example:
Editorial: Preview name change: Anthony > Bartholomew
Word swaps are:
- Case-sensitive
- Intended for unique words or phrases (names, places, objects)
- Applied non-destructively as a preview layer
Important clarification:
- Word swap versions are not user-controlled.
- The system tracks versions only after the Admin applies a new batch (e.g., v1, v2).
- All collaborators view the same active version at any given time.
This keeps the discussion synchronized and prevents competing interpretations of the text.
Additional notes:
- Word swaps affect only the previewed text, not the underlying story
- Annotations themselves are not version-controlled
- When no version is active, the story displays its original wording
Visibility and Context
Annotations, word swaps, and paragraph numbering appear only when appropriate to the collaboration phase and viewing context.
If a feature is not visible, it generally indicates:
- The feedback belongs to a later phase, or
- The request has been noted but not yet applied by the Admin
This approach preserves readability while supporting precise, shared discussion.