What is a flow management system?
A flow management system is a recurring job written down as a flow: every step in order, one owner for each step, a turnaround time for each, and a rule for what happens when a step is late. That is the whole idea. The acronym FMS makes it sound like a category of software, but it started as a way of thinking, and the thinking is the part that matters.
Every business already runs flows. A purchase request becomes an approval, becomes a PO, becomes a receipt at the godown, becomes a payment. A customer complaint becomes an assignment, becomes a site visit, becomes a resolution the customer confirms. A new joinee becomes a set of documents, a login, a seat, and a first-week plan. These are not projects. They happen the same way every week, and the business has usually never written down how.
If you have not met the term before, nothing is lost. "Process flow" and "workflow management" mean the same thing. FMS is the phrase that spread through Indian coaching programs, so a founder who did one of those courses and a consultant who says "workflow" are pointing at the same structure with different words.
Why do so many FMS builds start in Google Sheets?
Because it is free, it is fast, and it forces the right conversation. You cannot fill in an owner column without deciding who owns the step, and that decision is usually the first time anyone in the business has been made to say it out loud.
The typical build looks the same everywhere. A tab per process. Columns for step name, owner, TAT, status, remarks. A row per step. Colour-coding on the status column, green for done, red for pending. Somebody is made responsible for keeping it updated, and for a month it works beautifully.
That month is real progress, and it is worth having. A business that has written its top five flows into a sheet understands itself better than one that has not. The problem is what the sheet quietly becomes afterwards.
Where does a spreadsheet FMS actually break?
It breaks at the point where recording stops being enough and something has to act. A sheet holds a plan. It has no way to make any part of that plan happen.
Four things go wrong, and they go wrong in this order.
The file goes stale. Not because anyone is careless, but because updating it is a separate chore from doing the work. The store manager who received the material has finished his job; typing it into a tab is extra. Within a few weeks the sheet describes a business that no longer exists.
The chasing lands on one person. Someone has to open the file, read down the status column, notice the blanks, and ring people. In most SMEs that person is the owner, and if it is not, it is an MIS assistant whose resignation would take the whole system with them. Either way the flow is running on a person, not on the system, which is the exact dependency the FMS was supposed to remove.
"Done" becomes a word rather than a fact. A cell reading Completed proves that somebody typed Completed. It does not prove the reading was taken, the photo exists, or the party actually signed. In a factory or a hospital, that gap is where the money and the risk both sit.
TAT is a column, not a clock. Writing "8h" next to a step does not start anything counting. Nothing is ever late until a human notices it is late, which usually happens after the customer has already called.
What does an FMS need to do that a checklist app cannot?
It has to survive a handover, and real handovers are not tidy. This is where most tools stop, and it is worth knowing the specific gaps before you buy anything.
Work has to branch on value. A purchase of ₹40,000 and a purchase of ₹8,00,000 should not follow the same approval path. If everything reaches the owner, the owner becomes the bottleneck he was trying to escape.
Steps have to run in parallel. When three departments can start at once, forcing them into a queue adds days for no reason.
A failed check has to go back one step, not to the beginning. Rework is normal in any real operation. A tool that can only restart a flow will be abandoned the first week it costs somebody an afternoon.
The process has to change without breaking the jobs already running on it. You will improve a flow while forty instances of the old version are live. Both have to keep working.
A checklist app does none of this, because it was never asked to. It is a good tool for one person's repeating list, and it is the wrong tool for a process that crosses three departments.
How do you move a flow off the sheet without losing a month?
Take one flow, not fifteen. Take the one causing the most trouble right now, which in most businesses is either purchase approval or whatever the customer complains about.
Open the sheet and go column by column. The step name becomes a step with a real owner that opens on that person's phone when it is their turn. The owner column becomes an assignment. The TAT column becomes a clock that starts when the step does, with the reminder going out before it runs out. The status dropdown stops being something anybody sets, because completing the work sets it. The remarks column becomes the proof the step will not close without.
Expect to find three or four steps in the sheet that stopped being real months ago. Everybody works around them and nobody has removed them. Catching those is worth as much as the software.
Then leave it alone for two weeks before adding the second flow. Businesses that install fifteen flows in month one end up with fifteen half-used ones, and the team decides the whole idea does not work.
This week, do the smallest version of this: open your flow sheet, find the step that gets chased most often, and write down who should have been told when it slipped. If the honest answer is "me, by opening the file", you already know what the sheet is not doing.