Media Operations and Project Management

Introduction

Media organizations transform ideas, information and creative concepts into products and services: news bulletins, films, television programmes, podcasts, advertisements, streaming content, live events, social campaigns and digital publications. This transformation is operational. It requires the coordinated management of people, equipment, information, suppliers, money, time and quality standards.

Media operations and project management are closely related but not identical. Operations are the continuing systems that support regular production and distribution. Project management coordinates a temporary undertaking with a defined objective, beginning and end. A media company may operate a daily newsroom while simultaneously managing a documentary, a platform migration and an advertising campaign as projects.

Effective media managers must therefore make practical decisions about scope, budgets, workflows, resources, schedules, suppliers, risk, quality and continuity. They must also balance creative uncertainty with managerial accountability. A strong project plan does not eliminate creativity; it creates the conditions in which creativity can be delivered reliably, legally and economically.

Learning Objectives

By the end of this chapter, students should be able to:

1. Distinguish media operations from media projects and explain their relationship.
2. Design a project scope, work breakdown structure, workflow and schedule.
3. Prepare and control a media budget using appropriate cost categories and performance measures.
4. Allocate human, technical and financial resources while managing constraints.
5. Compare traditional, agile and hybrid project-management approaches.
6. Apply supply-chain, procurement and vendor-management principles to media production.
7. Establish quality controls, performance standards and useful operational metrics.
8. Develop risk, crisis-continuity and recovery plans for media organizations.
9. Evaluate ethical, legal, technological and governance implications of operational decisions.

1. The Operational System of a Media Organization

A media operation can be understood as a system of inputs, transformation processes, outputs and feedback. Inputs include editorial ideas, commissions, audience data, staff time, capital, software, locations, rights and supplier services. Transformation consists of research, planning, production, editing, verification, packaging, distribution and audience engagement. Outputs include content, audience value, advertising inventory, subscriptions, reputation and financial returns. Feedback comes from audience analytics, complaints, reviews, commercial results, post-project evaluations and regulatory findings.

Operations management concerns repeatability and reliability. A broadcaster needs dependable transmission, a newsroom needs a daily assignment process, and a streaming service needs stable content delivery. Project management concerns a temporary change or deliverable, such as launching a new channel, producing a series or relocating a studio. Projects often consume operational resources and may change the operation itself.

Three interdependent constraints are commonly called the project constraint triangle:

• Scope: what the project will deliver.
• Time: when it must be delivered.
• Cost: the approved financial resources.

Quality is not simply a fourth independent constraint. It is affected by decisions about scope, time, cost, resources and standards. Expanding scope without additional time or money may reduce quality or increase risk. A professional manager makes such trade-offs explicit rather than allowing them to occur invisibly.

Stakeholders and governance

Stakeholders include commissioning editors, audiences, journalists, producers, directors, technical staff, finance teams, legal advisers, advertisers, platforms, regulators, vendors, rights holders and communities represented in content. A stakeholder register should identify each party's interests, influence, information needs and preferred method of engagement.

Governance defines who may approve scope, expenditure, editorial changes, risk responses and release. Typical roles include a project sponsor, project manager, workstream leads, finance controller and quality or compliance reviewer. Separating production responsibility from approval authority can reduce conflicts of interest, particularly when legal, safety or editorial impartiality is involved.

2. From Brief to Deliverable

A project begins with a brief. A useful brief states the problem or opportunity, intended audience, proposition, deliverables, success criteria, assumptions, exclusions, budget range, deadline and approval process. Ambiguous briefs create scope creep: the gradual addition of work without corresponding resources or schedule changes.

A scope statement converts the brief into an agreed boundary. It should specify:

• deliverables and acceptance criteria;
• activities included and excluded;
• required formats, versions and platforms;
• rights, accessibility and compliance requirements;
• dependencies and assumptions;
• decision-makers and approval gates.

Work breakdown structure

A work breakdown structure (WBS) decomposes the project into manageable deliverables and work packages. For a short documentary, the hierarchy might be:

