Share a standards report with your client – Step-by-Step Guide | Vibe96
Vibe Studio

Share a standards report with your client

Published Last updated 2 min readBy Vibe96 team

Short answerVibe Studio can issue a standards report for a version of your app, with a PDF and a code anyone can check. It becomes a certificate when every go-live check passes.

Your client asks: "How do I know this was built properly?" A standards report is your answer.

What the report is

A report of the Vibe Studio standards a version of your app follows. It shows:

  • how many standards apply to this app,
  • how many required rules are met, and whether any must-fix rule is open,
  • the checks every app passes before it goes live,
  • how the app was checked while it was built.

It states what Vibe Studio checked automatically, what was reviewed with AI, what was tested in a browser, and what you as the owner confirmed.

Report or certificate

  • A standards report describes where the version stands.
  • It becomes a certificate when every go-live check passes. The page then says "Ready to go live".

Be clear with your client: it is issued by Vibe Studio for that version. It is not a certification by an outside body.

Get the report

  1. Open your project.
  2. Open the Visual View.
  3. Find Standards report for your client.
  4. Issue the report for your working version.
  5. Open it, download the PDF or share its link.

Anyone can check it

Every report has a code printed on it, in a form like VS-XXXX-XXXX. Your client types the code on the verify page and sees one of three answers:

  • This report is genuine, with its details. If the copy they were given says anything different, it has been changed.
  • This report was withdrawn by the owner, so it no longer describes the app.
  • No report with this code. If the code was typed correctly, the copy is not genuine.

๐Ÿ’ก Send the link and the code, not only the PDF. A PDF can be edited; the verify page cannot.

One version only

A report covers one version. When the app changes, issue a report for the newer version and share that one. You can withdraw an old report at any time.

Raise your score before you share

  1. Run a QA check on the version. See Check your app's code quality and security.
  2. Send the fixes to your checklist and build.
  3. Run Test Lab on the main journeys.
  4. Confirm the points that only you can confirm, such as your privacy texts.
  5. Issue the report again for the new version.

Your own standards count too

Rules you add under Skills & standards in your account apply to every build. A standard you switched off is off for the project, and you can switch it back on in the project's Settings.

๐Ÿ’ก Agencies and freelancers: put the report in your hand-over pack with the source code download and the admin login. It makes the hand-over feel complete.

Questions

Is the certificate issued by an outside body?

No. It is issued by Vibe Studio for one version of your app and says what was checked.

How can my client check that a report is real?

They type the code printed on the report on the verify page.

Does a report cover later versions?

No. A report covers one version. Issue a new one when the app changes.

Was this guide helpful?