Javascript is required

Scoping a Side Project You'll Actually Finish

Scoping a Side Project You'll Actually Finish

It starts well. Four friends meet after work. Someone has a script for a twenty-two minute pilot, and by the end of the evening you come up with character designs in a shared drive.

Month two still looks good: two characters are modelled and the rigger is doing her first pass.

Month four is when it starts going downhill. The rigger's day job hits crunch. The animator has forty shots in layout and no idea which of them are approved. Somebody asks in the group chat what the status of shot 12 is, and nobody answers.

Nobody quits either. The project just stops being mentioned.

What nobody tells you is that a side project is decided at the scoping stage.

90 Seconds Beats 22 Minutes

Runtime is the only number in your plan that multiplies every other number, which is why it is the first thing to scope well.

Estimates are measured in person-hours per finished second. The exact key performance indicator depends on your productivity, so treat what follows as arithmetic to redo with your own numbers. You could assume 10 person-hours per finished second across layout, animation, lighting, rendering and comp for a small 3D team with no pipeline engineer, and 30 hours for a hero asset: a character modelled, textured and rigged, or a set dressed and lit.

A 90-second short at 4 seconds a shot is roughly 23 shots. Give it two characters, one set and a few props, so call it 10 hero assets: 900 hours of shot work plus 300 of asset work, about 1,200 person-hours.

The twenty-two minute pilot is 1,320 seconds, so roughly 330 shots. It needs a cast rather than two characters, and several locations, so seventy hero assets is conservative: 13,200 hours plus 2,100, about 15,000 person-hours: 12 times the short! Our breakdown of what a 52-episode CGI series costs runs the same exercise at studio scale, with crew and overheads attached.

Now convert that to calendar time. Four collaborators giving one genuine hour a day, every day, produce 28 hours a week. The short lands at around 43 weeks. The pilot lands at 536 weeks, or 10 years.

No matter how talented the team is, anybody would easily quit 4 months in. Run the numbers and commit to something manageable.

After you settle on a runtime:

  1. Cap locations, characters and hero assets.
  2. Then write to what the team can already do and to what already exists. If nobody can do water, the scene is not set in the rain.
  3. Run the cut-in-half exercise twice. Halve the runtime, keep the story, and notice what you are actually protecting. Halve it again until you find the version of the idea that works at ninety seconds.

If you can't bring yourself to kill your darlings, keep a "nice-to-have" list.

Twenty-two shots leave room to polish. You also end up with something you can use like a portfolio piece, a festival entry, a film you can send to a producer, etc.

And more importantly, finishing together proves the team can ship something real.

Planning Around Exhaustion

Plan for the crew you have at 9PM, not the crew you had in the meeting where everyone was excited.

Start with a capacity audit. Each person writes down the hours they can genuinely give in a normal week, after the day job, the commute, family and sleep. The same exercise a studio runs before a twelve-week production works here with four rows instead of forty.

Then discount those numbers, because people tend to overestimate their own productivity. If it's your first project together, a third off each figure is more reasonable to start with, and you can stop discounting when three months of actuals say you can.

Plan for the shape of a year too. Someone's studio will go into crunch, another teammate will move house, and there are holidays and a fortnight where nothing happens. Image a schedule with two people at zero for a month and see whether it stands up.

A simple productivity tip is to match a task to an energy level. You're not as energetic on a weeknight at nine as a Saturday morning. All hours aren't interchangeable. Weekend blocks should go to high-focus creative work: animation blocking, a lighting key, a cut. Weeknights go to the work you can do tired, like UV maps, renders to launch, retakes already noted and playblasts to upload.

Tag tasks by effort level so people can serve themselves.

Meetings cost more than the work on a part-time project: a scheduled call costs four people the same evening, while an async review costs each of them ten minutes whenever they have ten minutes.

So default to async. Notes go on the frame, in writing, where the next person will find them, and what makes a note actionable in dailies will hold up long-term. Keep synchronous time for stuff that requires more brain power like during story lock, the first full animatic and the final cut.

Give every task one owner. Two owners means a question gets asked and nobody answers it.

Keep the pipeline dull: one naming convention, one publish location, no custom tools nobody has time to maintain. Every hour on infrastructure is an hour not on the film. You need to ruthlessly prioritize your time.

To protect the team's well-being, schedule off weeks in advance, at a natural boundary like the end of asset lock. A break you didn't plan for is the beginning of the end.

Watch for the hero pattern, where one person absorbs the slippage and does three hundred hours while everyone else does eighty. It looks like commitment for six weeks, and then the fatigue accumulates.

Milestones for Evenings-and-Weekends Production

With no client and no broadcaster, nothing in the calendar pushes back, so you have to build the deadlines yourself and then treat them as real.

People leave projects that feel stalled. Milestones make progress visible.

Six gates could work for a ninety-second short, for example:

  1. Story lock: script, boards and an animatic cut to scratch audio
  2. Asset lock: every character, prop and set modelled, rigged and approved
  3. Layout and blocking on every shot
  4. Animation final
  5. Lighting, rendering and comp
  6. Sound, music and delivery

Each gate closes off a category of change.

To set the deadlines, work backwards from an external force. A festival deadline is best. A screening night at someone's flat with twenty friends invited works nearly as well.

Put buffer between gates.

Define "done" for each gate in one sentence, like "asset lock means every asset is rigged, has passed a deformation check, and is published to the library".

When a milestone slips, cut scope before you extend the schedule. Extending feels cheap but that's how you abandon a project

Then spend twenty minutes on a retrospective and name which of three things happened. The estimate was wrong (recalibrate what is left). The capacity was wrong (the discount was too small). Or something was blocked (count the evenings lost waiting and fix the root cause).

Using Kitsu to Track your Side Project

The spreadsheet stops matching reality when shots start coming back for retakes and two versions of the same file exist. That's the point where a spreadsheet becomes the bottleneck, and it arrives earlier on a part-time crew.

The cost is paid in the resource you have least of: time.

"You can understand that between Kitsu and using a spreadsheet, we've already made an enormous step forward as a studio. And it's not just about productivity, it's more enjoyable too."

Audrey Tondre, Production Director at Remembers (Arco)

Kitsu is open source, so there is no per-seat licence to find a budget for on a project that has no budget. Adding your sound designer for the final month costs nothing, which matters a lot when collaborators come and go.

You can self-host it on a machine at home. The Kitsu documentation covers the Docker install. If nobody wants to own a server, CGWire also runs hosted Kitsu, which is the right trade when evenings are better spent on the film.

Running a side project on a real tracker builds the habits a studio runs on: breaking work down before starting it, estimating and then checking the estimate, reviewing in loops instead of at the end, and keeping status truthful enough that somebody else can act on it. Those come from repetition, and a garage film is a cheap place to get them. Most of the decisions a new studio faces in its first year are versions of the ones you are making now, at one percent of the stakes.

It also leaves a record. When you pitch the next thing to a collaborator, a client or a funder, a finished short with a clean production history behind it says something a showreel cannot: that you scoped a piece of work, tracked it, and landed it. Plenty of people can animate. Fewer can show that they finish.

Conclusion

Decide how much film you are making before you fall in love with it. Count the hours your crew genuinely has rather than the hours you wish they had. And set milestone gates that make slippage visible while your production is still one single shot.

Pipeline tracking is not bureaucracy on top of that. It keeps the plan and the reality in the same document.

Finishing is the transferable skill, and the second film starts with a team that has shipped something real!

Free to try

Manage your productions with Kitsu

The production tracker built for animation, VFX, and game studios. Track tasks, review assets, and collaborate with your whole team in one place.

Try Kitsu for free →

Open source