1. Development

• research
• treatment and proposal
• rights and contributors

1. Pre-production

• schedule and locations
• crew and equipment
• risk assessment

1. Production

• interviews
• observational filming
• data and media management

1. Post-production

• edit
• sound and colour
• captions and graphics

1. Delivery

• legal and editorial review
• masters and metadata
• publication and evaluation

The WBS is deliverable-oriented, not merely a list of staff activities. Each work package should have an owner, an estimated effort, dependencies, acceptance criteria and a completion definition. Decomposition should stop when a package can be estimated, assigned and monitored without further ambiguity.

Workflow design

A workflow specifies how work moves between people, systems and approval points. A basic media workflow is:

brief → research → planning → production → ingest and backup → edit → review → compliance and rights clearance → final mastering → distribution → evaluation

Workflows should identify hand-offs, information required at each stage, expected service times, rework procedures and escalation routes. Digital asset management is especially important. File naming, version control, metadata, access permissions, backup and retention policies prevent lost media and accidental publication of obsolete versions.

A workflow may be represented through a RACI matrix:

One person may be responsible and another accountable, but accountability should not be diffuse. A RACI matrix is most useful for cross-functional tasks and approval gates, not for documenting every minor action.

3. Scheduling and Time Management

A schedule translates the WBS into dates, dependencies and resource commitments. Common tools include milestone plans, Gantt charts, network diagrams, Kanban boards and release calendars.

A dependency identifies how one activity relates to another. In a finish-to-start dependency, Activity B cannot start until Activity A finishes. Other relationships include start-to-start, finish-to-finish and finish-to-start with a lag. Managers must distinguish technical dependencies from preferences. If an edit can begin with rough footage while filming continues, the schedule may use parallel work rather than an unnecessarily sequential process.

The critical path is the sequence of dependent activities that determines the shortest possible project duration. If activity durations on the critical path increase, the project completion date normally increases unless the manager changes resources, methods or dependencies. Activities with scheduling flexibility possess float. In a simple network, total float may be expressed as:

Here, earliest start and latest start are calendar or time-unit values calculated from the project network. The expression is applicable when the schedule uses a consistent time scale and the relevant network logic has been correctly established. A zero-float activity is commonly critical, although calendars, constraints and resource limits can complicate that interpretation.

A schedule should include more than creative work. It must allow time for contracting, travel, permits, data transfer, backups, accessibility versions, fact-checking, legal review, client feedback, technical quality control and contingency. A deadline that ignores these activities is not a realistic deadline.

Worked example: capacity planning

A post-production team has 120 available labour hours during a week. A project requires 75 editing hours, 20 sound hours and 15 graphics hours. Planned work is therefore:

75 + 20 + 15 = 110 hours.

The unused capacity is:

120 − 110 = 10 hours.

This does not mean that ten hours can automatically be sold to another project. Meetings, administration, sickness, technical failures and uneven daily demand may consume some of the apparent capacity. Capacity planning should therefore distinguish nominal capacity from effective capacity. If management deliberately reserves 15% of the 120 hours for interruptions, effective planned capacity is:

120 × (1 − 0.15) = 102 hours.

The 110-hour plan then exceeds effective capacity by 8 hours. The manager must re-sequence tasks, add approved resources, reduce scope or negotiate the deadline.

4. Budgeting and Financial Control

A media budget is a financial representation of the project plan. It should be built from the WBS rather than from an arbitrary total. Typical cost categories include development, personnel, freelance labour, equipment, locations, travel, insurance, rights, production services, post-production, accessibility, distribution, marketing, administration and contingency.

Costs may also be classified as:

• Direct costs: traceable to a project, such as a camera rental.
• Indirect costs: shared overheads, such as office administration.
• Fixed costs: unchanged within a relevant activity range, such as a licence fee.
• Variable costs: change with output or usage, such as per-minute captioning.
• Committed costs: contractually agreed but not yet paid.
• Actual costs: costs already incurred.

