How to Map a Capital-Raising Regulatory Path

A capital raising path map is a written sequence listing every approval, filing and disclosure a particular raise requires, the body each one goes to, the source it came from and the date that source was read. The map is built before anything is committed. Building one is a procedure of twelve steps; how the underlying mechanisms work is covered separately.

A path mapA written sequence of every approval, filing and disclosure a raise requires, with the body each one goes to. exists because the expensive mistakes in a capital raise are almost never about the finance. The mistakes are about a step that came in the wrong order, a body nobody had on the list, or a requirement somebody read once eighteen months ago and has been repeating from memory ever since. The three failures look completely different when they land, and they have one cure between them: a single sheet on which every requirement, its body, its source and the date that source was read are all visible at the same time. A map turns three invisible problems into one sheet anybody can look at.

The steps below are instruction rather than explanation. Twelve of them, in order. The moment a step starts explaining a mechanism, two things go wrong at once. The procedure stops being usable at speed, and the explanation starts stating requirements that move. So how any form of capital raising actually works, what any approval requires and how long anything takes are each covered separately. So the steps say what to write down and where to go and confirm it, and they stop there. Vindhya Ceramics Private Limited, an invented unlisted manufacturer, asked Sarvodaya Capital Advisors Private Limited, an invented advisory firm, to lay its path out on one sheet. The Vindhya case runs through every step below.

What is a regulatory path map, and what is it for?

A path map is one sheet with rows on it. Each row names a thing that must happen, the body it happens with, the document that says so, and the date somebody last read that document. Around the rows sit three more things: the arrows marking which row cannot begin until another is finished, the name of the person who will actually do each row, and a short closing list of everything the path leaves out. A path map is not a plan, a budget or a timetable, and it carries no dates other than the dates on which its sources were read. Everything on it is either a requirement or a record of where a requirement was confirmed.

Think of it the way a household thinks about adding a room upstairs. Nobody starts with the cement. Somebody sits down and writes out the permissions the work needs, the office each one comes from, and who in the household is going to stand in which queue. The list is dull, it takes an evening, and it is the difference between a build that pauses for six weeks and one that does not. A capital raise has the same shape and higher stakes, and the only reason firms skip the evening is that the list feels like something everybody already knows.

Step one: what is written down before anything is opened?

Write down three things and nothing else. What is being raised. From whom it is being raised. In what form. Write them in the words the law uses rather than the words the meeting used, and keep pushing until the sentence would mean the same thing to somebody who was not in the room. If the sentence in everybody's head is that the company is bringing in an investor, that sentence is unusable on a map: it does not say what instrument, it does not say from whom, and it does not say in what form. Then stop. Do not look anything up yet, do not name a body, and do not start listing approvals. The first line of a path map is a description of the raise in the words the law uses, written before any regulation is opened.

The same thing happens at a counter without anybody noticing. A person asking for a new connection is never asked first what they want; they are asked what they are and what exactly they are applying for. The form the clerk hands over depends on the answer. Guessing the form first fills in the wrong one very neatly.

Step two: what is established about the entity that is raising?

Step two establishes the form of the entity, writes it on the same sheet as step one, and goes no further into it. The kind of entity and its current status go down in one line each. Vindhya Ceramics Private Limited is an unlisted manufacturer, and those two facts about it were written down before Sarvodaya opened anything at all. The pull to start reasoning about what the form implies is worth resisting. Such reasoning is the next several steps, and doing it here means doing it from memory. The path starts from the entity rather than from the raise, so the form of the entity is established before a single regulation is opened.

Step two is the step people skip, and they skip it because it feels like something already known. Everybody at the firm knows what kind of entity the firm is. The trouble is that the map is not built for the people who already know; it is built to be handed to somebody who does not, and to be checked later by somebody who was not there. A map whose first two rows are missing says nothing about what path it is a map of, so nobody can check it.

Step three: how is the Act that governs a raise of that form found?

Step three takes the sentence from step one and the entity from step two and goes looking for the governing Act. The search starts at the body already believed to be involved, opens its published list of Acts, and reads the names. The name of the Act goes on the map and nothing else about it: not what it says, not what somebody thinks it means, not what somebody said it covers. If two Acts plausibly reach a raise of this form, both are written down and the second is marked unresolved rather than chosen between now. A map that starts summarising is a map that has started guessing, so at step three the name of the Act is recorded and nothing about its contents.

Sarvodaya Capital Advisors Private Limited runs this step with Devaki Suresh at the keyboard and Kamala Ravindran reading over her shoulder, and the rule between them is that anything either of them says from memory gets written in a different colour until it has been found in a published source. The colour rule is a small discipline, and it does most of the work of this entire procedure.

Step four: which bodies go on the list, and which one gets left off?

Step four lists every body the governing Act empowers, one line each, with the site at which that body publishes its own material written beside it. Then, before the list is treated as finished, the company law side is added. The instruction is not to check whether it applies, but to add it and then find out. The company law authority was already there before anybody thought about raising anything, so it never feels like part of the raise, and it is the body most often missing from a first draft of a path map.

