Every engagement ends in a document, and most of them stop being used within a month of arriving. This collection specifies mine: what is inside each one, how it is structured, which numbers are computed rather than asserted, and what a client can still do with it six months later.
Three commitments apply to every deliverable in this collection. They are what separate a document that gets worked from a document that gets filed.
Every finding is a record with a fixed field set, so it can be sorted, filtered, assigned, counted across engagements, and dropped into a tracker. A paragraph cannot be any of those things.
An estimate carries the basis it was computed from, and the basis is recorded even when the estimate is null. A number without a stated derivation is a number a client can dismiss.
Owner, status, verification method, and verification date are fields on every record. Shipped and Verified are separate states, and a declined recommendation keeps the note explaining why.
If one of these documents is the thing your team is missing, or you want the specification adapted to a portfolio, a migration, or an in-house standard, the conversation starts here.