How Do I Mark an OnlyFans Chatter Applicant's Custom Test Answers on OFM Jobs?

When a candidate submits a custom test on OFM Jobs, go to the Custom Tests Results area, find the completed attempt, and click the Mark answers action. That action opens at the first unmarked answer and steps you through each written, file, or voice response that requires a human judgment before any hiring decision can be made.

Quick facts

Where do I find a completed custom test to review?

Completed custom test attempts appear in the Custom Tests Results area of OFM Jobs.

Completed custom test attempts appear in the Custom Tests Results area of OFM Jobs. Each row represents one candidate's submission. When a row is ready for review, its action reads Mark answers followed by a count of unscored responses. Click that action to open the marking view, which starts at the first answer that still needs a human score.

The count shown next to Mark answers tells you exactly how many responses are waiting. If a test contains only multiple-choice or auto-scored questions, no manual marking step exists and the row moves directly to a Decide state. The marking queue only appears when the test design includes at least one written, file, or voice question ^[2].

What does "Mark answers with a count" mean in the results table?

"Mark answers" followed by a number means that specific test result contains that many responses that cannot be scored automatically and are still waiting for a human reviewer.

"Mark answers" followed by a number means that specific test result contains that many responses that cannot be scored automatically and are still waiting for a human reviewer. The count is a live tally: it decreases each time you score one answer and save it. Once the count reaches zero, the action label changes to Decide.

This count is the clearest signal that a result is actionable. A result sitting in the queue with a count greater than zero is not stalled or broken; it is simply waiting for a reviewer to work through each open answer. Candidates in this state see "Being marked" on their own view, which prevents them from interpreting the delay as a rejection ^[2].

Which custom test answer types need a person to mark them?

Three answer types require a human mark: written answers, file uploads, and voice recordings ^[2].

Three answer types require a human mark: written answers, file uploads, and voice recordings ^[2]. These formats cannot be scored by the platform automatically because the quality of the response depends on judgment, not pattern-matching. Multiple-choice and other objective question formats are scored without manual input.

Understanding which question types carry a marking obligation matters at test-design time, not just review time. A test built entirely from objective questions will produce results that move straight to Decide with no manual step. A test that includes even one written, file, or voice question creates a mandatory review stage for every submission ^[2]. OFM Jobs supports both pre-built assessments and custom tests built from scratch ^[3], so the question mix is entirely in the agency's control.

How do I review written, file, and voice answers?

Click Mark answers on the candidate's row in Custom Tests Results.

Click Mark answers on the candidate's row in Custom Tests Results. The marking view opens at the first answer that has not yet been scored. For a written answer, read the response and assign a mark. For a file upload, open or download the file, assess it, and record your score. For a voice answer, play the recording and mark it before moving to the next question.

Each answer is handled individually. The interface steps through them in order, and your progress is saved as you go. You are not required to complete all marks in a single session, but the Decide action remains locked until the count reaches zero across all three answer types. Take care with voice answers in particular: the recording must be played and assessed before the question can be marked, as the platform does not auto-score audio content ^[2].

What does "Being marked" mean on the candidate's test?

"Being marked" is the status a candidate sees on their own test view when their submission includes hand-marked answers that have not yet been scored.

"Being marked" is the status a candidate sees on their own test view when their submission includes hand-marked answers that have not yet been scored. It signals that a reviewer is working through the result and that no decision has been made ^[2].

Candidates do not see the individual marks or partial scores while review is in progress. The status updates once marking is complete and a decision is recorded. This matters operationally: a candidate seeing "Being marked" is not receiving conflicting signals about their application status. There is no need to contact the candidate separately to explain the delay, and no obligation to retake the test while marks are pending.

Why are Approve, Hold, and Not a fit unavailable?

Approve, Hold, and Not a fit are disabled because one or more hand-marked answers have not yet been scored.

Approve, Hold, and Not a fit are disabled because one or more hand-marked answers have not yet been scored. The platform enforces this gate deliberately: a decision made before all evidence is in would not reflect the full test result. The three options unlock only once every written, file, and voice answer in that submission carries a mark ^[1].

If you open a result expecting to see Decide and instead see Mark answers, check the count. At least one answer is still open. Work through the marking view until the count reaches zero, then return to the results table. The action will have changed to Decide. This is not a bug or a permissions issue; it is the designed workflow separating the marking task from the hiring decision.

The result is also measured against the threshold that was set when the test was originally sent to the candidate. Adjusting the standing pass bar after the fact does not retroactively change how that result is judged ^[4]. The result view shows exactly which threshold applied ^[4].

What can I decide once every answer is marked?

Once every hand-marked answer has been scored, the action on the candidate's row changes from Mark answers to Decide.

Once every hand-marked answer has been scored, the action on the candidate's row changes from Mark answers to Decide. Clicking Decide presents three options: Approve, Hold, or Not a fit ^[1].

Approve moves the candidate forward in the hiring pipeline. Hold parks them for later review without issuing a rejection. Not a fit ends that candidate's progression. Each decision is recorded against the result.

This separation between marking and deciding is intentional. Marking is about reading the evidence; deciding is about acting on it. Keeping them as distinct actions means a reviewer cannot accidentally close out a candidate before finishing their assessment. Because OFM Jobs can process large volumes of applicants, with the platform handling over 20,000 applications in a single day ^[5], this structure helps agencies maintain a consistent standard across a high-volume queue without letting individual decisions slip through before reviews are complete.