Law firm social media compliance: a workflow, not a promise
This page describes how an approval queue works and how it fits inside the review process your firm already runs. It is general information about workflow. It is not legal or compliance advice.
Every firm that markets already has a review process, even if it is informal — a partner reads it before it goes out. The problem is that the process was designed for a handful of items a year and social media produces a hundred. The volume is what breaks it, not the medium.
The workflow described here is the response: make drafting cheap, keep review mandatory, and give the reviewer a queue that is fast enough to actually work through. Nothing about that changes who decides what your firm publishes.
Why review matters more here than in other industries
Most businesses can publish a mediocre post and lose nothing. A law firm's public writing sits closer to its professional obligations, and readers are often in a difficult situation and inclined to treat what they read as guidance meant for them.
That caution is sensible. It is also why removing the review step to move faster is the wrong trade. The right trade is to make everything around the review step cheaper, so the step itself is easy to sustain.
Volume is the real risk factor
One post a quarter gets read carefully. Forty posts a quarter get skimmed unless the queue is built for skimming well. Design for the volume you actually intend to publish.
Readers arrive with a problem
Someone reading a firm's post about a legal process is often in the middle of one. Writing that explains rather than prescribes is a smaller ask of the reader and of the reviewer.
How an approval queue works
Agents research and draft. Each draft lands in a queue with the platform, the scheduled time and the full text in one view. A person opens it and chooses: approve, edit and approve, or reject.
Approved posts publish at their scheduled time. Edited posts publish as edited, and the edit is fed back so later drafts move in that direction. Rejected posts never publish. An unreviewed queue does not go out, so the default state of the system is silence rather than exposure.
There is no bypass
There is no setting that allows an agent to publish without a human approving that specific post. This is a property of the product, not a configuration a busy week can override.
The unit of review is the post
Approval applies to one post at a time, with its exact final text. Approving a topic or a batch of themes is not the same thing and does not happen here.
Who should hold the approval role
The answer most firms arrive at is: whoever already reads public-facing material. Introducing a new approver because a new tool arrived tends to create ambiguity about who is actually responsible.
What is worth deciding explicitly is the backup. A single approver means a two-week trial produces a two-week gap. Naming a second reviewer, with the same authority and standard, keeps the queue moving.
Name a primary and a backup
Two people who both understand the firm's standard. Not two people who each assume the other is watching.
Write the standard down once
A short internal note on what this firm will and will not publish makes the review faster and makes it consistent between reviewers.
Keeping a record of what was approved
Each post in the queue carries the text that was approved and the account that approved it. Firms use this as an internal record of their own process — what was published, in what form, with whose sign-off.
This is a description of how the workflow behaves. It is not a claim that the record satisfies any retention or supervision requirement that may apply to your firm. What your firm needs to keep, in what form, and for how long is a question for your compliance officer or counsel.
The record is a workflow property
It exists because approval is a discrete step with a person attached to it. Treat it as internal documentation, and check separately with your compliance officer about anything beyond that.
Comments and direct messages
The published post is the part firms plan for. The comment underneath it is where the difficulty usually appears, because a general post followed by a tailored reply to one person's facts is a different kind of communication than the post was.
The common practice is to decide in advance what happens in the replies: acknowledge, thank, and move anything specific to a private channel or a scheduled call. Decide it once, write it down, and make sure whoever monitors the accounts knows it.
Have one prepared move
A short, standard reply that thanks the person and offers a call is easier to use consistently than judgment applied fresh each time under time pressure.
Decide who monitors and how often
An unmonitored comment section is a slower version of the same problem. Assign it, even if the assignment is ten minutes a day.
What Bolta does not do
Being explicit about the boundaries is more useful than reassurance.
Bolta does not review your posts for professional appropriateness. It does not know your firm's obligations, your practice areas' particular sensitivities, or what your compliance officer would say. It does not publish anything a human at your firm has not approved, and it does not make any firm compliant with anything. It is a drafting engine and an approval queue. The judgment stays with your firm.
No compliance review
Drafts are steered toward explanation over prescription as a writing default. That is a stylistic default, not a legal check, and it does not replace your reviewer.
No guarantees of any kind
Bolta makes no representation that its use satisfies any professional, regulatory or ethical requirement applicable to your firm.
A review checklist
A process for the person who approves posts. Adapt it to the policies your firm already has, and check anything you are unsure about with whoever owns compliance where you work.
Name the approver and the backup
Two people, both with authority to publish on behalf of the firm, both familiar with what the firm will and will not say publicly.
Write a one-page internal standard
What this firm publishes, what it does not, and what always goes to a second read. One page, reviewed with your compliance officer if you have one.
Read the full text, not the topic
Approve the exact words that will publish. A topic sounding fine is not the same as the draft being fine.
Check the framing before the wording
Ask whether the post explains something or tells a reader what to do. Fixing the framing is usually one sentence and it resolves most concerns at once.
Confirm nothing identifies a matter or a client
Including details that are individually harmless and jointly identifying. This is the check worth slowing down for.
Decide the reply policy before publishing
Know what happens when someone comments with their own facts, and make sure whoever watches the account knows it too.
Keep the approved version
The queue retains what was approved and by whom. Confirm with your compliance officer whether your firm needs anything further.
Re-read the standard once a quarter
Practice areas change and so do the platforms. Fifteen minutes a quarter keeps the standard from becoming a document nobody follows.
Where Bolta fits
Bolta’s agents research and draft posts, then hold them for review. The approval workflow is designed so that a human reviews every post before publication. Bolta does not decide what is appropriate for your firm to say, and it does not replace the review your firm already does. Follow the policies you already have, and consult your compliance officer or counsel on anything specific to your situation.
Frequently asked questions
Does Bolta make my law firm's social media compliant?
No. Bolta is a drafting and approval workflow. It does not review posts for professional appropriateness and makes no representation that its use satisfies any requirement applicable to your firm. What it provides is that every post is read and approved by a human at your firm before it publishes. Compliance judgments remain with your firm and its counsel.
Can a post go out if nobody at the firm reviews it?
No. Drafts sit in the queue until someone approves them. If the queue is not reviewed, nothing publishes. That is deliberate: for a firm, silence is a much better failure mode than an unreviewed post appearing on a public account during a busy week.
Who at the firm should approve social media posts?
Most firms use whoever already reads public-facing material, typically a managing partner or a designated marketing supervisor. The useful addition is naming a backup with the same authority, so a trial week does not stop the queue. Your firm's own policies should drive this decision rather than a general guide.
Is there a record of who approved each post?
The queue retains the approved text and the account that approved it, which firms use as internal documentation of their own process. That is a description of how the workflow behaves, not a claim about meeting any retention or supervision requirement. Confirm your firm's needs with your compliance officer.
What should we do about comments on our posts?
Decide the policy before you publish rather than in the moment. The common approach is to acknowledge publicly and move anything involving a specific person's situation to a private channel or a call. Assign someone to monitor, even briefly each day, and give them one prepared reply to use consistently.
Is anything on this page legal or compliance advice?
No. It is general information about how an approval workflow operates. It is not legal or compliance advice and does not describe any obligation that applies to you. For what your firm can and should publish, consult your own compliance officer or counsel, who knows your practice areas and your existing policies.
See what Bolta would write for your firm
Bolta’s agents research, draft and schedule posts. Nothing reaches a public account until a person on your side approves it. Paid plans start at $19/month, and there is a free Starter tier.
Last updated: 2026-07-27