Working notes on running client engagements in Obsidian. Each one is built around a component from our MIT-licensed repository, and each describes a mechanism you can check rather than advice you have to take on trust.
A statement of work lists what you will deliver. Scope is settled by the other two sections: what is explicitly out, and the assumptions you priced on.
If a line item names work instead of an artifact, it cannot be submitted, accepted or checked. How to write deliverables as things.
A deliverable can only be accepted by someone empowered to accept it. Naming that person is a field on the engagement, filled before the work starts.
A client commitment is not your task. Recording both in one list hides where an engagement is actually blocked.
Work the client has accepted can sit unbilled, because a tracker built around unfinished work stops at done. One query finds it.
The components these guides describe are published as an MIT-licensed repository: https://github.com/engagementdesk/obsidian-consulting-components
Engagement Desk is not affiliated with, endorsed by, or supported by Obsidian or by the author of Dataview. Those are separate products from separate publishers, distributed under their own terms.