--- id: KB-TL-028 url: https://app.codecontract.io/help/trackline/how-this-differs-from-a-document-management-tool idioma: en categoria: trackline subcategoria: empezar audiencia: usuario nivel: basico actualizado: 2026-08-23 tambienEn: [es] relacionados: [KB-TL-001, KB-TL-019, KB-TL-029] citadoPor: [KB-TL-019, KB-TL-030] --- # How this differs from a document management tool _A document manager stores what you already have. Here the work is getting what you do not have yet, and it is held by someone who does not work for you._ **Responde a:** difference between a document manager and trackline · we already have a shared folder for this · why do we need this if we already have a document repository · what does it add over asking for documents by email **A document manager solves the problem of finding what you already have. This one solves getting what you do not have yet.** Two different jobs, rarely done by the same tool, because the second depends on someone outside your organisation who has no account in your systems and no obligation to learn them. ## Where the work sits, in each case | The work | Document manager | Here | | --- | --- | --- | | Where the document is | You already have it | A third party has it | | Who acts | Someone inside | Someone outside | | The typical problem | Finding it | Getting it to arrive | | What success means | It is filed | **Nothing is missing and it is on record who provided it** | > [!IMPORTANT] > **The practical difference is who does the chasing.** In a shared folder, when a certificate is missing nothing happens: the folder does not warn you, does not know it is missing, and cannot know, because it does not know what should be there. Someone on your team has to remember, look, write the email and look again next week. That work — remembering and looking again — is the part a person no longer does here. ## The five things that change **En corto** - **Whoever responds needs no account.** They open a link, upload, done. Asking them to register is where half the responses are lost. - **The channel is chosen by the person answering**, not by the one asking: email, WhatsApp, SMS, a call or the portal. The supplier who never opens email does read messages. - **Status belongs to the case, not the file**: what is missing, from whom, and since when, on one screen. - **What arrives is reviewed and extracted**, not just stored. An expired certificate that has been filed is still expired. - **And there is a record of who provided what and when**, which is different from having the file in a folder. ## When the document manager is what you need 1. **When the document is already yours** — Signed contracts, manuals, internal policies. There is nothing to request. 2. **When the problem is search and permissions** — High volume, many versions, who sees what. That is a repository's job. 3. **And when they coexist, which is the normal case** — This handles the outside stretch; what is already closed lives where it always did. > [!WARNING] > The most expensive starting mistake is treating this as «a folder with reminders». Set it up that way — a list of documents someone ought to upload — and you end up with what you had plus a tool in the middle. **What changes the outcome is defining what is requested, from whom and by when**, because from then on the system knows what is missing and can chase it on its own. Without that definition there is nothing to chase. **Does it replace our repository?** No. It handles getting the document; long-term storage can stay where it is. **What if asking by email already works?** Then you do not have the problem. It usually shows up going from ten requests to a hundred. **Can we export what we collect?** Yes, the whole case. No data is trapped in here. ## Ejemplos **An accountancy firm keeps everything in per-client folders. For a group insurance renewal it needs the same certificate from 140 companies and builds a spreadsheet to track who has sent it.** - Turns the spreadsheet into a one-document template - Launches to all 140 at once - Watches the status screen instead of the spreadsheet → The spreadsheet disappears: who has sent and who has not sits on the same screen as the requests, and updates itself. **A purchasing team has an immaculate repository, yet 30 % of new suppliers take over three weeks to onboard because a document is always missing and nobody knows which.** - Defines onboarding as a case with its six documents - Lets the system ask and remind - Reviews only what arrives → Three weeks become four days, and what is missing is visible without asking anyone. **A construction firm shares a cloud folder with twenty subcontractors. Two months in there are 400 files named things like «scan_2.pdf» and nobody knows which belong to the company starting tomorrow.** - Requests each document against a specific requirement and company - Stops accepting loose uploads - Closes the shared folder to new files → Every file arrives already knowing whose it is and which requirement it meets: the filename stops mattering. **A quality manager finds during an audit that she has the supplier's certificate but cannot show when it was provided or who sent it.** - Collects by request from now on, not by email - Lets the delivery record build itself - Attaches that record to the audit file → Next audit, «when did they give it to you?» is answered on screen instead of by reconstructing an email thread. **A company receives documents by email and drags them into the folder by hand. The person who does it goes on holiday for two weeks.** - Replaces the manual dragging with link-based collection - Splits follow-up between two people - Checks status on return → The two weeks stop being a hole: what arrived is filed and what is missing is still being chased. **A small supplier barely uses email and answers on WhatsApp. The shared folder is not even an option for him.** - Sends the request over WhatsApp - Receives a photo of the document from his phone - The photo enters the case like any other delivery → He stops being the impossible supplier: he answers where he already answers, and it lands in the same place as everything else. **A 12-person company pays for a repository almost nobody opens, because the real work — chasing those who do not send — still lives in two people's inboxes.** - Leaves the repository for closed archives - Moves collection to requests with automatic reminders - Measures how many manual reminders remain → Manual reminders drop to almost zero, and the repository starts receiving documents that have already been checked. **Migrating document systems, the team discovers that who delivered what lived in the emails, not in the repository, and does not migrate.** - Separates the archive (files) from collection (who, when, against what) - Lets collection keep its own trail - Exports the whole case, not just the files → The next migration carries the traceability too — the half that always used to be lost.