How an Information Barrier Works in a Live Transaction

An information barrier is an arrangement that keeps information about a live transaction away from the people in the same organisation who trade, advise or decide on the same names. The barrier runs on three layers at once: systems access, physical separation, and recorded behaviour, including a wall-crossing procedure. A barrier exists so the rest of the business can carry on working while the transaction runs.

The situation comes before the definition. A definition only makes sense once the problem it was built for is visible. Somewhere inside an organisation, a small group of people are working on a purchase that has not been announced. In the same organisation, and often on the same floor, other people are doing entirely ordinary work: selling to customers the target also sells to, advising clients, making decisions about the company's own shares and its own disclosures. Neither group is doing anything improper. The difficulty is that the first group is holding something the second group must not receive, and the second group cannot simply be sent home until the transaction is over.

Here is the everyday version, and it is closer than it looks. One person in a household knows that a large surprise is coming: a gift has been bought, the money has gone out, arrangements have been made with two relatives. Everybody else in the household carries on entirely as normal, and that is the whole point of the arrangement. The wrapping paper lives in a cupboard nobody has a reason to open. The receipt is not left on the kitchen table. The surprise is not protected by shutting the household down, so nobody in the household is asked to stop cooking, stop talking or stop spending. The surprise is protected by putting one thing in one place and being careful about the two or three routes by which it could accidentally come out. An information barrierAn arrangement inside one organisation that keeps information about a live transaction reaching only the people working on it, while everyone else carries on normally. is that same idea, run deliberately, written down, and tested.

Harivansh Packaging Limited, an invented manufacturer, is listed on both Indian exchanges and makes rigid and flexible packaging for food and personal care customers. Harivansh Packaging has agreed to buy all of Sundarban Polymers Private Limited, an unlisted maker of flexible packaging films that sells to some of the same customers. Devyani Kulkarni is the chief financial officer of Harivansh Packaging Limited. Ashwin Rege leads the transaction team. The advisers on both sides act for the buyer and for the seller. Every figure that follows belongs to this one purchase.

Two earlier subjects carry straight into this one. Materiality settled which information about a transaction cannot be shared, and it settled why a list of the people who hold that information exists at all. The transaction team settled who is inside the work and how somebody gets added to it. A barrier settles neither of those questions. A barrier is the control that keeps the information with the team while everybody else keeps working.

One warning comes before the mechanism, and it is easier to hear at the start than at the end. A barrier decides who holds information. A barrier does not decide what a person who holds it is allowed to do. Holding and doing are two different questions with two different answers from two different places, and being on the correct side of a barrier settles the first one and nothing at all about the second.

What is an information barrier actually for?

Ask what the organisation would have to do if the barrier did not exist, and the purpose stops being abstract immediately. On this transaction, twenty two weeks ran from term sheet to completion, of which the conditions period alone was nine. The twenty two weeks belong to this purchase alone, and another transaction with different conditions to satisfy would run to a different length. But hold the number for a moment as a length of time. For twenty two weeks, Harivansh Packaging Limited has to keep making packaging, keep invoicing customers, keep talking to the people who buy from it, and keep making its own ordinary disclosures on schedule. If protecting the transaction meant freezing all of that, the protection would cost more than the transaction is worth, every time.

So a barrier is not secrecy for its own sake. A barrier is what lets the rest of the business keep operating rather than stop every time a transaction starts. Reframing the barrier that way changes what a good barrier looks like. A barrier that is so restrictive that the commercial team cannot answer a customer's question has not succeeded quietly, it has failed expensively, and it will be worked around within a week by people who have deliveries to make. The design target is a small, well defined inside, and an outside that notices nothing.

Look at who is on each side on this purchase. Inside are Devyani Kulkarni, Ashwin Rege and the transaction team, the workstream owners who are actually reading the diligence material, and the external advisers to both sides. Outside are the people running the packaging plants, the people who deal with the customers that both Harivansh Packaging and Sundarban Polymers sell to, and anybody handling the company's regular disclosures. The disclosure people are worth pausing on. The instinct is to assume that finance and disclosure must all be inside the barrier. They are not, and they should not be. Disclosure work carries on to its own calendar throughout, and the fewer people who hold the transaction, the more truthfully that ordinary work can be done.

