# Writing an assessment > What an assessment is, how sections draw a different paper for every candidate, and why a reviewer rather than you is the one who publishes it. Source: https://www.revquix.com/docs/mentors/writing-an-assessment Last verified: 2026-09-10 --- An assessment is the exam behind a certified program. Somebody sits it, the platform scores it, and a pass issues a credential with your name or Revquix's on it. Everything you write lives under [assessments](https://www.revquix.com/dashboard/mentor/assessments). ## Sections are pools, not chapters This is the one idea the rest of the screen depends on. A paper is made of **sections**. A section holds a set of questions and draws **a few of them** per candidate: you might write twenty and set the section to draw five. Two people sitting the same assessment therefore see different questions. > **Note** - This is what makes a leaked paper cheap > > A candidate who memorises the questions they were asked has memorised a fifth of your pool, and the > next person draws a different fifth. Writing a deep pool is worth more than any other anti-cheat > measure on the page, and it costs nothing at runtime. Every candidate still sits a paper worth the same. A section is worth **draw count x marks per question**, and the assessment total is the sum over its sections - so the total is fixed by the settings, never by which questions came up. Draw count and marks per question are each **1 to 100**. If a section draws more questions than its pool holds, the checklist stops you before it can be sent. ## What you can ask Four question types: - **Multiple choice** - one correct option. At least two options, exactly one correct. - **Multiple answer** - several correct options. At least two options, at least one correct, and never all of them. - **Short text** - a line of typed text. - **Long text** - an essay or a worked explanation. > **Note** - Short text is the one that decides who grades it > > Give a short-text question a list of accepted answers and the platform grades it. Leave the list > empty and it becomes a person's job - yours, in [grading](https://www.revquix.com/dashboard/mentor/grading). Long text is always graded by a person. Coding questions exist in the system but cannot be authored here. They are not on this surface yet. ## The pass bar, the clock and the strike limit **Pass percent** is 1 to 100, and the marks needed are worked out from it and **rounded up** - a 70% bar on a 3-mark paper needs 3, not 2. **Duration** is 5 to 360 minutes. **Integrity strikes** is how many integrity signals a sitting may collect before it is closed early and submitted as it stands. Leaving the exam tab, dropping out of full screen and pasting into an answer all count; signals are recorded whatever this is set to. It is 0 to 20 and starts at 3, and **0 turns the ladder off** - signals are still recorded and none of them count, which is a real setting for a low-stakes paper rather than a mistake. When a sitting is closed this way, the reason travels onto the record an employer can see. All three are frozen once anything has been graded against them. Moving a bar under an attempt that has already been scored would change a result somebody was told. ## You write it, a reviewer publishes it There is no publish button on this screen, and that is the design rather than a missing feature. 1. **Draft.** Everything is editable. A checklist on the page lists what is still missing, and the Send button stays disabled until the list is empty. 2. **Send for review.** The assessment locks. It is read-only while it waits, so the person reading it cannot have it change underneath them. If you need to fix something, **Withdraw** it, edit, and send it again. 3. **Approved.** Approving is what publishes. Nothing else does. You will also see who the credential is issued as - **you**, hosted and verified by Revquix, or **Revquix** itself. That is set during review and is read-only to you. ## Reading the certificate before you send it The editor draws the certificate your assessment will issue, beside the fields that decide what is on it: the title in the serif it will be printed in, your name as Course Mentor, and the score a candidate who just cleared your bar would carry. > **Note** - It is a specimen, and it says so three times > > The holder, the score and the certificate number on the preview are examples - the eyebrow reads > "Revquix Verified - Specimen", the number is `RQ-SPEC-IMEN-0000-0000`, and the footer says the word. > Nothing you can do on this screen produces a real credential. It is worth a look before you send, because the title is the one thing on that sheet you control and it is read with none of this page around it. The pass bar, the time allowed and any integrity note are deliberately not on the certificate - they live on the verification page the code opens, which is the record an employer checks. ## After it is published The structure freezes. Sections, draw counts, marks and the pass bar stop being editable, because they are what already-graded attempts were measured against. Two things still move: - **Wording.** Prompts and explanations stay editable, so a typo or an ambiguous sentence can be fixed without a new version. - **The pool.** You can keep adding questions. A new question waits for a reviewer to stamp it and is **not drawn until then** - so adding one and seeing nothing change is the system working, not a failure. For anything structural, press **Revise**. That copies the assessment into a draft you can edit freely while the published one stays live and sellable, and the copy replaces it when approved. ## Attaching it to what you sell An assessment does nothing on its own. It is attached from your service or package editor, which is why the row sits under Sell rather than beside grading - see [your services](https://www.revquix.com/docs/mentors/your-services). - [Your services](https://www.revquix.com/docs/mentors/your-services) - What you can sell, and where an assessment gets attached. - [Session packages](https://www.revquix.com/docs/mentors/session-packages) - Building a package, and how validity works.