The Tier meeting, on one screen.
A Tier board is usually a whiteboard, a spreadsheet and somebody's memory of what was agreed yesterday. OgmaQ runs the meeting itself: today's questions are answered on the meeting screen, the board colours itself against the targets you set, and what is off target becomes a discussed item, an owned action, or a request to the Tier above — carried into tomorrow without being retyped.
Start, answer, agree, complete
Four steps on one screen, in the order a stand-up actually walks them. There is no separate place to go and answer the questions, because that is the meeting.
Start today's meeting
The facilitator opens the team's meeting for today. Attendance is recorded on the same screen, not in a separate note.
Answer today's questions
Each of the team's questions takes a number or a Yes / No. The board colours itself as the answers land — nobody scores anything by hand.
Discuss what is off
An off-target question becomes a discussed item with the prompts your site uses. From it: an action with a named owner and a date, or a request to the Tier above.
Complete the meeting
Completing it freezes the board as it stood — the record of what this meeting actually saw. Open actions and unresolved requests carry to tomorrow as themselves.
The board freezes when the meeting is completed, not when it starts — a meeting that froze before anyone had answered would freeze a board of “no data”, permanently.
Your questions, your targets, your categories
Each team has its own questions. A question carries a category, an owner, a unit, how often it is asked, and what “good” means — and OgmaQ works out the colour from that, every time, rather than storing a status somebody set.
What a question can be
Five kinds, because a real board is not all percentages.
- Higher is better — right first time, adherence, attendance.
- Lower is better — downtime, open deviations, yield loss.
- Within a range — measured by how far outside it sits, not just in or out.
- Yes / No — coloured by your target, so “any safety topics to raise?” is red on Yes.
- Informational — carried and shown, deliberately never coloured.
Questions file under Safety, Quality, Cost, Delivery and People by default — the letters a lean practitioner already reads. Rename them, retire one, or add your own; a question always says which category it belongs to, including on the lists that are deliberately not grouped.
Set the target, then a warning band and a critical threshold. A question that misses its target reads amber; one past the critical threshold reads red. You choose where those sit — nothing is inferred.
A missing answer is recorded as no data, never as zero. A day nobody answered shows as an absence rather than quietly counting as a good day.
One square per day per question, coloured by the same rule the tile uses. Six weeks of a question on one row, so “this keeps happening on Mondays” is visible without a report.
A conversation that leaves something behind
The point of the meeting is not the board. It is the three things that can come out of a question being off, each of which is a record with an owner rather than a line in someone's notebook.
The item
What happened, why it is off target, whether it is within the team's control, and whether today's plan is at risk — your prompts, editable, each one bound to its own field so renaming it does not lose the history.
Somebody's job
A named owner and a due date. It appears on that person's My Actions list beside everything else they owe — not in a second inbox — and a completed action is a record, not an editable note.
A request upward
When it is not within the team's control, it goes to the Tier above — born open and unowned, so it is visibly nobody's until the receiving team takes it, instead of quietly being everybody's.
Support goes up, never sideways. A request can only be raised to a strictly higher Tier: the picker offers only higher teams, and the database refuses an equal or lower one. That is what keeps a Tier structure a structure rather than a group chat.
Carry-over without retyping
Yesterday's open items are not copied into today's meeting. They are today's open items — the same records, still open, with their own history attached. Nothing is transcribed, so nothing is transcribed wrongly.
Running a team's meeting takes the permission and membership of that team. Holding the permission on a team you are not on runs nothing, and that is resolved in the database rather than hidden on screen.
An answer is added, never edited away. Recording a corrected value leaves the earlier one in place, so the board's history is what the team actually saw on the day.
A completed meeting keeps the board it froze. Re-opening last Tuesday shows Tuesday's numbers, not today's recomputed against Tuesday's date.
Tier 1 is the frontline and a parent sits on a higher number. Teams carry a department and a cadence — every day, weekdays, or weekly — and the hierarchy is yours to build.
OgmaQ is not connected to your other systems, and does not pretend to be. Two sources work today: a person answers the question, or OgmaQ counts its own records — open escalations, batch reviews pending, findings raised in the last day. Every other source exists in the data model so that a future connector is a provider rather than a redesign, and an administrator sees those listed as not available rather than as something to configure.
A support request is not a GMP escalation. It is a Tier-to-Tier ask for help. Where a discussion item turns out to be a GMP issue, it is raised as an escalation through the normal intake and linked — one record, on the auditable path, in the same workspace. OgmaQ is operational management support: it is not a validated GMP system of record by default and makes no 21 CFR Part 11 / EU Annex 11 compliance claim.
See how we draw the lineWhat a site lead asks first
Does OgmaQ connect to our MES, ERP or LIMS to read KPI values?
No. Two sources work today: a person answers the question, or OgmaQ counts its own records — open escalations, batch reviews pending, findings raised. The other source types exist in the data model so a future connector is a provider rather than a redesign, and an administrator sees them listed as not available rather than as something to configure. Nothing pretends to be connected.
Can a team ask another team at the same Tier for support?
No. A support request goes to a strictly higher Tier — the picker offers only higher teams and the database refuses an equal or lower one. It is born open and unowned: only the receiving team takes and resolves it, while the raising team can amend or withdraw it.
Is a support request a deviation or an escalation?
No, and the product is careful about it. A support request is a Tier-to-Tier ask for help and is never routed as a GMP escalation. If a discussion item turns out to be a GMP issue, it is raised as an escalation through the normal intake and linked to the item — so it lands on the auditable path with triage, decision and closure, rather than living on a board.
Who can run a Tier meeting?
Someone who holds the permission and is a member of that team. Holding the permission on a team you are not on runs nothing. The rule is resolved in the database, so the screen and the server agree.
What happens if nobody answers a question today?
It reads as no data, never as zero. A missing answer is recorded as an absence, so a day nobody answered is visibly blank on the month grid instead of quietly counting as a good day — and a month of blanks never summarises as “on target”.
Can we change the categories and the discussion prompts?
Yes. The categories ship as SQCDP — Safety, Quality, Cost, Delivery, People — and an administrator renames, reorders, retires or adds to them for the whole workspace. The discussion prompts are editable in the same place, and each stays bound to its own field, so renaming a prompt does not orphan the answers already given under it.
Do we have to run this module?
No. Daily Management is one of OgmaQ's nine modules. It ships switched on so you can see it, and an administrator switches it off in one click if your site does not run Tier meetings here — the destination leaves the sidebar, and teams, questions, meetings and actions already recorded are kept.
The module system. How OgmaQ is composed, what a switch does and — more importantly — the four things a switch is deliberately not allowed to do.
See all nine modulesWhen a board item is a GMP issue. It leaves the board and becomes an escalation in the same workspace — triaged, decided and closed on one auditable path.
See the full productBring a photo of your board to the demo.
We will build your Tiers, your categories and your questions on fictional demo data, and walk one morning end to end — answers, a discussion, an action and a request upward.
Or email hello@ogmaq.com directly.