A cost baseline is the approved time-phased budget against which expenditure is monitored. It should not be changed informally merely to make performance appear favourable. Approved changes should be documented with their reason, impact and authorisation.

A simple cost estimate is:

The summation covers all relevant cost items. Quantity may be hours, days, units or licences; unit cost must use the same currency and time basis. Contingency is a planned allowance for identified uncertainty, not a secret fund for unapproved scope expansion. Its size should reflect the quality of estimates, risk exposure and organizational policy.

For example, a project has the following direct estimates: crew £8,000, equipment £3,000, locations £2,000, post-production £7,000 and rights £1,500. The subtotal is:

8000 + 3000 + 2000 + 7000 + 1500 = £21,500.

If approved contingency is 10% of the subtotal, contingency is £2,150 and the budget baseline is £23,650. This calculation assumes that the percentage is defined as a proportion of the subtotal. It should not be confused with a percentage of the final total, which would produce a different result.

Earned value concepts

For larger projects, earned value management compares planned, completed and actual work. Three basic measures are:

• Planned value (PV): budgeted value of work scheduled by a date.
• Earned value (EV): budgeted value of work actually completed by that date.
• Actual cost (AC): cost actually incurred for completed work.

Two common indices are:

An index of 1 indicates parity with the relevant baseline. An SPI below 1 indicates less budgeted work has been completed than planned; a CPI below 1 indicates that actual cost exceeds the budgeted value of completed work. These indicators depend on credible progress measurement and should not be interpreted as a substitute for editorial or quality judgement.

Suppose PV is £40,000, EV is £36,000 and AC is £45,000. Then SPI is 36,000 ÷ 40,000 = 0.90, while CPI is 36,000 ÷ 45,000 = 0.80. The project is behind the planned rate and obtaining £1 of budgeted work has cost £1.25. A manager should investigate the causes rather than simply cut quality-critical work.

5. Resource Management and Supply-Chain Thinking

Media production is a supply chain. Ideas and commissions enter at one point; specialist labour, facilities, technology, rights and services are acquired; content is transformed and delivered to audiences or clients. Disruption at any link can affect the entire project.

Supply-chain thinking asks five questions:

1. What inputs are essential?
2. Who controls or supplies them?
3. What lead time and capacity constraints exist?
4. What alternatives are available?
5. What information and quality standards must move between parties?

Resource planning includes people, equipment, locations, software, data, facilities and money. Managers should assess availability, skill, workload, safety, accessibility and substitution options. Over-reliance on one editor, cloud provider, camera supplier or rights holder creates a single point of failure.

Procurement and vendor management

A professional procurement process usually includes requirements definition, market research, quotation or tender, evaluation, negotiation, contracting, onboarding, monitoring and close-out. Selection should consider total value rather than only price. Relevant criteria may include:

• technical capability and compatibility;
• reliability and capacity;
• price and payment terms;
• data protection and cybersecurity;
• insurance, safety and legal compliance;
• accessibility and sustainability;
• references and service-level commitments;
• ownership, licensing and exit arrangements.

A contract should state deliverables, milestones, acceptance tests, intellectual-property ownership or licence scope, confidentiality, data handling, change control, cancellation, liability, insurance, dispute resolution and payment conditions. Verbal promises are difficult to manage when a project is under pressure.

A service-level agreement (SLA) translates expectations into measurable standards. It may define uptime, response time, restoration time, delivery format, defect thresholds and escalation. A manager should distinguish a service-level target from a remedy: the former states expected performance, while the latter states what happens if performance fails.

Vendor relationships require active management. Performance reviews should use evidence such as on-time delivery, defect rates, responsiveness, budget variance and incident records. Ethical procurement prohibits conflicts of interest, undisclosed commissions, discriminatory selection and misuse of confidential bids.

6. Traditional, Agile and Hybrid Approaches