The principle that decides the boundary is need to knowThe test that a person is given information only where their actual task cannot be done without it, rather than because of seniority, interest or convenience., and it is a harsher test than it sounds. Need to know does not mean would find it useful, would be interested, is senior enough, or will be annoyed to find out later. Need to know means this person's task cannot be completed without this information. Seniority is the most common way the test gets quietly abandoned. Somebody very senior is told because it seemed awkward not to tell them, and now the inside is larger by one person who has no task inside it. Every addition of that kind makes the barrier weaker without making the work any faster.

Notice the two claims the picture is not making. The picture does not say the outside group is less trusted, and several of them are more senior than several people on the inside. The picture does not say the outside group is being protected from temptation, though that is a real benefit. The picture says something narrower and more useful: the outside group has work to do that does not require this information, so they do not receive it, and because they do not receive it their work can continue without a single change. The measure of a barrier is not how much it stops, it is how little the outside has to change.

Why does a barrier run on three layers rather than one?

Because information does not have one route out. It has three, and they are genuinely different from one another, so a control that closes one of them does nothing at all about the other two.

The first route is a file. Something is saved, attached, forwarded, copied or shared, and it moves as data. The second route is a page. Something is printed, carried, left on a desk, put in a bin or picked up from a tray, and it moves as paper. The third route is a sentence. Somebody says it, in a lift, on a call taken in an open area, at a client dinner, or to a colleague who asked a friendly question. A permission setting has no view on what somebody says out loud, and a well run meeting room has no view on who can open a folder. Each route therefore needs a different kind of control.

The three layers come from those three routes. The systems layerThe part of a barrier made of access rights: who can open which folder, drive or mailbox, and who cannot. covers the file. Physical separationThe part of a barrier made of rooms, printers, screens and desks: where material is worked on and where paper is allowed to go. covers the page. The behaviour layer, whose central mechanism is wall-crossing, covers the sentence and the decision to bring somebody in. There are three layers because there are three routes, and a gap in the layer that covers one route lets the material out no matter how well the other two are built.

Three separate routes are why an organisation that has spent heavily on one layer can still be badly exposed. Access rights can be bought, configured and reported on, so access rights get the attention. Paper and speech are the layers that get a paragraph in a policy. The material does not know which layer had the budget.

What does the systems layer actually control?

The systems layer is the plainest of the three and the easiest to state: everything about the transaction lives in one place, and the permissionsThe settings that decide which named people can open, edit or copy a folder, drive or mailbox. A permission is granted to a person, not to a document. on that place name the people inside the barrier and nobody else. One drive, one folder structure, one distribution list, granted by name. Everything else follows from that single design decision, including the ability to answer the question the barrier exists to answer: who holds this.

Two details do most of the work and both are unglamorous. The first is that permission is granted to a named person rather than to a group. A group is a moving object: people join it, leave it and get added to it for reasons that have nothing to do with this transaction, and the moment transaction material sits behind a group permission, the inside of the barrier changes shape without anybody deciding that it should. The second is that copying out of the place is blocked rather than discouraged. A folder that can be copied elsewhere is a folder whose permissions are advisory, and advisory permissions are not a control, they are a preference.

Then there is the codenameA neutral name given to a transaction so that the target and the acquirer are not identified in ordinary traffic such as calendar entries, file names and subject lines.. A codename exists for a specific and slightly odd reason. Most information about a transaction leaks through the containers rather than the contents. Nobody reads a seventy sheet diligence pack over a holder's shoulder in a lift. People read the title of the meeting in a calendar, the name of the file on a screen, the subject line of the message on a phone, the header printed on the sheet in the tray. So this transaction is called Project Kadamba, and every one of those containers should say Project Kadamba and nothing else.

A codename works only if it is used in every place a name could appear, and the place where it is forgotten is almost always the place nobody inspects. Calendar entries get the codename because somebody set that rule on day one and everyone remembers it. File names are set by whoever saves the file, at speed, at the end of a long day, and a working spreadsheet saved as the target's own name has quietly undone the entire arrangement. Nothing was leaked. The file simply announces the target to anybody who can see a file list, including anybody who receives it later by accident, and file lists are seen constantly by people who never open a single document.

Why does the oldest layer fail in the most ordinary way?

