How to Map a Listed-Company Disclosure Requirement

A disclosure map is one internal table listing every kind of event that can put a listed company under a duty to tell the market something, with five things against each: what triggers it, where it goes, the role that signs it off, where the timing is stated, and when that source was last read. The map is built once, in nine steps, and then kept current.

The moment a disclosure duty starts running is the worst possible moment to be finding out what it asks for. Somebody is on the phone, somebody else wants to know whether this is even a thing that gets told to anybody, and the one person who knows where the answer is written is on a train. A disclosure mapA written table of every disclosure duty a company carries, with the trigger, the route, the approver and the source set against each one. exists to take that moment apart in advance. Every step in this procedure moves one part of the work out of the moment of the event and into a calmer week. On the day, the only thing still open is the judgement.

A company listed in India points its rows at Indian addresses, and the map that holds those rows is an internal working document. Nobody outside the company obliges it to exist in any particular shape. The shape is worth being careful about all the same, and the design decisions in steps four, five and seven are what separate a map that stays true from one that ages into a liability.

Vindhya Ceramics Private Limited, an invented ceramics manufacturer, is one year past its listing. Prerna Wadekar is its company secretary and compliance officer, and the map is hers to build and keep. In that first year Vindhya Ceramics Private Limited made 31 disclosures: 25 of them periodic and 6 of them events that arrived without warning. Her map runs to 19 rows, one for each kind of event that could put the company under a disclosure duty.

Nine steps follow, in order. A copied figure goes stale in exactly the way a badly built map does, so requirements, periods, thresholds and deadlines are read at the source rather than carried in a procedure. Every step instead points at where those things are read, and that single habit is what the whole procedure is built around.

Step one: which events could put this company under a disclosure duty?

Take a blank sheet and list every kind of thing that could happen to Vindhya Ceramics Private Limited and start a disclosure duty running. Work from three places and only three: the requirement set itself, opened at the source rather than recalled; the company's own board papers and minutes from the last year; and the things that happen specifically in this trade, the ones nobody outside it will list. Write kinds of event, never instances. Not the kiln order from one named buyer, but a customer contract ending. Do not sort the list, do not rank it, do not drop a kind because it seems unlikely, and do not stop at the ones that already happened. One line each, and then put the pen down. Step one produces rows and nothing else, and every step after it adds one column to those rows.

Prerna Wadekar's list came to 19 kinds of event. In the year that followed, 12 of the 19 fired at least once and 7 never fired at all. The 7 were not wasted work. A row for something that has not happened yet is the only reason anybody will know what to do the first time it does, and by definition the first time is the occasion when nobody has a memory to fall back on. The same logic appears on the laminated sheet inside a lift, the one naming what to do if the lift stops between floors. Almost nobody who reads the lift notice has ever been stuck in a lift. The notice is printed for the one person who will be.

Step two: what goes in the trigger column, and in whose words?

Against each row, write the triggerThe thing whose occurrence starts a duty running. in the words the requirement itself uses, copied rather than summarised, with the place it was copied from beside it. Then, on a second line in the same cell, write what the trigger would look like if it happened at this company, in the company's own vocabulary. A person in the sales office should recognise that second line. Two lines per row, both of them short. Do not add a note about how likely the trigger is, do not write what the trigger seems to be getting at, and do not merge two rows because their triggers look similar. A paraphrase records what one person understood on the day it was written, and six months later nobody can tell the paraphrase from the source, so it is the paraphrase they act on.

Work it through on the row for a customer contract ending at Vindhya Ceramics Private Limited. Line one of that cell holds the requirement's own wording, copied, with the address it came from. Line two holds the local translation: a ceramics supply agreement of the kind this row covers comes to an end, is terminated by either side, or reaches its date and is not renewed. Now the person in sales who hears that a buyer is not renewing has a sentence to recognise, and Prerna Wadekar has a sentence that still matches the source when somebody checks it against the source a year later.

The second line is something a household already does without calling it a step. When a household writes down what the electrician actually said, in the electrician's words, and then writes underneath what that means for the kitchen, the two versions do different jobs. The first survives an argument. The second is the one anybody can act on.

Step three: what route does each disclosure travel, and where is that written?

For every row, record the routeThe defined path by which a disclosure reaches the market, including who it goes to and through which channel.: who the disclosure goes to, through which filing channel, in what form, and where that is set out. Take it from the source and write the address it was taken from in the same cell. Where a row travels two routes, write both and write which one goes first. On the day, a person following the row needs an order, not a set. Where a route cannot be established yet, do not leave the cell empty. Write that the route is not established, put the date on it, and put the row on the list of things to close out. An empty cell reads as nothing to do. A dated gap reads as somebody has to do this. The distance between those two readings is the distance between a hole in the map and a hidden hole in the map.

Of Prerna Wadekar's 19 rows, 17 had their route established in the first sitting. The other 2 needed a call to the exchange's listing desk before anything could go in the cell, and both carried a dated note saying the route was not established until that call was made. Seventeen plus two is nineteen, and the two open cells were visible to anybody who opened the file. Being visible is the whole reason they were written that way.

