Choose a document by the relationship it describes

Start with the real activity

Write down what is happening before choosing a title. Are you hiring someone to deliver a project, sharing sensitive business information, renting a property or describing how a website operates? The document should follow that relationship. A familiar name is not enough if its sections address a different situation.

For a service agreement, collect the deliverables, responsibilities, timing and payment arrangement. For an NDA, describe the information to be shared, its purpose and the people involved. Keep unanswered questions visible. Choosing a document is a starting point for review, not confirmation that its clauses fit your circumstances.

Separate contracts from website information

A contract brief describes a proposed arrangement between parties. A website policy brief describes actual operations. Preparing a privacy or cookie policy therefore starts with an inventory of the website’s forms, tools and data flows, rather than a list of promises copied from another business.

For a legal notice, gather the operator’s verified details and describe the actual service. Compare the brief with the live site. If a contact form, payment tool or analytics service is planned but not installed, label it as planned in your working notes so it is not accidentally described as current.

Make the brief specific

Use a small table or a clear list for names, roles, amounts, currency and dates. Distinguish the person who negotiates from the person who will sign, and record any uncertainty about representation. For a lease, note the property and intended use; for employment, note the role and working arrangements.

Partnership discussions need their own record of contributions, proposed ownership, responsibilities and decision making. Do not force these into a generic services template simply because it has two signature lines. When several document types appear relevant, list the separate purposes and ask which documents should work together.

Prepare a reviewable next version

Before drafting, write three things: what you already agree, what remains open and which questions need professional review. Give the reviewer enough context to understand the relationship without searching through an entire inbox. Preserve the supporting messages or records separately and identify the version you used.

The next useful milestone is a coherent draft with accurate details and visible open issues. Check the country or region involved before relying on it. An attractive layout, a PDF export or a completed questionnaire does not resolve questions about legal suitability. Treat the document’s substance and its presentation as separate checks.

For example, a freelancer preparing a website project may need a service agreement for the work and a separate record of what client information will be shared. Write down those purposes before combining clauses. If the work later changes, revisit the brief and identify which document needs updating instead of adding the same vague paragraph to every file.

Sponsored