Trust & quality

Feedback should be traceable enough to trust.

Recensio is built for a simple standard: builders should be able to see what happened, and creators should know exactly what quality requires before they accept.

Evidence record

What made that path feel unclear?

Defined product task

Create one invoice draft

Creator reflection

Original answers, linked to the assignment

Builder access

Raw response or video plus transcript

Traceable signalQuality reviewed

What we protect

A clear chain from product task to usable evidence.

A real assignment behind every response

Each submission is connected to a creator, a matched test, and a defined product task — not an anonymous content pool.

Evidence builders can inspect

Builders receive raw written answers or a recording with its transcript, so the context behind an observation remains visible.

Original work is expected

Creators confirm their feedback is their own. Submissions receive an originality screen, and unusual signals are reviewed before an account decision is made.

Useful context, not contact details

Builders get matching context and submitted evidence for the test. Creator personal contact details are not included in standard result views.

The evidence path

What happens before feedback reaches a builder.

Quality is not a single promise at the end. It is a sequence of clear expectations, attributable work, reviewable evidence, and measured moderation.

  1. 01

    A builder defines the evidence

    The brief sets one product task, the intended audience, evidence format, and the questions that matter.

  2. 02

    A creator sees the whole job

    Before accepting, a creator sees the task, reflection format, stated reward, and quality requirements.

  3. 03

    The experience becomes evidence

    Creators complete the task, then submit original written reflection or a recorded review with a transcript.

  4. 04

    Review protects the signal

    Quality and originality checks help keep the submission on brief. Approved work moves to the creator's earnings balance.

  5. 05

    Builders receive the source

    Feedback is delivered as readable answers or a video and timestamped transcript — not rewritten into an unsupported verdict.

Fair enforcement

A flag starts a review. It is not the final decision.

Automated originality signals help surface work that needs attention. A moderator confirms a policy violation before a submission is rejected, a warning is recorded, or an account is suspended. Confirmed AI use leads to a ban and replacement of the submission.

No black box summary

The original response stays close to the decision.

Builders can read the written response in context or play a submitted video alongside its transcript to revisit the specific moment a creator described. We do not manufacture testimonials, scores, or feedback to fill a result.

We want the rules to be as clear as the feedback.

Read the working policy pages or send the team a specific support request.