Home / Platform

One platform, from first submission to citable record.

The Article Management System is our own software, shaped by the editorial work we do on it. Four parts - submission and review, publishing, researcher identity, and preprints - share one record, so a paper is entered once and carries its history to publication.

Hands typing at a laptop keyboard

The journey of a paper

Every stage tracked, nothing lost in between.

1

Submit

Authors submit against the form and file types that venue has configured.

2

Review

Chairs assign reviewers and can run an automated similarity check; iThenticate/Turnitin integration is supported when the venue's licence is active; scores and comments come back on schedule.

3

Decision

Accept, revise or decline, with revision rounds fully tracked.

4

Camera-ready

Final files and any publication fee are collected and verified — with a pre-filled IEEE eCopyright (eCF) hand-off for IEEE venues.

5

Production

Metadata, copyright and payment checked before a DOI is reserved.

6

Published

The article page goes live with its DOI and citations.

Printed pages, an open notebook and a pen on a desk

Publishing Module

A production line built for a permanent record.

The Publishing Module runs on its own subdomain and shares the AMS database, so there is exactly one canonical record for each publication. A paper reaches it only after it has cleared acceptance, camera-ready, and any fee due.

  • Checklist-gated DOIs. Metadata, copyright and payment are verified before a DOI is reserved.
  • Fixed, checksummed PDFs and formal correction, retraction and withdrawal notices.
  • Every article three ways — a full-text HTML page, the PDF of record, and JATS 1.3 XML, the format PubMed Central requires and aggregators harvest.
  • Linked reference lists — each reference resolves to Crossref where we hold its DOI, and to Google Scholar otherwise.
  • Supplementary files — datasets, appendices and code published alongside the article.
  • Six citation styles plus BibTeX and RIS, Google Scholar tags and structured metadata.
  • Compiled proceedings volumes and a persistent public venue page per series.
Rows of shelved volumes in a library

Identity & early sharing

The Federation and the preprint server.

Every author gets a single Technology Fist identity with a member ID, profile and service record that follows them across every conference and journal. When work is ready to share early, the preprint server posts it, moderated, with its own DOI.

  • One member ID and profile across all venues, ORCID-linked.
  • A reviewer service record and downloadable certificates.
  • Moderated preprints posted with a clear not-yet-peer-reviewed label.

Beyond the plans

Four optional modules, enabled per venue on request.

These are not part of any plan and are off by default. A venue asks for the one it wants and we enable it for that venue, so a conference carries only what it uses. Prices are quoted case by case.

Federation Reviewer Network

Search members across the whole platform who have opted in to reviewing, by subject — with each one's review service record, current workload against their own declared capacity, and automatic conflict-of-interest checks. Reviewers control their own listing and every invitation is theirs to decline.

Portable peer review

An author can carry the reviews of a decided paper to another venue on the platform. Each reviewer decides separately whether their report travels and whether their name goes with it; confidential comments to the chair never do. The receiving editor sees it as background, never as a decision.

Indexing & compliance readiness

Score a venue against DOAJ, Scopus, Web of Science and COPE expectations using its own record, see exactly which criteria are unmet and how to fix each, and export an evidence pack for an application. Readiness only — the decision always rests with each service.

Live event layer

Ticket types, delegate registration with capacity limits, on-site check-in, and attendance or presentation certificates issued only against a real record — each carrying a code anyone can verify on a public page. These certify that someone attended or presented at a specific event; they are not academic qualifications, degrees or diplomas, and we neither issue nor accredit any.

Built for every role

Each role gets its own console.

Each dashboard opens on the work that is waiting for that person, with the deadline attached.

Authors

Submit, track each paper through a clear status stepper, upload camera-ready files, pay fees, and approve proofs.

Chairs & editors

Assign reviewers, manage the pipeline, record decisions, and run the venue website and programme on the plans that include them.

Reviewers

See assignments and deadlines in one place, review revised files with the author's response alongside.

Organisers

Register a conference or journal, manage registrations and author-fee records under your own payment arrangements, and publish the proceedings.

Specialists

Faculty and industry experts who review publishing applications and uphold standards across venues.

Super Chair

Platform oversight: an action inbox, KPIs, and every approval and audit trail in one console.

"Accepted, camera-ready, paid, published. The same record moves through every step, so what an author sees, what a chair decides, and what a reader cites never drift apart."

The AMS principle

Put your venue on the platform.

Register a conference or journal, or ask us to migrate an existing one. The workspace is provisioned after payment - usually within minutes - and you configure the call for papers from there.