ServiceNow Request Fulfilment and Service Catalog for Media and Entertainment

Request Fulfillment and the Service Catalog in a media company are the parts of ServiceNow that take a production team's requests for software, workstations, archive footage, storage and distribution work through approval to delivery. The page helps a catalog owner decide which request shape fits each production need and who approves each one.

Production requests in a media organisation split between routine items such as accounts and equipment, and production-critical requests where a missed deadline costs airtime or a release date. This page works through how a service catalog should handle creative software entitlements and version conflicts, archive and rights-restricted content requests that route to digital asset management teams, broadcast and streaming infrastructure requests, workstation and storage provisioning, and the reporting that content distribution schedules depend on, before settling which request shape fits each production need.

Creative Tool Ecosystem and Software Licensing

Creative professionals use specialised software: Adobe Creative Cloud (Photoshop, Premiere Pro, After Effects), DaVinci Resolve (color grading), Autodesk Maya and 3ds Max for animation, avid Media Composer (professional editing), and niche tools for visual effects, motion graphics, and broadcast graphics. Many of these applications are subscription-based (Adobe Creative Cloud, Avid subscriptions) and seat-licensed. Request Fulfillment and Service Catalog must manage software entitlements: when a new creative professional joins, Service Catalog requests should trigger allocation of appropriate software licenses. When someone leaves, licenses must be reallocated to minimise waste.

Software conflicts are common: different project teams may need different software versions (some edit using current releases, others using previous releases), and some software requires specific operating system versions or GPU compatibility. Service Catalog requests for creative software should capture the project context and required version, allowing IT to recommend compatible configurations and avoid installing incompatible software versions on shared workstations.

Digital Asset Management and Content Library Integration

Media organisations accumulate vast content libraries: archive footage, graphics, music, and effects. Digital asset management (DAM) systems index this content and enable searching and retrieval by production teams. Request Fulfillment should integrate with DAM: requests for archive access, content licensing, or asset catalogue updates flow through Request Fulfillment to DAM teams for fulfillment. If a producer needs to use archive footage in a new project, they submit a DAM access request, which is approved or denied based on licensing restrictions or archive restrictions, then the DAM team provides download links or configures access to the archive.

Rights and licensing are critical in media: archive footage may be restricted to specific uses, music may require synchronisation licensing for specific media types, and stock footage may have geographic or duration restrictions. Request Fulfillment workflows should enforce these restrictions: if a producer requests archive footage with geographic restrictions, the workflow should confirm the intended distribution territory and deny the request if mismatched. This prevents costly licensing violations.

Broadcast and Streaming Infrastructure Requests

Broadcast and streaming platforms require high-availability infrastructure. Live broadcast systems run 24/7; streaming platforms operate continuously with very high availability targets approaching full uptime. Request Fulfillment should support infrastructure requests from platform operations teams: capacity expansion (additional streaming servers, CDN capacity), redundancy improvements (failover systems, geographic distribution), and security updates (encryption upgrades, DDoS mitigation). These are often complex requests involving vendor coordination, testing, and production cutover planning. Build structured workflows that capture infrastructure requirements, coordinate with platform teams and vendors, and schedule changes during agreed maintenance windows.

Some broadcast and streaming requests are emergency scenarios: a primary streaming server fails and backup systems are activated, but capacity is reduced. Request Fulfillment should include rapid escalation paths for emergency infrastructure: on-call infrastructure engineers are alerted, emergency capital approval is secured for rapid expansion, and vendors are notified to expedite delivery of replacement equipment.

Production Workstation and Storage Provisioning

Creative professionals require high-performance workstations: powerful processors for video encoding, dedicated graphics cards for rendering, and fast SSD storage for working files. Request Fulfillment should guide users through workstation configuration based on their role and project type. A video editor needs different specs than a motion graphics designer; render farm operators need different specs than both. Service Catalog should include workstation request items for each persona, with guidance on recommended specs. When a request is approved, IT provisions the workstation and configures it with required software, then schedules a handover with the new user.

