The desk behind the journals and the conferences

§ 1the week

None of this is the science. All of it is the week.

The hard part of an editor's week is not the decision — it is remembering that the third reviewer never replied, that the second one is fifteen days late, and that the same person is already reviewing for the journal next door. The hard part of an organiser's week is the same shape: who paid, who is on the programme, who was actually at the door, and who is still waiting for a certificate.

Both are register work. Both are done today in a spreadsheet, a mailbox and somebody's memory — and both fail in the same quiet way, by a line nobody looked at.

§ 2journals

Connect OJS once. The desk fills itself.

A bridge plugin mirrors your submissions and your reviewer pool into the panel — one plugin to install, built for the OJS you are on, anywhere from 2.4 to 3.5. Nothing moves out of OJS: it stays your system of record, and every assignment and decision made here is written back into it.

What the desk keeps

Every submission with its round, its reviewers and their dates
Who is overdue, and by how many days — before the author asks
Assign a reviewer, record a decision; both land in OJS
Reminders that go out on a schedule instead of when someone remembers
Reviewer history and load across every journal and conference you run, not one at a time
Verifiable thank-you certificates, and a payment ledger when you compensate reviewers
Author fees collected into your own account, with the invoice and the receipt

Reviewer pool · all journals
Reviewer	Active	Journals	Median
H. Weber	4	3	11 d
T. Nakamura	2	2	19 d
A. Okoro	1	1	6 d
R. Silva	0	2	8 d

Editorial systems count a reviewer's work one journal at a time. If you publish five, the same person can be invited by three of them in the same week — and the third invitation is the one that gets declined.

§ 3conferences

From the call for papers to the certificate

Two ways in. Run the call and the reviewing here — submissions, blinded reviewing, decisions and letters — or keep reviewing where you are and import the accepted list as a file. Either way the rest is the same, and the rest is where the week actually goes: the registration form, the payment, the programme, the badge, the door, the certificate.

Optional: call for papers, reviewer pool, blind reviewing and the decision letter
A registration form with your fees, your discounts and your deadlines
Card payment into your own account, or bank transfer with a reference you can match
Programme and sessions, with clash checking
Badges that print, and QR check-in at the door on a phone
Attendance-backed certificates, each one verifiable from a public address
Session evaluation, and one message to every registered participant when something changes

What else is in the box

Area chairs — a meta-review layer between the reviewers and the committee.
Bidding — reviewers say what they want to read before anything is assigned.
Author rebuttal, and a discussion thread between the reviewers of one paper.
Committee console — the decisions of a whole track on one screen, with letters.
Abstract book from the programme, ready to print.
Badges and QR sheets for the desk, and scanning that works offline — the hall's wifi dies at three hundred people and the queue does not stop.
Meal and gala entitlements — one scan, counted once, no paper list.
Participants carried to next year's edition, so a returning delegate is not retyped.
Email to a whole group, and SMS when the room changes an hour before.
Reviewer payment ledger — who was paid, when, with the receipt attached.
Export of everything, as spreadsheets, whenever you want it.

The conference page, in detail

§ 4certificates

Eleven kinds of certificate, and each one knows where it came from

The certificate is the last thing a conference produces and the first thing a participant asks for. It is usually a mail-merge in a spreadsheet, and the spreadsheet does not know who actually presented, who chaired, who came to the door. Redaktum does, because it kept the register — so the certificate is issued from the record rather than retyped beside it.

Who gets one, and from which record

Presentation — from the published programme, so the name on it is the one that was in the session.
Attendance — from the door, not from the registration list. Somebody who registered and did not come does not get one; that would be a false document.
Session chair — from the programme.
Reviewer — from the reviewer pool, for the people who returned reports.
Best paper, second and third — the decision is the committee's; the certificate follows it.
Keynote, tutorial, special session organiser, committee.

Verifiable, and yours to design

Every certificate carries a verification link. A dean, a tenure committee or a funder opens it and sees what the conference recorded — no account, no login.
The design is the institution's: colours, type, border, page size, which blocks appear, your logo. One design, then every certificate of that conference matches it.
Issued in one pass after the conference, and reissued when a name is corrected — the old link keeps working, pointing at the corrected record.
Journal side too: a reviewer who reports for your journals gets the same thank-you certificate, from the same pool.

§ 5reviewers

One reviewer, one ledger — journals and conferences together

Ask any editor how much work a reviewer has done for the institution this year, and the honest answer is that nobody knows. OJS counts reviews carefully — inside one journal. Conference tools never look at the journals at all. Run five journals and a conference and the same person is six separate records, none of which can see the other five, and the fourth invitation goes out blind.

