Triage that asks your questions
Configure the screening questions your process actually asks. Let answers carry a preconfigured severity suggestion. Document who must be interviewed — and run the interview on the record. And when ink is required: print the form, sign on paper, and file the original in your validated QMS.
From first report to a documented decision
Every new event lands on the Triage Board and moves through one visible path — screened, questioned, decided — so nothing waits in an inbox for a routing call.
Deviation required
A genuine departure: the deviation is raised and investigated in your validated QMS — OgmaQ tracks the reference number and what happens next.
Process comment
A minor, in-control observation — recorded together with the documented reason it is not a deviation.
No further action
Assessed and closed with the justification on the record — and a stronger justification required when the risk signals are high.
Duplicate / existing record
Already captured — linked to the existing record so the history stays in one place.
Eight routing outcomes in all — including urgent management review, more information required, and a link to an existing QMS record — each with its own required fields, and follow-ups where the outcome creates them.
The questions are yours
Triage lives or dies on asking the right things. In OgmaQ the screening and decision questions are admin-managed question sets, scoped by form type, site and department — the most specific match wins, with one default as the fallback.
- Edit question text and help, set required and restricted flags, reorder, add your own
- Seven answer types — yes/no, yes/no/unknown, dropdowns, multi-select, text, number, date
- System questions stay bound to the fields the closure and severity engines read; custom questions ride alongside
- System questions retire, never delete — and every record keeps a snapshot of the exact questions it was asked
- Every change is versioned and audited the moment it goes live
Answers carry a suggested severity
Mark which answers affect severity and the level each one suggests. As screening answers land, OgmaQ shows a suggested severity — with the reason, question by question. No black box.
- Severity influence is configured per answer option — by your admins, to your rules
- The suggestion explains itself: the driving answers are named alongside the level
- Decision support only — the reviewer sets the severity, and changing it at decision time requires a written reason
- An optional risk-scoring overlay (factors, weights, score bands) can add a recommended severity and priority — applied only through a documented, audited override
The suggestion is decision support only — the reviewer sets the severity, and a change at decision time needs a written reason.
Decide who must be interviewed — then run it on the record
When triage calls for personnel interviews, the requirement becomes part of the record — who decided, why, whether QA must confirm the outcome — and closure waits for the interviews until they are complete. The interview itself runs in OgmaQ, on your question set.
- The requirement is a documented decision — owner, rationale and QA confirmation on the record — and once interviews are required, closure waits until each one is completed, or waived or deferred with a recorded reason
- Your 5M&E question set — People · Method · Material · Environment · Machinery — admin-managed and versioned
- Each interview keeps its own question snapshot; a later template edit never rewrites a captured interview
- Waive, defer or remove only with a reason — audited, with follow-ups landing in My Actions
Print it. Sign it on paper. File it in your QMS.
Some processes want a wet-ink signature on an interview record. OgmaQ is built for exactly that — deliberately without an electronic signature.
Print the interview record
A completed interview exports as a clean Personnel Interview Record — the details, the participants, every question and answer in captured order, and the summary. Print it, save it as a PDF, or download a self-contained copy.
Sign on paper — outside OgmaQ
Names are pre-printed where the record knows them; the signature and date lines stay blank for handwriting. OgmaQ does not capture, witness, verify or authenticate signatures — the export is not an electronic-signature record, by design.
File the original in your validated QMS
The signed original is filed in your QMS under your own procedures — the QMS stays the system of record. Keep a scan with the escalation as evidence, and track the QMS reference on the record.
The full picture of what lives in OgmaQ and what stays in your QMS: how we draw the line.
Asked and answered
Can we change the triage questions ourselves?
Yes. Administrators manage the triage question sets directly — question text, help text, required flags, answer types, ordering and severity influence. Changes go live versioned and audited, and every escalation keeps a snapshot of the exact questions it was asked.
Does OgmaQ set the severity automatically?
No. Answers can carry a preconfigured severity suggestion, shown with its rationale question by question — but it is decision support only. The reviewer sets the severity, and changing it at decision time requires a written reason.
Can interviews be signed electronically in OgmaQ?
No — deliberately. OgmaQ prints a Personnel Interview Record with blank signature and date lines for handwriting. Signatures are applied on paper, outside OgmaQ: it does not capture, witness, verify or authenticate them, and the export is not an electronic-signature record.
Where does the signed interview record live?
The signed original is filed in your validated QMS under your own procedures — the QMS remains the system of record. A scan can be kept with the escalation as evidence, alongside the QMS reference number.
See triage on your own process.
Book a walkthrough and we will run the whole path — your questions, severity rules, interviews and the print-and-sign hand-off — on your workflow.
Or email hello@ogmaq.com directly.