Skip to learning content

Contribute well · LESSON 2 OF 8

Turn useful work into a strong submission

Choose a suitable mission, document original work and respond to reviewer feedback.

7 minTwo knowledge checks
In this lesson 4 sections and a knowledge check

After this lessonPrepare evidence that a reviewer can understand and verify.

Start with the brief

Read the mission before starting. Check the requested deliverable, its published reward, deadline and remaining places. Choose a brief where you can add first-hand knowledge. The mission card describes the offer; approval is a separate decision.

One strong, original contribution is more useful than repeated variations of the same submission. Sending evidence does not award a reward automatically. A reviewer checks its quality, originality and relevance to the brief.

  • Identify the reader and the decision you are helping them make.
  • Check that the mission is still open before submitting.
  • Match every requested item in the brief to a piece of evidence.

Make the evidence easy to inspect

Use a stable HTTPS link that the reviewer can open without requesting private customer access. Include your own notes, labelled photographs or screenshots, the equipment and software versions, what you tested and what happened. Cite manufacturer documentation for specifications you did not measure.

Separate observations from assumptions. If you tested one setup, describe that setup instead of claiming the result applies everywhere. Include limitations and unsuccessful tests when they help someone make a better decision.

Remove passwords, API keys, payment details, personal information and customer network identifiers before sharing. Obtain permission for other people's photographs or work. An AI-generated claim is not evidence that a test happened.

Choose a review, video or guide

The Contributions tab provides separate review, video and guide formats. Choose a matching open mission before publishing for a reward. Its displayed HP amount is awarded only after moderation; an upload or positive rating does not award points automatically.

For a review, describe first-hand use, the intended audience, strengths and shortcomings. Honest negative reviews are welcome. For a video, share your original public YouTube or Vimeo link, describe the demonstration and include useful timestamps. For a guide, explain repeatable steps or a compatible shortlist with evidence and limitations.

Confirm that you created the work and have clearly disclosed any relevant reward opportunity or commercial relationship. The same evidence cannot earn another award simply by using a different link format, account or mission.

Use feedback to improve

Open Missions in your Igniter account, select the brief and submit your evidence link with clear notes. Check your submission status afterwards. Pending means it is waiting for review; it is not an approved reward.

If a reviewer returns the submission with feedback, address the specific missing evidence and resubmit where the mission allows. Do not create another account or duplicate the same work to seek another reward.

PUT IT INTO PRACTICE

Practice task

Draft a submission in five lines: the problem, your setup, what you tested, what happened, and one limitation. Add a link to supporting evidence only after checking it for private information.

This is a practice task. Submit to an appropriate open mission separately if you want your work reviewed.

CHECK YOUR UNDERSTANDING

What would you do?

Choose an answer for each question. You can retry after reading the feedback.

1. Which evidence is most useful for a failover guide?
2. A submission is pending. What does that mean?

Loading your learning progress…