A traditional or predictive approach defines substantial scope early and moves through planned stages. It is useful when requirements are stable, compliance is strict, dependencies are known and late change is expensive. A broadcast transmission upgrade or a regulated archive migration may benefit from formal stage gates.

Agile approaches accept that requirements and solutions may evolve. Work is divided into short cycles, often called iterations or sprints, and stakeholders review usable increments. A product backlog prioritises work; a sprint goal defines the immediate objective; a review gathers feedback; and a retrospective examines how the team can improve. Agile is not an absence of planning. It uses rolling-wave planning: near-term work is specified in detail while later work remains adaptable.

Agile methods are valuable for digital products, audience experiments, interactive formats and platform features where user feedback is significant. They are less suitable when every requirement must be fixed before work begins or when a live production cannot safely tolerate frequent change.

A hybrid approach may use predictive procurement, safety and delivery milestones with agile creative development. For example, a podcast platform project may have a fixed legal launch date and infrastructure contract while allowing iterative testing of user journeys and recommendation features.

The method should fit uncertainty, not managerial fashion. Managers should ask:

• Is the desired outcome clear even if the solution is uncertain?
• Can users review increments early?
• Are changes affordable and reversible?
• Are external approvals or contracts sequential?
• What evidence defines “done”?

7. Quality, Performance and Continuous Improvement

Quality has at least three dimensions in media: technical quality, editorial or creative quality, and service or audience quality. Technical quality may involve audio levels, image resolution, file formats, caption synchronization and platform specifications. Editorial quality includes accuracy, fairness, originality, context and respect for subjects. Service quality includes accessibility, discoverability, reliability and delivery on schedule.

Quality assurance (QA) designs processes to prevent defects. Quality control (QC) inspects outputs to detect defects. Examples include approved templates, fact-checking protocols, two-person verification of sensitive data, automated file checks, editorial review, caption review and final master inspection.

Acceptance criteria should be observable. “High quality” is weak; “all dialogue is captioned, the master meets the platform codec specification, names and figures are verified, and rights documentation is complete” is testable. Quality gates should occur before irreversible or expensive stages, such as before a shoot, before final mastering and before publication.

Useful indicators include:

Continuous improvement uses evidence to modify the system. A post-project review should ask what was expected, what happened, why differences occurred, and which process change should be tested. Blaming individuals without examining workflow design produces little learning.

8. Risk, Crisis and Continuity Planning

Risk is an uncertain event or condition that may affect objectives positively or negatively. A risk register records the risk, cause, consequence, probability, impact, owner, response and status. Responses to threats include avoiding, reducing, transferring or accepting the risk. Opportunities may be exploited, enhanced, shared or accepted.

A qualitative risk matrix ranks probability and impact. It is a prioritisation tool, not a precise prediction. A high-impact, low-probability event may deserve more attention than a frequent minor delay because its consequences are severe.

Business continuity planning addresses how essential operations continue during disruption. Media-specific disruptions include:

• loss of a studio, location or transmission facility;
• cyberattack or ransomware;
• cloud or platform outage;
• extreme weather or transport failure;
• illness or unavailability of key staff;
• legal injunction or rights withdrawal;
• misinformation, harassment or threats;
• loss or corruption of media files.

A continuity plan should identify critical services, recovery priorities, minimum operating requirements, alternate facilities and suppliers, communication channels, decision authority, data backups and restoration tests. A useful distinction is:

• Recovery time objective (RTO): maximum acceptable time to restore a service.
• Recovery point objective (RPO): maximum acceptable amount of data loss measured in time.

For example, an RPO of four hours means that restoration should lose no more than four hours of transactions or changes, assuming the backup system is properly configured and tested. Neither RTO nor RPO is meaningful without assigned owners, resources and exercises.

Crisis communication should be rapid, accurate, coordinated and appropriately transparent. A holding statement may acknowledge the incident without speculating. A crisis team should maintain an incident log, verify facts, protect personal information, brief staff and update stakeholders at agreed intervals. After recovery, a post-incident review should address both technical causes and organizational conditions.

