The console
Where procedures are written, published and supervised
Educate, Assist and Monitor efficiency are all set up here and two of the three then happen somewhere else. Everything an author or an administrator does happens at sop.mednais.com, and none of it is in the phone app. Write a procedure or draft one from a document; have somebody qualified publish it; invite the people who will run it; watch the runs in progress; read what came back.
Sign in with Google, Apple, a one-time code, or a password you set.
Three steps, and a person in the middle
The gate between drafting and running is deliberate, and it is not something we will let you switch off.
Write or draft
Type the steps, or upload the document they come from
Read it and publish
Somebody qualified in that work signs it off
Invite the people who do it
They run it on their phones and the record comes back
Six things the console does
Write a procedure
Steps in order, each one saying what to do and what it needs back: a confirmation, a checklist, a timed wait, a yes-or-no answer, a code
Or draft it from a document
Upload a PDF, a Word file or plain text and a language model writes the first pass from it. Scanned PDFs with no text layer are refused rather than guessed at
Publishing is a person’s act
A draft cannot be run. Somebody qualified reads it in full and publishes a version; the product will not publish one by itself
People and roles
Owners, administrators and members, with the authority between them enforced by the database rather than by hidden buttons
Invitations
Links with an expiry, a limit on how many times they can be used, and optionally a restriction to one e-mail domain. Join requests can be approved or refused
Runs in progress
A board showing who is on which step and how long they have been there. It refreshes every few seconds rather than instantly
One account, two other places
The console is where the work is prepared. The other two are where it is carried out and where it is read back.
Questions about the console
Mostly about what a draft is and what it is not.
What can I upload for a draft?
PDF, Word (.docx) and plain text. The type is decided by the file’s contents rather than its name. A scanned PDF with no text layer is refused with an explanation, because there is nothing in it to write a procedure from.
Does uploading a document produce a finished procedure?
No. It produces a draft. A language model can state an incorrect quantity or interval, omit a control the source requires, or attribute a requirement to a standard that does not contain it — so a person qualified in the work has to read the draft in full and publish it before anybody can perform it.
Where do the documents go?
Into your own organisation’s tenant. They are shown to no other customer and are not used to train any model. To draft from one, its extracted text is sent to the model providers named in our privacy policy — which matters if the document is a standard you licensed under terms that forbid that.
Can I brand the console for my organisation?
For the console, a name, a logo and a timezone, and nothing else: no theming, no colour scheme and no white-labelling of the screens your own staff use, and earlier versions of this site said otherwise. The exception is the page a printed QR code opens for somebody outside your organisation. That one is styled: eight designs and six accent colours, chosen once by an administrator and applied to the whole page, which carries your name, your logo and your support contact.
Look at it first
The demonstration needs no account and records nothing. Four example procedures, from four different kinds of work.
Open the demonstration