Document control software holds a factory's controlled documents and keeps them controlled. It covers procedures, work instructions, formats, specifications and drawings, with version history and approvals, distribution to the points where they are used, withdrawal of superseded copies, review due dates, records retention, internal audit scheduling and the retrieval an audit actually tests. Pentoggle is an AI platform that generates production-ready software from a plain English description, which means a factory can build document control around its own system instead of adapting to a template.
Most manufacturers in India already run Tally for accounting, some run Busy or Marg, and larger businesses may run SAP Business One. Those systems handle purchase, sales, GST and accounting well. This is not a proposal to replace them. Pentoggle builds the document control application around them, covering the workflows they were never designed for.
Key takeaways
- Writing the document is the part most factories complete. Controlling which copy is in use is the part that fails.
- The printed copy at the workstation is the real document, and it is the one nobody withdraws when a revision is issued.
- Documents have review dates that quietly pass, so a system can be fully documented and substantially out of date at the same time.
- An audit is largely a retrieval test, and the common finding is not that the work was not done but that it could not be shown.
- The number that matters is the share of controlled documents that are past their review date.
A note on certification
What a certified management system must contain, how documents must be controlled and what records must be retained are defined by the applicable standard, by your own documented system and by your certification body. Pentoggle applications hold documents, versions, approvals, distribution records and retention data as operational records. They are not a certified system, they do not confer certification, and they do not determine what your system must include. Confirm requirements with your management representative or certification body. In regulated environments where documents sit inside a validated system, they should stay there.
Why documented systems drift out of date
A factory pursuing certification writes a great deal. Procedures, work instructions, formats, control plans, specifications. The effort is real, it is usually done well, and it is largely completed before the certification audit.
What happens afterwards is the problem. A procedure is revised because a process changed. The revision is approved and filed. Meanwhile there are printed copies at four workstations, a scanned version in a shared folder, and a laminated instruction near a machine that nobody has looked at in two years. All of them are still in use.
None of this is dishonest, and most of it is invisible. The system is documented. The documents in circulation are not the documented ones.
The second failure is quieter. Documents carry review dates, typically annual. When the review date passes without a review, nothing happens visibly. Over three years, a significant portion of the system describes a factory that no longer exists, and this is discovered either at an audit or when somebody follows an instruction that is wrong.
What document control software holds
Document register
Every controlled document with its number, title, owner, current version, approval and status.
Version history
What changed at each revision, who approved it and when, with previous versions retained and marked superseded.
Distribution
Where each document is in use, including physical copies at specific locations, so a revision knows what to withdraw.
Acknowledgement
Where required, a record that the people using a document have seen the current version.
Review schedule
Review due dates per document, with alerts before they fall due and visibility of what is overdue.
Records retention
Which records are kept, where, for how long, and when they may be disposed of.
Internal audit schedule
Planned audits, coverage, findings and their closure.
Specifications and drawings
Customer specifications and drawings held as controlled documents where your system requires it.
Retrieval
Any document or record produced by search rather than by knowing which cupboard it is in.
The printed copy is the real document
Whatever a system says, the document that governs behaviour is the one physically present where the work happens. On a shop floor that means a printout, a laminated card or a photocopy in a file at the machine.
Every revision therefore has two halves. Issuing the new version is the half that gets done. Withdrawing the old copies is the half that does not, because it requires knowing where they all are, and in most factories nobody does.
This is the general form of a problem that appears throughout manufacturing in specific costumes. A machine shop running the wrong drawing revision. A fabricator whose fitter is working from an old print. A printing unit that ran superseded artwork. A cosmetics line that consumed labels carrying an old declaration. The mechanism is identical each time.
The fix is a distribution record. Each controlled document lists where its copies are, and a revision produces a withdrawal list alongside the new issue. Making the current version viewable on a phone at the point of use reduces the number of printed copies in the first place, which is the more durable answer.
An audit tests retrieval, not effort
Auditors sample. They ask for a specific record from a specific date, a particular calibration certificate, the training record for a named person, the last review of a named procedure.
The common finding in a well-run factory is not that the work was not done. It is that the record cannot be produced within the time available, or that what is produced is incomplete or unsigned. The work happened. The demonstration failed.
That makes retrieval the capability worth building, and it is testable without waiting for an auditor. Pick five records at random, of different types, from different periods, and ask for them. The time taken and the completeness of what comes back is a fair estimate of how the audit will go.
A document control application does not do the work of the system. What it does is make everything the system produced findable, which is a large share of what the audit is actually measuring.
Review dates are the quiet failure
A document that is past its review date is not wrong, and that is precisely why it is dangerous. It may be entirely accurate, or it may describe a process that changed eighteen months ago. Nobody knows which, because nobody has looked.
Because there is no visible symptom, this failure accumulates. A factory can hold a valid certificate while a third of its procedures have not been reviewed within their own stated cycle.
Holding review dates with alerts converts this into a small monthly task instead of an annual scramble before an audit. The review itself is often quick, since most documents will not have changed. The value is in the ones that have, where the review catches a drift between what is written and what people actually do, and either the document or the practice gets corrected while the gap is still small.
Why building this is now practical
Document management systems are typically priced and designed for organisations with a compliance function. A factory whose management representative also runs quality and sometimes production is not going to implement one, so control stays in folders and cupboards.
With Pentoggle you describe your document structure, your approval routes, where documents are used and how your review cycle works, and get a working application. When you add a document type, change an approval route, or start recording acknowledgements, you describe the change and the application updates. Most factories start with the document register, versions and review dates, because those three stop the drift.
Where document control looks different by industry
- CNC and Machine Shop Software, where drawing revisions govern what is being machined right now.
- Sheet Metal and Fabrication Software, where the drawing travels around the shop with the job.
- Printing and Packaging Manufacturing Software, where artwork versions carry the same risk.
- Auto Component Manufacturing Software, where control plans and customer requirements are controlled documents.
- Pharmaceutical Manufacturing Software, where documents inside the validated environment stay in your validated system.
Why manufacturers choose Pentoggle for document control
Built around your system
Your document numbering, your approval routes, your review cycle.
Distribution tracked
So a revision produces a withdrawal list rather than an assumption.
Current version at the point of use
Viewable on a phone, which reduces printed copies at source.
Review dates visible before they pass
Turning an annual scramble into a monthly task.
Changes in days
A new document type or approval route does not become a three month project.
The one number that runs document control
The share of controlled documents past their review date.
Certificates and audit results are lagging indicators, arriving once a year and reflecting the state of things some time ago. This number is current, entirely within your control, and it moves first.
Review it monthly. A figure creeping upward means the system is drifting away from the factory it describes, and it will keep drifting until somebody looks. A figure at or near zero means that when an auditor samples, what they find will match what actually happens on the floor.
Ready to build document control software?
Auditors rarely find that you did not do it. They find that you cannot show it.