Managing SOW & Document Templates
Published on June 15, 2026 QuoteX
PSC Document Templates: Setting Up Consistent SOW Documents
PSC Document Templates let administrators define predefined formats and structures for generating Statements of Work (SOW). Instead of rebuilding the document for every deal, you configure the layout once and PSC assembles each SOW from that template. This keeps legal language, project descriptions, and financial summaries consistent across every customer engagement.
| ⓘ | IMPORTANT Document templates specify the predefined format used when PSC generates SOW documents. A template is made of two parts: a template record (the container) and one or more document sections (the content that appears in the SOW). |
Why Use Document Templates?
- Consistency: every SOW uses the same approved structure and wording.
- Legal accuracy: standard legal boilerplate is maintained in one place and reused automatically.
- Live data: SOQL-driven sections pull current Quote, Timeline, and Resource data into the document at generation time.
- Speed: sections can be created manually or imported in bulk from a sample CSV.
- Multi-currency support: each template is tied to a currency, so you can maintain separate templates (for example, one for USD).
How a Document Template Is Structured
Setting up a template is a two-stage process. Complete Stage 1 before Stage 2, because sections can only be added to an existing template record.
| Stage | What You Create | Purpose |
| Stage 1 | Base Template (PSC Document Template record) | The header record that holds the template name and currency. It acts as the container for all sections. |
| Stage 2 | Template Sections (PSC Document Section records) | The individual blocks of the SOW, such as static legal text or dynamic data tables, shown in a defined order. |
Stage 1: Create a Base Template
The first step is to create the container for your document sections. This record does not contain any SOW content itself; it simply defines the template that your sections will belong to.
- Navigate to the PSC Document Templates tab in the Pre Sales Cloud Admin App.
- Click New.
- Template Name: assign a unique, descriptive name (for example, "General - SOW Template (USD)"). Including the purpose and currency in the name makes templates easy to tell apart later.
- Currency: specify the currency for this template.
- Save: this creates the header record for your document structure.
Figure 1: Creating the PSC Document Template header record with its name and currency.
Stage 2: Define Template Sections (The Display Settings)
Once the template record is created, you must define the individual sections that make up the SOW. This is done through the PSC Document Section related list on the template record. Each section represents one block of the final document.
Each section typically consists of:
- Display Order: a numerical sequence (for example, 1, 2, 3) that determines where the section appears in the document.
- HTML Content: static text, headers, and legal boilerplate that stays the same in every SOW.
- SOQL Query: a dynamic query used to pull specific data from the Quote, Timeline, or Resources into the document (for example,
SELECT Name, psce_Complexity__c FROM...).
Figure 2: The PSC Document Section related list on a Document Template record.
| ⓘ | How sections are built: the configuration sections associated with a Document Template record are dynamically constructed at runtime. This means the document is assembled from your section records each time an SOW is generated, so any change you make to a section is reflected in the next document produced. |
Section Types: Paragraph vs. Table
When creating a section you choose one of two types. Choose the type that matches the content you want to show.
| Type | Best Used For | Fields You Complete |
| Paragraph | Static content such as introductions, legal terms, assumptions, and other boilerplate. | Display Order and HTML Content. |
| Table | Dynamic data tables generated from a SOQL query, such as quote lines, timeline phases, or resources. | Display Order, Show Table Header, SOQL Query, Table Config JSON, and Table Style JSON. |
Steps to Create a Document Section
Follow these steps to create document sections for a Document Template record. Alternatively, you can download a sample CSV (the link is at the end of this article) for document section records and use the Salesforce native import wizard to load PSC Document Section records against the Document Template record you created (for example, General - SOW Template USD).
- Go to the Related tab on the detail page of the Document Template record (for example, General - SOW Template USD).
- Click the New button in the PSC Document Section related list to start a new document section.
- Select the Type of the document section: Paragraph or Table.
- Assign a unique Display Order for the section, ensuring a chronological order for proper display in the document.
- If it is a static paragraph section, add the HTML Content for that section.
- For dynamic data tables generated through a defined SOQL Query, check the Show Table Header box so that column headings are displayed.
- Include the SOQL Query for the section, using the {pv0} merge field to dynamically merge the Quote Id into the SOQL query at runtime. This ensures each SOW only shows data belonging to its own quote.
- Add the Table Config JSON (in JSON format) to specify what to display in the dynamic data table.
- Include the Table Style JSON (in JSON format) to specify how to display the dynamic data table.
- Click Save to save the document section.
- Repeat the steps above to add multiple document sections, in the chronological order in which they should appear in the SOW/Document.
Figure 3: Creating a PSC Document Section and completing its fields.
| ✔ | Prefer bulk setup? The steps above describe manual creation of document sections. If you would rather load many sections at once, download the sample data CSV for document section records (see the download links below) and import it with the Salesforce native import wizard. |
Tips and Common Pitfalls
| ⚠ | Check these first if a section does not appear as expected: | Make sure every section has a unique Display Order; the order controls where each block appears in the SOW. | For Table sections, confirm the SOQL Query includes the {pv0} merge field so the Quote Id is merged at runtime. | Confirm the Table Config JSON and Table Style JSON are valid JSON (matching braces, quotes, and commas). | Use Paragraph for static text and Table only when the content comes from a SOQL query. | Add sections to the correct Document Template record, especially if you maintain several templates for different currencies. |
Quick Reference
| Field | What It Does |
| Template Name | Unique name that identifies the template (for example, General - SOW Template (USD)). |
| Currency | Currency used by the template. |
| Type | Paragraph (static) or Table (dynamic). |
| Display Order | Position of the section in the generated document. |
| HTML Content | Static text, headers, and legal boilerplate. |
| Show Table Header | Displays column headings for dynamic tables. |
| SOQL Query | Pulls data from the Quote, Timeline, or Resources; use {pv0} for the Quote Id. |
| Table Config JSON | Defines what the dynamic table displays. |
| Table Style JSON | Defines how the dynamic table looks. |
Download the Sample CSV
Use either link below to get the sample document sections CSV for the Salesforce native import wizard.
| Google Public Link: DOWNLOAD CSV | Direct Download Link: DOWNLOAD CSV |
Knowledge Article Number: KA-00015