Project Manager status overrides

Not for requestors

Override (HUMAN) and Override (BRAT) are locked on the board on purpose. Only a project manager (or whoever is triaging the board) changes them. If you’re submitting a ticket, you’re done at the pre-submit checklist.

BRAT re-checks the board once a day and locks a ticket after two failed passes. These two override columns move a flagged ticket forward without waiting for the daily cycle. They do different jobs - one overrules BRAT, the other asks BRAT to look again.

The two override levers

Override (HUMAN) → “Yes” - promote a ticket now

The everyday lever, and it works whether or not BRAT has locked the ticket. Most Needs Attention flags are mundane: the submission form can’t set Scope, Request Type, or an Assignee, so BRAT correctly reports an empty column or gives advisory feedback, even though the brief is fine.

It’s a judgment call, not a bypass - and on a locked ticket there is no automated check behind it, so the diligence is entirely yours. Work the flags in order:

1. Read BRAT’s item update and sort what it flagged. Operational gaps (Scope, Request Type, Assignee - the columns the form can’t set) versus content gaps (a thin Creative Overview, a missing file or link, a scope/type mismatch).
2. If any flag is about content, stop - that’s a held or bounced ticket, not an override. Fix the brief, or bounce it back to the requester. HUMAN is never for bypassing a thin brief.
3. Confirm the brief clears the bar yourself - the same bar as the pre-submit checklist: a substantive Creative Overview or an attached PDF/Word brief, and every “see attached / see link” reference actually present in Files/Assets or Additional Link/s. Only once that holds, fill the operational columns BRAT flagged - typically Scope, Request Type, Assignee (Work).
4. Flip Override (HUMAN) → Yes (the only label - it’s either “Yes” or blank).

If every required column is filled, the automations fire and the ticket moves to In Progress. If anything is still missing, Monday silently resets the column to blank - that’s your signal a required field is empty. Fill it and flip again.

!

This is a judgment call, not a bypass. If a ticket was flagged because the brief itself is thin - something major missing, not just an empty column - flipping this just pushes incomplete work to a creative. Fix the brief, or bounce it back, instead. On a locked ticket especially, whoever flips it must be 100% certain every required element is in place: nothing re-checks it afterward.

Override (BRAT) → “Reevaluate” - make BRAT look again

Once a ticket is locked (two failed passes), the daily review skips it. Override (BRAT) → Reevaluate is the only way to put a locked ticket back in front of BRAT. (On a ticket that isn’t locked, it does nothing - the daily review still owns it.)

1. Confirm the locked ticket’s brief was genuinely improved since it locked - an expanded Overview, or the missing file or link now attached. If nothing changed, BRAT will just fail it again.
2. Flip Override (BRAT) → Reevaluate. BRAT re-judges the content immediately, instead of leaving the ticket to wait out the daily cycle.

If the brief now clears the bar, BRAT flips the ticket to Sufficient and moves it into the work queue itself - no manual status change needed. If it still falls short, you get a fresh round of feedback to act on. (This is the difference from HUMAN: there you assert the ticket is ready; here BRAT does, and advances it for you.)

Which one to use

Situation	Lever	What you’re doing
Brief is solid, the ticket just needs its columns filled	Override (HUMAN) → Yes	Overruling BRAT’s column complaint and sending it to work.
A locked ticket’s brief has since been fixed and you want BRAT to confirm	Override (BRAT) → Reevaluate	Handing the call back to BRAT, not making it yourself.