Storage for media files is often the bottleneck. A high-definition video project generates terabytes of raw footage, proxies, and renders. Request Fulfillment should allow project teams to request project-specific storage: fast NAS for active editing, cheaper archive storage for completed projects, and cloud storage for distribution and backup. Build capacity planning into storage requests so IT can forecast storage needs and provision infrastructure proactively.

Reporting and Scheduling for Content Distribution

Content distribution involves coordination across multiple platforms and teams: broadcast schedules, streaming platform release schedules, social media content calendars, and international distribution. Request Fulfillment should include catalog items for distribution scheduling: when a production is completed, teams submit distribution requests capturing target platforms (broadcast, streaming, social), target dates, target regions, and any platform-specific requirements (content ratings, subtitles, audio tracks). Fulfillment workflows coordinate with distribution teams, schedule encoding and platform uploads, and confirm content delivery by target date.

Choosing the right request shape for each production need

A service catalog owner in a production company faces a crowd of requests that look alike on the surface. A producer asking for a second edit suite, a freelance editor asking for a license seat and a shoot coordinator asking for a camera hire all arrive as “I need something”. They do not belong in one shape. A catalog item suits a fixed thing with a fixed fulfillment path, such as a standard workstation. A record producer fits a request that must create a record, with its questions answered first, such as a request for archive footage that depends on the intended use. An order guide suits a bundle that has to be assembled from several items, such as a full shoot kit for a remote location. Choosing the wrong shape is the root of most catalog complaints: the form asks too much for simple things, or too little for complicated ones.

An ordered build path for a production request

Catalog work goes faster when the team agrees the path before drawing any forms. The steps below apply to any request that has an approval and a fulfillment team behind it.

1. List the requests the production teams actually raised in the last cycle, and group them by the fulfillment team that handles them, not by the requester’s department.
2. Pick the request shape for each group, using the decision in the table as the test.
3. Write the questions that determine routing first. Every question that does not change who approves or who fulfils the request belongs in a later stage or should be dropped.
4. Attach approvals to the answers that create them, such as a rights approval that appears only when the intended use includes broadcast in a licensed territory.
5. Test each path with a request that is deliberately wrong, to confirm it is rejected or sent back with a reason rather than reaching fulfillment.

Where production requests often break

The first break is the approval that never arrives. A request routes to a budget holder who is on location for three weeks, and the request sits in a queue while the production waits. Give every approval step a delegate, and decide in advance which requests can be auto-approved within a defined limit that the budget holder has set. Deciding which requests qualify is covered in request eligibility. The second break is the change after submission. A producer changes the delivery date or the intended territory after the request is approved, and the fulfillment team continues with the old version. Make material changes a new request linked to the original, so the approval is repeated where it matters.

The third break is the form that asks for the production’s whole history. Producers often abandon long forms and then phone the service desk, which defeats the point of the catalog. Ask only what fulfillment needs, and let the context come from the production record, which already holds the schedule, the crew list and the location.

Signs the catalog is serving the production

Count how many requests reach fulfillment without a clarifying call, and how many are sent back for missing information. Both numbers show whether the questions match the work. Also compare the time producers wait for the first response with the time they wait for completion. A quick acknowledgement followed by a long wait is a different problem from a slow first response, and it needs a different fix.

When a catalog is the wrong answer

Some production needs are conversations, not requests. A director asking for a change in the way a studio is lit is not asking the service desk for anything, and forcing it into a form wastes everybody’s time. Use the catalog for things that have a defined fulfillment path, and send the rest to the production coordinator who can work out what is needed.

Questions catalog owners ask about production requests

Should a freelancer be able to raise requests directly?

Yes, when the request is for something they are already entitled to, such as a standard workstation for an engagement they have been booked on. Requests that commit company money or rights should still pass through the production manager who is accountable for the spend.

How should urgent requests be marked without flooding the queue?

Use a justification field with a short list of reasons that the production coordinator has agreed, and make the urgency visible to fulfillment without reordering the whole queue. A single label that everyone uses for everything can stop meaning anything within a month.

Who owns the catalog item when two production units want different versions?

One owner, one item, and variables for the differences. Two near-identical items with different names will drift apart, and the producers will end up choosing the one with the easiest form.