Step four: who approves each disclosure, and how is that approver named?

Against every row, write who signs the disclosure off before it leaves the building, and name that approverThe role that signs a disclosure before it goes out. by the role rather than by the person holding it. Where two approvals are needed, write both and the order they happen in. Where the approver is a body rather than an individual, write the body. Then keep one short separate sheet, away from the map, saying which human currently sits in each role, and keep that sheet current when people move. A role survives a resignation and a name does not. The approver column therefore carries the role, and the staffing sheet carries the person.

On Prerna Wadekar's 19 rows the approver column reads: the compliance officer on 11 rows, the finance director on 5, and the board on 3. Eleven plus five plus three is nineteen. Had she written people instead, 16 of the 19 rows would have carried somebody's name, and the morning the compliance officer resigned, 11 rows would have been wrong at once with nothing on the map to say so. Ratnakar Deshpande, the finance director, would still be right on his 5 until the day he was not.

Schools worked this out long ago. The form that says contact the class teacher keeps working through every transfer and every maternity leave. The form that names one teacher stops working the first September after she moves, and it stops working silently. A name on a form does not announce that it has expired.

Step five: how does the timing get onto the map without a deadline being typed in?

The timing column holds a pointerA reference to where a figure is stated, recorded in place of the figure itself., never a figure. Against each row write three things and stop: the name of the requirement that states the period, the address it is read at, and the date somebody last read it there. Do not write the period. Do not write a number of hours or days. Do not write immediately, or same day, or by the next morning. Each of those is a period wearing a word. If a draft of the map already has a period typed into a cell, delete the period and put the pointer in its place. The timing column names the requirement and the date it was read, never the deadline itself. No single design decision does more to keep a map honest.

Here is why this cell and no other. Think about how each column fails when it is wrong. A wrong route bounces, because the filing does not land where it was sent. A wrong approver corrects itself, because the person who should have approved it says so. A missing row announces itself the day the event happens and nobody can find it. Every one of those failures is loud. A wrong period is the only one that is silent: the row is followed exactly, on time by its own account, and nothing about the day feels wrong. The timing cell is the only cell on the map that can be wrong without looking wrong, and that asymmetry is what earns it a different design from every other column.

The cost of the pointer is one extra click on the day something happens, and that cost is real. The person following the row has to open the source and read the period there instead of reading it off the map. The cell never contained the period, so the cell cannot quietly go out of date. Households do this without instruction. Nobody sensible writes the electricity due date into a wall calendar as a fixed day of the month. The calendar entry says instead that the date is on the bill. The bill moves, the wall calendar keeps being right, and the one extra look at the bill costs eight seconds.

Step six: what source goes against each row, and why is the date the important half?

The last cell on every row carries two things. First the source: the body that issues the requirement, the name of the document, and the address it is read at. Second, and this is the half people skip, the date a named person last opened that source and checked the row against it. Not the date the row was written. Not the date the file was last saved. Any edit anywhere moves that date. The date that source was last read for that row. Write it per row and never once for the map. A single date on the front sheet makes the whole map look as fresh as its freshest line. A per-row read date is what makes staleness visible, and without it every row on the map looks equally current, including the ones nobody has touched since the day it was built.

The first time Prerna Wadekar ran a full check across the map, the read dates split the 19 rows three ways: 9 had been read within the last quarter, 6 within the last half year, and 4 had not been opened since the map was first written. Nine plus six plus four is nineteen. One date on the cover of the file would have shown a recently touched document and would have said nothing at all about those 4. The rows that need attention are never the ones somebody has been working on.

Step seven: which rows carry a judgement, and which are mechanical?

Go back through all 19 rows and put one of exactly two marks on each. A mechanical rowA duty with no judgement in it: the trigger is observed rather than assessed. is one whose trigger can simply be observed, where the thing either happened or it did not and nothing stands between the event and the duty. A judgement rowA duty whose trigger has to be assessed by somebody before anyone knows the duty has started. is one whose trigger has to be assessed before anybody knows the duty has started at all. Do not invent a third mark for the rows that feel like both. A third mark is where every row will eventually go. Where a row genuinely cannot be decided, mark it judgement. Then write against each judgement row, and only there, the role that gets woken to make the call. Write the role, never the answer. Marking every row mechanical or judgement means the person holding the map at nine in the evening knows in one glance whether a filing or a decision has just arrived.

On the map at Vindhya Ceramics Private Limited, 14 rows are marked mechanical and 5 are marked judgement. Fourteen plus five is the whole 19. In the year that followed, 12 rows fired: 10 of the mechanical ones and 2 of the judgement ones. Across the 31 disclosures made that year, 29 came off mechanical rows and 2 came off judgement rows. The single hardest of those 2 was the row for a customer contract ending. A row like that one is where the mark earns its place. Everything about the evening turns on whether somebody has to be woken up.

