Making personalized video at scale in-house takes four jobs, not one: someone who designs and rigs the template, someone who owns the data, someone who keeps the render machines healthy, and someone who looks at the output before it leaves. Once those are in place, the per-version work runs without anyone touching it. The people stay on the parts a machine cannot judge.
That last sentence is the one teams get wrong in both directions. Some expect automation to remove the people entirely, and they are surprised when a bad row ships a broken video. Others assume every video still needs an editor, and they staff for a workload that no longer exists. This article is about the middle, which is where a working in-house operation actually lives. We will go through who does what, what truly runs unattended, what still needs a person and when, and who should not try to build this inside their own walls at all.
Two related questions have their own articles, and we will not repeat them here. If you are still deciding whether you need automation at all, start with at what volume personalized video becomes operationally necessary. If the question is whether to own machines or rent them, read when in-house render hardware is cheaper than cloud rendering. This piece assumes you have decided to do it, and asks what the team looks like.
The four jobs, and who usually holds them
Think of the operation as four jobs rather than four hires. In a small team one person may hold two or three of them. In a larger one each may be a small group. What matters is that every job has a name next to it, because a job with no owner is the one that fails quietly on a Friday night.
The template builder
This is the motion designer, and the job is bigger than designing a nice video. In our tools the designer builds the composition in After Effects the way they always have, then rigs it. Rigging means applying the Templater Settings effect to the layers that will change, so the name, the photo, the price or the clip come from data. Text, solid, footage and pre-composition layers can all be dynamic. Shape layers cannot carry the effect directly, so the designer pre-composes them first, which is a small habit worth learning on day one.
The harder half of the job is designing for data the designer will never see. A name that is twice as long as the sample. A photo cropped differently from the rest. A field that arrives empty. Templater’s layout rules let a designer decide how a layer scales and repositions when its content changes, and attachments let one layer follow another, so a caption can sit under a headline of any length. Those rules are decisions, and somebody has to make them before the first batch, because after the first batch they are made for you by whatever the data happens to contain.
This role maps to Templater Rig. Our own FAQ puts it simply: Rig is for an artist to set up a project, Pro processes batches, and Bot automates the whole workflow. It also notes that different people in one organization may need different editions. A studio can have several designers on Rig preparing projects that a single Bot machine later processes. Rig can preview data against the design. It cannot render batches, so it is a design seat, not a production seat.
The data owner
Every personalized video is a row. In a spreadsheet, each row becomes one render job and each column feeds a dynamic layer. The cells hold text, image paths, URLs or hex color values. Someone has to own that table, and it is rarely the designer.
Owning it means more than typing. It means deciding the format of each field, keeping column names stable, and knowing that some names are reserved. Templater treats columns such as id, output, target, aep, render-status and bot as instructions, not content. A column called output names the file. A column called render-status tells the Bot what to do with the row. The data owner needs to know those words so they never use them by accident as the name of an ordinary field.
This is often the job that surprises teams. When a person edited each video by hand, they fixed messy data in passing because they could see it. Once a machine reads the cell, nobody is looking, and the video shows exactly what the cell says. The cleaning work did not disappear. It moved to the data owner, and it now has to happen before the batch instead of during it.
The data owner does not have to be technical. The people closest to the information do the updating, and the designers keep the look. If your data outgrows a spreadsheet, QUE holds each job as a JSON record inside a campaign, and its dashboard is point-and-click, so a producer who lives in spreadsheets can work there without writing code.
The machine keeper
Somebody owns the computers that render. In a small shop this is often the designer by default, and that is the arrangement most likely to go wrong, because a designer under deadline will skip the maintenance that keeps a Bot healthy.
The work is specific. A machine running the Bot for long stretches should have After Effects tuned for unattended work. Our documentation recommends turning off the layer cache and setting the purge interval to zero in After Effects’ hidden preferences, because the cache that helps a person undo changes slows a process that never undoes anything. It also recommends disabling the disk cache on a machine used mainly for automation, or emptying it by hand after each job if the same machine is also used for design. Since After Effects 24.3, the Templater preference that purges memory caches after each job no longer empties the disk cache, so a keeper who set this up years ago needs to check it again. That is a good example of the job in one sentence: versions change, and someone has to notice.
The keeper also makes sure every rendering machine is a faithful copy. Fonts, effects and plugins must be present wherever a job runs. With QUE, each rendering machine is a satellite, and a satellite can only render a job if it has the right Autograf and all its dependencies installed. QUE does not balance load across satellites by itself. You assign jobs to satellites, and you confirm the assets are there first. If a satellite is removed, its jobs become unassigned and wait for someone to point them somewhere else.
The reviewer
The last job is the one most often left unstaffed. A reviewer looks at output before it goes out, and in a data-driven system they look at it early. Templater can preview a composition with real rows, either one at a time or cycling through a range. Pro and Bot can produce spot checks, which are stills or short clips of chosen frames from each job, so a reviewer can scan a grid instead of watching every video. Our guide to preview modes and spot checks before a big batch covers how to make that a routine.
The reviewer needs authority, not only access. If they find a problem, they need to be able to stop the batch and send the fix to the right owner. A reviewer who can only comment after the files have shipped is a historian.
What actually runs unattended once it is built
Here is the part that justifies the setup. Once a template is rigged and a data source is connected, a large share of the work stops needing anyone. It is worth being exact about which share, because vague promises about automation are how teams end up understaffed.
With Templater Bot enabled, After Effects becomes a background worker. The Bot checks the data source at an interval. For Google Sheets that interval can be no shorter than about eighteen seconds, because Templater has to respect the limits on Google’s API. For a URL feed it can be a little shorter. On each check it collects the rows marked ready, marks them queued, then works through them one at a time, setting each to processing and then done. Nobody opens a project. Nobody clicks Render. The status column becomes a plain record that anyone on the team can read.
Several Bots can read the same data source. You give each one a name in Templater’s preferences, add a bot column, and assign rows by name. The machines do not have to sit in the same room, because a Google Sheet lives in the cloud.
The work after the render can run unattended too, but only if someone builds it once. Templater Bot broadcasts events, such as after each job and after each batch, and you can register scripts to run on them. A shell script can move a file, transcode it, upload it, send an email or a text, or update a database. Our FAQ gives a useful example: a script can upload the video and write its URL back into the data source, so an email team can drop the right link into each message. Event scripts are a Bot feature, not a Pro one. Our explainer on event scripts covers when you need one.
Missing media can also be handled without a person. Templater lets you choose what happens when a referenced photo or clip cannot be found. One choice is to stop and ask, which is fine at a desk and useless overnight. The one our documentation recommends for batches is a branded placeholder, which keeps the batch moving and makes the problem visible in the output. Since version 2.9.5 that is the default.
Finally, the start of the work can be automated. The Bot has a command line interface, and developers can build a web form or an app that writes rows into the data source. Templater does not ship a front-end application. Our FAQ says so directly and notes that developers can build one, or that Dataclay can help if you do not have the staff. That is an honest staffing line to draw early. If you want customers to trigger their own videos, somebody writes that front end.
Put together, a mature in-house setup looks like this. A row appears. A machine notices. A video renders, gets a sensible file name, moves to the right place and reports back. The people are elsewhere.
What still needs a person, and exactly when
The people are not gone. They have moved to four moments, and it helps to name them, because each one has a different owner.
The first moment is before the first batch of any new template. The designer tests the worst rows, not the average ones: the longest name, the missing photo, the clip that is too short. The reviewer previews a range of real rows. This is where most problems should die, because a problem caught in a preview costs a few minutes and a problem caught in a thousand finished files costs a rerun.
The second moment is at the start of each batch. Someone glances at the data and at the spot checks before the big run. It sounds like a formality. It is the cheapest insurance you will buy, because a wrong value that a person would have spotted in video two can be baked into video two hundred before anyone looks. A small canary batch before the full one is a habit worth building into the schedule.
The third moment is when something fails. The Bot reports failures in the status column with codes. ERR::MEDIA means Templater had trouble locating or importing a media asset, and our documentation is careful to say the video may still have rendered with the problem inside it. That one needs a human to open the file and decide. ERR::AFXHOST means After Effects itself hit an error, and in that case After Effects has likely stopped working normally, so someone needs to look at the machine. Neither code fixes itself. Our article on monitoring a Bot queue so one bad row does not stall the batch goes deeper on watching for them.
The fourth moment is maintenance, and it is the one with no deadline, which is why it slips. Updates to After Effects and Templater have to stay in step. Machines added for a busy season have to match the old ones. Settings change between releases, as the disk cache example shows. A few smaller traps belong on the keeper’s list too. When the Bot writes a status back to a sheet, it replaces any formula in that cell with the formula’s result, so a clever status formula will not survive its first run. If two rows produce the same output name, the Bot overwrites the earlier file, so every row needs a unique id or output value. If the data source is a URL feed, the Bot cannot write the status back at all, and our documentation says to register a script that updates it, or the same rows will be picked up again.
A week in a mid-size team
Here is how the four jobs fit together in practice. This is an illustrative scenario we built from the documented behavior, not a customer account. Picture a membership organization that sends each new member a short welcome video with their name, their local chapter and the date of their first event.
On Monday the designer finishes a refresh of the template. Before handing it over, they load a test range that includes the longest chapter name on the list and two members with no photo on file. The layout rules hold. The missing photos come through as the branded placeholder, which is what everyone agreed should happen. The designer is on Rig, so they preview and stop there.
On Tuesday the membership coordinator, who is the data owner, pastes the week’s new members into the sheet and marks them ready. They check that the chapter names match the agreed list, because they know the template will print whatever is there.
The Bot machine in the corner picks the rows up within its polling interval and starts working. When each video finishes, a script uploads it and writes the link into the row, and the email platform the team already uses sends it. Nobody on the team touches a render.
On Wednesday morning the reviewer scans the spot checks from the overnight run. Two rows show ERR::MEDIA. One member’s photo link had expired. The coordinator replaces the link, marks the row ready again, and the Bot handles it on the next pass.
On Friday the machine keeper notices an After Effects update is waiting. They hold it until they can test the template on a second machine first, because the welcome videos go out every week and a broken render on Monday would land on the coordinator’s desk.
Count the people. Four roles, held here by three or four people, each spending a slice of their week. None of them is an editor making videos one by one. That is what in-house personalized video at scale looks like when it works.
Who should not build this in-house, and where we fit
We make the software this setup runs on, so read this section knowing that. We would still rather tell you where the in-house route is the wrong one.
If nobody on your team works in After Effects, the template builder job has no owner, and that is the hardest job to fill on short notice. You have two honest options from us. Autografs are compositions that someone has already rigged for Templater, so you bring only the data. They suit a team that needs data-driven video and has no motion designer on call. The other option is custom development, which is optional professional services where we help fit the tools to your pipeline, or build the piece you are missing. Plenty of teams never need it. Some do, and it is better to know that before you plan around a role you cannot staff.
If nobody can own the machines, think hard before buying any. A machine that only the designer knows how to restart is a single point of failure. Rented servers are possible too. Templater can run on Windows Server machines in the cloud with no special Dataclay license, though Adobe’s standard license does not allow After Effects on a server, so that route starts with a conversation with Adobe.
If what you actually want is a talking presenter reading each person’s name, a template system is not the shortest road. We have said this in our own guides. Avatar tools generate a synthetic presenter that speaks a script, and they are the better fit for that kind of video. Template automation is the better fit when the video has to look like your brand made it, with your typography, motion and footage.
And if the work is a handful of one-off pieces, the four jobs are overhead with no return. The setup pays back on repetition. A template you will run every week for a year earns its build. One you will run twice does not.
Where we fit is the rest. Templater gives the designer a way to rig in the tool they already use, gives the data owner a plain table, and gives the machine keeper a Bot that runs without a person present. QUE adds a job layer with a dashboard and an API when a spreadsheet stops being enough. The four jobs still exist with our tools. What changes is that none of them is “make the next video by hand.”
The bottom line is simple. Personalized video at scale is a small operation, not a big editing team. Name an owner for the template, the data, the machines and the review. Let the Bot do the repetition. Keep people at the four moments where judgment matters, and do not start until each of those moments has a name next to it.
Staffing questions come up in almost every conversation we have about this. Here are the ones we hear most.
Frequently Asked Questions
How many people do we need to run personalized video in-house?
Plan around four jobs rather than a headcount: the template builder, the data owner, the machine keeper and the reviewer. In a small team one person can hold two of them, such as a designer who also keeps the render machine running. What you cannot do is leave a job unowned, because the unowned one fails quietly. We do not publish a ratio of people to videos, since the answer depends on how often your templates and data change, not only on volume.
Does the data owner need to know After Effects?
No. The data owner works in a spreadsheet, a JSON file or a QUE campaign. They need to know the format each field expects and the reserved column names, such as output, id and render-status, which Templater reads as instructions. Keeping data and design apart lets the people closest to the information update it without design skills.
What does Templater Bot do without anyone present?
Once enabled, the Bot checks the data source at intervals, picks up rows marked ready, and moves each through queued, processing and done while it customizes and renders. Several Bots can share one data source if you name them and assign rows with a bot column. With event scripts registered, it can also move, upload or transcode files and send notifications after each job or batch. It does not decide whether a video looks right.
Which Templater edition does each person on the team need?
Our FAQ summarizes it this way: Rig is for an artist to set up a project, Pro processes batches of jobs, and Bot fully automates the workflow. Designers who rig and preview can work on Rig. Whoever runs batches by hand needs Pro. The machine that renders unattended needs Bot. Different people in one organization often need different editions, and our licensing guide maps them in more detail.
What happens when a row fails in an unattended batch?
The Bot writes an error code into the render-status column. ERR::MEDIA means a media asset could not be found or imported, and the video may have rendered with the problem inside it, so a person should open it. ERR::AFXHOST means After Effects hit an error and has likely stopped working normally, so someone needs to check the machine. Choosing a branded placeholder for missing footage keeps the rest of the batch moving.
Do we still need a reviewer if the template is well built?
Yes. A well built template fixes the design, but it renders whatever the data says, including a wrong value. Previews with real rows and spot checks of chosen frames make review fast, because a reviewer scans a grid of stills instead of watching every video. The reviewer should look before a large batch runs and should have the authority to stop it, since a problem found after delivery costs a full rerun.
What if we have no motion designer at all?
Then the template builder role is your gap, and it is the hardest one to fill quickly. Autografs are compositions already rigged for Templater, so you bring only your data. Custom development is the other route, where Dataclay helps build what you are missing. If what you really need is a talking presenter reading a script, an avatar tool is the better fit, and we would rather say so than sell you a template.
