The document collection / Service contract

Service Contract Template

Format a service agreement with party details, contract reference, term, and numbered articles. Supply your approved provisions and generate a consistent document for each engagement.

Paper format
Letter
Included
HTML layout + sample JSON
Customization
Content, colors, typography
Rendering
Handlebars + Chromium

Preview the sample document, then make it yours. Change the layout in your editor or clone it into your RelayPDF dashboard to create an editable draft.

Open full-size preview
RELAYPDF / DOCUMENT COLLECTION
Letter HTML → PDF
Make it work for you

From a sample to
your next document.

This layout uses standard HTML and CSS with Handlebars fields. The preview is rendered from the downloadable source and sample data shown below.

Use the sample as a starting point. Your application supplies dates, labels, and calculated amounts; the template handles their presentation.

  1. Personalize the design

    Update the organization name, typography, and CSS accent colors. Replace the sample wording with content appropriate to your business.

  2. Connect your data

    Keep the field structure in the sample JSON and replace its values. Repeating arrays create the document’s rows or sections.

  3. Preview, publish, generate

    Test with your longest content. Publish the draft, then generate PDFs using its templateId and fresh templateData.

What you can customize

FieldPurpose
numberYour document reference; use a stable, unique identifier.
issuedOnDate supplied by your application; ISO dates work with the template’s date formatter.
titleEditable document content. Replace the sample value with your own data.
providerStructured details for this section. Match the nested fields in the sample JSON.
clientStructured details for this section. Match the nested fields in the sample JSON.
termEditable document content. Replace the sample value with your own data.
articlesNumbered agreement provisions with headings and body text.

Start with real sample data

Download sample JSON ↓
Inspect sample JSON
templateData / JSON
{
  "number": "SC-2204",
  "issuedOn": "2026-03-21",
  "title": "On-call signage maintenance",
  "provider": {
    "name": "Northline Press",
    "address": "184 Canal Street\nBrooklyn, NY 11231"
  },
  "client": {
    "name": "Harborpoint Realty",
    "address": "90 Pier Road\nJersey City, NJ 07302"
  },
  "term": "12 months from the date above, renewing month-to-month unless either party gives 30 days notice.",
  "articles": [
    {
      "id": "1",
      "heading": "Services",
      "body": "Provider will repair, replace, and clean wayfinding at dock 3 during business hours, with a four-hour response on weekday calls."
    },
    {
      "id": "2",
      "heading": "Fees",
      "body": "A retainer of $640 per month covers two site visits. Extra visits bill at $95 per hour plus materials at cost."
    },
    {
      "id": "3",
      "heading": "Access",
      "body": "Client will leave the north gate open or provide a code. Provider will call the floor lead before cutting power."
    },
    {
      "id": "4",
      "heading": "Limit",
      "body": "This contract does not cover structural work, electrical upgrades, or damage from vehicles."
    }
  ]
}

Clone through the API

POST /v1/templates
curl https://api.relaypdf.com/v1/templates \
  -H "Authorization: Bearer $RELAYPDF_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Service Contract Template","galleryId":"service-contract"}'

This creates an account-owned draft. Publish it before using its slug or UUID as templateId with templateData on POST /v1/pdf. Follow the complete template workflow →

Will the PDF match this preview?

The preview uses the same HTML and sample data included with this template. RelayPDF renders HTML using Chromium. Use the document’s intended Letter paper size and enable print backgrounds. Review page breaks when you add longer content or more rows.

Can I use my own branding and data?

Yes. Edit the HTML and CSS, replace the sample values, and keep the field names your template expects. Save your customized draft in the dashboard and publish a version when it is ready for your application.

Keep exploring.