WhatsWorkRequest 14 days
THE CONNECTED ARCHITECTURE

Work creates documents. Documents carry the context.

WhatsWork + WhatsDocs connects the execution methodology with the documents that bring the work to completion.

Explore connected documentsRequest 14-day trial

A document is more than an attachment. It belongs to a client, a project, a task, a document type and a version.

WhatsWork

The work execution layer.

  • Reusable Work Blueprints
  • Milestones, tasks and responsibilities
  • Checklists, guidelines and reviews
  • Discussions and progress

WhatsDocs

The document work automation layer.

  • Document context and classification
  • Approved formats and structured answers
  • Systematic file and folder naming
  • Storage and retrieval workflows

A business layer above storage.

The architectural approach separates document business context from physical storage. Google Drive, Nextcloud or other supported repositories can provide the storage layer where implemented. Local and Office workflows follow the integration and synchronisation supported by the deployment.

Office remains where the document work happens.

WhatsDocs describes native Word, Excel and PowerPoint ribbon integration. Users profile documents by client, category and year; business context drives naming and placement. A permanent document identifier preserves identity across revisions.

01 / PROFILE

Give the document context

Select its client, category and financial year. Associate it with the relevant project and task.

02 / WORK LOCALLY

Save at desktop speed

Regular Ctrl+S saves in the local workspace while the document is being prepared.

03 / PUBLISH A REVISION

Update deliberately

Use Update to WhatsDocs to publish a cloud revision through the defined archive workflow.

Document workflow reference: WhatsDocs features ↗

GENERATED FOLDER PATHACME / 2025-26 / Statutory-Audit / 01-Engagement
GENERATED FILE NAMEACME_SA202526_Engagement-Letter_v01.docx

Client + 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.

Repository support, Office integration and synchronisation should be confirmed for your implementation. Visit WhatsDocs ↗

DEFINE ONCE. EXECUTE REPEATEDLY. IMPROVE CONTINUOUSLY.

Put your organisation’s knowledge to work.

Start with a blueprint. Give every engagement a clear path to completion.

Request your 14-day trial