Wordspecs

Blog

Spec sheets for agencies: one house format for every client

Private beta. Access is by waitlist, and paid plans open when the beta ends. Join the waitlist.

When every project lead builds a client document from scratch, the clients receive files that look like they came from different companies. A house format fixes that. This article sets out one template, how client variants fit into it, how to hand documents over, and how a change record settles disputes later. The agency and clients in the examples are fictional.

What clients notice

Clients notice whether a document is easy to review. The same sections in the same order, requirements they can refer to by ID, and a clear status on every page make review easier. When the layout changes from project to project, clients spend their attention finding things instead of checking them.

A house format with variants

A worked house template

Larkspur Creative is a fictional agency that builds websites and product catalogues. Each project document it produces has these sections, in this order:

  1. Summary. One paragraph on what is being built, for whom, and why now.
  2. Scope. What the agency builds, tied to a numbered scope version such as v1.2.
  3. Deliverables. A list with IDs (D1, D2 and so on), each with its due milestone.
  4. Out of scope. Named items that are not included, written out so nobody has to guess.
  5. Assumptions. What the agency relies on from the client, such as content supplied by a given date or access to a staging server.
  6. Requirements. One row per requirement, with an ID (REQ-001), a priority of Must, Should or Could, and one decision per row.
  7. Acceptance criteria. A testable condition for each deliverable or requirement, with an observable result rather than a judgement such as "works well".
  8. Timeline and milestones. A date for each milestone (M1, M2 and so on).
  9. Change process. How a change is requested, who decides, and where it is recorded.
  10. Sign-off. The names and roles of the people who approve this version, the date, and the version label.

Client variants

Three fictional clients each need one extra section on top of the house template:

ClientExtra sectionWhy the client needs it
Kestrel Dental GroupCompliance and data handlingPatient records have legal handling rules. The section lists where data is stored, who can access it, and how long it is kept.
Mapleton Water BoardAPI appendixTheir engineers connect the meter feed to their own systems. The appendix lists endpoints, request fields and error codes.
Orrin RetailLocalisation tableThe shop launches in four languages. The table lists each language, its date and currency formats, and the string count for translation.

When a variant becomes part of the house template: when a second client asks for the same section, or when a service line needs it on every project. Until then it stays a variant. This keeps the house template short enough that a project lead fills it in properly every time.

Handing over

Clients ask for different formats: a PDF for sign-off, a Word file to comment on, and Markdown for their engineers. Export all three from one source on the same day. Copies made by hand drift apart as soon as one of them is edited, and that is how two versions end up in circulation.

Use this checklist for each handover:

  1. Confirm the source carries the approved version label, for example v1.2, and that drafts are labelled separately, for example draft-3.
  2. Check that every template section is present, that every requirement and deliverable has a unique ID, and that no placeholder text or old client names remain.
  3. Export the PDF for sign-off as orrin-retail-catalogue-scope_v1.2.pdf. File names are lowercase, use hyphens instead of spaces, and read client, document, version.
  4. Export the Word file for comments as orrin-retail-catalogue-scope_v1.2.docx, and the Markdown file for engineers as orrin-retail-catalogue-scope_v1.2.md, using the same base name.
  5. Open all three files and check that the version label, the date and the IDs REQ-004 and D5 match in each.
  6. Write a short cover note with the version, the date and the change IDs included since the last version, for example CR-003.
  7. Record the send in the change record: date, recipients by role, file names and the sign-off due date.
  8. Keep the export set in the project folder and mark older versions as superseded instead of deleting them.

A worked change record

Orrin Retail is a fictional client. It signed scope v1.0 on 2026-09-08. Every later request is written into the change record before any work starts. Here is the record for the first weeks after sign-off:

ChangeDateChange requestedRequested byApproved byEffect on deliverablesEffect on timelineOutcome
CR-0012026-09-22Add a size guide page to the product templateClient marketing leadClient product owner and agency account leadD3 gains one page type. Scope moves to v1.1.M2 moves from 2026-10-02 to 2026-10-09Approved
CR-0022026-10-05Show live stock levels on product pagesClient engineering leadClient product owner and agency account leadNone. Recorded as out of scope in v1.1.NoneDeclined. It needs its own integration agreement.
CR-0032026-10-14Change D5 from a PDF guide to a Markdown file for the client's engineersClient engineering leadClient product owner and agency project leadD5 format changes. The same source exports to Markdown, so the work itself is unchanged.NoneApproved. Scope v1.2.

The record settles disputes because it holds dates, names, roles and the version each decision applied to. Suppose the client's marketing lead writes on 2026-10-20 that live stock was always part of the project. The agency does not argue from memory. It shows CR-002 with its date and decision, and it points to the out-of-scope list in v1.1, which the client signed on 2026-10-06 and which names live stock. The argument is then about two signed documents rather than who recalls the call. The same record shows that the size guide was added formally, with its effect on the timeline, so the agency is not relying on memory or trust either.

Common ways agency specs go wrong

How Wordspecs supports this

Wordspecs offers fixed templates for product specs, datasheets and API overviews, saved templates for your own house format, export to Markdown, PDF and Word, and on the Team plan shared templates and version history. Your house template is saved once, new documents start from it, and each export comes from the same source. See the sample sheets and join the waitlist.

Related: spec sheets for teams.

Join the waitlist