Pilot cohort · accepting №01 – №05

Run your next
conference without
the spreadsheet sprawl.

Sidang handles the full paper lifecycle — abstract, review, revision, payment, camera-ready, proceedings — on one tenant-scoped platform. Built for the WoS/Scopus-tier cadence, not the Google-Forms improvisation.

Request pilot access or see how it works ↓
500+ papers per conference, multi-track
Double-blind enforced, by default
MYR · FPX Malaysia-first payments
Sidang — at a glance
26
editorial states, enforced by a state machine
§
14d
strict payment policy, auto-enforced
†
2
critical emails, never missed or duplicated
✓
100%
audit trail, every action logged
§ 01The Capabilities

Everything your committee runs manually, already built.

Six years of running conferences distilled into one opinionated platform. Each tenant gets their own subdomain, their own branding, their own team — without reinventing the workflow each edition.

Multi-track submission

Tracks with their own keywords, chairs, and review pools. Paper codes auto-generated per conference (IPCME2026-001, -002…).

Double-blind peer review

Anonymized PDFs, per-paper reviewer rounds, structured scoring on originality, technical merit, clarity and significance.

Payment after acceptance

The Model B international standard. Auto invoice PDF, 14-day clock, proof upload, secretariat verification, receipt — with a strict drop policy for non-payment.

Camera-ready to proceedings

Final PDF + copyright form upload. Secretariat formatting checks. Certificates auto-generated for presenters, reviewers, and chairs.

Tenant-scoped multi-conference

Run a series, an annual, and a satellite event from one account. Each on its own subdomain — no cross-tenant leakage, enforced at query level.

Audit & compliance by default

Every state change, upload, email, and verification is logged. PDPA-aware export and deletion flows. Double-blind enforced at the render layer.

§ 02The Lifecycle

One workflow, seven stages, zero spreadsheets.

The editorial lifecycle Sidang enforces. Each transition fires a typed event — emails, invoices, audit logs — so your team never chases handoffs.

  1. I¶ abstract

    Abstract submission

    Author submits with track selection and co-author declarations. Paper code auto-assigned; confirmation email fires on transition.

    author-led
  2. II§ screening

    Chair screening

    Track chair accepts or rejects within the abstract window. Decision email is templated per outcome.

    chair-led
  3. III¶ full paper

    Full paper upload

    Anonymized PDF uploaded against the full-paper deadline. Storage canonical on DO Spaces; optional Drive mirror.

    author-led
  4. IV§ peer review

    Peer review

    Two to three reviewers. Structured scoring on originality, technical, clarity, significance — with reviewer confidence.

    reviewer-led
  5. V† accepted

    Final acceptance

    Chair finalises the decision. Invoice auto-generates, Email 2 queues, payment clock starts — all in one transition.

    ☆ seal · accepted
  6. VI§ payment

    Payment & verification

    Fourteen-day clock, bank-proof upload, secretariat verification, receipt PDF. Unpaid papers drop, strictly.

    secretariat
  7. VII⁂ published

    Camera-ready & published

    Final PDF + copyright form approved. Certificates issued. Paper enters the proceedings. Audit trail sealed.

    ☆ seal · published
§ 03The Before & After

Stop patching your conference together.

What running a 500-paper conference on email, Google Forms, and a shared drive actually looks like — and what Sidang replaces it with. Side by side, one spread.

Without Sidang — the status quo

  • ×One Google Form per stage, drifting across editions.
  • ×Manual copy-paste of deadlines into 14 confirmation emails.
  • ×Reviewer assignments on a shared sheet — conflicts missed.
  • ×Invoices drafted individually; payment chasing by WhatsApp.
  • ×Camera-ready uploads to Google Drive, no formatting review.
  • ×Certificates designed in Canva, sent one by one.
  • ×No audit trail when something goes wrong post-hoc.

With Sidang — the method

  • ✓One platform, every stage — configured once per conference.
  • ✓Templated emails rendered with tenant variables, logged, auditable.
  • ✓Reviewer bids & COI declarations surfaced at assignment time.
  • ✓Auto-invoicing, 14-day clock, strict drop policy, no chasing.
  • ✓Camera-ready & copyright in one upload. Formatting workflow.
  • ✓Certificates auto-generated, tenant-branded, bulk-issued.
  • ✓Every transition logged; every action attributable.
§ 04The Pilot Programme

Onboarding our first five conferences.

We're partnering with a small cohort of academic organisers to refine Sidang with real workflows. You get a bespoke deployment, we get direct feedback. No lock-in. Full data export, always.

  • —Dedicated subdomain, configured end-to-end
  • —DO Spaces + Drive mirror, per tenant
  • —Direct line to the build team
  • —Flat pilot fee. No subscription yet

We reply within two working days. Your details are used to respond — nothing else, no marketing.

§ 05Questions & Answers

Honest answers.

The questions conference organisers keep asking us. If yours isn't here, write to us.

How does Sidang handle double-blind review?

Authors upload an anonymized PDF for review; reviewer identities are stripped from the feedback surfaced to authors ("Reviewer 1", "Reviewer 2" rather than names). Confidential chair-only comments are kept separate. The PDF viewer layer enforces this — it doesn't rely on reviewers remembering.

Can we mirror files to our own Google Drive?

Yes, optionally, per tenant. Spaces is primary and source of truth; Drive mirror is asynchronous and best-effort so Drive rate limits never slow your authors down. You pick which categories to mirror — submissions, payments, reviews, certificates — and the refresh token is encrypted at rest.

What's the payment model for conferences?

v1 uses the international-standard Model B: pay after acceptance. Auto-invoice on final acceptance (Email 2), 14-day clock (configurable), author uploads bank proof, secretariat verifies in the dashboard, receipt PDF emailed. If unpaid by day 14, the paper is dropped from proceedings — no grace. Payment gateways (Billplz / ToyyibPay / Stripe) arrive in v2; the abstraction is already in place.

Do you support reviewer bidding?

The data model does — reviewers can express bids (want / willing / neutral / avoid / conflict) per paper. The self-service bidding UI is on the v2 roadmap; in v1, chairs assign reviewers manually via the dashboard. COI-declared conflicts are surfaced at assignment time.

Is it ready for WoS / Scopus submission?

The editorial workflow and audit trail are built to satisfy indexing requirements. Metadata export (OAI-PMH) and DOI/Crossref assignment ship in v2. v1 proceedings are generated from your own camera-ready PDFs; we don't lock the content.

Where are you based? Data residency?

Built in Malaysia. Default deployment is a Singapore / Malaysia VPS with DO Spaces in SGP1. You can bring-your-own infrastructure — we'll deploy there for enterprise tenants.

How do we migrate from our existing setup?

Pilots include a migration consult. Anything in a spreadsheet can typically be imported — papers, authors, reviewers, and their assignments — before your next submission window opens.

Request pilot