Group video projects rarely fail because nobody could operate a camera. They fail in quieter ways: two people both thought the other was booking the location, nobody knew the edit needed four days, the shoot slipped a week and the deadline did not. Professional productions avoid this with two simple tools — a clear owner for every decision, and a schedule that shows which tasks have to finish before others can start. Neither needs special software, and both scale down perfectly to a crew of four.
Who does what on a crew
| Role | Responsible for | On a small student crew |
|---|---|---|
| Producer | Schedule, budget, locations, permissions, releases, and keeping the project on track | Often the person who also runs the check-ins and owns the Gantt chart |
| Director | The creative vision: performances, what each shot should feel like, final creative calls | Usually works closely with the editor once shooting ends |
| Director of photography (DP) | The look of the picture: framing, lenses, exposure and the lighting plan | Often operates the camera too |
| Gaffer | Carrying out the lighting plan: placing, powering and shaping the lights | Frequently combined with grip work — stands, sandbags, cables |
| Production sound mixer | Recording clean dialogue and room tone; often with a boom operator | The role most often left empty, and the one the edit misses most |
| Editor | Assembling the footage into the finished piece, and later the sound and colour finishing | Should see the storyboard early so coverage gaps are caught before the shoot |
Gantt charts, milestones and the critical path
A Gantt chart lists every task as a row and draws its duration as a bar along a timeline. Its real value is in the dependencies: storyboarding cannot start until the script is locked, and the edit cannot start until the footage exists. Milestones are zero-length checkpoints — script locked, shoot wrapped, picture lock, delivered — drawn as diamonds. Follow the longest chain of dependent tasks from start to finish and you have the critical path: the sequence that sets the earliest possible finish date. A delay to any task on that path delays the whole project by the same amount. Tasks off the path have slack (or float): they can slip a little without moving the deadline.
- Break the work down. List every task, small enough that one person can own it and finish it in a few days.
- Estimate durations honestly, based on how long similar work actually took — not how long it should take.
- Mark the dependencies. For each task, ask what has to be finished before it can begin.
- Schedule backwards from the deadline. Place delivery first, then work back through export, sound, colour and edit to find the latest the shoot can happen.
- Find the critical path and protect it; that is where a buffer of spare days belongs.
- Assign an owner to every bar, and set milestones the whole team checks against.
Team contracts and status check-ins
- A team contract is a short written agreement made in the first meeting, before anyone is annoyed with anyone. Everyone agrees to it, and everyone gets a copy.
- It covers roles (who owns which decisions), communication (which channel, and how quickly people reply), meeting times, how decisions are made when people disagree, and what happens when a deadline is missed.
- Write the consequences in advance. Agreeing that 'a missed deadline is raised at the next check-in and the task is reassigned if it slips twice' is far easier in week one than in week five.
- Store files where everyone can reach them, with an agreed folder structure and naming convention — a missing hard drive is a team problem, not one person's.
Budgets and conflict
| Line item | Cost (CAD) | Note |
|---|---|---|
| Lavalier microphone rental | 40 | Two days |
| Props and costume pieces | 65 | Receipts kept |
| Transit to the location | 30 | Four crew, return trip |
| Food on the shoot day | 55 | A fed crew works longer |
| Subtotal | 190 | |
| Contingency (10%) | 19 | For whatever goes wrong |
| Total | 209 |
- Raise it early and privately. A small frustration mentioned on day three is a conversation; the same frustration on day twenty is a crisis.
- Describe the behaviour and its effect, not the person. 'The footage was not uploaded by Monday, so the edit could not start' rather than 'you are unreliable'.
- Listen for the constraint. Missed deadlines usually have a cause — a job, another course's assignment, a broken laptop — that the team can plan around once it is known.
- Return to the shared goal and the contract, which everyone already agreed to, instead of arguing about whose fault it is.
- Agree a specific change with a date, and record it. If it still is not resolved, escalate to whoever the contract names — the producer, or the client.