When Should a Document Workflow Use a Dossier Instead of a Folder?

A folder can organize the files for a contract, claim, or application. When the business needs to track what is missing, who must review it, which documents were approved, and what happens next, the workflow needs a record of the matter itself.

That record is often called a dossier or case file. It connects documents to a stable business identity, responsibilities, and lifecycle. A folder can still provide a useful view of those documents.

Distinguish the folder, the dossier, and the release package

Folders can have metadata, permissions, and workflows too. The reason to introduce a dossier is that the business matter needs its own identity and rules, independent of where its files appear.

Start with three questions

• Does the matter have its own lifecycle? A claim may move from collecting evidence to review, decision, and closure.
• Does readiness depend on several documents? An application may need a completed form, identification, and supporting evidence before review.
• Must you reproduce an approved set later? A signing package needs the exact versions and recipients that were approved.

A dossier is useful when these requirements cannot be reliably managed through file organization alone. Keep the model as small as the process allows.

1. Give the business matter a stable identity

Assign a permanent identifier, business reference, type, owner, and status. Add participants, dates, sensitivity, and other fields only as the process requires. Renaming a matter or moving its folder should not break integrations, audit history, or links to its documents.

Keep the dossier’s status separate from document versions. Uploading a revised schedule does not by itself make the whole contract approved. Record each business transition with its actor, time, applicable rules, and any approved exception.

2. Record why each document belongs

Give linked documents clear roles: primary agreement, schedule, amendment, evidence, decision, or correspondence. Define which roles are required, how many documents each allows, and what makes a version eligible for the next step.

For example, a contract may need one approved primary agreement and two required schedules before signing. A readable file called “Schedule B” is insufficient if it is still a draft or belongs to another contract.

Make amendments and replacements explicit. Retain the link to the earlier document, effective date, approval, and replacement rule. Removing a document from the current view should not silently delete its history or release a hold.

3. Freeze the approved selection before release

Create a package manifest: a protected list of the exact document versions, order, recipients, and purpose. For generated or signed output, also record the template version and relevant preparation settings. Keep the resulting files and approval linked to that manifest.

If a selected document changes, require the appropriate review before creating a replacement package. An approval for one set of versions must not silently authorize a later set. Protect approved snapshots from editing; a mutable list of links to “latest” versions cannot reproduce an earlier release.

Example: a schedule changes after approval

1. Prepare Contract C-204

   The dossier links the agreement, Schedule A, and Schedule B. The readiness check requires an approved version for each role.

2. Approve the signing package

   Package P-7 selects agreement version 3, Schedule A version 2, and Schedule B version 1. Approval records that exact selection.

3. Receive a revised schedule

   Schedule B version 2 arrives. It is added to the dossier for review and does not replace version 1 inside P-7. If the revision must be signed, prepare and approve a new package and resolve any existing signing transaction through the provider’s supported process.

4. Retain the outcome

   Link the executed package and completion evidence to the dossier. Keep previous approvals and package history so staff can explain which documents were actually sent and signed.

Keep access and retention specific to the documents

Dossier access should not automatically expose every linked file. Legal advice, identity documents, and medical evidence may need tighter permissions. Check document access in search, previews, package generation, exports, and sharing, including files linked from another matter.

External recipients should receive only the approved package. Internal notes, superseded drafts, and unselected attachments must remain outside that delivery path.

Closure can supply a retention trigger where the applicable rule calls for it. Different document roles may have different retention periods and holds, so closing or deleting the dossier must not override their requirements. Record the actual trigger and verify disposition against current policy.

Four checks before relying on the model

• Rename or move the folder. Confirm that the matter’s identity, document links, and integration references remain valid.
• Remove a required document or replace it with a draft. Confirm that the next workflow step is blocked.
• Update a document after package approval. Confirm that the approved snapshot stays reproducible and the new selection requires review.
• Share a package and close the dossier. Confirm that restricted files remain inaccessible and active holds still prevent disposition.