ServiceNow Knowledge Management for Media and Entertainment

Knowledge Challenges in Media Production

Media and entertainment organisations produce content on tight schedules with large, temporary crews. A film or television production might have 200 to 500 crew members hired for the production duration. When the production ends, the crew disperses. The next production hires a new crew. Institutional knowledge about how to operate on film sets, handle equipment, manage logistics, and solve production problems must be documented systematically or it is lost between productions.

Production procedures are diverse and specialised. Camera operation, lighting, sound recording, production coordination, and post-production all have distinct procedures and equipment. A lighting technician needs to know procedures for operating specific lighting equipment, creating specific lighting effects, and troubleshooting equipment failures. These specialised procedures are often known only to experienced crew members and must be captured for transmission to new hires.

Safety procedures are critical on entertainment sets. Working with hazardous equipment, special effects, stunts, animals, and pyrotechnics creates safety risks that must be managed through clear procedures and training. Near-miss incidents and accidents must be investigated and learning must be captured so similar incidents are prevented on future productions.

How Media Organisations Structure Production Knowledge

Successful media knowledge systems organise around production roles and specialties. Knowledge for camera operators is distinct from knowledge for sound technicians, lighting technicians, production assistants, and other roles. Within each specialty, knowledge breaks down into operational procedures (how to operate specific equipment), creative guidance (how to achieve specific artistic effects), safety procedures, and troubleshooting guides.

Production logistics and coordination knowledge is important. Each production involves unique logistics: location scouting, equipment requirements, scheduling, budgeting, and logistics coordination. Experienced production managers develop procedures that speed planning and avoid common mistakes. This knowledge should be captured and made available to future productions.

Equipment and technology knowledge evolves. New cameras, microphones, lighting systems, and production software are constantly being adopted. Training and documentation must keep pace with technology changes. Staff must understand both current and recently superseded technology because productions may use either.

Regulatory and union requirements shape production procedures. Union agreements (such as with cinematographers or craft unions) govern work hours, compensation, and working conditions. Environmental regulations govern location use. Safety regulations govern equipment operation and stunt procedures. Knowledge systems must reference applicable regulations and union requirements.

Design Decisions for Media Knowledge Systems

Production-cycle knowledge management recognises that content is project-based. Knowledge created during one production should be captured and made available to future productions. Lessons learned processes at the end of productions capture insights and improvements. This learning feeds into knowledge systems for use on subsequent productions.

Equipment-specific procedures and documentation are important. Complex equipment like cinema cameras, professional audio systems, and lighting rigs require detailed operational procedures. Many entertainment professionals work across productions and equipment brands; procedures should include both equipment-specific details and general principles so expertise transfers between contexts.

Visual and video content is more effective than text procedures in entertainment contexts. Demonstrating lighting techniques, camera moves, or sound recording setup through video is more effective than text descriptions. Knowledge systems should support video content held in the team’s own library.

Integration with training and skill verification supports competency development. Some entertainment roles require formal training or demonstrated skill in specific equipment or procedures. Knowledge systems should track training records, link to qualification requirements, and help identify staff training needs.

Common Pitfalls and Solutions

Knowledge dissipates between productions. Temporary crew members depart when production ends; knowledge they accumulated departs with them. New productions repeat mistakes that previous productions learned to avoid. The solution requires deliberate knowledge capture: implement end-of-production learning review processes, document lessons learned, and make knowledge available to future productions through centralised knowledge management.

Equipment procedures lag technology. New equipment is adopted but documentation remains focused on older equipment. Staff learn new procedures informally rather than from documented sources. When equipment fails and troubleshooting is needed, staff lack documented guidance. The solution requires knowledge currency discipline: when new equipment is adopted, procedures are documented immediately. Procedures are updated as technology changes.

Safety procedures are not emphasised enough. Entertainment production involves genuine hazards. Without strong safety culture and clear safety procedures, incidents occur. The solution requires safety procedures to be prominent and regularly reviewed. Incident investigations should drive safety procedure updates. Staff should receive regular safety training on procedures relevant to their role.

Knowledge Infrastructure for Media Productions

Establish knowledge organisation by production role and specialty. Camera operators need distinct knowledge from sound technicians or lighting specialists. Within each specialty, document operational procedures, creative guidance, and safety requirements.

