Build a company research dossier that remains searchable
A useful company dossier has an identity page, an inventory of sources, untouched originals, and separate working notes. Organize around the reporting entity rather than a ticker alone. The goal is to retrieve the correct evidence later, not to accumulate the largest possible folder.
The SEC metadata documentation supports checking filer identity. The Library of Congress format resources provide background on format sustainability. The folder design below is an original manual workflow, not a claim that a particular research product implements it.
Start with an identity page
Record the legal entity, stable identifier when available, market-specific securities, sourced aliases, and the date of the last identity check. Make this page the entry point to the dossier. A company rename should update aliases and links without destroying the old paths people may use to find historical material.
Keep originals and notes in separate locations. An original file should retain a record of where it came from and when it was obtained. An annotated or converted copy belongs with working material and points back to its original. This distinction makes it possible to inspect the source without inheriting another researcher’s highlights or extraction errors.
Hypothetical dossier layout
Assume fictional Redbank Engineering has two market listings and an earlier company name. This example describes local files, not existing CoTrading functionality.
entity-redbank/
identity.md
sources.csv
originals/
working/
questions.md
reviews/The identity page connects the two securities without assuming identical rights. The source manifest lists each report’s period and version. The questions file lists missing evidence. A review note links to source IDs rather than copying every PDF into another folder. The example name is hypothetical; actual entity identifiers must come from checked sources.
Make the manifest the search surface
Use columns for source ID, title, issuer, period, publication date, version, language, official URL, local path, and inspection status. Add only fields you will maintain. An empty “verified” column is less useful than a precise status such as identity checked, paragraph inspected, or file not yet read.
When a new document arrives, check whether it is a duplicate, a new version, or a related document. Add a new source row when identity changes. Do not overwrite an older row just because the filename is similar. If several formats represent one report, link them to the same disclosure object while retaining their file identities.
Verify retrieval rather than appearance
Test the dossier with three tasks: find the latest inspected annual report, find the source used in an old note, and identify an unanswered question. Each task should be possible from the identity page and manifest. If success depends on remembering which download folder you used, the dossier needs a better locator.
Check paths after moving or exporting the folder. Relative paths can help portability, but they still need a real retrieval test. Save a small readme that explains the directory and the meaning of statuses. Another reader should not have to infer your filing system from file dates.
Boundaries and common mistakes
A dossier is an organizational aid, not an investment thesis, a guarantee of completeness, or a source of independent confirmation. More files do not mean more corroboration. A release copied to several sites may still be one issuer statement.
Common mistakes are using only ticker-based folders, mixing annotations with originals, and keeping an index that is never updated. Another is collecting every available item without a research question. Begin with the sources needed for your active questions, document coverage, and expand when a new task justifies it.
A final record check
Before adding a new folder level, ask which retrieval question it solves. A structure based on every possible market, year, and document type can become difficult to maintain. Keep the physical layout modest and let the manifest carry searchable attributes. Test a renamed entity and a historical note specifically, because these cases expose weaknesses hidden by retrieval of the latest report.
FAQ
Do I need a database to build a dossier?
No. A text identity page and a maintained spreadsheet manifest can support a small archive. Choose tools you can retrieve and export reliably.
Should all group companies share one folder?
Use separate entity identities and explicit relationship links. A group-level entry page can connect them without merging different reporting subjects.