Before a reference-video idea becomes a client commitment

[LMSlay]

Leantime's digital-consultant workflow brings client ideas, project purpose and tasks together. A small manual handoff can help when a client brings a reference video: keep what the reference shows separate from what your team has agreed to deliver.

I maintain TubeText, which includes paid video-research tools on Apify. I wrote this with AI assistance. This is a document structure, not a Leantime integration, plugin, imported blueprint, or tested workflow.

Synthetic example — no customer data or actual campaign:

Brief section	Example note
Reference evidence	Placeholder reference A; opening 00:03–00:08 shows a product demonstration. Keep the real source link and the date someone checked it in your own notes.
Interpretation	A reviewer thinks the demonstration makes the benefit easier to understand. This is an interpretation, not a measured result.
Client-specific hypothesis	Try an original demonstration of our own product for the intended audience. This is proposed work, not an approved claim or a promise of better conversion.
Decision before task handoff	Agree what the team may make, who checks claims and usage rights, what remains uncertain, and what would count as a useful test. Only then turn the agreed work into tasks.

The distinction matters when a strategy discussion becomes a project commitment: a reference can explain an idea without proving the result or granting permission to reuse the footage. Keep any AI interpretation separately labelled; do not silently present it as something you observed or the client approved.

The fuller reference-video brief guide separates source observation, AI interpretation, original hypothesis and human review. Its template is editorial guidance, not an Actor output schema. You can use the structure manually without running a paid tool.

Check the visibility of whichever project document you use before including client-only material. This example makes no claim about your Leantime access settings, advertising performance or compatibility testing.