Creative Software Tools and Digital Workflow

01Purpose and scope

• This manual supports the course Creative Software Tools and Digital Workflow. It is written as a working reference for people who use design, photo, illustration, video, and publishing applications to produce client or internal work, and for those who coordinate the people and files around that work. It describes how tools are selected, how files move from capture or creation through editing and review to final delivery, and how teams keep that movement orderly.
• The scope covers general practice that applies across most creative software, including raster and vector editing, layout, image and video finishing, and export for print, web, and broadcast. It does not teach the commands of any single application. Where a specific product's behavior matters, such as how a file format stores layers or how a plug-in handles color, check that product's current documentation because features change between versions and between subscription tiers.
• Practice changes with context. A solo illustrator working on a sketchbook project needs very little process. A studio handing finished packages to a printer, a broadcaster, or an agency with its own specifications needs much more, and the specifications those outside parties set are the authority for that work. Treat this manual as the baseline and adjust it to the requirements in each contract or brief.

02Core principles

• Keep the source separate from the output. Editable masters, such as layered documents, project files, raw captures, and uncompressed audio, should be stored apart from exported deliverables. Exports are disposable and can be regenerated. Masters are expensive to recreate and often hold the only record of decisions made during editing.
• Prefer reversible edits. Adjustment layers, smart objects, clip-based timelines, and parametric shapes let a reviewer ask for a change without rebuilding the piece. Destructive steps such as flattening, rasterizing, or baking transforms into pixels belong at the end of a job, after the design is accepted, and should be recorded as a deliberate step.
• Decide the output first. Before opening a project, know the pixel dimensions, resolution or viewing distance, color space, file format, frame rate, and accessibility requirements. Most rework in creative production comes from discovering late that a file was built for the wrong destination.
• Make names carry information. A file name should say what the file is, which version it is, and where it sits in the pipeline. Names that rely on memory, such as final2 or newest, produce errors that surface at print proof or client review.
• Limit the tools in use. Each additional application adds file conversion steps, license requirements, and learning load. Choose a small set that covers the work and use each for what it does best.

03Planning and preparation

• Start with a brief that names the deliverables, audience, channels, dates, approval path, and any technical specifications from the client or destination. If a brief omits these, write down the assumptions and get them confirmed before production begins. A short written list of assumptions is often the cheapest protection against a dispute later.
• Set up the project structure before creating content. Create a root folder with subfolders for source assets, working files, exports, and reference material. Store fonts, licensed images, and any third-party templates with their license documents. Confirm that each licensed asset permits the intended use, including print run size, geographic reach, and duration where those terms apply.
• Choose the color and document setup deliberately. For print work, confirm the intended printing process and the ICC profile or proofing condition the printer uses, and request a current proof or specification sheet rather than relying on a generic preset. For screen work, decide on the working color space and whether the audience will view on consumer devices with varying calibration. For video, confirm frame rate, resolution, aspect ratio, and audio levels against the delivery specification.
• Estimate hardware and storage needs. Video projects in particular can consume large amounts of storage for raw footage, proxies, caches, and renders. Confirm that the workstation and backup targets have enough space for the project, and plan where render caches will live so they do not fill the system drive.
• Agree on a review plan. Decide how many review rounds are included, who approves, what format feedback should arrive in, and how changes after approval will be handled. Tools for annotated review exist, but a shared written feedback log is often enough for small teams.

04Recommended workflow

1. 1
   : Build the project from the brief. Create the document or timeline with the exact output dimensions, color settings, and frame rate confirmed in planning. Save the first version with a name that records the project, the deliverable, the version number, and the date of the working session in a format your team agrees on.
2. 2
   : Gather and check source material. Import photographs, illustrations, footage, and audio into the project's source folder rather than linking to files on a desktop or in a download folder. Check resolution, sample rate, and color profile on arrival. Flag any file that is too small for its intended size or that carries an unknown profile.
3. 3
   : Block out the structure before detailing it. For a layout, place the grid, headings, and image frames with placeholder content. For a video, assemble the rough cut from selects and leave titles and grading for later. Early structure review catches problems in hierarchy or pacing when they are still cheap to fix.
4. 4
   : Work in layers, groups, and nondestructive steps. Use adjustment layers for tone and color, masks for selective changes, and smart objects for repeated graphics. Name layers and tracks clearly. Group related elements so a reviewer can toggle them. Avoid merging layers until the final export stage.
5. 5
   : Run an internal review before the client sees the work. Check spelling, cropping, edge contrast, text legibility at the intended size, and audio levels. Print or view the piece on the same kind of device the audience will use, because screens and paper reveal different problems.
6. 6
   : Export deliverables from the master. Use the export preset that matches the specification sheet, and generate every required format from the same master so versions do not drift. Keep the export settings in the project notes so the same output can be reproduced after a revision.
7. 7
   : Package and archive. Collect the final exports, the editable master, linked or embedded fonts where licensing allows, a list of included assets, and the approval record in one delivery folder. Store an archive copy on separate media from the working drive, and label it with the project name and the version that was approved.

05Quality checks, risk controls and compliance

