All posts
quickbuckproofguide

What counts as proof of work on QuickBuck (real examples by gig type)

QuickBuck Editorial·May 6, 2026
What counts as proof of work on QuickBuck (real examples by gig type)

Clean proof on the first try is the highest-leverage skill on QuickBuck. Examples for UGC clips, app testing, location verification, reviews — plus the 3 rejection reasons that account for 80% of all rejections.

What proof looks like, by gig type

UGC clips

Good proof: a raw 9:16 video file, 15-30 seconds, no music baked in, the brand product visible and the brief's required hook spoken in the first 1.5 seconds.

Bad proof: a music-overlaid clip, wrong aspect ratio, no audio, or the product never clearly visible.

App testing

Good proof: a screenshot of the moment you completed the requested in-app action, plus 3-5 sentences of honest written feedback. If a review-on-store bonus was offered, also a screenshot of your published review.

Bad proof: a screenshot of the app's home screen with no evidence you completed the action; one-word feedback like "good app."

Location verification

Good proof: a photo of the requested item (store display, product on shelf, signage) with EXIF metadata intact. Some gigs also require a timestamp visible in the photo.

Bad proof: a photo with EXIF metadata stripped, screenshots of someone else's photo, or a photo of the wrong item.

Honest reviews

Good proof: a screenshot of your published review with the relevant URL. If a written review was requested, the body matches what was actually published.

Bad proof: a screenshot of a draft that hasn't been submitted, a review of the wrong product, or a review with a screen-name that doesn't match what appears on the platform.

Surveys

Good proof: a screenshot of the survey's "thank you" / completion page, OR a unique completion code returned from the survey platform.

Bad proof: claim of completion without the visible completion page or code.

The three rejection reasons that account for 80% of all rejections

  1. Didn't follow brief exactly. Wrong aspect ratio, missing required text, wrong duration.
  2. Proof is unverifiable. Cropped screenshots, stripped metadata, blurry images.
  3. Submitted past slot expiry. The slot timer ran out before submission landed.

A pre-submission checklist

Before you click submit, verify:

  • [ ] Does the proof match every requirement in the brief, line by line?
  • [ ] Is the proof file the format the brief asked for?
  • [ ] If a screenshot, is it full-screen and unblurred?
  • [ ] If a video, is it the correct aspect ratio and duration?
  • [ ] If a link, does it resolve publicly without login?
  • [ ] Did you submit before slot expiry?

That checklist reduces rejection rate by 70%+.

What good proof looks like in practice

The mental model: imagine the poster opens your proof in 30 seconds, alone, without context. Can they verify the work was done? If yes — clean proof. If they have to chase you for clarification — bad proof.

What happens when you nail proof every time

Within 5-10 clean completions you'll notice:

  • Trust level rises.
  • Higher-paying gigs become visible.
  • Posters re-invite you for repeat work.
  • Reservation caps grow (more concurrent gigs).

The single highest-leverage action on QuickBuck is clean proof, every time, on the first try.

Read more about how proof reviews work or browse open gigs.

Frequently asked questions

What is proof of work on QuickBuck?+

Evidence that you completed a gig as briefed. Format varies by gig type: a screenshot of in-app action, a 15-30 second video clip, a photo with EXIF metadata intact, a link to a published review, or a survey completion code. The brief specifies what proof is required — read it twice.

Why is my proof being rejected?+

Three reasons account for 80% of rejections: (1) Didn't follow brief exactly — wrong aspect ratio, missing required text, wrong duration. (2) Proof is unverifiable — cropped screenshots, stripped metadata, blurry images. (3) Submitted past slot expiry — timer ran out before submission landed. Fix these three and your rejection rate drops to near zero.

Can I re-submit if my proof is rejected?+

Yes if the gig allows revisions. The poster will note the reason in your gig history; you have a brief window (usually 30-60 minutes) to re-submit. Repeated rejections affect your trust level, so quality matters more than speed. After 3+ rejections in a short window, your trust score drops and higher-paying gigs become invisible.

What does good proof look like for a UGC clip?+

Raw 9:16 video file, 15-30 seconds, no music baked in (unless brief asks for it), brand product visible for at least 50% of frames, hook line spoken in first 1.5 seconds, audio clean (no background noise), file format matches brief (.mov or .mp4 typically). Bad: music-overlaid clip, wrong aspect, blurry product shots.

What does good proof look like for app testing?+

Screenshot of the moment you completed the requested in-app action (not just home screen) + 3-5 sentences of honest written feedback using the expected/happened/fix template. If a review-on-store bonus was offered, also include screenshot of your published review. Bad: home-screen screenshot with no proof of completion, one-word feedback.

What does good proof look like for location verification?+

Photo of the requested item (store display, product on shelf, signage) with EXIF metadata intact (don't strip it via screenshot or save-as). Some gigs require a timestamp visible in the photo. Bad: photo with metadata stripped, screenshot of someone else's photo, photo of the wrong item or wrong location.

What's the pre-submission checklist that cuts rejection rate?+

Five checks before clicking submit: (1) Does proof match every requirement in the brief, line by line? (2) Is the file in the correct format the brief asked for? (3) If a screenshot, is it full-screen and unblurred? (4) If a video, correct aspect ratio + duration? (5) Did you submit before slot expiry? This checklist reduces rejection rate by 70%+.

Articles related to this one.