Handling revisions

With Kaedim’s streamlined process, revisions are fewer, faster, and clearer.

Revisions are a normal part of the creative process. At Kaedim, we’ve designed our revision workflow to keep feedback cycles fast, efficient, and clear so you always get assets aligned with your vision.

When to Request a Revision

You can request a revision whenever:

• The asset doesn’t fully match your concept art or input images.

• You’d like changes to proportions, details, or style.

• Technical adjustments are needed (e.g., polygon count, textures, rigging).

• The asset needs to be brought closer to game-ready standards.

• You'd like to test variations for an asset.

  • Check out the Branching feature

---

How to Submit Feedback

1. In Flow

   • Open the asset card.

   • Click “Request Revision.”

   • Add clear notes about what you’d like changed.

   • (Tip: Use images with numbered callouts for the fastest turnaround.)

2. Be Specific

   • Instead of: “Make it look better”

   • Try: “Adjust the handle length (1), make the texture darker wood (2), and reduce polygon count for LOD0 (3).”

What Happens Next

• Processing – Our team confirms your revision request in Flow and starts working on the edits.

• Update Cycle – AI + artist adjustments are made.

• Delivery – You’ll receive a revised version as a new version for review.

---

Revision Limits

• Major style or direction changes after production has started may be considered new assets rather than revisions.

  • In these cases, the Branching feature should be used.

• Revisions must be relevant to the current pipeline stage. For example:

  • Geometry changes should be requested during the modeling stage, not once the asset has entered texturing.

  • Similarly, large design changes should be made before rigging or animation.