A design prompt does not need your customer list to describe a welcoming visual style. Before opening an AI tool, separate the creative problem from the private information attached to the project. The aim is a useful brief that communicates composition, audience and constraints while exposing only what the task needs.

Key takeaways

  • Describe the intended design decision before selecting inputs.
  • Replace personal and commercially sensitive details with fictional placeholders.
  • Keep an approved reference folder separate from the complete project archive.
  • Review the selected tool’s data settings before uploading anything.

Start with the output, not the attachment

Write one sentence explaining the task: “Explore three layout directions for a community event tote.” Then list what the result must communicate, where it will appear and what the designer must avoid. None of those instructions requires a spreadsheet of attendees or an unreleased financial presentation.

The NIST Privacy Framework is a voluntary resource for identifying and managing privacy risk. The practical briefing method below is our suggested workflow, rather than a claim that a short checklist establishes compliance or eliminates risk.

For a cotton canvas tote, a brief can state that the composition should remain readable on the selected product’s approved print area. Ask for the actual artwork template separately; do not let a generated layout invent the usable dimensions.

Make a public-input version

Create a new document instead of pasting the entire original brief. Include the product type, general audience, desired tone, permitted colors and output format. Use public brand guidance only when you are authorized to share it with the chosen service.

Replace the client name with “Example Organization.” Replace a real event date with “EVENT DATE.” Describe a geographic theme broadly if an exact address is unnecessary. Remove personal names, email addresses, order identifiers, confidential pricing and access information. An invented name should be clearly fictional rather than a lightly altered customer identity.

Check images as well as text. A screenshot may contain a browser tab title, a private file name or a visible contact record. A clean excerpt prepared for the creative task is easier to inspect than a full desktop capture.

Keep the prompt useful

A practical prompt might read: “Propose three text-only layout descriptions for an educational event tote. Use the fictional title COMMUNITY DAY. Aim for calm, friendly typography with one large heading and one short supporting line. Do not invent a logo, certification, sponsor or product specification.”

This requests design directions without giving the tool confidential source material. Add the exact public color values if needed, but keep proprietary artwork outside the prompt until its use has been authorized. A request for descriptive options may be enough before any image upload is considered.

Check the service before sending

Review the specific account and product settings for retention, access, sharing and use of inputs. Do not assume that every account type, integration or plan follows the same policy. If the available information is unclear, use a nonconfidential example or complete that part of the task without the tool.

NIST’s AI Risk Management Framework treats trustworthiness as a consideration across AI design, use and evaluation. It does not certify the particular tool or prompt used for your project. Record which public inputs were approved so another team member can understand the boundary later.

Hand off a clean decision record

Save the sanitized prompt, the chosen direction and any unresolved questions in the project folder. Keep that record distinct from private order administration. Before preparing production artwork, follow the print-ready artwork checklist and confirm the selected product’s actual requirements.

The accompanying briefing diagram uses short labels because the distinction between allowed inputs and withheld details must be understandable. It represents an example workflow, not the security architecture of an AI provider.

Brief questions

Is removing a name enough?

Not necessarily. A combination of dates, locations or unusual project details may still identify someone. Remove details the creative task does not require.

Can an AI tool approve the brief for privacy?

Treat that as a separate organizational decision. Do not upload sensitive information merely to ask whether it is sensitive.

Discuss your design brief with Brilliantor using a nonconfidential project summary. Share the product category, creative goal and the questions you need answered first.