How do ESOP companies share operating performance with employee-owners?

Keep operating performance separate from plan information.

Employee-owners hear about two kinds of numbers. One is plan information: account balances, share value, vesting, and distributions, which come from the plan administrator, the valuation firm, and the trustee. The other is operating performance: jobs, orders, margins, backlog, and service levels, which come from the company’s systems every working shift. This guide is about the second kind, the numbers people can see and act on in their work.

Keeping the two apart avoids confusion and avoids promises nobody should make. A dashboard that tries to estimate share value from monthly results invites questions that only the valuation advisor can answer, and it can mislead people about their accounts. Plan statements and plan communications belong with the administrator and the company’s legal and tax advisors, who understand the rules that apply to them.

What operating software can do is make the underlying business visible and give finance clean records to hand the plan’s advisors when they ask. When employee-owners understand how jobs, branches, and the company are performing, the link between daily work and the value of the business becomes easier to see, without anyone presenting a number that belongs in a plan statement.

Choose a few measures employee-owners can influence.

The most common mistake is sharing too much. A full income statement means little to a crew lead or a warehouse picker, and a long list of indicators teaches people to ignore all of them. Start instead with a small set of measures that people at different levels can actually move through their decisions: job margin, backlog, utilization, on-time delivery, rework, safety incidents, or time to invoice.

Each measure should come with a plain definition written for someone outside finance. Say what the number counts, where it comes from, how often it updates, and what a good result looks like. A short sentence such as margin is what is left from the job’s billings after labor, materials, and subcontractors does more for understanding than any chart design.

Involve people from the field and the branches in choosing the measures. They know which numbers reflect their work and which ones depend on decisions made elsewhere. A measure that a crew cannot influence tends to feel like a judgment rather than information, while one they can move gives them a reason to look at the scorecard and talk about it with their manager.

Show each measure at the level where people work.

Company totals are too distant for most people. A project manager wants to see the projects they run, a branch manager wants the branch compared with plan and with its peers, and leadership wants the company picture with the ability to drill into any branch or job. The same measure, defined the same way, should be available at each of those levels.

Role-based views make that practical. A crew or a site team sees its jobs, a manager sees the branch or division, and leadership and the board see the whole company. Every figure should link to the records behind it, so a person who questions a number can see the jobs, invoices, or orders that produced it instead of waiting for finance to explain it.

Decide deliberately what stays restricted. Individual pay, personnel matters, customer pricing, and some contract terms are usually not suitable for company-wide views, even in a culture that values openness. Write these rules down with leadership, apply them by role and location in the software, and log exports, so openness about performance does not turn into exposure of sensitive records.

Build the numbers from shared records with agreed definitions.

Performance figures lose credibility when they are assembled by hand for each meeting. Different branches may calculate margin or backlog differently, a spreadsheet may carry an old formula, and nobody can trace a figure back to its source. Employee-owners notice when the number in the meeting does not match what they see in their jobs, and trust in every later report suffers.

The steadier approach is to connect the ERP, project accounting, and field systems to a shared reporting layer and calculate each measure once, from those records, using definitions finance and operations have agreed in writing. Branch tools and spreadsheets that hold important data are either connected or replaced over time, so every view draws on the same source.

The same records can then serve several audiences. Crews and managers see scorecards, leadership sees the company view, the board sees an operating pack, and finance can prepare the operating extracts the plan’s administrator and valuation advisor request. When those groups all look at numbers built the same way, conversations focus on the business rather than on reconciling different versions of it.

Pair the numbers with regular conversation and a named person for each measure.

A scorecard by itself changes little. Companies that make shared performance useful tie it to a routine: a short review at the start of each job meeting, a regular branch conversation, and company results explained at an all-hands meeting with time for questions. Managers need a little coaching in how to read the measures with their teams and how to talk about a result that falls short.

Give each measure a named person responsible for its definition and its data. When a figure looks wrong, people should know whom to ask, and the answer should lead to a fix in the source records rather than an adjustment in a spreadsheet. Keep a simple log of definition changes, so a trend that shifts because the calculation changed is not mistaken for a change in performance.

If your company wants employee-owners to see job and branch performance from records they can trust, Baybloom can map the systems involved, agree on the measures and access rules with leadership and finance, and scope a first release around one scorecard. Plan administration and valuation stay with the plan’s advisors, and each later phase is scoped and priced separately.

Put it into practice

Talk through the project you are considering.

Bring the workflow, the systems around it, and the questions you need to resolve. We can help define a useful next step.