Skip to content

How it works

Know each step first

A mission, start to finish

Every step tells you up front what happens to your time and your credits.

PersonalSample data

Before you start

Read the rules, check the credits, then start

Payment retries are charging customers twice

Credits
10
Paid by
You
Time
75 minutes
  • Mission rules read
  • Server deadline understood
Start mission

From the catalog to the start page

Read the brief before committing. Starting the mission is a separate step with its own terms.

  1. Choose and read

    Check the scenario, deliverables, content language, and published details. Piece previews appear only where provided.

  2. Inspect cost and time

    For invitations, separate the invite deadline from the mission working time. Check Pricing for this attempt's cost.

  3. Accept the rules and start

    Read each confirmation box carefully. Opening a brief or mission link doesn't enter the workspace.

Read the details

Credits and time begin at different moments

  1. Queue, prepare, then start the clock

    If capacity requires a queue, credits may be held first—you can still leave before preparation starts. Once preparation begins, mission credits are used and cancelling may not return them (you'll see a warning first). A successful workspace entry starts the server timer; re-entering the same attempt keeps the original deadline.

    Two distinct boundariesDiagram
    Credits
    1. Reserved
    2. Preparation starts
    Time
    1. Not running
    2. Entry accepted

    Check the live quote and warnings for your attempt, not sample prices.

Inside the workspace, you direct the work

Files, terminal, and AI live in one browser workspace. See AI and the workspace for tools and logging details.

  1. Read the supplied material

    Read the brief and workspace files first. You can edit files directly or guide AI within the mission's rules.

  2. Review approval requests

    When an action needs approval, inspect what AI wants to do and approve or reject it. An AI request never widens your permissions.

  3. Inspect the change

    Verify saved files and actual command output. An AI saying 'Done' doesn't replace saved work or mission evaluation.

Read the state while working

Closing the page does not pause time. Asking AI to stop does not undo completed work.

SituationWhat it meansNext step
AI workingA turn is still runningUse Stop and wait for confirmation before redirecting
AI budget insufficientNew requests that exceed budget are blockedEdit, use the terminal and submit within time and permissions
DisconnectedThe page may be staleRe-open the same attempt and check saved files

Review before submitting the snapshot

  1. Submit includes a review step

    Clicking Submit opens a review screen first, so you can still go back before confirming. Once submitted, grading uses that exact snapshot and mission version—not later edits. If time runs out, the server submits your saved work automatically, even if you close the tab. For manual submissions, verify the accepted status.

    Review the submissionDiagram
    Before confirmation
    Can return to work
    Submission accepted
    Snapshot bound to evaluation
    While checking
    Can close the page

After submission, follow the evaluation state

Grading continues if you close the page. Time estimates appear when available and aren't guaranteed.

  1. Checking

    Queues and workload can add time. Check back on the same attempt—don't resubmit just to keep checking running.

  2. Defense remains

    Missions with required Defense hold results until you finish it. Follow the prompt on screen.

  3. Result available

    Updates stay in notifications; emails depend on your settings. Open your attempt to view the result.

Defense is a conversation about the work

  1. An AI reviewer asks one focused question at a time

    Where enabled, Defense follows submission. The AI reviewer sees your recorded, participant-visible work—such as file changes and run outputs—plus mission themes, without answers or hidden-check outcomes. Defense has no separate score and doesn't change BUILD, though required completion can gate result release.

Choose a language and answer from your work

The window runs up to 30 minutes from your first answer—not from Submit. It may end earlier once the reviewer has enough context.

  1. State your preferred language

    The first question asks your preferred language. Choose one in which you can explain the work clearly.

  2. Refer to actual work

    Explain what you observed, why you chose that approach, and what you verified. Don't guess what you think the AI wants to hear.

  3. Read completion status

    Recorded platform downtime doesn't count against your window. Check the displayed status to confirm completion.

A worked example of an inspectable explanation

Sample explanation only—not a mission answer or grading rubric.

PartConcrete example
ObservationTwo documents describe different conditions, so I checked their effective dates.
ChoiceI limited the change to the period covered by that document.
CheckI checked the change against the requirement and inspected the recorded run.

Defense adds context behind your decisions—it doesn't prove identity, total mastery, or sole authorship.

If something breaks, check the same attempt first

Workspace connection lost

Use the reload button shown and check your saved files and chat. Unsaved edits may be lost while the mission clock keeps running.

Result held or not issued

Check the reason and next action. No verdict doesn't mean you failed—different issues have different recovery paths.

Result appears wrong

Report it from the result page before the listed deadline—normally 14 days after release. Include what happened, what you expected, and the actual result.

A review has an outcome you can follow

Results are provisional and can be corrected through review—that's our standard.

  1. Reports tie directly to that attempt

    Describe what happened on this attempt. Use Help or the result page for live status—never include passwords or secrets.

  2. Read the approved remedy

    Where eligible, you can request credits back, a retake, a recheck, or a new Defense. Submitting a request isn't automatic approval—our team checks the incident first.

  3. Corrections keep history

    Corrections stay visible in the record. Rechecks evaluate the saved submission, not files edited later.

With a result, choose the next action

  1. Keep the interpretation grounded in this attempt

    Open your issued result, check the requirements, then review any permitted work evidence. See How we measure for levels, BUILD, symbols, and comparison rules; Who sees what for sharing; and For you for your next practice.

    Where the result leadsDiagram
    Interpret
    How we measure
    Practise
    For you
    Disclose
    Who sees what

Before you start

Can I close the page during evaluation?

Yes. Once your submission is accepted, evaluation runs in the background. You can come back to the same attempt anytime to check status.

Does every mission have Defense?

No. Check the mission brief to see if Defense is included. When required, results stay locked until you finish it.

Does reporting an issue give me an instant retake?

No. Every report is reviewed first. Check the outcome and any granted credit or retake on your attempt page.

Know the flow. Choose your work.

Read the selected mission’s brief and start page before confirming.