• Check technical output against the specification, not against memory of the specification. Common checks include confirming color mode and profile, embedded image resolution at final size, bleed and trim for print, safe margins for video, loudness targets for audio, and file format and codec. Automated preflight tools in print and video applications can catch many of these, but a person should still look at the result on the actual medium.
• Control rights and permissions as a deliberate process. Keep a register of licensed fonts, stock images, music, and footage with the license type, the permitted use, and the expiration of any term. Do not assume that a free-for-personal-use asset is cleared for commercial use. Copyright, trademark, and publicity rules differ by jurisdiction and by license, so for anything with legal exposure, consult the license text and, where needed, qualified legal counsel.
• Watch for accessibility requirements. Text contrast, font size, alternative text for images, captions for video, and reading order in documents are increasingly expected by clients and in some public procurement. The specific legal requirements depend on jurisdiction and sector, so confirm them with the client or the relevant authority rather than assuming a general standard applies.
• Protect files and personal data. Client photographs can include identifiable people, and footage can capture private locations. Confirm releases where they are needed, restrict access to sensitive material, and remove embedded metadata such as location data before external delivery when the brief or your policy requires it.
• Handle regulated content with care. Creative work for medical, financial, legal, safety, or pharmaceutical clients often carries required wording, disclaimers, or approval steps. This manual does not replace the judgment of qualified professionals or the approved procedures of the organization responsible for that content, and some materials may require formal sign-off before release.

06Collaboration and documentation

• Assign roles explicitly. A typical small project has a producer who owns the brief and schedule, a designer or editor who owns the master files, a reviewer who gives consolidated feedback, and a delivery lead who handles exports and handoff. One person may hold several roles on a small job, but the responsibilities should still be written down.
• Use a single source of feedback. Feedback that arrives by phone, in chat, and in marked-up PDFs from different people is hard to reconcile. Ask reviewers to send comments through one channel, identify the person and version each comment refers to, and mark items as accepted, declined, or pending. A declined item should carry a reason.
• Keep a project log. Record major decisions, font and color choices, export settings, asset substitutions, and the reasons for them. When a client questions a change six months later, or a new designer picks up the work, a short log answers the question faster than reconstructing the history from file timestamps.
• Share files in a controlled way. Cloud storage and shared drives are common, but sync conflicts can overwrite work or duplicate files. Use check-in and check-out conventions, separate working copies for each contributor, or a version control approach suited to binary files. Large video projects often need a media management tool or a separate shared media store rather than a general file sync service.

07Measures and continuous improvement

• Track a small set of indicators. Useful measures include the number of review rounds per deliverable, the share of files delivered without a technical correction, time from brief to first internal review, and the number of asset or license issues found after delivery. Choose measures that point to a decision you can make, and avoid collecting numbers that no one reads.
• Review completed projects in a short retrospective. Ask what caused the most rework, which steps took longer than planned, and which checks would have caught the problem earlier. Write the answers as changes to the templates, presets, or checklists the team uses, so the lesson carries into the next job.
• Maintain templates and presets. Document templates, export presets, color settings, and naming conventions are valuable only if they are current. Assign an owner to review them when a software version changes, when a major client updates specifications, or when a recurring error appears.
• Know the limits of measurement. Creative quality is partly subjective, and short cycle times can hide weak work. Pair speed and error measures with periodic review of finished pieces against the original brief, and be cautious about drawing conclusions from a small number of projects.

08Common mistakes and how to prevent them

• Building at the wrong resolution. A logo drawn at screen size and later scaled for a banner or signage will look soft. Prevent this by setting the document size from the largest intended use, or by building in vector form for logos and illustrations that must scale.
• Flattening too early. Merging layers before approval makes changes slow and error prone. Keep a master file with all layers, and create flattened copies only for export or for a specific external requirement.
• Ignoring color profiles. Images imported without a recognized profile, or converted repeatedly between color spaces, shift in appearance across devices and printers. Set a working profile at the start, convert deliberately at output, and check proofs on the right viewing conditions.
• Relying on fonts that are not packaged. A file that opens correctly on the designer's machine can fail at the printer if fonts are missing or substituted. Include licensed fonts where the license allows, or convert text to outlines for final artwork that will not be edited.
• Losing track of versions. Files named final, final_v2, and final_really_final cause delivery to the wrong version. Use a numbered version scheme, record the approved version in the log, and keep the older versions in an archive folder rather than the working folder.
• Underestimating render and export time. Video and high-resolution print exports can take hours. Schedule renders before deadlines, test a short segment first, and avoid exporting a full project for the first time on the day it is due.
• Skipping the destination check. Work reviewed only on a bright monitor can look different on a phone, a printed page, or a broadcast monitor. Build a habit of viewing the piece in the form the audience will see it.

09Practical checklist

• Confirm the brief, deliverables, specifications, approval path, and license terms in writing before production starts.
• Set up the project folder structure and store licensed assets and fonts with their license records.
• Create the master document or timeline with the exact output dimensions, color settings, and frame rate.
• Import source material into the project folder and check resolution, profile, and audio levels on arrival.
• Keep edits nondestructive and name layers, groups, and tracks so a reviewer can follow them.
• Run an internal review on the destination medium and correct legibility, cropping, and timing issues.
• Export every deliverable from the master using the documented preset and record the settings.
• Run technical preflight against the specification and inspect the output on the actual medium.
• Collect feedback through one channel, log each comment with its status, and record decisions.
• Package the final exports, master, asset list, and approval record, and store an archive copy on separate media.
• Hold a short retrospective and update the templates, presets, or checklists with what was learned.

★Learning sources

• Micro Degree: Creative Software Tools and Digital Workflow
• Micro Degree: 2D Animation Fundamentals
• Micro Degree: 3D Animation Techniques
• Micro Degree: Illustration Fundamentals