Planning Assets, Hardware, Software & File Management
Identifying the Assets You Need
Before any media product can be created, a producer must identify every asset that will be needed. Assets fall into several categories: images (photographs, illustrations, icons); audio (background music, sound effects, voiceover recordings); video clips (footage, screen recordings); graphics (logos, charts, diagrams); and text (copy, captions, headings). Listing all required assets at the planning stage prevents the common problem of reaching the editing phase and discovering that a critical file is missing, unavailable or in the wrong format.
For each asset, a creator should note: what the asset is; whether it will be created from scratch, sourced from a stock library, or provided by the client; who is responsible for obtaining or creating it; and any legal considerations such as copyright or licence requirements. This asset list becomes part of the pre-production documentation and helps ensure the project remains on schedule.
Hardware and Software for Asset Creation
Different asset types require different hardware and software. A digital camera or smartphone is used to capture photographs; a microphone and audio interface capture high-quality audio; a graphics tablet allows artists to draw digitally; a scanner converts physical drawings into digital files; and a powerful computer is needed for video rendering. Choosing the right hardware for the job affects the quality and speed of asset creation.
Software choices are equally important. Common applications include: Adobe Photoshop or GIMP for editing still images; Adobe Illustrator or Inkscape for creating vector graphics; Adobe Premiere Pro or DaVinci Resolve for video editing; Audacity or Adobe Audition for audio editing; and Canva or Adobe InDesign for layout and publication design. Each application is specialised for a particular type of asset; using the wrong tool can lead to poor-quality outputs or unnecessary file conversions.
For the exam, you need to know the correct hardware and software pairing for common asset types: still images (camera/scanner + Photoshop/GIMP); audio (microphone + Audacity/Audition); vector graphics (graphics tablet + Illustrator/Inkscape); video (video camera + Premiere Pro/DaVinci Resolve); publication layout (computer + InDesign/Canva).
Understanding file formats is essential for saving and sharing assets correctly. For images: JPEG (lossy compression, small file size, best for photographs on the web); PNG (lossless, supports transparency, best for logos and graphics with sharp edges); GIF (lossless, supports simple animation, limited to 256 colours, best for short looping web animations); TIFF (lossless, very large files, used in print production where maximum quality is needed). For audio: MP3 (lossy compression, small file size, good for web streaming and podcasts); WAV (uncompressed, very large files, used in professional audio production where editing quality matters). For video: MP4 using the H.264 codec (efficient lossy compression, widely compatible, standard for web and social media delivery). For print-ready documents and layouts: PDF (preserves formatting across all devices and print setups). Choosing the correct format depends on the intended use: web delivery favours small, compressed files; professional editing and print favour uncompressed or lossless formats.
File Naming and Version Control
Good file naming and version control practices are essential in any media project. File names should be descriptive, consistent and free from spaces or special characters that can cause compatibility problems across different operating systems. A sensible naming convention might be: project-name_asset-type_version-number, for example charity-poster_hero-image_v3.psd. Version numbers allow a creator to keep earlier iterations of a file in case a later version needs to be rolled back. Without version control, overwriting a working file with a broken revision can cause hours of lost work.
A sensible folder structure for a media project separates assets by type. A top-level project folder might contain sub-folders named: images, audio, video, graphics, exports and working-files. Keeping all assets for one project in a single, well-organised folder structure ensures files are easy to find, easy to share with a team and easy to hand over to a client at the end of the project.
In a professional context, poor file naming has real consequences. A file named “final2_ACTUAL_v3_USE THIS ONE.jpg” is a common but damaging mistake: if a colleague is asked to use the correct version, they cannot identify it at a glance. Spaces in file names can break web links and script references. Special characters such as & or # can cause errors in some operating systems and web servers. In team projects, file naming conventions should be agreed at the start of the project and documented in the work plan so that everyone applies them consistently. In a school context, clear file names also make it far easier for an assessor to navigate submitted work.