Skip to content
Prototype support

Know what to try—and where the demo stops.

This guide covers uploads, network failures, the free preview and full-paper queue, account deletion, and the support infrastructure that still has to be completed before public launch.

Public inbox
Not configured for this prototype
Upload limit
25 MB per PDF · two PDFs required
Live result
Free preview · entitled full-paper queue
Urgent support
Use an appropriate local or school service
01

Current support status

Self-service guidance is available, but a monitored public support channel has not been configured.

This is a development prototype. It does not yet publish a verified support email address, ticket form, response-time promise, safeguarding contact or service-status page. Do not send sensitive student data to an unverified address or social-media account claiming to represent Remark.

Before public launch, the operator must add a monitored contact owned by the real operating entity, define response and escalation procedures, and explain when support staff can access account or upload metadata.

02

Prepare both upload files

A clean answer script and the matching official scheme give the demo the best chance of finishing.

  • Upload two different PDF files: the completed answer script and official marking scheme for the same paper.
  • Each PDF must be non-empty and no larger than 25 MB.
  • Use a complete, non-encrypted PDF with no interactive forms, scripts, embedded files or launch actions. Production also requires an explicit clean verdict from the configured malware scanner.
  • Scan pages flat, upright and in order. Include blank answer pages because they can indicate an unanswered question.
  • Confirm the syllabus, paper, session and variant carefully before analysis.
  • Do not include an unrelated blank question paper in place of either required file.
03

If analysis says “Failed to fetch”

That message means the browser did not receive the expected server response; connectivity, deployment configuration or a timeout may be responsible.

  1. Reload the same address you used to open the app. During local testing, confirm the development server is still running; from another device, both devices must remain on the same network.
  2. On a deployed site, check the public health endpoint and deployment logs. Missing database, authentication, storage, scanner, billing, email or worker configuration can deliberately keep production marked not ready.
  3. Check that neither PDF exceeds 25 MB and try a smaller, optimised scan if the connection is slow.
  4. Do not switch between localhost and a LAN address during the signed-in session; that can change the site origin and authentication context.
  5. If files were saved, open Past Papers and inspect the existing upload before retrying. The full-paper queue uses idempotent jobs, so repeated analysis requests should reuse the active or completed job.

The free preview can take up to roughly two minutes at the server boundary. Entitled full-paper analysis is queued as a durable background job with persisted progress and bounded retries, so the report can be revisited without keeping the upload request open. Both modes still depend on the external AI service and can fail or require human review.

04

Understand the demo result

Free access marks one paired question; an active Season Pass can queue a provisional whole-paper analysis when enabled.

The free preview reads both PDFs but marks one question only. It shows criterion-level evidence, confidence and warnings for that selected question. “Preview complete” means that bounded analysis finished; it does not mean every question was marked.

When full-paper analysis is enabled, an account with an active Season Pass can queue every locatable question for background processing and revisit a persisted report. Results remain provisional, incomplete questions stay visible, and low-confidence work remains flagged. The separate dashboard, seeded paper reports, grade estimates, insights and plans still use fictional demonstration data and do not yet update from that report.

05

If a provisional mark looks wrong

Check the source evidence first and do not treat an AI estimate as an official result.

  • Confirm the detected question number and that the two PDFs are for the same paper.
  • Compare each quoted evidence fragment with the student’s original working.
  • Check the criterion wording and dependencies in the official scheme.
  • Treat low-confidence or illegible evidence as requiring human review.
  • Ask a teacher or qualified examiner before relying on the result for an important decision.
06

Account and file controls

Signed-in students can download or delete uploads and can remove the prototype account.

  • Open Past Papers to download the answer or scheme PDF and delete that saved upload.
  • Open Settings to download a JSON export of your account, setup, upload metadata, marking results, policy records and payment-status history. Passwords, OAuth tokens, storage keys and raw PDFs are excluded.
  • Open Settings to delete the prototype account and its account-owned records.
  • Google sign-in is available only after the operator configures valid OAuth credentials; email/password sign-in is the alternative. Production email verification and password reset also require the configured transactional-email provider.

Read the privacy template before uploading personal student work and the AI transparency page before trusting a mark.

07

Urgent, safety or legal issues

Remark is not an emergency, safeguarding, mental-health or legal-support service.

Do not rely on this prototype for an urgent safety, safeguarding, abuse, self-harm, examination-integrity or legal matter. Contact the responsible adult, school safeguarding lead, exam centre, emergency service or other appropriate local authority instead.

A production launch aimed at minors requires a clear, monitored safeguarding escalation path. That path is not present today.