The information was never hidden. It simply had no governed route from the person who noticed it to the person who could act.
At the quarterly close, the CFO stops on a single line: an inventory variance nobody can explain.
Tracing it takes eleven days.
The answer, when it arrives, is infuriatingly simple. The barcode scanner at bay three double-counts some parcels. A known fault. A specific fault. A two-hour fix.
Then comes the question that ruins the rest of the meeting. How long?
Six weeks. And eleven people on the warehouse floor knew. Not one, not two. Eleven. They knew in week one, they talked about it among themselves, and they built a manual workaround for it.
It was never a secret. It was information sitting one floor away from the person who could have ended it in two hours.
01Nobody hid anything
Before you land on "culture of silence," trace what actually happened.
In week one, a floor worker told his supervisor. The supervisor was dealing with a late truck and said he'd look into it. He did look into it, three days later, and mentioned it to the shift lead in a corridor between two meetings. The shift lead meant to put it in his weekly report, and then the report filled up with something more urgent.
Three genuine attempts to report. Three good intentions. Zero written trace.
That isn't silence. That's information that tried to climb three times and found nothing to carry it.
And the distinction isn't semantic. If the problem is culture, the fix is a memo and a workshop. If the problem is a channel, the fix is infrastructure.
Here it was a channel. The information moved verbally, and verbal dies at the first interruption.
02The direction nobody designs for
Almost everything you've built for internal communication travels downward. Announcements, policies, management updates, leadership messages. Downward tooling is mature, polished, and measured.
Upward gets left to three things: an open door, a suggestion box, and hope.
The trouble is that the value of information isn't split evenly between the two directions. Downward information tells people what you decided, which you already know. Upward information tells you what you don't know. And it's the only thing that can stop an inventory variance from becoming a line item at quarterly close.
When the upward channel closes, the information doesn't disappear. It turns into something else: a manual workaround, an abrupt resignation, a post on a jobs site, or a number in a financial report six weeks later.
03Three reasons a report never climbs
One: there's no address.
The floor worker doesn't know where to send a note about faulty equipment. He knows his supervisor, so the supervisor becomes the only bottleneck. And the capacity of that bottleneck equals how busy one person is on one day.
In Tawasol, every type of report gets an address. Subjects are defined in advance as categories, and the employee picks one from a dropdown when submitting, so the report routes correctly instead of routing to the nearest available human. It lands in a central inbox in the dashboard, with its category and its location in the top bar. Whoever opens it knows what it is and where it came from before reading a line.
The bottleneck disappears, because the report no longer has to pass through anyone.
Two: the report arrives without evidence.
"The scanner at bay three acts strangely sometimes" is a hard sentence to act on. The person receiving it can only ask about it, and asking takes two days.
In Tawasol, a report is submitted from the phone with photos, video, and GPS location metadata attached. It arrives with what proves it and what locates it. The screen registering the double count is attached. The bay is identified by coordinates, not by description. The recipient starts working in the first minute instead of starting an investigation.
Three: a name is sometimes expensive.
Some of what you need to know will never be said with a name on it. A note on the safety of a procedure. On the conduct of a manager. On a practice everyone knows exists and nobody wants to be first to say out loud.
In Tawasol, an employee can submit without a name using the anonymous option, and can send private feedback directly to management. You're not opening a door to chaos. You're opening a door to information that would otherwise have stayed entirely outside your view.
An anonymous report in week one beats a signed report in week six. And it beats the one that never comes by a much wider margin.
Before you read on, run this yourself. Write down the last five operational problems that cost you money this year. Next to each, write two dates: when it actually started, and when you found out. You won't need a report or a consultant; the team knows the first date and will give it to you in one meeting. The distance between those dates, multiplied by five, is the cost of your broken upward channel, in your own numbers. Nobody can argue with that figure, because you produced it.
04The part that decides whether anyone reports again
This is where most reporting systems fail, and the failure happens after the report is received, not before.
The worker who reported in week one never heard anything back. Not a rejection, not an acceptance, not a question. From where he stood, his report vanished.
When the next report-worthy thing happened, he didn't report it. That wasn't insubordination. It was a reasonable inference from experience.
In Tawasol, the conversation is a thread with a state. The responsible person replies inside the thread, attaches reports or images as needed, and closes it when the matter is resolved, moving it from active to closed. Two results: a clean workspace for whoever handles incoming reports, and a record of what came in and what got done.
The more important effect doesn't show on the dashboard. It shows in the behaviour of the person who reported and watched it land and close. That person reports again. And people who report again are your entire early-warning capability.
05The signals that arrive before a report does
Not all upward information arrives as a report. Some of it arrives much earlier, if you're looking.
When a management message goes out through the app, recipients can comment and react positively or negatively. The dashboard shows who reacted, how, and when, along with the full comments and the names attached to them. It also shows who viewed the message, and which unit each viewer belongs to.
That isn't a popularity measurement. It's a radar.
An announcement drawing negative reaction concentrated in one unit is telling you something in that unit isn't working — before it reaches you as resignations or missed deliveries. And an entire unit where nobody opened it is telling you something else, possibly worse.
When you don't want to wait, ask. Surveys go out as a message type and collect employee feedback in documented form. Urgent alerts go out with receipt and read tracking, so you know who actually got the instruction rather than who was supposed to.
The difference between an organisation that finds out early and one that finds out at close isn't a difference in management intelligence. It's a difference in how many points exist where information touches a visible surface.
06Replay the six weeks
Take what happened, and put all of this in place.
On day three, the worker opens the app, selects the subject "equipment faults," photographs the screen registering the parcel twice, and submits. The report carries its category and location, so it reaches maintenance rather than a supervisor occupied with a late truck.
On day four a technician replies inside the same thread asking for confirmation, and gets a second photo. On day five the scanner is fixed in two hours and the thread is closed.
No variance. No eleven days of tracing. No line item stopping a quarterly close.
And eleven people on the warehouse floor learned something they'll use next time: reporting here produces a result.
The problem wasn't solved because someone became more attentive. It was solved because the information found a route upward that didn't run through anyone's memory or anyone's calendar.
07What your team knows right now, and you don't
At this moment, while you're reading, there's something twelve people in your organisation know and you don't.
That's not an accusation. It's a description of how information behaves in any structure bigger than twenty people. The only question that matters is how many weeks it stays that way, and what it costs when it finally surfaces.
The CFO in that meeting wasn't short on competence. He was short six weeks.
Send us the escalation path for one department — who reports to whom, through what medium, and what gets documented — and we'll return it as a written Upward Reporting Diagnostic: the exact point where a report dies, why it dies there, and the practical alternative at each point. A document you can read out in your next operations meeting, not a slide deck. Send it to contactus@tawasolapp.com with "Upward Reporting Diagnostic" in the subject line.
Tawasol. Your team, connected.