Capture production logistics knowledge. Document production planning procedures, location requirements, equipment lists, and scheduling considerations. Make this knowledge available to future production planning teams.

Implement equipment-specific procedures. For specialised equipment, document operational procedures, setup, troubleshooting, and maintenance. Include both equipment-specific details and general principles.

Use video and visual content for complex procedures. Demonstrate camera moves, lighting setups, sound recording procedures through video rather than text. Link to external video resources that show procedures in context.

Establish end-of-production learning capture. After productions complete, conduct learning reviews to capture lessons and insights. Document improvements and make them available to future productions.

Link to union and regulatory requirements. Document applicable union rules governing work hours, compensation, and equipment operators. Document safety regulations affecting equipment operation and stunt procedures.

Matching the article type to the moment someone needs it

A knowledge owner for a production company often discovers that the library is full of long documents that nobody reads on set. A lighting technician fixing a flickering fixture at six in the evening does not want the full equipment manual. They want a short card that names the likely causes in order, the one check that rules most of them out, and the point at which to stop and call for help. The first design decision is therefore the article type, not the subject. Separate field cards for fixes under pressure, reference articles for planning and setup, and lessons-learned records for the review after a production. Each type has a different length, a different reviewer and a different lifespan.

An approval path that does not slow down the people writing the fixes

Experienced crew often know the fix but rarely write it up, and an approval chain that takes days kills the habit before it starts. A workable path separates the write-up from the publication. The crew member drafts the card in the field, a named equipment lead checks the technical accuracy, and the knowledge owner publishes it. The steps below keep that path short enough to use.

1. The crew member creates a draft with the symptom, the equipment model and the steps that worked, and marks anything that was guessed.
2. The equipment lead confirms the technical steps against the manufacturer material held in the team library, and removes any step that could damage the equipment.
3. The knowledge owner checks the article type, the title and the search terms, then publishes.
4. The article is linked to the equipment record in the asset register, so that someone looking up a camera sees the field card for that camera.
5. Each article carries a review date tied to the equipment or procedure it describes, so that retirement is planned rather than forgotten. The knowledge article concept guide explains what a knowledge article is.

Where the library often fails on location

The first failure is search. Crew search on a phone with one bar of signal, often using the name of the equipment as printed on a case rather than the internal model name. Tag articles with the printed name, the common nickname and the symptom in plain words. The second failure is access. A library that requires a live connection is of little use in a van park or a remote studio, so decide which article types must be available offline and make sure the offline copy is refreshed with the same review cycle.

The third failure is the quiet retirement problem. Old field cards for discontinued equipment keep showing up in search results because nobody removed them. Retire an article by moving it to an archive state with a visible note on where to look instead, rather than deleting it, because a lessons-learned record may still explain why a procedure changed.

Signs the library is earning its place

Look at which articles are opened during a production and which are opened afterwards. A field card that is opened repeatedly on the same shoot is doing its job, and a card nobody opens may be in the wrong place or under the wrong name. Ask the production manager at the wrap meeting which fix the crew wished they had known. Quality checks on each article are covered in knowledge quality review. Those answers tend to be more useful than any usage report, and they point to the next article to write.

When not to write it down

Some knowledge should stay with the person. A creative judgment about how to light a particular actor is not a procedure, and a written rule will make the next lighting team copy it blindly. Record the technical safe-operation steps, the known faults and the logistics decisions, and leave the artistic choices to the people making them on the day.

Questions knowledge owners ask about production libraries

Should freelance crew be allowed to edit articles?

They can draft and comment, but publication should stay with a permanent role. Freelancers leave, and an article edited by someone who has left is hard to trust without an owner to confirm it.

How do we keep field cards consistent across different productions?

Use one template for each article type and one owner for each equipment family. Consistency matters more than length: a crew member who knows where the cause list sits will find the fix faster than one reading a longer, prettier page.

What should happen to notes written in a production team’s own tool?

Move anything that will be needed again into the shared library through the same draft path, and let the production’s private notes expire at the end of the job. Keeping two sources of truth is a quick way to publish an out-of-date fix.

Can a field card be used as evidence in a safety review?

Not on its own. A card records the recommended approach. The safety record has to show what was done on the day, who authorized it and whether the procedure was followed, so link the two rather than treating the card as the record.