vaayaa Inclusive Education
Creative risk assessment

Design Foundations and Visual Theory Risk Assessment: Briefs, Rights, Accessibility and Production Controls

A worked example of how a student design team finds, scores and controls risks in visual work, from unclear briefs and unlicensed imagery to accessibility gaps, version confusion and file compatibility problems.

Updated November 2026 8 hazards assessed Review every 6 months Highest risk: Critical to Medium
See the Design Foundations and Visual Theory course

Executive summary

This assessment shows how a small design team can find, rate and control the risks that matter most to the quality, rights and reputation of visual work. Eight risks were chosen because they are plausible in everyday design practice, from briefs that grow without limit to files that fail at the printer. The highest inherent score sits with unlicensed assets, because a rights breach can force a reprint and a claim at the same time. Unclear briefs and accessibility gaps are also common and serious. Each risk is scored before controls and again after existing and added controls. Most risks fall to Medium or Low once the proposed controls are in place, but asset licensing stays at High because the impact of a claim is hard to reverse. The first actions are a written scope list, an asset log, a single master folder for versions and a contrast check before each review.

Focus area
Visual design, graphic foundations and visual theory practice
Setting
Student or small studio design team producing branding, print and digital visual work for a client brief
Method
Five by five likelihood and impact risk register

Scope

This assessment covers a small design team working through one visual project from brief to final files, including research, concept sketches, colour, type and layout decisions, testing and handover. It looks at risks to rights, confidential material, schedule, budget, approvals, accessibility, cultural fit and production quality. Jurisdiction, client sector, tools and team size are assumptions made for teaching, and the assessment does not describe any real client, brand or agency.

Context

The team has a lead designer, two junior designers, a project coordinator who holds the client contact, and an external illustrator used on some pieces. Work is made in standard design and layout software, with shared cloud folders for files and a messaging channel for feedback. The client supplies a short brief, brand guidelines and some confidential product information. Each risk is scored before controls to show its natural level, then again after the existing controls and the added controls proposed here. The scores are examples for learning, not measurements of any real project.

Objectives, assets and stakeholders

The objective is to deliver accurate, accessible and well made visual work on time and within budget, while protecting the rights of others and the confidence of the client. The assets in scope are the design files, the brand guidelines, licensed images and fonts, confidential client information, the project schedule and budget, and the reputation of the design team. Stakeholders include the design team, the client and its customers, the printer or publishing platform, the illustrator and other suppliers, and the end users who will see or use the work. Clear roles matter: every risk has one owner role, and the project coordinator keeps the risk register current and reports at each review.

Risk matrix: before and after controls

Each cell shows hazard numbers placed by likelihood and impact. Compare the two grids to see how controls move each hazard.

Before controls

Inherent risk

Risk before controls: rows are likelihood from almost certain to rare, columns are impact from insignificant to catastrophic. Cells list hazard numbers.
1
Insignificant		 2
Minor		 3
Moderate		 4
Major		 5
Catastrophic
5 Almost certain
4 Likely Likelihood 4, impact 3, score 12, high: H01 H04 H06 Likelihood 4, impact 5, score 20, critical: H02
3 Possible Likelihood 3, impact 3, score 9, medium: H05 H08
2 Unlikely Likelihood 2, impact 4, score 8, medium: H07 Likelihood 2, impact 5, score 10, high: H03
1 Rare

After controls

Residual risk

Risk after controls: rows are likelihood from almost certain to rare, columns are impact from insignificant to catastrophic. Cells list hazard numbers.
1
Insignificant		 2
Minor		 3
Moderate		 4
Major		 5
Catastrophic
5 Almost certain
4 Likely
3 Possible
2 Unlikely Likelihood 2, impact 2, score 4, low: H04 H05 H08 Likelihood 2, impact 3, score 6, medium: H01 H06 Likelihood 2, impact 4, score 8, medium: H02
1 Rare Likelihood 1, impact 4, score 4, low: H03 H07
  • Low 1 to 4
  • Medium 5 to 9
  • High 10 to 16
  • Critical 17 to 25

Hazard register

A summary first, then the detail for each hazard.

Summary of hazards with scores before and after controls
No.HazardBeforeAfterOwner
H01 Unclear brief and scope creep 12 High 6 Medium Project coordinator
H02 Unlicensed imagery, fonts and third-party assets 20 Critical 8 Medium Lead designer
H03 Exposure of confidential client material 10 High 4 Low Project coordinator
H04 Approval and version-control failure 12 High 4 Low Lead designer
H05 Schedule and budget overrun 9 Medium 4 Low Project coordinator
H06 Accessibility and usability failures 12 High 6 Medium Lead designer
H07 Cultural, ethical or stereotyped imagery 8 Medium 4 Low Lead designer
H08 Production and file compatibility defects 9 Medium 4 Low Lead designer
H01