9. Technology, Automation and Artificial Intelligence

Cloud collaboration, digital asset management, remote production, automated quality checks, workflow orchestration and audience analytics have changed media operations. Automation can reduce repetitive work, improve metadata consistency and identify technical errors. However, automation may also propagate incorrect metadata, expose confidential material or create opaque decisions.

AI tools can assist with transcription, translation, search, summarisation, scheduling, audience segmentation, synthetic media detection and rough-cut support. Responsible use requires clear human accountability. Managers should assess:

• accuracy and bias, especially for accents, minority languages and sensitive subjects;
• copyright and licensing of training data or generated outputs;
• privacy and confidentiality of uploaded material;
• disclosure and consent for synthetic or manipulated content;
• security, auditability and vendor retention policies;
• consequences of automation for employment and professional skills.

AI should not be treated as an unquestionable editor, fact-checker or rights authority. Human review remains necessary for consequential editorial decisions, legal claims, identity, consent and representation. Organizations should maintain an approved-tools register and document acceptable use, review standards and incident escalation.

10. Ethics, Regulation and Governance

Operational efficiency cannot justify unlawful or unethical practice. Media managers must integrate legal and ethical requirements into planning rather than treating them as final obstacles. Relevant concerns include copyright, moral rights, privacy, defamation, confidentiality, consent, employment law, health and safety, accessibility, advertising standards, data protection and platform rules. Exact duties vary by jurisdiction and media sector; professional advice should be obtained for high-risk projects.

Ethical operations also concern representation and working conditions. Scheduling should not normalize excessive hours or unsafe environments. Procurement should avoid exploitation and hidden conflicts. Accessibility should be planned through captions, transcripts, audio description, sign-language interpretation, readable design and inclusive testing where appropriate.

Governance documents create institutional memory. Approval logs, rights records, risk registers, version histories and incident reports make decisions auditable. Auditability protects both the organization and individuals by showing who approved what, on what evidence and under which policy.

11. Illustrative Case: The Delayed Investigative Series

Background

A fictional regional broadcaster commissions a six-part investigative podcast series for release in twelve weeks. The approved budget is £48,000. The project involves freelance reporters, confidential sources, field recording, legal review, audio post-production, transcripts and distribution through several platforms.

Problem

After four weeks, only one episode has entered editing. Two interviews require additional verification, a key freelance reporter is unavailable, and the initial budget report shows £19,000 spent. The original plan assumed sequential research, recording and editing, leaving little time for legal review or accessibility versions.

Analysis

The project manager first separates facts from assumptions. The remaining budget is £48,000 − £19,000 = £29,000, but committed costs and future rights fees must be identified before treating this as spendable cash. A rapid WBS review reveals that transcripts, legal review and platform testing were under-scoped. The schedule is reconstructed using dependencies, and editing is allowed to proceed on verified material while later reporting continues.

Risk analysis identifies three high-priority threats: loss of investigative capacity, legal delay and source-security failure. The project also has a quality risk: pressure to publish could reduce verification. The manager therefore rejects an option to remove legal review, even though it appears to save time.

Approach and solution

The team adopts a hybrid method. A fixed launch date, legal gate and accessibility requirement remain non-negotiable. Editorial development is managed through weekly planning and review cycles. A second qualified reporter is contracted under a documented agreement. The team uses encrypted storage for sensitive materials, separates identifying information from working audio, and establishes a two-person verification rule for serious allegations.

A revised budget reserves money for the additional reporter, transcription and legal review. The producer creates a daily risk check during fieldwork and a weekly dashboard showing milestone status, committed cost, actual cost, unresolved rights and defects. The commissioning editor approves a scope change: two lower-priority episodes are shortened rather than reducing verification standards.

Outcome

The series launches one week later than the original date but within the approved revised budget. All episodes include transcripts, and the broadcaster documents the legal basis for publication and source-protection procedures. Audience completion is strong, but the post-project review identifies avoidable weaknesses in the original brief, especially the failure to budget for accessibility and investigative verification.

