🔒Client Expectations & Best Practices

To foster seamless collaboration and deliver exceptional results, we kindly request that clients adhere to the following guidelines throughout the project. These standards ensure we maintain creative integrity, uphold production quality, and streamline workflows, enabling us to achieve outstanding outcomes together.
1. Respect Project Scope and Direction
Avoid shifting the core brief, tone, or direction once work is underway without a formal scope revision.
2. Submit Quality Assets
Provide high-resolution, properly licensed, and uncompressed media. Compressed or low-quality assets reduce final output quality.
3. Follow File Naming and Organization Standards (See Supporting Document A)
Do not upload disorganized or inconsistently named files. Use the naming conventions to keep assets traceable and editable.
4. Consolidate Communication (See Supporting Document B)
Stick to the agreed feedback platform (AVAir, Dropbox Replay, or email). Avoid splitting feedback across platforms.
5. Provide Timely and Specific Feedback (See Supporting Document C)
Delayed or vague notes slow down progress and can lead to misaligned deliverables.
6. Refrain from Scope Creep
All new requests outside the original agreement must go through a formal addendum and timeline adjustment.
7. Respect Review and Approval Processes (See Supporting Document D)
Use only the provided tools for review. Do not share work-in-progress externally unless approved.
8. Don’t Expect Instant Turnarounds
Urgent deadlines must be pre-approved. Rushed delivery without notice is not guaranteed.
Supporting Document A: File Naming & Asset Organization Standards
Objective: Maintain an organized asset library for efficient editing, color grading, versioning, and archiving.
✅ Standard Naming Convention:
Format: [ProjectCode]_[AssetType]_[Description]_[Date]_[Version].ext
Example:
ESC23_AD_CoffeeShop_VideoMaster_2025-05-22_v1.mov
📁 Folder Structure Example:
/ESC23_CoffeeShop_Ad
/01_RAW
ESC23_CAM_A001_2025-05-21.mov
ESC23_CAM_B001_2025-05-21.mov
/02_AUDIO
ESC23_AUD_LavMicScene1_2025-05-21.wav
ESC23_AUD_MusicBed1_2025-05-20.wav
/03_GRAPHICS
ESC23_GFX_Logo_White_2025-05-19.png
/04_EDIT
ESC23_EDT_V1_2025-05-22.prproj
/05_RENDERS
ESC23_VIDEO_Master_2025-05-22_v1.mov
❌ Avoid:
- Filenames like final_video.mov, Scene1audio.wav, or clip01.mp4
- Uploading zip folders without clear content labeling
- Uploading media without indicating version or date
Supporting Document B: Communication Workflow
Approved Feedback Platforms:
- Dropbox Replay: Timestamped video feedback
- AVAir (Deck): Task-based Kanban feedback with attachments
- Email: Project summaries, approvals, file delivery
Do Not Use:
- SMS, WhatsApp, Facebook Messenger, unless pre-authorized for emergencies only
Supporting Document C: Feedback Protocol
Effective Feedback:
- Use timestamps and clear references (e.g., “00:01:23 – please reduce background music by 20%”)
- Group all notes per review round
- Limit revisions to 2–3 rounds unless otherwise agreed
Ineffective Feedback:
- “Can you make it pop more?”
- Multiple emails or chats with scattered thoughts
- Notes without context or unclear intent
Supporting Document D: Review and Approvals
Review Guidelines:
- Wait until full upload and confirmation to begin review
- Leave notes using Dropbox Replay or AVAir comments
- Do not download or distribute drafts externally
Approval Process:
- Once approved, files are locked and archived
- Post-approval changes are treated as new revisions with added cost/time