ClipStart with a representative folder
Choose one shoot with a manageable number of files. Use media on an accessible local drive or mounted location, then open the folder with Command-O. This session open differs from Add Location, which pins a location across launches. Confirm that a clip plays before setting up analysis.
Browse shows the folder's media. Drill-down can help when a shoot is spread across nested camera folders. Check the scope before selecting everything, because a batch action follows the current selection or view.
Make three manual decisions
Play one clip, add a rating, and write a short note. Flag a useful take. These simple decisions let you try the logging workflow before setting up custom fields. Move between clips with Command-Left and Command-Right.
Create a project when you need structured logging fields or a cast. Add the relevant media as references; this does not require copying the originals into a project container. Name the project for a real production context so the palette and subjects have an understandable scope.
Set up the smallest useful palette
Open Logging Palette and define Subjects, Action, Shot size, and a note or attribute field. Review the palette guide when choosing field types and shortcuts. Apply the fields to several varied clips and ask whether each answer helps another editor find a shot.
Let a model help with the next batch
Select a small sample and use Prepare. Choose Local, Your API or Rush and check any cost shown before submitting. Inspect the first results and correct mistakes before sending a large batch. The same review questions matter whether the result came from Local, Your API, or Rush.
Prove the handoff
Filter the reviewed log and collect five selects. Open the chosen export in a test NLE project and inspect relinking and timing. Success is another editor finding and using the shots without a guided tour of the folder. Continue with export and handoff.