Unclear brief and scope creep

Strategic Before 12 After 6

The brief does not define the audience, deliverables, formats or number of revisions, so the team keeps adding pieces and rounds of changes beyond the agreed work, and the final output does not match what the client expected.

Who or what is affected: Design team, client and project coordinator

Causes

Vague client goals, verbal requests made in passing and no agreed limit on revisions.

Consequences

Lost hours, missed deadlines, unpaid extra work and a disputed final design.

Existing controls

  • The coordinator sends a short written brief at kick off.
  • The team holds one review meeting with the client at the midpoint.

Control gaps

Requests arrive through informal messages and are accepted without being logged or priced.

Additional controls

  • Prevent: Agree a written scope list with deliverables, formats and revision limits before any concept work starts.
  • Detect: Log every new request against the scope list and flag any item that adds work outside it.
Likelihood 4 x impact 3 before; 2 x 3 after Owner: Project coordinator Target: Within 14 days Early warning: More than two requests in a week that are not on the agreed scope list.
H02

Unlicensed imagery, fonts and third-party assets

Legal and compliance Before 20 After 8

Photographs, icons, illustrations or typefaces are used without a licence that covers the intended use, such as print runs, paid advertising or commercial merchandise, so the team infringes rights held by others.

Who or what is affected: Design team, client, asset owners and the public

Causes

Images pulled from search results, assumptions about free use and fonts shared between team members without a licence.

Consequences

Takedown demands, licence claims, forced reprints and damage to the client relationship.

Existing controls

  • The team uses stock libraries that require a login to download assets.
  • The lead designer checks that each font is installed from a licensed source.

Control gaps

The asset log is kept only for some projects, and licence limits for print or paid media are not checked.

Additional controls

  • Prevent: Keep an asset log that records the source, licence type, permitted uses and expiry for every third-party item.
  • Detect: Review the asset log before each client review and before final files are released.
  • Respond: Replace any asset whose licence does not cover the intended use and inform the client at once.
Likelihood 4 x impact 5 before; 2 x 4 after Owner: Lead designer Target: Within 21 days Early warning: An asset in the layout with no source or licence recorded in the asset log.
H03

Exposure of confidential client material

Technology and data Before 10 After 4

Unreleased product details, customer names or internal plans supplied for the brief are shared through public links, personal devices or mockups posted online, so private information reaches people who should not see it.

Who or what is affected: Client, client customers and design team

Causes

Public links for quick feedback, personal storage accounts and unreleased designs shown in portfolios.

Consequences

Breach of the client agreement, loss of trust, possible claims and early product disclosure.

Existing controls

  • Files are stored in a shared folder limited to named team members.
  • Staff sign a confidentiality agreement before joining the project.

Control gaps

Shared links are created quickly during reviews and are rarely checked afterwards.

Additional controls

  • Prevent: Use placeholder content in public portfolio work and remove any real client data before posting.
  • Detect: Check the sharing settings of the project folder each week and review access lists.
  • Recover: Revoke shared links, request removal from any public site and inform the client within one working day.
Likelihood 2 x impact 5 before; 1 x 4 after Owner: Project coordinator Target: Within 14 days Early warning: A shared link to project files that is open to anyone with the address.
H04

Approval and version-control failure

Operational Before 12 After 4

Several versions of a file circulate with different names, comments are applied to the wrong version, and a final file is sent to print or the client before sign-off, so the wrong design goes out.

Who or what is affected: Design team, client, printer and end users

Causes

Late changes made in copies, feedback sent to several people, and approvals given by email reply rather than a formal record.

Consequences

Reprints, wasted budget, client complaints and approval disputes.

Existing controls

  • Files carry a date in the file name.
  • The client signs off in writing at each stage.

Control gaps

Approval is recorded in messages that are not linked to the file version they approve.

Additional controls

  • Prevent: Use one master folder with a naming rule, version numbers and a single owner for each file.
  • Detect: Compare the final file against the signed proof before any export or upload.
  • Respond: Stop the print or send order and reissue the approved version when a mismatch is found.
Likelihood 4 x impact 3 before; 2 x 2 after Owner: Lead designer Target: Within 21 days Early warning: Two files with the same name and different content in the project folder.
H05

Schedule and budget overrun

Financial Before 9 After 4

Time spent on research, exploration and rework exceeds the plan, and external costs such as printing, licensed assets or an illustrator are not estimated early, so the work runs late and over budget.

Who or what is affected: Design team, client and project coordinator

Causes

Optimistic estimates, late client feedback and exploration that is never capped.

Consequences

Missed deadline, absorbed costs, rushed work and a damaged client relationship.