The physical layer looks quaint next to access rights. The layer is rooms, printers, screens and desks, and it can be described without a single technical word: work on the transaction happens in one room, that room has its own printer, screens face away from walkways, and paper does not sit on a desk overnight. There is no configuration to admire and nothing to report on. The physical layer also fails in the most ordinary way. A document that reaches an open printer has defeated a perfectly configured drive without anybody doing anything wrong at all.

The sequence is completely undramatic. A workstream owner is inside the barrier, has correct access, opens the correct file from the correct drive, and needs to read forty printed sheets properly rather than read them on a screen. They press print. That default was set when they joined and has never been changed, so the default printer is the one nearest their usual desk, in an open area. Forty printed sheets, carrying the printed header, come out in a tray that anybody walking past can reach. Every single step was taken by an authorised person acting reasonably. The material is now on paper in a place with no access list at all.

The corridor and the lift belong to the same layer and behave the same way. A conversation between two people who are both inside the barrier is a perfectly proper conversation, and it becomes a leak purely because of where it happened. The physical layer is described in terms of places rather than rules for that reason: saying the transaction is discussed in these two rooms and nowhere else is far more effective than instructing people to be careful what they say in the lift. The first is a boundary a person can hold in their head. The second is an instruction to remain permanently vigilant, and no one manages that for twenty two weeks.

What is wall-crossing, and why is it recorded?

The third layer is behaviour, and its central mechanism is the one moment when the barrier is deliberately opened. Wall-crossingBringing somebody from outside a barrier inside it on purpose, so that they can help with the transaction, with the decision and the date written down. is what happens when the transaction needs somebody who is currently outside. Not somebody who wandered in, not somebody who guessed, not somebody who was told by a colleague being helpful. Somebody who is brought across on purpose, by a person with the authority to decide it, with a record made.

A crossing has four elements and all four are required. First, a named approver decides. Not the team collectively and not the person who happens to need the help. A decision that anybody can make is a decision nobody is accountable for, and the size of the inside will then grow every week. Second, the date and the reason are recorded. Somebody will later ask who held this and from when, and a barrier that cannot answer from when has only half an answer. Third, the person is told plainly what they now hold and what it means for them. Fourth, they go on the list of the people holding the information, settled earlier in this sequence and simply updated here.

The third element is the one that gets skipped, and it is the one that protects the person rather than the transaction. The other three protect the organisation: they produce a decision, a record and a list. The third is the only one that exists for the individual being crossed. Somebody who is told the deal in a corridor as a favour has been handed a restriction they did not ask for and were never told about, and they may take an entirely ordinary decision afterwards without knowing that anything about their position has changed. Telling somebody plainly is not a courtesy at the end of the process. Being told plainly is the point at which somebody becomes able to act sensibly at all.

There is one more thing a recorded crossing does that is easy to miss. A recorded crossing makes the inside of the barrier a knowable set at every date, rather than a rough idea. Ask on any given morning who was inside on the fourteenth, and an organisation with recorded crossings can answer in a minute. An organisation without them can only say roughly the team, plus whoever else was pulled in, and the second answer is not an answer to anything.

How does a restricted list differ from the list of people who hold the information?

Two documents get confused constantly, and the confusion is not careless. Both are created at the same time by the same people for the same transaction. The two still answer completely different questions.

A restricted listA list of the securities on which activity is restricted while a transaction is live. It names companies and instruments, not individuals. names securities. A restricted list answers which names activity is restricted on, and its entries are companies and instruments. The list of the people holding the information names individuals. That list answers who is holding this and from when, and its entries are people and dates. One is a list of what. The other is a list of who. The two answer different questions, so a single document that tried to be both would be either circulated too widely to be safe or too narrow to be useful.

Keeping them apart is not a stylistic preference. The restricted list has to reach everybody whose activity it restricts, a large group, many of whom know nothing about any transaction and should be told nothing. The design is deliberate: a person can be told this name is restricted without being told why, and the restriction works perfectly well without the reason. The list of holders is the opposite. The holders list is the record of exactly who is inside, and every additional person who reads it is another person who now knows the shape of the transaction. Merging them means either circulating the names of the holders to a large group, or keeping the restricted list so tight that the people it was meant to restrict never see it.

