Connect Your Documents. See the Full Picture.

Documents rarely exist in isolation. A contract references its schedules and amendments. A project proposal depends on a feasibility study. A new policy supersedes an older one. Dockria's Document Relationships let you formalise these connections, creating a navigable network that reflects how your documents actually relate to each other.

Six relationship types cover every common scenario: link documents as related for general associations, establish parent/child hierarchies for document families, mark dependencies for sequential processes, create reference links for supporting materials, flag superseded documents to prevent outdated versions from being used, and track amendments to their source documents.

Automatic relationship rules take the manual work out of linking. Configure rules at the document class level — for example, every new amendment automatically links to its parent contract, or every project deliverable automatically references the project charter. These rules ensure your document network stays complete and consistent without relying on users to remember.

Lookup properties go even further by pulling metadata values from linked documents. When a purchase order is linked to a vendor record, the vendor's name, registration number, and payment terms automatically populate on the purchase order. This eliminates duplicate data entry, reduces errors, and keeps information synchronised across your document network. Looked-up values are shown inline alongside the document's own properties, so reviewers see the full context — vendor terms next to the purchase order, parent contract reference next to an amendment — without having to open the linked document.

Relationship rules respect your document class hierarchy. A rule defined on a parent class — for example, 'every Contract Amendment automatically links to its parent Contract' — is inherited by every more specific child class beneath it, such as Supply Contract Amendments or Lease Contract Amendments. This means you configure once at the most general level that makes sense, and the rule applies consistently across every specialised class your organisation defines, without manual duplication and without rules drifting out of sync.