Existing controls

  • The coordinator keeps a simple task list with due dates.
  • Hours are recorded weekly by each team member.

Control gaps

Hours are recorded but not compared with the plan until the project closes.

Additional controls

  • Prevent: Estimate hours and external costs for each stage and agree a contingency of spare time before the work begins.
  • Detect: Compare planned and actual hours at each review and flag any stage more than ten percent over.
  • Respond: Reduce scope on agreed lower priority items when a stage is at risk of overrun.
Likelihood 3 x impact 3 before; 2 x 2 after Owner: Project coordinator Target: Within 30 days Early warning: A stage that has used more than 75 percent of its hours with less than half its tasks complete.
H06

Accessibility and usability failures

Operational Before 12 After 6

Text is too small or low in contrast, colour alone carries meaning, reading order is confused, or interactive pieces are hard to use with a keyboard or screen reader, so people with low vision, colour blindness or other needs cannot use the work.

Who or what is affected: End users with disabilities, client and design team

Causes

Aesthetic preference for low contrast, small type on dense layouts and no test with real users.

Consequences

Excluded users, poor usability reviews, client rework and possible legal complaints in some regions.

Existing controls

  • The lead designer checks the colour palette by eye during review.
  • Type sizes follow a minimum set in the brand guidelines.

Control gaps

Accessibility checks are not written into the review checklist and are often skipped under time pressure.

Additional controls

  • Prevent: Test every colour pair for contrast and add a text or shape cue wherever colour carries meaning.
  • Detect: Review the work with a simulated colour blindness filter and a screen reader before each client review.
  • Respond: Provide alternative text and a plain text version when a fault is found after release.
Likelihood 4 x impact 3 before; 2 x 3 after Owner: Lead designer Target: Within 30 days Early warning: Any text and background pair that fails the contrast check or any element that relies on colour alone.
H07

Cultural, ethical or stereotyped imagery

Reputational Before 8 After 4

Symbols, colours, gestures or imagery carry unintended meanings for some audiences, or portray groups in stereotyped ways, so the design causes offence or misreads the client's message.

Who or what is affected: Target audiences, client, design team and wider public

Causes

Limited knowledge of the audience, reliance on stock imagery and little time for research.

Consequences

Public criticism, withdrawn campaigns, client embarrassment and loss of professional standing.

Existing controls

  • The brief asks the client to name the intended audience.
  • The team reviews the work with a second designer before release.

Control gaps

Cultural checks depend on one reviewer and are not recorded for each concept.

Additional controls

  • Prevent: Research the meaning of key symbols and colours with the target audience before concepts are shown.
  • Detect: Ask a reviewer from outside the team to flag any image or phrase that may be read as stereotyped.
  • Respond: Withdraw and revise any piece that causes concern and record the change in the project log.
Likelihood 2 x impact 4 before; 1 x 4 after Owner: Lead designer Target: Within 45 days Early warning: Feedback from a test reviewer or audience member that flags a symbol, colour or image as offensive or unclear.
H08

Production and file compatibility defects

Technology and data Before 9 After 4

Colour profiles, fonts, image resolution or bleed settings do not match the output method, so the printed or screen version looks different from the approved proof, or files fail to open at the printer or on the client's system.

Who or what is affected: Printer, client, end users and design team

Causes

Default software settings, unembedded fonts, low resolution images and late changes to format.

Consequences

Print errors, rejected files, extra cost and visual differences from the approved proof.

Existing controls

  • The team uses a standard template with bleed and margin guides.
  • Final files are exported as a PDF before handover.

Control gaps

Preflight is not run on digital pieces, and output specifications are not written into the brief.

Additional controls

  • Prevent: Set colour profile, resolution and font embedding rules for each output type before design starts.
  • Detect: Preflight every final file against the printer or platform specification before it is sent.
  • Recover: Keep editable source files and a corrected export ready to resend within one working day.
Likelihood 3 x impact 3 before; 2 x 2 after Owner: Lead designer Target: Within 21 days Early warning: A preflight report that shows missing fonts, low resolution images or incorrect colour profiles.

Rating method and evaluation

Each risk is rated on two five-point scales. Likelihood runs from Rare to Almost certain, and impact runs from Insignificant to Severe. Multiplying the two gives a score from 1 to 25, which falls into one of four bands: Low from 1 to 4, Medium from 5 to 9, High from 10 to 16 and Critical from 17 to 25. The score is a guide for ordering work, not a precise measurement. Inherent risk is the score before any controls. Residual risk is the score after the existing and added controls, and it must never be higher than the inherent score. Impact is judged on money lost, time to correct, harm to people who use the work, damage to the client relationship and any legal exposure. A rights or confidentiality risk is never rated down only because it has not yet happened. Anything still High needs a dated plan from the lead designer, anything Medium needs routine checks with a named owner, and anything Low is accepted and watched. The team should challenge the ratings at each review, and any rating is revisited when a warning indicator reaches its threshold.