The pattern is worth recognising because it repeats. People forget the permanent thing, never the exotic one. The lane outside a house has always been there, so nobody in a household forgets to arrange the wedding hall and everybody forgets that the lane needs permission to be blocked. On a path map, the bodies that arrive with the raise announce themselves. The one that was there all along has to be added deliberately, by somebody following a written step rather than by somebody remembering.

Step five: which clause of the regulation is read first?

Find the regulation that deals with a raise of this form and open it. Now read the application clauseThe part of a regulation stating who and what it applies to. before the clause that prompted the search. The part of that clause which reaches this entity goes on the map, in the map builder's own summary, with today's date written against that summary. If the application clause does not reach the entity, the regulation closes and the work goes back to step three, rather than carrying on into the substantive clauses to see whether they might be relevant anyway. A map built on a regulation that never reached the entity is not slightly wrong, it is wrong in every row at once. Read the application clause first.

The pull in the other direction is strong and worth naming. The document was opened with a question, the question is answered somewhere in the middle, and the middle is where the search box lands.

Step six: how are the approvals listed, and in what order?

List every approvalA permission that must be obtained before a step can proceed. the path requires, one line each, with the body that gives it written beside the line. The lines are then reordered so they run in the order the path requires rather than the order they happened to be found in. The map is a list of what must happen and where each requirement is confirmed, and it is not a description of anything, so nothing is written about what any approval requires or how long it takes. A summary of what the body will want is the first thing on a map to go out of date, so an approval row carries the permission, the body and the source and never that summary.

Order matters here in a way that will not be obvious until step nine. The reordering happens now, with the approvals in front of the map builder and the reasoning fresh. A list assembled in discovery order follows the order somebody's search results came back in, and search results are not an order at all.

Step seven: how are the filings listed, and against which body?

List every filingA document that must be submitted to a named body., one line each, with the body it goes to written against every single line. The body column is never left blank, not even temporarily. If the body cannot be named, the row is not yet a filing; it is a note that something exists, and it belongs in a queue of unresolved items rather than on the map. A filing with no body written against it is not a filing on a path map, and leaving the column blank is how a requirement quietly becomes somebody else's problem.

The blank column is more dangerous than a missing row, and that is not obvious. A missing row is discovered when somebody reads the map and asks where a thing went. A blank column looks like work in progress on a map that otherwise looks finished, so everybody reading it assumes the person before them was about to fill it in.

Step eight: how are the disclosure documents listed?

List every disclosure documentA document that must be produced and made available as part of the path. the path requires, by name, one line each. Each one is named, and there it stops. The contents of any such document are a separate exercise entirely, and the moment they appear on the map the map has turned into a draft of something else. So the contents are not described, no drafting starts, and no note is made of what the document should say. Against each name go the place where the requirement to produce it was read and the date it was read. At step eight the documents are named rather than written, and a map that has begun describing contents has stopped being a map.

Sarvodaya keeps the three kinds physically separate on the map, in three columns, and Nirmal Achari holds the disclosure column because he writes for a living and is the person most likely to notice when a document has been named loosely. Three columns rather than one list. The three are satisfied in three different ways, and only one of them opens the next step.

Step nine: which steps cannot begin until another one finishes?

Go down the rows and mark every dependencyA step that cannot begin until an earlier step is finished.: each row that cannot begin until a named earlier row is finished, with that earlier row written against it. Mark them as pairs, not as a general sense of order. Any reader can then pick up a single row and see exactly what has to be complete before it starts. Rows that depend on nothing get a dash rather than a blank, so a reader can tell the difference between independent and unexamined. A list says what must happen and a path says what must happen before what, so marking dependencies is what converts a complete list into a path.

Every household knows this shape from a wedding. There are forty things on the list and thirty-eight of them are genuinely independent. The two that are not will be the two that go wrong. The caterer cannot be confirmed until the hall is confirmed, and the hall cannot be confirmed until the date is fixed, and the list of forty items shows none of that because a list has no arrows in it.

Step ten: what goes in the source and date field on every row?

Against every row, without exception, go two things: where the requirement was read, and the date it was read. Not the date the instrument carries. The date a named person opened the source and read it. Both entries go in the source and date fieldThe record of where a requirement was read and when a person actually read it., and it is the column that everybody wants to leave until later. A source column filled in afterwards is filled in from memory, and memory is the exact failure the column exists to prevent. The field is filled row by row as the work goes. The source and date field is the least interesting column on a path map and the only one that shows a reader which rows nobody has confirmed lately.

The column buys a queue. Without it every row on the map looks equally confident, and confidence spread evenly across a map carries no information at all. With it, the rows sort themselves: the oldest dates go to the top of the list of things to check, and the question stops being whether the map is right and becomes which four rows to confirm this week. The second question is far smaller and far more answerable.

Step eleven: whose name goes against each step?

