Delivery Check
Turn a Roblox asset commission into a clear, reviewable agreement. Inspect the delivered work, compare revisions, confirm required files, and approve payment with an evidence trail.
Roblox checks whether an asset can work. BountySmith helps you verify whether the creator delivered what you paid for.
Three steps, from the brief to the release.
Convert the brief into specific deliverables, formats, technical limits, references, and review criteria before work begins.
Inspect the submitted asset, compare versions, read what was measured and what the creator included as evidence, and request changes against the original agreement.
Approve once the agreed requirements are met and the required source files are on the record. They unlock on release, and the decision and delivery record stay attached to the bounty.
Roblox's official validation result answers whether the asset meets platform requirements. A creator can include it with the delivery as evidence; BountySmith records it and does not verify it. The bounty also carries requirements that platform validation cannot answer, some measured from the files and some written into the studio's own checklist.
Every Delivery Check bounty keeps the agreed criteria, the delivered evidence and the studio's decision together on the bounty. This is what that record looks like.
Delivery Check record
Market stall set, low-poly. Version 2, submitted against revision 2 of the requirements.
Agreed before work began. A later revision is numbered, and the creator acknowledges it before submitting the next version.
Required file formats
.glb review export required to submit; .fbx source checked by file name
Style and reference match
Against the 6-image reference board
Poly or complexity target
Under 6,000 triangles, found 4,812
Texture requirements
1024 px maximum, found 1024 px
Required variants
3 requested, 2 found
Rig
None required, none detected
Pivots and attachments
Pivot at the base of each mesh
What the creator submitted and what was read from it.
Browser-viewable 3D exports
market_stall_day_v2.glb and market_stall_dusk_v2.glb: Viewable now, download after approval
Creator notes
One note on V2, one on V1
Version history and changes
V1 changes requested, V2 under review
Roblox validation result
Screenshot included by the creator with V2. Recorded, not verified by BountySmith
Final source-file package
2 files: Unavailable until approval
Submission timestamps
V1 on Oct 9, V2 on Oct 17
Made by the studio. Recorded on the bounty with the evidence above.
Approve delivery
Releases the payment and unlocks the final files.
Request specific changes
Written against the criteria above. The next version is numbered and compared.
Open a dispute if necessary
An admin reviews the same record. Payment stays held meanwhile.
Review export: Viewable now, download after approval
Source files: Unavailable until approval
Clear limits make the record worth trusting.
Triangle counts, texture sizes and rigs are read from the review export and the texture files. Variants are counted as one review export per variant. Required formats are checked by file name. They tell you what was delivered. They do not tell you whether it is right for your game.
Every version submitted against a Definition of Done waits for the posting studio: only you can approve it or send it back, and no timer approves it. Checks inform the decision; they never make it. On a funded bounty outside contests, if you make no decision for 14 days, the held payment moves to an admin payment review, where it can be released, refunded or held for more evidence. A version submitted while the bounty had no requirements keeps the ordinary 7 days review window instead.
The review export reaches your browser before you approve, so the 3D viewer can show it. The creator knows this when they submit. The download appears after you approve.
When the bounty requires source files, archives and source packages stay unavailable to the studio until approval releases the payment. Approving is what hands them over.
Requirements, every revision to them, each version, each check result, each change request and the final decision are visible to the studio and the working creator alike.
Delivery Check runs today on any bounty in the Modeling category that keeps at least one requirement in its Definition of Done. The pilot adds a supervised run: bring one real commission, we set up the acceptance criteria with you, watch the delivery go through review, and you keep the record.