Final submission

Last updated Nov 19, 2026View as MarkdownFor AI assistants

The submission is the work your credential is built on. What reviewers look at, which formats are accepted and how review leads to a credential.

The final submission is the deliverable you produced for the challenge. It is what your reviewers evaluate, and it is what your credential is anchored to.

Treat this page as the checklist you run before you click submit.

What you submit

Every challenge brief states the expected deliverable format. Common formats:

  • Slide deck (PDF): typical for strategy, market analysis, go-to-market and creative briefs.
  • Written report (PDF or Markdown): typical for research, policy and scientific writing.
  • Code repository (Git URL with a README): typical for software, machine learning and data engineering.
  • Design artefact (Figma link, image set or CAD file): typical for product, UX and hardware.
  • Mixed: a deck plus a working prototype, or a report plus supporting data.

If the brief says "10-page deck maximum", respect the limit. Reviewers stop reading at the stated cap, and padding past it does not help.

What reviewers look at

Reviewers work from the rubric stated in the challenge brief. There is no hidden rubric: what is published is what gets scored.

The patterns that show up most often:

1. Problem framing

Did you understand the real question? Many submissions answer the surface question and miss the actual one. The strongest submissions open by restating the problem in their own words. That restatement alone tells a reviewer a lot.

2. Structure

Reviewers read submissions in order. A clear arc (problem, approach, key findings, recommendation, caveats) outperforms one that buries the conclusion on slide fourteen.

3. Evidence-to-claim ratio

Every claim should be backed by something: data, analysis, a source, reasoning. Submissions that read as opinion without scaffolding rarely land, however confident the prose sounds.

4. Honesty about limitations

Strong submissions name what they do not know. Reviewers notice it. Submissions that pretend total certainty come across as junior.

5. Craft

Spelling, grammar, layout, design polish. Not the main thing, but consistent sloppiness drags down strong work. Run a final pass.

What gets you a "needs revision"

A submission can come back for revision rather than acceptance. The usual reasons:

  • The submission ignored a stated constraint, such as "under 10 pages", "include a cost estimate" or "use the provided dataset".
  • The deliverable is in the wrong format for the brief.
  • Critical reasoning steps are missing, so the reviewer cannot follow how you got from problem to conclusion.
  • Significant factual errors that would mislead someone acting on the submission.

A revision request is not a rejection. It is a specific list of things to fix. Most revised submissions are accepted on the next round.

What gets you a "not accepted"

A non-acceptance is rare and tends to need several compounding issues, for example a submission that ignores the rubric, does not engage with the brief and has critical factual errors. You are told the specific reasons.

You can attempt the challenge again and treat the first attempt as a thorough learning experience.

From submission to credential

The process runs in this order:

  1. Your submission lands. You get a receipt.
  2. A reviewer is assigned. Reviewers pick up submissions as soon as they can.
  3. The review is completed. Capstone-style and team challenges can take longer.
  4. You get a decision: accepted, revision requested or not accepted, with a written rationale.
  5. The credential is issued once your submission is accepted.

The credential is the next step

When your submission is accepted, Ewance issues your verifiable credential, anchored on a public blockchain so it can be confirmed without trusting Ewance. The mechanics are on the next page: Certificates.

On this page