There is a second reason to keep them apart, and it is about time. The two documents change on different days. The restricted list changes when the transaction reaches a stage where restriction is warranted and when it ends. The list of holders changes every time somebody is crossed, and on this purchase that happened repeatedly across the twenty two weeks. A document that has to be reissued to a wide group every time one person is added will not be reissued, and within a month it will be wrong.

Where do barriers actually fail?

Not where the policy expects. The picture in most policies is of a person who wants the information and goes looking for it. The failures that actually happen are made by people who were trying to get their work done and took the path the environment offered them.

Here is the list, and every item on it is boring on purpose. A shared drive whose permissions were set once at the start and never reviewed against the team as it changed. A printer in an open area, reached by a default nobody chose. A calendar entry carrying the real name because it was created before the codename was agreed and never renamed. A distribution list that includes an assistant who was added years ago for an unrelated reason. A conversation in a lift between two people who are both properly inside. A leaver whose access was never removed, given that leaving a team is a slower administrative event than joining one. A laptop screen on a train.

Every one of these is a design failure rather than a discipline failure, and the fix is to design the environment so the mistake is harder rather than to ask people to be more careful. The distinction is worth defending, and the instinct after an incident is always to issue a reminder instead. Reminders decay. A default printer that points into the transaction room does not decay. Copying that is blocked rather than discouraged does not decay. A monthly comparison of the access list against the current team does not decay either. The comparison is an event on somebody's calendar rather than a state of mind.

The household version is exact. Where people are repeatedly told to remember to lock the front door, some evening it stays open. Where a lock is fitted that engages when the door closes, the problem disappears and nobody had to become a better person. Barriers are built the same way: reduce the number of moments where a person has to choose correctly. Over twenty two weeks a person will face that moment several hundred times.

What does a barrier not do?

The limit of a barrier is the part that gets softened, so read it slowly. A barrier controls who holds information. Controlling who holds information is the barrier's entire function, and a barrier performs it well. A barrier does not decide what a person who holds the information may then lawfully do, it does not make a transaction anybody's business, and it is not a defence for anything.

The confusion is easy to fall into because both questions arrive in the same conversation. Somebody is crossed over the barrier on a Tuesday, and by Tuesday afternoon they are asking two questions at once: am I allowed to be in this room, and what does this mean for the shares I hold. The first is an internal question and the barrier answers it completely. The second is a question about unpublished information and what may be done while holding it. The second question is settled by the Securities and Exchange Board of India (SEBI) at sebi.gov.in and not by any internal arrangement, and being on the correct side of a barrier answers none of it.

Notice how the two questions can come apart in both directions. Somebody may be entirely correctly inside the barrier, approved, recorded and told, and still face a restriction that has nothing to do with the barrier and everything to do with what they now hold. Equally, somebody may never have been crossed at all, and have picked something up by accident from a printer tray, and the fact that no approver ever named them changes nothing about their position. The barrier is a record of intention. A barrier is not a status that travels with a person into a different question.

A barrier is practice that an organisation chooses to build, not a requirement anybody sets. Requirements about unpublished information and about what an intermediary or a listed company must maintain are set and published elsewhere. Those sources settle what must be done, as against what is sensibly done.

How is the barrier built on this particular transaction?

A mechanism described in general is easy to agree with and hard to use, so now put the three layers on the actual purchase. Harivansh Packaging Limited is listed, and its shares trade at an assumed Rs 300/- across 18.00 crore shares, giving an assumed market capitalisation of Rs 5,400 crore. Both figures are assumed, and a real market price would move the capitalisation in proportion. The shares trading is the single fact that makes a barrier necessary here rather than merely tidy. An unannounced agreement to buy Sundarban Polymers Private Limited is something the market does not have.

Now the case that arises in practice, the one that makes wall-crossing necessary rather than theoretical. The commercial workstream has to understand the customers that Harivansh Packaging and Sundarban Polymers both sell to. The shared customers are a real diligence question with a real answer, and the person who knows those customers properly sits outside the barrier, in the commercial team, and has been dealing with them for years. There is no clever way around this. The work needs them.