Learning points

1. A budget is credible only when it reflects the full WBS and committed obligations.
2. Schedule compression should not remove safety, legal or editorial quality gates.
3. Hybrid management can combine fixed governance requirements with iterative creative work.
4. Scope reduction is preferable to silent quality degradation.
5. Confidentiality and information security are operational requirements, not merely legal add-ons.

Challenges and Limitations

Media projects contain uncertainty that cannot be eliminated by planning. Creative quality is partly subjective, audience response is difficult to predict, and external events may change relevance or demand. Forecasts and metrics can create false confidence when underlying data are incomplete. Earned value may measure progress poorly if deliverables are highly creative or if “completion” is difficult to define.

Agile methods can become chaotic without product ownership, prioritisation and a definition of done. Predictive methods can become bureaucratic when documents are maintained for their own sake. Vendor competition may reduce cost but increase coordination or ethical risk. Automation may increase speed while weakening human judgement. Managers must therefore use frameworks as decision aids, not as substitutes for professional reasoning.

Best-Practice Checklist

Before approving a media project, confirm that:

• the brief, scope and exclusions are explicit;
• deliverables have acceptance criteria;
• the WBS includes rights, accessibility, data, safety and distribution;
• estimates identify assumptions, contingency and committed costs;
• dependencies, milestones and resource capacity are realistic;
• roles and approval authority are documented;
• vendors are evaluated on capability, risk and total value;
• quality gates and version controls are defined;
• risks have owners and response plans;
• continuity priorities, backups and communication procedures are tested;
• AI and automation use is governed and reviewed;
• lessons learned will be recorded and applied.

Chapter Summary

Media operations provide the repeatable systems through which organizations create and distribute value, while projects deliver temporary outputs or change. Effective management begins with a clear brief, defined scope, stakeholder governance and a deliverable-oriented WBS. Workflows, RACI matrices, dependency analysis and realistic capacity planning convert intention into coordinated action.

Budgets should be built from work packages, distinguish direct and indirect costs, include uncertainty transparently and be monitored against an approved baseline. PV, EV, AC, SPI and CPI can support performance analysis when progress and costs are measured consistently. Supply-chain thinking highlights dependencies among staff, facilities, rights holders, technology providers and distributors. Vendor management requires clear requirements, fair selection, suitable contracts and evidence-based performance review.

Predictive, agile and hybrid methods each have appropriate uses. Quality must be defined through observable standards and protected by assurance, control and approval gates. Risk registers, continuity plans, RTO, RPO, tested backups and coordinated crisis communication help organizations remain resilient. Finally, technology and AI can improve operations only when privacy, copyright, security, fairness, accountability and human judgement remain central.

Key Terms

Agile project management: An iterative approach that delivers work in short cycles and incorporates feedback.

Acceptance criteria: Observable conditions that a deliverable must meet to be approved.

Business continuity: The capability to maintain or restore essential operations during disruption.

Critical path: The sequence of dependent activities that determines the shortest achievable project duration.

Earned value (EV): The budgeted value of work actually completed by a specified date.

Float: Scheduling flexibility available to an activity without delaying a defined project milestone.

Governance: Structures and authorities used to direct, approve and control a project.

Hybrid method: A project approach combining predictive and agile practices.

Operational capacity: The amount of effective work an organization can perform with available resources.

Planned value (PV): The budgeted value of work scheduled to be completed by a specified date.

Quality assurance: Planned processes intended to prevent defects.

Quality control: Inspection and testing used to identify defects in outputs.

Recovery point objective (RPO): The maximum acceptable period of data loss measured in time.

Recovery time objective (RTO): The maximum acceptable time for restoring a service.

Risk register: A controlled record of risks, causes, effects, owners and responses.

Scope creep: Uncontrolled expansion of project requirements.

Service-level agreement (SLA): A documented agreement specifying measurable service expectations.

