Bonusuri.md: prepare a clear task and verifiable evidence

Bonusuri.md organizes the relationship between a company publishing an activity, a participant completing it and an administrator reviewing the result. The documented platform includes separate role panels, evidence uploads and a WhatsApp route for some actions.

The central relationship is between requirement, result and reward. A well-written task tells participants what to do and allows reviewers to explain their decisions. This guide uses a fictional page-testing example to show how to prepare that relationship.

Choose a question feedback can answer

Start with a specific uncertainty. A business might want to know whether visitors can find delivery conditions on a phone. That question concerns navigation and can produce observations useful for improving content or design.

Turn the question into an action: “Find the delivery information and explain where you looked”. Asking whether a website looks attractive leaves the criterion too broad. When participants attempt the same activity, differences between their responses become easier to interpret.

Choose one objective per task. A form or product comparison can be tested separately later. A short scenario reduces participant effort and allows each observation to relate to a particular step rather than becoming a general assessment of several unrelated features.

Read the rules before defining the activity

The Bonusuri.md participant rules allow activities such as private feedback, testing and bug reporting. Rewarding public reviews, ratings or manipulation of external platforms is excluded. Select a research activity that collects honest observations through the appropriate channel.

Check the conditions displayed for the actual participation. The reward, instructions and necessary information should be understood before starting. For a real activity, the current task page and rules take priority over an editorial example explaining a possible workflow.

For the company, the objective may be a decision about page clarity. For the participant, it is completing the requirement and submitting evidence. Those perspectives need to meet in a task that can be performed and assessed without contradictory expectations.

Write instructions people can follow on a phone

Specify the page address, relevant device and expected result. In our example, a participant opens the page on a phone, searches for delivery information and describes what they find. If timing matters, explain observation without imposing artificial urgency that changes ordinary browsing behaviour.

Use short steps and show where results should be submitted. Complete instructions reduce follow-up messages. If an image is required, state what needs to be visible and which personal information should be kept out of the submitted material.

Provide an example of acceptable structure: page visited, action attempted, observation and evidence. Leave the opinion open. The example should explain reporting format rather than suggesting that only a favourable assessment of the website can be approved.

Request evidence suited to the question

For a visual issue, a screenshot can provide context. For a broken link, the reviewer also needs the page address and attempted action. For unclear wording, request the passage and an explanation of the difficulty. Choose evidence according to what you need to verify.

An image alone may demonstrate that a page was opened without explaining the experience. Combine it with a short observation. In the delivery example, the participant could describe where they expected the information and which label helped them find it.

Collect only necessary material. A navigation task can be completed without identity documents, payment card details or personal conversations. Use a test environment and fictional information when assessing a form so participation does not accidentally create real orders.

Understand the platform’s roles and stages

In the Bonusuri.md project, companies follow activities, participants manage their tasks and administrators review evidence and rewards. Separate interfaces reflect different responsibilities and keep relevant information close to the action each role needs to perform.

Publication, participation, evidence submission and approval are distinct stages. An uploaded result may still need checking or clarification. In a WhatsApp flow, mentioning the task and retaining context helps the administrator associate the message with the correct activity.

When requesting clarification, identify the missing element: the relevant screenshot, page checked or action description. Participants should be able to correct the information without repeating the entire activity. A useful review decision refers to the published requirement and received material.

Separate result approval from reward payment

The platform rules connect payment to approval and verification of necessary information. Read the current task and payment conditions. Keep “submitted”, “approved” and “paid” distinct so you understand which stage the participation has reached.

If something is unclear, ask a question referring to the activity and stage. You might request confirmation that evidence arrived or an explanation of a missing element. A precise conversation is easier to resolve than a general message about a balance without task context.

Turn observations into concrete changes

Group feedback by the problem encountered: difficult information discovery, unclear labels, form failures or mobile display issues. Retain examples that explain the situation. Repetition can guide prioritization, while severity may make a single observation important enough to investigate.

Rewarded participants form a testing context with selection limitations. Interpret their responses as observations about the task rather than automatic evidence of commercial demand or SEO growth. For sales decisions, supplement them with information about customers who actually enquire and purchase.

Repeat the scenario after improving the page

Select a change connected to the observed problem and record the page version. If you move delivery conditions, repeat the task with comparable instructions. Check whether people can find the information more easily and which questions remain.

A successful task produces a verifiable result and a useful business decision. Bonusuri.md supplies the activity structure; instruction quality and review practice determine how much the team can learn from each participation.