SystemManufacturing Intelligence

Tier Meeting Management

A tier meeting system for CDMO plants: agents fill each SQDCP square from the plant's systems before the shift, keep every action with an owner who accepted it, and move items up the tiers on the board's own clock.

See one morning's board, meeting and escalation ↓
Watch with transcript →
The problem

Fifteen minutes spent reading out numbers someone colored by hand at dawn

Before the first shift meeting, a supervisor opens the MES, QMS, LIMS, maintenance system, ERP and safety log, and colors each square with a marker, a sticky note for the reason. When a feed is missing, the square can end up green. At the area meeting most of the time goes to reading those numbers aloud.

Actions land on a whiteboard or a shared sheet with a name and a date, and the next morning someone asks whether it was done and takes the answer on trust. An item the line cannot solve is written on a card and carried up; one the area cannot solve waits for someone to raise it at the plant meeting. A client's delivery risk reaches the account lead days late.

Built forArea managersLine leadsPlant headsQA operations managers

The Problem Today

The board is built by hand before dawn, the meeting goes to reading numbers aloud, and an item one tier cannot solve waits for someone to remember it.

243
211.22(d) quality unit: FDA's most cited drug line in FY2025 published
164
211.192 investigations, the second most cited line, FY2025 published

Copied onto the board by hand

  • MES
  • QMS
  • CMMS
  • ERP
  • Minutes spent reading aloudNumbers recited at the board while decisions wait for later
  • Closed on someone's wordNobody opens the work order or the signed record next morning

The Solution

  1. Every square filled from the systemsColored by the board's rules before the shift, each with its reason and source
  2. The draft board challengedSegregated product is not scrap, so cost is corrected before anyone reads it
  3. Actions exist once acceptedProposed in the room; the owner opens the record and signs to take it on
  4. Items climb on the board's clockUnsolved items rise on their own, and the next tier reads every hold

Built-in controls

  • No action is live until its owner accepts it
  • Owners do not close their own actions
  • Held batches and stopped lines stay QA's call

What You Get

A risk reaches the person who can act on it the same morning, with an owner who accepted it and a date.

  • Supervisors freed from the markerThe board is filled and sourced before the shift starts
  • Repeat problems named for a real fixAn item back three times in a month is flagged as recurring
  • Done means the evidence arrivedWork orders and signed records checked in their systems the next morning
Features

Tier meeting features, from the filled board to the plant head's agenda

One processing area's morning: the board fills at 06:40, the area manager runs tier 2 at 07:30, and a client delivery risk reaches the plant head's agenda.

demoThe plant, its lines, crews, clients and figures are sample data.

  1. 01Letter calendars

    SQDCP board for a tier meeting, every square filled from the plant's systems

    • One square a day for each letter. Safety, quality, delivery, cost and people are drawn as calendars, so the month's pattern sits beside today's color.
    • Colored by the board's own rules. Each square cites the rule and the record that set it; a missing feed shows no data and names who to ask.
    • The agenda built letter by letter. Each item arrives with its source, a proposed owner, a due date, in time boxes that add up to fifteen minutes.
  2. 02Quality square

    The quality square in red, with the deviation record behind it

    • The source record shown in the square. The deviation's readings, hold and qualification status open straight from the board, so the question of red is settled before the meeting.
    • The board points at the QMS record. A red square leaves the deviation where it lives; only QA can change a quality color, and loosening one waits for the plant head.
  3. 03Board checker

    Board checker corrects a cost square before the board is published

    • The draft challenged against its source. The checker reads the hold record and finds the tablets segregated pending QA's decision rather than rejected, so cost turns amber.
    • Corrections left on the square. The note stays where the room sees it, so everyone knows what the agents got wrong and why the color changed.
  4. 04Steer

    Steer the agents during the tier 2 meeting, and the action changes owner

    • Steering in the room's own words. The area manager types what the room decided; the action keeper changes the owner and logs the steer for the plant head to read.
    • Actions proposed to their owners. The new owner receives what, when and the evidence that will close it, and takes the action on only by accepting.
  5. 05Escalation

    Tier escalation process for a client delivery at risk, with owner and date

    • The hold record opened before accepting. The owner reads the hold behind the risk, so the item goes up with its evidence.
    • An owner named before it goes up. The area manager picks the owner and the due date, and the item reads awaiting owner until that person accepts.
  6. 06Tier 3 agenda

    Plant head's tier 3 agenda, the delivery risk on top with its owner

    • Both area meetings on one agenda. Items from the plant's two area meetings arrive each with its owner, due date and the record behind it.
    • Receipt signed once an owner accepted. The plant head cannot sign received at tier 3 until the named owner has opened the hold record and accepted.
  7. 07Evidence check

    Yesterday's actions checked against their evidence in each system

    • The evidence looked up in its system. Work orders, signed records and schedule versions are found in the CMMS, QMS, LMS or ERP before the meeting starts.
    • Partial shown as partial. A read-and-sign missing signatures stays partial, and a closed work order with an unsigned calibration stays open.
  8. 08Tier ladder

    Tiered accountability on one ladder, each item climbing on its clock

    • Clocks per tier, rules per item. Unsolved items move up when the tier's clock runs out, and same-day rules lift a red quality square or a delivery risk at once.
    • Holds read by the next tier. Holding an escalation takes a reason code from the tier lead; the plant head reads every hold.
  9. 09Recurring items

    Recurring items named, and routing rules learned from the area's rulings

    • A problem that keeps coming back, named. An item seen three times in a month is proposed as recurring and the area manager decides, so the fix goes to its cause.
    • Routing learned from rulings. Who gets hardness and tooling actions becomes a proposed rule that applies once the plant head approves, and nobody approves a rule drawn from their own rulings.

Only QA operations can change the color of a quality square