Stakeholder: A person or organization that affects, is affected by or perceives itself affected by a project.

Work breakdown structure (WBS): A hierarchical decomposition of project deliverables and work packages.

Review Questions

Short Answer Questions

1. What is the difference between media operations and a media project?
2. Define scope creep and state one method for controlling it.
3. What information should a work package contain?
4. Distinguish quality assurance from quality control.
5. What do RTO and RPO measure?

Long Answer Questions

1. Explain how a media manager can convert a creative brief into a controlled project plan.
2. Compare predictive, agile and hybrid approaches and identify an appropriate context for each.
3. Discuss how supply-chain thinking improves media procurement and vendor management.
4. Explain the role of budgets, cost baselines and performance indicators in project control.
5. Analyse the relationship between quality, schedule, cost and scope in media production.

Analytical / Application Questions

1. A video project has a fixed launch date, uncertain audience requirements and strict accessibility obligations. Recommend a project-management approach and justify your choice.
2. A supplier repeatedly delivers files late and with technical defects. Design a vendor-performance and escalation plan using contract, SLA and quality-control principles.
3. A newsroom loses access to its main editing facility after a cyber incident. Develop the first five operational priorities in a continuity and crisis-response plan.

Multiple Choice Questions with Answers

Question 1

Which item is most appropriately included in a project scope statement?

A. A list of unrelated industry trends

B. Deliverables, exclusions and acceptance criteria

C. Only the names of project employees

D. A guarantee that no risk will occur

Correct Answer: B. Deliverables, exclusions and acceptance criteria

Question 2

A project has planned value of £40,000, earned value of £36,000 and actual cost of £45,000. What is its cost performance index?

A. 0.80

B. 0.90

C. 1.11

D. 1.25

Correct Answer: A. 0.80

Question 3

What is the primary purpose of a work breakdown structure?

A. To eliminate the need for a budget

B. To decompose deliverables into manageable work packages

C. To replace all stakeholder communication

D. To calculate audience ratings automatically

Correct Answer: B. To decompose deliverables into manageable work packages

Question 4

Which situation most strongly supports an agile approach?

A. Stable requirements and a legally fixed technical specification

B. A project requiring iterative user feedback and evolving requirements

C. A safety inspection with a prescribed checklist

D. A supplier invoice reconciliation

Correct Answer: B. A project requiring iterative user feedback and evolving requirements

Question 5

In a RACI matrix, the accountable person is the person who:

A. Receives every project email

B. Performs every task personally

C. Owns the final decision or outcome

D. Provides an external quotation

Correct Answer: C. Owns the final decision or outcome

Question 6

If a project subtotal is £21,500 and contingency is 10% of that subtotal, what is the budget baseline?

A. £21,600

B. £22,150

C. £23,650

D. £24,500

Correct Answer: C. £23,650

Question 7

Which practice is an example of quality assurance rather than quality control?

A. Inspecting the final master for audio defects

B. Testing captions after delivery

C. Establishing a standardised review and verification process

D. Rejecting a file that fails a codec test

Correct Answer: C. Establishing a standardised review and verification process

Question 8

What does an RPO specify?

A. The maximum acceptable time to restore a service

B. The maximum acceptable amount of data loss measured in time

C. The total project budget

D. The number of staff needed for a production

Correct Answer: B. The maximum acceptable amount of data loss measured in time

Question 9

Which is a sound vendor-management practice?

A. Selecting solely on the lowest quoted price

B. Leaving deliverables undefined to preserve flexibility

C. Defining measurable service standards and escalation procedures

D. Avoiding written contracts for trusted suppliers

Correct Answer: C. Defining measurable service standards and escalation procedures

Question 10

Why should human review remain central when AI is used for media operations?

A. AI cannot perform any repetitive task

B. Human accountability is needed for accuracy, bias, rights and consequential decisions

C. Automation always increases production cost

D. AI systems are legally prohibited in all media work

Correct Answer: B. Human accountability is needed for accuracy, bias, rights and consequential decisions