Put one named person against every step, including the steps nobody wants. Not a team, not a function, not an initial: a person who has seen their name on the row and has agreed to it. Where a row genuinely needs two people, name the one who is answerable for it finishing and name the second as support, so there is never a row on which two names each assume the other. A name against every row is what converts a map from a description of the path into work somebody has agreed to do.

The same thing fails in a shared flat. The roster on the fridge says the kitchen gets cleaned on Sundays. A fact about Sundays is not a fact about any person, and the kitchen is filthy by the third week. Put four names down the side and the same roster starts working, not because anybody became more responsible but because a name is a thing another person can point at. On the map for Vindhya Ceramics Private Limited, twelve step rows carry four names between them: Kamala Ravindran, Devaki Suresh, Nirmal Achari and Harish Vaze.

Step twelve: what does the path not include?

Write the exclusion listThe written statement of what a path does not include, kept as part of the map rather than as a note.: a short closing block naming what falls outside this path. Everything anybody has been assuming is put to the room, one thing at a time, and asked of it whether it is on the map. If it is, it is already a row. If it is not, it goes on the exclusion list in one line. Then the date the whole map is re-checked is diaried and written at the foot of the map. The exclusion list is the shortest part of a path map and the part that does the most work. An assumption nobody had said out loud finally has to be written down there.

Any household that has ever taken a builder's quotation knows why this block exists. The quotation lists what is included, and it is accurate, and the argument three months later is never about anything on it. The argument is about the one line that was never written anywhere: not included, not excluded, simply never asked about by anybody. On the map for Vindhya Ceramics Private Limited the exclusion list ran to four lines, and one of those four was something the company had been quietly assuming since the first meeting.

How is the map kept current once it is written?

Re-checking runs by the dates rather than by the calendar. The rows are sorted by their source and date field, the oldest taken first, the source opened again and the row either confirmed or amended, and the new date written. The whole map is done on the diaried date, and the oldest rows before that if the raise has moved on. A path map does not become false as it ages, it becomes unconfirmed, and the difference is that unconfirmed is a state that can be worked through row by row.

Notice what this discipline refuses to do. Remembering is the failure the whole procedure is arranged against, so the re-check never asks anybody to remember whether something has changed. The re-check asks only for two mechanical acts: sort by date, open the source. Devaki Suresh at Sarvodaya Capital Advisors Private Limited runs it the same way she runs the rule change register. She works down a column rather than thinking hard about what might have moved.

What did the map for Vindhya Ceramics actually contain?

Vindhya Ceramics Private Limited, an unlisted manufacturer, asked Sarvodaya Capital Advisors Private Limited to lay out the path for raising capital, and Sarvodaya produced one sheet. Every count below belongs to that one path and to no other. The map ran to twelve step rows, and across them it listed six approvals, nine filings and three disclosure documents, eighteen obligations in total.

Two things on that map are worth copying. The first is the source and date column, set out in the second table below. Every step row carries the date Devaki Suresh read the source behind it, so the rows confirmed on 3 February sit visibly older than the rows confirmed on 14 June, more than four months apart on the same map. The second is the last row, the shortest on the map and the one that did the most work. Writing out what the path did not include is where Vindhya Ceramics discovered it had been assuming something that nobody at either firm had ever said aloud.

The right hand column, read down, tells something the left hand column cannot. Four rows were confirmed in the week the work started and have not been touched since, and three were confirmed in the week the map was finished. Nobody has to argue about whether the map is current. The map has already sorted itself into what to check first, and sorting itself is the entire return on a column that took four seconds a row to fill in.

Who uses a path map outside a compliance office?

A lender's credit team uses one without calling it that. A raise that depends on a permission nobody has listed is a raise with an unpriced risk of stopping. So when a borrower says it is raising capital and the loan turns on that raise happening, the first thing a careful credit officer asks for is the list of approvals and who they come from. A path map is the document that lets somebody outside the firm see the shape of a raise without being told what to think about it.

An analyst uses it the same way, in reverse. Given a company that has announced a raise, the useful question is not what the raise will do to the numbers but what has to happen first and who has to say yes. The timetable actually lives there, and it is the part that press coverage tends to skip. A director uses it differently again. Harish Vaze, non executive on Sarvodaya's board, reads the map to find rows with no name and rows with an old date, the only two things on such a map that a board member can usefully act on in twenty minutes.

And a person who is being asked to put money into a small company can use the same map. The document to ask for is the path map. Not an opinion about whether the raise is a good idea, but the list: what has to happen, who says yes to each one, and when somebody last checked. A firm that has that map will hand it over. A firm that has not will explain why the map is unnecessary, and that explanation is itself the most informative thing said to anybody that day.

Vindhya Ceramics Private Limited, Sarvodaya Capital Advisors Private Limited, Kamala Ravindran, Devaki Suresh, Nirmal Achari and Harish Vaze are invented.
Educational material. Not advice on any investment, tax, budget or market position.