Line leads raise, area managers decide or send up, plant heads take what reaches their meeting, and QA keeps the calls on product.

Area managers

Run the area meeting and own the area's actions and escalations

  • A board ready before the meeting
  • Fifteen minutes spent on decisions
  • Agents that follow the room's steer
Line leads

Run the shift-start huddle and send up what the line cannot fix

  • Items carried up on the clock
  • The person who decides a stopped line
  • No board to color by hand
Plant heads

Chair the plant leadership meeting, approve board rules, read every hold

  • Escalations that arrive with owners
  • Each hold with its reason code
  • Proposed rules ready to approve
QA operations managers

Decide holds and stopped lines, and own the quality color

  • Quality squares that point at QMS records
  • Actions that reach them as proposals
  • Escalations they accept by signature

Seven read-only feeds behind every square, with nothing written back

Each square cites one of these, read-only; the safety letter is workplace safety alone.

MES and eBROutput, stops, in-process checks and the batch record
QMSDeviations, holds and change controls behind the quality and delivery squares
LIMSResults waiting and out-of-specification results
CMMSBreakdowns, tag-outs and the work orders that close actions
ERPSchedule adherence, client call-offs and delivery dates
EHS logWorkplace injuries and near misses for the safety square
Shift roster and learning recordsCrew on the floor against the minimum, and read-and-sign records
More screens

Line C2's restart stays blocked on the huddle screen until QA decides

Around the board and the meeting: the crew square, the sent-on line, the huddle, open actions, the network review and the trail.

The people square and the night rosterThe night crew on the floor against the minimum for both nights, and the rule that turns the square amber.
What the meeting sent onThe sent-on line during the meeting: the delivery risk awaiting its owner and the stopped line for information, each with who acts.
The compression line huddleThe line lead's tier 1 view: each line's state at 06:40, a stopped line whose restart stays blocked until QA decides, and what went up to tier 2.
Open actions across four plantsEvery open action with board, letter, owner, due date and state; closing in bulk needs a sample of the evidence opened first.
Four plants on the same lettersThe head of operations' tier 4 view: each area board's letters today and the month's red and amber days per letter, read-only.
Each steer, acceptance and correction loggedEvery person's and agent's step, what each signature means and its session; the minutes export reads unsigned until the area manager signs.

demoSample data, from the working solution.

The board checker caught the square filler counting held tablets as scrap

Plan, sources and confidence show on every agent's tile, along with whom it passes work to.

Square filler

Reads the plant systems for the last day and colors each square by the board's rules, with reason, source and confidence.

  • Colors no square without a source
  • Shows no data for a missing feed, not green
  • Changes no QMS record
Board checker

Reads the draft board as the plant head and an auditor would, square by square against each source.

  • Changes no color without quoting the source
  • Leaves each correction on its square
Agenda builder

Orders the agenda letter by letter in time boxes, with the huddles' items and yesterday's actions.

  • Drops no safety item
  • Adds no item without a source
Action keeper

Turns what is said into actions with owner, due date and evidence type, and checks that evidence next morning.

  • Makes no action live before its owner accepts
  • Closes no action
  • Takes no free text as evidence
Escalation clerk

Applies the tier clocks and the same-day rules, and places accepted items on the next tier's agenda.

  • Escalates nothing without the tier lead's acceptance
  • Hides no hold from the next tier
Recurrence watcher

Names items that keep returning and proposes routing rules from past rulings.

  • Applies a rule only once the plant head approves it

An escalation cannot be signed as received until its owner accepts it

A signature counts once its signer has had the underlying record open for the set reading time.

Action owner
Sees
The record behind the action, open for the set reading time
Signs
Acceptance of the action, or a refusal giving its reason code
Area manager
Sees
Each proposal, steer and hold raised in the meeting
Signs
Accepted escalations, holds with their reason code, and the minutes
Plant head
Sees
The escalated item and the hold record behind it
Signs
Receipt of each escalation, agreeing or lifting a hold, and learned rules
QA operations manager
Sees
The deviation or hold record behind a quality square
Signs
Changes to a quality color, and loosened settings the plant head proposed
Closer of an action
Sees
The evidence where it was recorded
Signs
The close, only on actions someone else owns

What plant heads ask before moving a tier meeting onto agents

What is a tier meeting?

A tier meeting is a short daily stand-up at one level of the plant: line huddles, area meetings, plant leadership and a network review, each reading safety, quality, delivery, cost and people. Here agents fill the tier meeting board from the plant's systems, keep each action with an owner who accepted it and carry items up the tiers on the board's clock.

What goes on an SQDCP board?

One calendar per letter, safety, quality, delivery, cost and people, with a square per day colored green, amber or red by written rules. Each square here carries its rule, its reason and the record that set it, and a missing feed shows no data instead of a color.

How does the tier escalation process work?

Each tier has a clock: an item unsolved at the line moves to the area, then to the plant leadership meeting, then to the network review. Same-day rules lift a red quality square on a client product, or a delivery at risk, straight to the plant leadership meeting. A tier lead may hold an item only with a reason code, and the next tier reads the hold.

Can the board decide on a held batch or a stopped line?

No. A red quality square points at the QMS record. QA alone decides on a held batch or a stopped line, and restarting the line stays blocked on the line lead's view while the deviation is open.

How are actions from tiered meetings closed?

On evidence, by someone other than the owner. The action keeper looks for the closed work order, the signed record or the published schedule the next morning, and shows partial evidence as partial.

What is a tier two meeting?

The area meeting, one level above the line huddles. The area manager takes up what the lines could not solve, names owners and due dates, and sends what the area cannot solve to plant leadership on the board's clock.

Bring one week
of your tier boards.

Send a week of one area's boards and action log, and see which squares, actions and escalations the agents would have changed.