So they are crossed, and here is what it looks like done properly. Ashwin Rege is not the approver simply because he needs the help. A named approver decides, and on this transaction the approver is Devyani Kulkarni. The date is written down, and so is the reason, the shared customer analysis and nothing broader. The person is sat down and told plainly: there is an unannounced transaction, they now hold information about it, what that means for them, and who to ask if they are unsure. And their name goes on the list of the people holding the information, with that date beside it. Four steps, one afternoon, and the barrier is now a smaller, knowable set rather than a rough idea with an exception in it.

Then there is the figure that makes the restricted list necessary, and it is not a figure about the target at all. Work the funding of this purchase.

The two totals say different things, so read them carefully. The Rs 1,140 crore is what the sellers of Sundarban Polymers Private Limited receive, and it is the enterprise value of Rs 1,320 crore less Sundarban Polymers' own net debt of Rs 180 crore. The Rs 1,140 crore is a fact about the target. The second total is a fact about the acquirer: Rs 740 crore of borrowings becomes Rs 1,740 crore, 2.35 times where it started. The Rs 1,740 crore sits on the balance sheet of the listed company itself, and that is why the restriction attaches to the securities of Harivansh Packaging Limited and not only to something happening at an unlisted target.

The listed acquirer is the practical reason the restricted list names securities. Somebody maintaining the list does not need to know that Sundarban Polymers exists. They need to know that activity on the Harivansh Packaging name is restricted, and the reason can stay entirely inside the barrier where it belongs. The two documents work together precisely because they were not merged.

How would anyone know whether a barrier works?

By testing it, and the reason this block exists at all is that almost nobody does. A barrier is written down at the start of a transaction, everybody agrees with it, and then it is never checked again until something goes wrong, at which point what is discovered is that it stopped describing reality in week four. An untested barrier is a diagram, and the test costs a morning while the failure does not.

Three tests do most of the work, and none of them needs a specialist.

The second of those is an access reviewA scheduled comparison of who currently has access to transaction material against who is supposed to have it, done name by name., and its value comes entirely from being scheduled. A review that happens when somebody remembers is a review that happens once. The third is the neglected half and deserves a sentence of its own: joining a barrier is an urgent event that somebody chases, and leaving one is an administrative event that nobody chases, so an inside that only ever grows is the normal state of an unreviewed transaction.

The first test is the interesting one, and it is worth being precise about what a barrier testA deliberate attempt, by an authorised person outside the barrier, to reach transaction material, run to find out what is actually reachable. is for. A barrier test is not a trap for the person doing the reaching, who is authorised and is doing it on purpose. It is a check on the environment. If they find nothing, the systems layer is doing what the diagram claims. If they find a copy of a folder in a group location, the organisation has learned something that no policy document would ever have told it, and has learned it on a quiet Tuesday rather than after an announcement.

How does a lender, an analyst or a household read this?

Three different readers use the same idea for three different purposes, and none of them is reading it as a compliance document.

A lender being asked to fund the Rs 1,000 crore reads the barrier as evidence about the borrower's control of its own information. Control of information is a proxy for something the lender genuinely cares about: whether this company can run a process without surprises. A lender is going to be inside a small group holding an unannounced fact for weeks. The question they are quietly asking is whether the borrower's arrangements are good enough that the lender's own position does not become awkward. A borrower who cannot say who holds the transaction has just answered that question badly, before any credit work has started.

An analyst covering the packaging sector reads it from the outside, and mostly reads its absence. An analyst notices that a company's people became slightly unavailable, that a scheduled meeting moved, that a name they cover has been quiet. None of that is information and none of it is actionable. A well built barrier is precisely what keeps it that way, and the whole design is that the outside of the company continues to behave exactly as it did. The visible sign of a barrier working is that there is nothing to see.

An investor already holding the shares reads it as a fairness question, and it is the sharpest of the three. An investor cannot verify a barrier and will never see one. An investor can reasonably expect that the company's arrangements are built so that the information reaches the market before it reaches anybody's dealing screen. A barrier is one of the few internal controls whose entire purpose is to protect people the company will never meet.

And the household reader, who is not on a transaction at all, still meets this mechanism. Anybody who has handled a household matter that involves money and relatives has run a barrier by instinct: the discussion happens in one room, the papers stay in one drawer, and one person decides who gets told and when. Where it goes wrong at home is exactly where it goes wrong at work. Somebody is told in passing and never told what it means, and then acts on it entirely reasonably, having never been given the third step.