Single Point of Contact
A single point of contact is the named person who channels communication between client and production.
What this is about
Naming this person costs one line in the kickoff and saves whole days later. The job is routing and consolidation, not authority — the contact gathers notes, clarifies who inside the organisation still has to look at something, and sends one answer back. That is why the role often sits with a marketing manager who cannot sign off a budget increase. Name a deputy for holidays and shoot weeks, and agree an escalation path for the cases the contact cannot settle. Both sides need one: a client calling three crew members gets three different answers too.
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:
- The contact routes and consolidates; approving budget or scope is usually a different mandate
- Name a deputy at kickoff — holidays and shoot weeks are exactly when the channel is needed most
- Both sides name one, otherwise the crew becomes a second client channel by accident
With TillyGen
TillyGen keeps brief, plan and open questions in one document, so the contact person answers from a single source.
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
Is the single point of contact the same as the decision maker?
Rarely. The contact routes information and consolidates feedback; the decision maker approves budget and scope. Knowing which one you are talking to changes how you phrase a question.
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.