The two marks describe different problems, and they need different people at different speeds. A mechanical row needs somebody competent and awake to execute it. A judgement row needs somebody with the standing to make a call the company will have to defend later. Ringing the second person for a mechanical row wastes a night. Failing to ring them for a judgement row is the mistake that costs, and the mark exists to stop anybody working out which is which while the phone is ringing.

Step eight: who holds the re-check, and where is it written down?

Put a re-checkThe scheduled reconfirmation of every row on the map against its own source. in a diary with a date against it and a role against it, and write both onto the map itself rather than into a private task list or somebody's memory. A re-check means opening each row's source, reading the current text there, and then doing one of two things: amending the row, or re-dating it. Give the re-check to a role, the same way step four gives approvals to roles. The duty to run it then does not walk out of the building with a person. And write on the map what the re-check covers. An instruction to review the map is not something anybody can execute. An instruction to open every source and re-date every row is.

Then the part people leave out. Record the nil finding. When a row is read carefully and nothing has changed, write the date, the role and the words no change. An unrecorded clean review looks exactly like no review at all. Six months on, a row that somebody opened, read line by line and found identical is indistinguishable from a row nobody opened, unless the person who opened it wrote that down. The nil finding is not paperwork about paperwork. A dated nil finding is the only evidence that a row has been looked at, and it takes eight words.

Run the first re-check at Vindhya Ceramics Private Limited. Coming into it, the 19 rows split by how long each had gone unread: 9 within the last quarter, 6 within the last half year, and 4 untouched since the day the map was written. Coming out of it, 15 rows were re-dated with a nil finding and 4 were amended. Fifteen plus four is the whole 19 again. The 4 that were amended were the 4 nobody had opened since the map was built. The overlap is not a coincidence and it is not bad luck. Rows go wrong in the dark, and the re-check exists to turn the light on at a date somebody chose in advance rather than at nine in the evening.

Step nine: what does the map say about an event that no row covers?

Write a standing procedure for the event the map does not yet describe, and put it at the head of the map rather than at the end, where it will be found by somebody who is scrolling quickly. The standing procedure has four parts and no more: who is told first, the role that decides whether the event belongs on the map at all, how that decision gets recorded, and when the new row is written. Name roles for the first two. Do not try to describe the event itself. The entire case the standing procedure is written for is the one nobody has described yet. A map that says nothing about the uncovered event lets its own silence read as an answer, and the answer silence gives is that nothing needs doing.

Every household with a first aid box has met this. If the box holds a card saying ring this number for anything not in here, the missing bandage is a problem with an answer. If the box holds no card, the missing bandage reads as evidence that a bandage was never needed. The box is identical in both cases. The card is the whole difference, and it costs one line.

In its first year the standing procedure at Vindhya Ceramics Private Limited was not used once. All 31 disclosures came off rows that already existed, and no event arrived that the map had not anticipated. A procedure used zero times in a year is not evidence that the procedure was unnecessary. Zero uses is evidence about the year.

What does the finished map look like on the day something happens?

Nine steps produce one artefact: 19 rows, five columns, a mark on every row, a read date on every row, and a standing procedure at the head. Here is the row for a customer contract ending at Vindhya Ceramics Private Limited, unpacked in the order somebody actually reads it at nine in the evening. Every cell below was filled in on a quiet afternoon months earlier, and not one of them is being worked out now.

Notice the direction. On the day, somebody reads one row across, left to right, and stops. Nobody scans a column. A column answers a question about all 19 kinds of event at once, and nobody has that question at nine in the evening. The row is the unit the map is used in, so the row is the unit the map should be laid out for. Laying the map out for the row has practical consequences: keep a row on one screen without scrolling sideways, keep the mark at the left where the eye lands first, and never split one row's cells across two sheets to make the columns look tidy.

Who reads this map apart from the person who built it?

Four kinds of reader, and each of them changes how carefully the map is written. The first is the writer's own successor. A compliance officer inheriting a map inherits the read dates with it, and the first thing a careful successor does is run a re-check to find out how much of what they have been handed is still true. The second is the board's audit committee. An audit committee does not want the map read out to it, and does want to know how many rows carry a judgement mark and who is named against them. The third is a diligence team working on a further raise or a lender's review. A diligence team asks to see how the company knows what it must tell the market, and reads the read dates before it reads anything else. A map with dates on every row survives all three of those readings, and a map with a single date on the cover survives none of them.

The fourth reader is the one nobody plans for: the person covering while the compliance officer is on leave, at nine in the evening, who has never opened the file before. Everything in steps four, seven and nine exists for that person. The approver written as a role means they can find who to call without knowing anybody. The mechanical or judgement mark means they know within a second whether to execute or escalate. The standing procedure at the head means that even an event nobody anticipated has a first move. A map written for that person works for everybody else by accident.

Vindhya Ceramics Private Limited, Prerna Wadekar and Ratnakar Deshpande are invented.
Educational material. Not advice on any investment, tax, budget or market position.