Counsel: escalations, redlines & playbook

The legal queue — what routes to a lawyer, and the playbook that drives the drafting.

5 min read

Counsel works a focused queue instead of every document. The routine flows on its own; a lawyer's attention goes where it's actually needed.

Two lanes, not one

Escalations split by kind. Business terms — above-the-line deals and rates above the market threshold — are the producer's call and route to a quick message sign-off, not to a lawyer. Counsel gets the genuinely legal exceptions:

  • Paper that must change — a redline a producer bumps up when the agreement itself needs edits.
  • Talent or agent comments that turn into legal asks.
  • Minors — patria potestad handling and guardian consent.
  • Evidence-sensitive matters — anything where the record needs a lawyer's eye.

Redlines, not rubber stamps

An escalation opens with the agreement marked up against the playbook. Findings are color-coded — within the preferred position, near the fallback, or beyond the walk-away — so counsel reviews a position, not a blank page.

Your forms, your playbook

The firm brings its own forms. BALA is not a law firm and ships no master library: at onboarding you upload your contracts, BALA turns them into your templates, and derives your starting playbook from them — one clause, one position. Your templates, playbook, and learning loop are yours alone, never shared with another firm.

The form document behind each clause opens from the Playbook. A gap review reads your template and flags holes — consistency and structure it can state plainly, and legal questions it routes to your counsel — but it never writes the legal content. That stays your professional judgment.

Human in the loop

Positions the learning loop suggests from resolved matters, and gaps the AI flags, always wait for a lawyer to accept. BALA supplies the workflow; the firm supplies the judgment.