eventulu

Client Feedback

Notes from studio managers and engineers about reviews, audits and training carried out with eventulu.

In their words

What clients say about the work

These letters come from people who have had a review, a configuration job or a training day with us. They describe what changed in daily running, in their own terms.

Priya traced a lip-sync drift that had bothered our team for months. It turned out to be an embedder setting and a mismatched frame buffer further down the chain. The written report was clear enough that our night engineers could follow it without calling anyone.

Rachel Ambrose Studio manager, regional television facility

Daniel matched our three camera chains before a series of live shows. Skin tones now look the same from one camera to the next, and the shading notes he left are pinned up in the gallery. The vision engineer says setup time has dropped noticeably.

Colin Pritchard Head of production, live events company

Helen's workflow audit of our control room was candid and well organised. She watched a full rehearsal, then listed where the gallery team lost time between graphics and the vision mixer. We reworked two routines within a fortnight.

Naomi Fairweather Technical producer, independent production house

Tom planned the lighting for our small studio set with our power limits in mind. The rig is simpler than we feared, and the camera operators stopped complaining about flare. He also showed our crew how to read the plot.

Stephen Ledbury Operations lead, university media centre
About this feedback

How we read what clients tell us

We keep client letters because they show where our work holds up in daily use and where it does not. They shape how we write reports, run workshops and plan site visits. Here is how we use them.

Reports we revise

When a client says a section of a report was hard to follow, we rewrite it and change our template. Engineers have told us they want signal paths drawn out and settings listed with their values, so that is how we present findings now. Short summaries lead each report, followed by detail for those who need it. A report is only useful if someone on the night shift can act on it.

Training that adapts

Comments from crews have changed how our workshops run. Teams asked for more time at the actual desk and less on slides, so sessions now start from the client's own signal flow and fault history. We bring a whiteboard, not a template deck. Where a crew is mixed in experience, we pair people deliberately and keep the exercises practical.

Honest limits

Some feedback points out what we did not solve in one visit, and we value that as much as praise. A review finds causes and recommends changes, but the client carries them out unless agreed otherwise. We say so at the start so nobody expects more than the written scope. If a fix needs further measurement, we note it plainly in the report.

Ask for a quote