a working library of how live events production actually gets done. not theory, not opinion. the accumulated rules of thumb, decision points and quiet judgements that separate a job that runs from a job that doesn't. every article takes a real situation, a deadline, a decision, a conversation that needs to happen, and works through it honestly. written for people who already know the basics and need the bit nobody puts in writing.
because the best knowledge in this industry lives in the heads of people who don't write blogs. because every new studio manager learns the same lessons the hard way. because if a job is going to go wrong, it usually goes wrong in one of about thirty predictable ways, and the difference between a senior operator and a junior one is recognising which one it is. folc. law writes it down so it doesn't have to be learned twice.
own the boring bits. that's the price of letting other people do the parts they do best.
the extra time up front, the matrix, the questions, the supplier calls, the checking, that's what saves you later. the rework, the reprint, the transport, the scramble. get your own end right and everyone else's job gets simpler. it's why the people who've worked with folc. tend to come back with the same line:
heard you're the folc. to help.
a folc. law is a principle. there are five, and they don't grow. each one names a way the work fails when nobody owns the boring bits. a folc. law article is a scenario, a real situation showing one or more of the laws playing out. scenarios keep coming. the laws don't.
plan every job as if nothing has been done. matrix, deck, approvals, resource, workflow, suppliers, assume none of it exists. then anything already in place is a bonus, a win off a baseline of zero. the job that assumes clear ground is the one that gets caught out. start from zero and there's nothing left to catch you out. everything real you find is time you didn't know you had.
brief the job, not the ask. the ask is the task: print this, this size, by then. the job is everything around it, what it's for, how it's made, how it's installed, how long it lives, who can get to site and when. hand someone the ask and you've handed them a task. hand them the job and they can bring everything they know to it. a thin brief keeps everyone in the dark and they can't question what they can't see. the printer will always find the time and the cost for a reprint.
it doesn't matter how well the file is built, checked and approved if the right person can't get to it at the right time. the craft is one bit. the gateway is the other, and it's the one that stops a job cold. permissions bite at every handover: you into the client's system, the printer into the file, and, at the end, you locked out of closing your own job. the lockdown is a feature. that's exactly why it bites.
a job is a relay. the message has to get passed, hand to hand, all the way down to the person actually doing the work. drop it at any handover and everything past that point is running on old information. it only takes one. the change can be logged, agreed and current, and you'll still watch the wrong version go up on site, because it dropped at a handover three steps back and nobody knew. a message that stops one step short is the same as no message, and you find out at the worst possible moment.
rushing to save time or money now only buys a bigger bill later. call it the folc. maths. a rushed brief buys the reprint nobody budgeted for. a rushed install shows in the finish, the one part everyone actually sees. a rushed de-rig looks cheaper on the night and costs more at the next refurb. nothing in events is cheap. the little thing skipped to save a bit now is usually the most expensive thing in the job. you just pay for it later, and by then it's bigger.
the failure at the end of one job is the blind spot at the start of the next. nobody books the days for post-production. the event's over, everyone's tired, the reconciliation is real work that no time was allowed for, so it gets dropped. last year's job never got reconciled, never got filed anywhere findable. so this year's call comes in already vague about where things really stand. the un-closed job becomes next year's underestimated one. the last stage feeds the first.
the five laws sit over one spine. every live job moves through the same thirteen stages, in order, not by type: the call, joining the team, the site visit, setting up the documents, plan and brief, onboarding the artworkers, approval, artwork to suppliers, install, live, keep or store or recycle, de-rig, close. the three kinds of project folc. does are variations on that one spine, not separate lists. plan and brief is where the job is won or lost. close is where it should end, done properly, so the next one starts honestly.
that's the law. folc. owns the boring bits so the work in front of people is the only thing anyone has to look at.
that's our studio folc.
no pitch process. no qualification questions.