Likelihood, impact and rating bands

Likelihood

  • 5 Almost certain: Expected to happen in most circumstances.
  • 4 Likely: Will probably happen in many circumstances.
  • 3 Possible: Could happen at some time.
  • 2 Unlikely: Not expected, but it could happen.
  • 1 Rare: Only in exceptional circumstances.

Impact

  • 1 Insignificant: No lasting effect. Handled within routine work.
  • 2 Minor: Small effect that is quickly corrected.
  • 3 Moderate: Noticeable effect that needs managed effort to correct.
  • 4 Major: Serious effect on people, delivery or reputation.
  • 5 Catastrophic: Severe or lasting effect that threatens the whole activity.

Bands (likelihood x impact)

  • Low (1 to 4): Accept and monitor.
  • Medium (5 to 9): Manage with routine controls.
  • High (10 to 16): Senior attention and a treatment plan.
  • Critical (17 to 25): Act first. Do not proceed until reduced.

Monitoring, escalation and review

Review this assessment every 6 months, and sooner when an indicator below reaches its threshold.

Early-warning indicators and escalation thresholds
Indicator to watchEscalate when
Requests for work that are not on the agreed scope list.Escalate to the project coordinator when more than two unlisted requests arrive in a week, and to the client lead before any extra work starts.
Assets in the layout with no source or licence recorded in the asset log.Escalate to the lead designer at once, and remove the asset from the layout until its licence is confirmed.
Shared links to project files that are open to anyone with the address.Escalate to the project coordinator at once, revoke the link and inform the client within one working day.
Stages using more than 75 percent of planned hours with less than half their tasks complete.Escalate to the project coordinator at the next review, and to the client lead if the final date is at risk.
Text and background pairs that fail the contrast check or elements that rely on colour alone.Escalate to the lead designer before any client review, and hold the piece until both issues are fixed.

Contingency arrangements

If a serious event occurs, such as a licence claim, a leak of confidential material or a print run with the wrong design, the project coordinator pauses external sharing and orders, preserves all versions and informs the client promptly. The lead designer replaces the affected asset or reissues the approved file. Legal or licensing advice is sought where a claim is made, through the client or the team's supervisor. The schedule is re-planned with the client, and the team agrees any cost change in writing before work resumes.

Prioritized action plan

  1. Agree a written scope list with deliverables, formats and revision limits, owner project coordinator, within 14 days.
  2. Create an asset log with source and licence for every third-party item, owner lead designer, within 21 days.
  3. Set up one master folder with version rules and a written approval record, owner lead designer, within 21 days.
  4. Add contrast, colour blindness and screen reader checks to the review checklist, owner lead designer, within 30 days.
  5. Preflight every final file against its output specification, owner lead designer, within 21 days.

Conclusion

Strong visual work depends on a few steady habits: a written scope, a licence log, one master version, a contrast and accessibility check, and a preflight before any file leaves the studio. The highest scores sit with asset rights, unclear briefs and accessibility, and each has controls that bring the residual score down. Treat the register as a living record, review it every six months or at each major project change, and seek qualified advice for any real legal, licensing or privacy question.

Assumptions and limitations

Assumptions

  • The project is a paid or assessed piece of client work with a fixed deadline and a fixed budget.
  • The team uses common design software and shared cloud storage on managed devices.
  • Jurisdiction is not specified, so copyright and privacy duties are described in general terms only.
  • The client has not yet confirmed final brand colours, fonts or image sources at the start of the project.

Limitations

  • The scores are examples for learning and do not describe any real client, project or design practice.
  • Copyright, trademark, privacy and accessibility rules differ by country and change over time, so specialist review is needed.
  • This is educational content and is not legal, licensing or professional advice.

Related frameworks to study

  • Gestalt principles of perception
  • WCAG accessibility guidelines for contrast, text alternatives and navigation
  • Design thinking process for clarifying briefs
  • Hierarchy of controls

Creative Risk Assessment

China, India, United States, Indonesia, Pakistan, Nigeria, Brazil, Bangladesh, Russia, Japan, Mexico, Philippines, Vietnam, Egypt, Turkey, Germany, United Kingdom, France, Italy, Canada, South Korea, Australia, Spain.

For Learning Reference Only: This assessment demonstrates how risk assessment principles are applied in a practical setting, providing a useful reference for learning and understanding. Actual assessments may be adapted to suit specific site conditions and circumstances.

Keep learning

Study the subject behind this assessment.

Design Foundations and Visual Theory course Read the best practices for this course

More Creative risk assessments

Hourly Active: 39,499 Learners