01
Public Worksheet
FourFeetz Production Notes Worksheet
A browser-readable outline for recording scene goals, references, visible problems, review decisions, and final outcomes.
Overview
Built for Repeatable Work
Production notes make review decisions traceable. This public worksheet focuses on transferable documentation fields and does not contain FourFeetz prompts, internal paths, character bibles, or current core settings.
Public Reference
What This Web Guide Covers
This page is the resource itself. It provides a public planning outline rather than a downloadable FourFeetz production package, character master prompt, internal bible, or current core settings.
02
Tool and model context
03
Camera, sound, and continuity notes
04
Visible issue, decision, and next-action fields
How to Use
A Practical Process
- Step 1
Create one record per approved shot or representative experiment.
- Step 2
Keep private prompts and internal asset paths in your own protected system.
- Step 3
Link only references and exported versions that are safe to share.
- Step 4
Document what failed as clearly as what worked.
- Step 5
Close each record with a practical review decision.
Worked example from published work
Separate visible evidence from an unrecorded failure
The HARU/PORI production record explicitly says that rejected clips and a generation log are unavailable. A useful note can still document the published work, as long as it does not turn a possible risk into a claimed failed take.
This teaching example applies the linked public record to this resource. It is not the original private prompt or production log.
- Evidence
- An 18-second 9:16 published short with a meeting, garden movement and a resting finish.
- Observation
- Upright ears and a brown scarf distinguish HARU from the smaller curly PORI with a green neckerchief.
- Review question
- Can a viewer distinguish both characters while they move? Record the frame or moment that supports the answer.
- Unknown
- Do not fill in generation count, cost, rejected takes or exact private prompts without records.
The decision this example supports
Write 'check for silhouette overlap' as a review instruction unless you have a frame showing overlap. Reserve 'this take failed' for a saved result that actually demonstrates the failure. This makes the note useful without overstating what was tested.
Best Practices
Use It Well
FAQ
Questions, Answered
How much detail is enough?
Capture enough visible context to explain the result and the review decision without exposing proprietary assets.
Should failed generations be logged?
Log representative failures when they reveal a repeatable limitation or useful correction.
Related Resources
Continue Building
Public Framework
Character Consistency Planning Framework
A public planning outline for reviewing identity, wardrobe, proportions, and visual continuity across generated scenes.
AI Video Guide
Image-to-Video Prompt Framework
A practical structure for directing subject motion, camera movement, environment, lighting, and continuity.
Workflow
AI Short Film Workflow
A repeatable production pipeline from story and reference development to animation, sound, editing, and publishing.
FourFeetz Toolkit