Submitting a proof of work
Pick the source that carries the strongest evidence, attach what a buyer can check, and file it under the category you want to be found in.
Everything runs from /proofs. A proof is one specific thing you built plus the evidence that you built it, and it takes about two minutes to file once you have the link.
Pick the source that carries the strongest evidence you have, not the one that is quickest to paste. A repository a reviewer can open beats a screenshot of the same work, every time.
What you can submit
Code & Models
Work that carries authorship a machine can checkGitHub Repository
The repository URL. It has to be public, or a reviewer sees a 404 rather than your work. Your GitHub account must be connected in Settings first.
GitHub Commit
The repository URL plus the commit hash, for one specific change you authored.
Pull Request
The pull-request URL - useful when the work landed in someone else's repository.
HuggingFace Model
The model URL, with your Hugging Face account connected. A model card with no weight files does not confirm much.
Live Work
Something running that a buyer can watch or openLive Automation / Demo URL
A URL anyone can open without a login. A live page alone never auto-approves - the demo video is what carries this one.
Automation Demo / Walkthrough
A YouTube, Loom or Vimeo link. Here the video IS the proof, so no second video is asked for.
Workflow Screenshot
An image file, up to 10MB. Weakest evidence on its own - a screenshot shows a result, not that you produced it.
Documentation
What you wrote up around the buildTechnical Documentation
The document itself, up to 10MB. Redact client names before uploading if the work was under NDA.
Technical Presentation
The deck, uploaded or linked.
Manual Entry
A written description. Nothing to check automatically, so the demo video is doing all the work here.
Outcomes
Evidence the work did something for someoneAutomation Case Study
Picked from the portfolio items already on your profile - add one there first if the list is empty.
Client Testimonial
The testimonial, with a link to where it is published if there is one.
Published Research / Article
A link to the article, paper or talk.
External Certification (course / credential)
The credential URL from the issuing body. Supporting evidence only - not the same thing as a REWORK certificate, which is built from verified proofs.
14 types across 4 groups. Spreading proofs across groups is what the coverage meter on /proofs measures.
You do not need all fourteen. Spread matters more than volume — four proofs across four groups says more about you than eight repositories, and the coverage meter on /proofs is measuring exactly that.
What every submission asks for
- Title and description. Write the title as the thing, not the technology: "Invoice triage bot for a 40-person finance team" tells a buyer more than "n8n workflow".
- Category and subcategory. This is how your proof is found. It is the same taxonomy the marketplace search uses, so filing an ETL pipeline under "Other" removes it from the list of people who do ETL pipelines.
- Skills. These are what a verified proof awards you. Claim the ones the work actually demonstrates — a reviewer reads the evidence against the list.
- The outcome. Optional, and the single highest-value optional field on the form. A metric and a result ("time to close: 6 days to 2") is what a buyer scans for. Fill in both boxes — a metric with no result is discarded on submit without warning.
- A demonstration video, depending on the source. The rule is on its own page — see when a video is required.
Video links must be YouTube, Loom or Vimeo. Google Drive, Dropbox and self-hosted files are refused — and because the field validates whatever is in it, a half-typed link will block the submit button even where the video itself is optional. Clear the field rather than leaving a partial URL in it.
Two limits worth knowing before you start
10 submissions per day
Counted across proofs and imported skills together, and it resets at midnight in your own timezone. Selecting more than the remainder in a bulk import submits what fits and leaves the rest selected for tomorrow.
One piece of evidence backs one proof
The same video, link or file cannot support a second proof, including under a different category or client. Rejected and expired proofs release their evidence, so a corrected resubmission is always allowed.
The second one is the one people meet by surprise. Reusing one recording across several proofs looks like more work but reads as less: a reviewer opening two proofs and finding the same video learns that one of them is padding. If you genuinely did the same job for two clients, that is one proof with two outcomes, not two proofs.
Uploaded files are matched on their contents, not their filename. Re-uploading the same file under a new name is still the same evidence.
What happens the moment you submit
Your proof appears in your list straight away with a status. GitHub and Hugging Face submissions are checked for authorship immediately, so those either come back verified within seconds or go to a reviewer with the reason attached. Everything else goes straight to the review queue.
If the server refuses a submission you will see why on the form — a duplicate, the daily limit, or a provider you have not connected yet. It is never a silent failure, so if you got a green confirmation the proof is genuinely filed.
The quick route
The Verification tab on /proofs carries a shorter version of the same form, for when you are already looking at your trust standing and want to close a gap without switching screens. It writes exactly the same record and is held to exactly the same rules.