Feedback Loops with Artists

We want to make sure every asset meets your standards. To do that, we’ve built a clear feedback loop that keeps everything organized and easy to track.

💬 How to Give Feedback

1

Review the asset

Once an asset is ready, you’ll receive it in the Kaedim platform for review.

2

Request a revision

  • Click the “Request Revision” button.

  • Write down your feedback in clear, specific terms (e.g., “Please make the leather texture less shiny” instead of “It looks off”).

  • If needed, attach reference images or notes to show exactly what you’d like.

3

Submit your request

  • Keep all your notes together in one revision request whenever possible.

  • If some changes are urgent (e.g., blocking progress), mark them clearly as priorities.

4

Receive the updated asset

  • Our artists will review your request, make the changes, and upload a new version.

  • You’ll be notified when the updated asset is ready.

5

Approve or request further changes

  • If everything looks good, mark it as approved.

  • If more changes are needed, simply submit another Request Revision

Most revisions are returned within 1-2 days - depending on the complexity of the request.


⚠️ When to Escalate

  • Minor adjustments: Just use the revision tool.

  • If something feels unclear or repeated issues occur: Your Art Lead will step in to help align direction.

  • If a deadline is at risk: Flag it in your revision request and tag your Account Manager in your comms channel (Slack/Teams).


Best Practices

  • Be specific: Point out exactly what needs changing and where.

  • Use references: Attach screenshots or examples when possible.

  • Stay consolidated: Gather team feedback before submitting, so we can act quickly and avoid duplicate notes.


🏅 Why This Matters

Using the Request Revision feature keeps all feedback in one place. This means:

  • Nothing gets lost in side conversations.

  • Both your team and ours can track what’s been requested and completed.

  • You’ll get faster, more accurate results with fewer back-and-forth cycles.

Last updated

Was this helpful?