Export assets for web and mobile

We need web and mobile assets ready for the front-end team by Thursday. Export the required PNGs, JPEGs, and WebP assets at 1x, 2x, and 3x sizes, include a compressed SVG for icons, name files with the page, component, and scale (for example: header-logo@2x.png), and drop them into the shared folder for Kevin to pick up in that order after you verify transparency and background color consistency.

Before I send this to engineering, make approving easier: put a single spreadsheet at the root that shows each asset, its usage (hero, thumbnail, icon), required scales, file formats, and final file sizes; surface any images that had manual cropping or raster effects applied; and flag any assets with unclear responsive rules that might make developers hesitate.

I handed off a folder and the front-end lead, Kevin, says one of the icons was exported as a GIF and he can't scale it. Kevin needs a vector version and wants to know whether animations were baked in. I told him I exported everything per the spec but I don't know which artboard or which layer I used for that icon, and I can't tell if a masked group prevented SVG export. What likely went wrong and what is the fastest, least disruptive fix to give Kevin usable assets today?

Every release we end up re-exporting dozens of assets because developers change scale or ask for different formats after the handoff. I want fewer back-and-forths. Which predictable decisions should I lock down before export, which naming and folder rules cut the most confusion, and what sign-off from product or engineering would reduce rework by half?