Redaktum keeps one ledger across everything the institution runs. Open reviews and completed ones, per person, journals and conferences in the same row — and a single certificate that counts all of it.

Total load per reviewer, not per installation — so the next invitation goes to someone who is free
Where the load sits: which journal, which conference
Suggestions rank on that total, so the person halfway through three papers for your conference is not offered a fourth
One certificate of appreciation, numbered and verifiable, counting every review they did for you
If a journal cannot be reached, the screen says the count is short — it does not quietly show a smaller number

§ 6money

The money is never ours to hold

Author fees and registration fees go into your payment account and your bank account. We are not in the middle of it, and we never take a share of what you collect. What we sell is the subscription below — a fixed amount, known in advance, unaffected by how good your year was.

Taking it

Cards run through your own Stripe account — your key, your checkout, your settlement. Bank transfer sits next to it, and a transfer stays declared until you match it against your statement: nobody gets a badge because they said they paid.

Seeing it

One screen for what actually came in over twelve months, journals and conferences apart, next to what is still waiting to be confirmed and how long it has been waiting.

Proving it

A reconciliation report reads your whole Stripe account — not only what came through us — and puts every charge beside the registration or author payment it belongs to. Charges nothing here accounts for are marked, not dropped. It downloads as a spreadsheet.

Holding other people's money is a regulated business in Türkiye and a distraction everywhere else. The register knows what was paid because your provider told it, not because the money stopped here.

§ 7price

Per journal, per year. Per event, once.

What would it cost us?

Journals Conferences a year Registrations you expect

Total, a year

Journals · per year

Journals	Each
1–2	$590
3–5	$490
6 or more	$390

Or a tenth of that a month — paying for the year is two months cheaper.

Conferences · per event

Registrations	Each
up to 150	$290
151–500	$590
501 or more	$890

Never a share of your registration income. A workshop of eighty should not pay for a congress of eight hundred.

Free for 30 days — up to three journals and one conference. No card, no call; when it ends, everything you recorded stays readable.

Start free

Card, or invoice and bank transfer — the way most institutions actually pay. Invoices are issued in USD or EUR by Duokod Yazılım Teknoloji Limited Şirketi in Türkiye, VAT-free as an export of services; EU business customers account for VAT under the reverse charge. Three journals or more, or a congress series: write to us.

§ 8asked

What editors and organisers ask first

We are still on OJS 2.4.

That is one of the reasons journals come to us. PKP stopped supporting the 2.x line and modern tools skip it. The bridge covers 2.4 through 3.5 — you install the one built for your version, and it speaks the same contract either way.

Does this replace OJS?

No, and it is not trying to. OJS stays the system of record: submissions and reviewers are mirrored here, and what you do here is written back. If you stop paying us, your journal is exactly where it was.

Do you read or check the manuscripts?

No. Redaktum handles the register around the work — who has it, what is due, what was decided. The manuscript file is not something the product opens.

We only run a conference, not a journal.

That works on its own. The account is per institution; a journal is optional, an event is optional, and you pay only for what you open.

Can we pay by invoice and bank transfer?

Yes, and most institutions do. We issue an invoice in USD or EUR, complete your supplier registration forms, and activate the subscription when the transfer arrives. Card payment works too.

Where is our data, and can we sign an agreement?

On a dedicated server in Türkiye, backed up daily. You are the controller and we are the processor; the agreement that covers it — a data processing agreement with the standard contractual clauses — is signed with your organisation before you sign up. Ask and we will send it to your legal desk.

What if we want to leave?

Your submissions and reviewer records live in your OJS, not here. Registers and participant lists export as Excel or CSV; certificates, invoices and the programme come out as print-ready files you save or print from the browser; and your organisation's own record — members, journals, subscriptions, payments — downloads as JSON. There is nothing to negotiate your way out of.

§ 9notes

Author fees and registration fees are collected into the institution's own payment account and bank account. Redaktum is never the payee and takes no share of them; the only money that reaches us is the subscription.
Conference price is per event and by participant count, not by income. The bands and what is included are on the conferences page.
Launch pricing, quoted per journal per year. Monthly is a tenth of the annual price, so twelve months paid up front costs ten. Half price in the first year for the first ten customers, in exchange for a case study we may publish. Organisations established in Türkiye are billed in lira at a lower local price; the panel shows it once your invoice details name the country.
Five journals of one publisher, who have used these tools daily since before they were a product. Their names appear here when they have given written permission, not before.

The science is yours. The register doesn't have to be.