A common language. Before the work begins.
Stop rebuilding the same terminology with every assignment. Standardise how work is classified, named and found.
Project Type → Milestone → Task → Document Category → Document Type → Document Name. Controlled masters provide the vocabulary that reusable blueprints build on.
Define the masters
Establish the approved project types, milestones, task names and document classifications for your organisation.
Import & reuse
Bulk-import your masters and choose controlled values when building templates rather than inventing new names each time.
Apply naming rules
Combine client, project, period, document type and version to establish consistent identifiers, file names and folder paths.
From “Audit Latest” to an identifiable document.
A shared taxonomy makes organisational work searchable, reportable and reusable. Naming rules reflect business meaning, so a document’s identity survives beyond the individual who created it.
ACME / 2025-26 / Statutory-Audit / 01-EngagementGENERATED FILE NAME
ACME_SA202526_Engagement-Letter_v01.docxClient + Project + Document Type + Version. One naming rule, applied consistently.
Illustrative naming preview. This demonstrates the rule; it does not create files or connect to a repository.
Identity is more than a file name.
A unique document identifier links the file to the project and task it belongs to. The classification records what it represents. The version describes its revision. The storage path defines where the file lives. Together, these layers provide traceability.
Put your organisation’s knowledge to work.
Start with a blueprint. Give every engagement a clear path to completion.
Request your 14-day trial