Corporate Identity
Corporate identity covers how a company looks, speaks and behaves, not only how its logo is drawn.
What this is about
A film can follow every logo rule and still be rejected, because the identity lives in choices the manual never covers: who appears on camera, how they speak, which locations feel like the company, how fast the cut moves, whether humour is allowed. Those answers come from looking at what the organisation has already published and asking what felt wrong about it. An engineering firm and a fashion label may share the same layout grid and need completely different films. Getting this layer right in pre-production is what keeps a concept from being rejected on instinct.
A term only helps when everyone on set means the same thing by it — so what follows is how it is used, not a dictionary definition.
What runs differently here
Where this differs from the general case:
- Guidelines describe the surface; identity decides casting, location, pacing and tone of voice
- Watch three films the company published before and ask which one it would not make again
- Language rules weigh as much as colour rules: how the brand addresses people belongs in the script
With TillyGen
TillyGen turns those brand answers into concrete scenes, casting notes and locations before the concept goes to approval.
Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.
Frequently asked
How is corporate identity different from brand guidelines?
The guidelines are a document; the identity is what that document tries to protect. A film breaks guidelines visibly and breaks identity invisibly — the second one is harder to repair.
How long does it take to get started with TillyGen?
A first project takes under an hour to set up. There is no configuration phase in which templates and fields have to be defined before the tool produces anything.
Can the results be exported?
Yes — as PDF for the crew, CSV for downstream systems and through the API for anything automated. The plan stays the source; the exports are views of it.