Skip to content

Documentation written your way

DownloadSpeak to sales

A demo of the FusedFrames desktop app, showing a document library's Template tab: the structure (the sections and fields) that every document in that library is written to.

Every document produced in the format you set

Template
What every document holds. You cannot change this after you create the library.
Template type
Custom template
Section 1
Section title
Document control
Section type
Fields
Subheading
Identifiers, ownership and review dates, carried on every controlled document.
Field 1 label
Document ID
Field type
Single line text
What this field should contain
The controlled identifier this procedure is filed under in the quality system. Use the existing prefix and number for the owning function rather than creating a new one.
Example 1
SOP-FIN-014
Example 2
SOP-FIN-021
Required
Field 2 label
Version
Field type
Single line text
What this field should contain
The revision this document is at. The major number moves when the procedure itself changes, the minor number when only the wording does.
Example 1
3.0
Example 2
2.1
Required
Field 3 label
Process owner
Field type
Single line text
What this field should contain
The team accountable for keeping this procedure correct and current, not the individual who happened to be recorded carrying it out.
Example 1
Finance operations
Example 2
Accounts receivable
Required
Field 4 label
Next review
Field type
Single line text
What this field should contain
The date this procedure must next be reviewed, twelve months from the last approved revision unless its risk rating says sooner.
Example 1
12 March 2027
Example 2
01 September 2026
Required
Section 2
Section title
Purpose and scope
Section type
Fields
Subheading
Why the procedure exists and exactly where it applies.
Field 1 label
Purpose
Field type
Multi line text
What this field should contain
What this procedure guarantees, in one or two sentences. State the outcome it protects and the standard it has to meet, not the steps that get there.
Example 1
Ensure every refund is authorised, recorded against the original payment and confirmed to the customer within one working day.
Example 2
Ensure every supplier invoice is matched to an approved purchase order before it is scheduled for payment.
Required
Field 2 label
Scope
Field type
Multi line text
What this field should contain
Who this applies to and where it stops. Name the boundary clearly and point at the procedure that takes over beyond it, so nothing falls between two documents.
Example 1
All card refunds up to $500 raised by the finance operations team. Refunds above $500 follow SOP-FIN-021.
Example 2
All UK supplier invoices below £10,000. Overseas invoices follow SOP-FIN-032.
Required
Field 3 label
References
Field type
Bulleted list
What this field should contain
The controlled documents, policies and forms this procedure depends on or hands off to, one per line. Cite them by document ID so the chain can be followed in an audit.
Example 1
SOP-FIN-021: Refunds above $500
Example 2
POL-FIN-002: Refunds and returns policy
Required
Section 3
Section title
Responsibilities
Section type
Timeline
Subheading
Who does what in this procedure, by role.
Field 1 label
Role
Field type
Single line text
What this field should contain
The role that carries this responsibility. Always a role, never a named person, so the procedure survives someone moving on.
Example 1
Finance operations analyst
Example 2
Finance manager
Required
Field 2 label
Responsibility
Field type
Single line text
What this field should contain
What this role is accountable for within the procedure: performing it, checking it, approving it or being informed of it.
Example 1
Raises the refund and records it against the original payment.
Example 2
Approves any refund above the analyst's authorisation limit.
Required
Section 4
Section title
Procedure
Section type
Timeline
Subheading
The authorised steps, in the order they must be carried out.
Field 1 label
Application
Field type
Single line text
What this field should contain
The system this step is carried out in, named as it appears on screen rather than as a category: “Stripe”, not “the payment provider”.
Example 1
Stripe
Example 2
Admin panel
Required
Field 2 label
Instruction
Field type
Single line text
What this field should contain
A single instruction, starting with a verb, covering one meaningful action. Specific enough to follow without prior knowledge of the system.
Example 1
Refund the full amount and set the reason to Requested by customer.
Example 2
Mark the order as refunded and attach the refund reference.
Required
Field 3 label
Expected result
Field type
Single line text
What this field should contain
What the operator should see that confirms this step worked, so they can stop and escalate if they do not see it.
Example 1
A Refund issued confirmation appears against the payment.
Example 2
The order status reads Refunded.
Required
Section 5
Section title
Revision history
Section type
Timeline
Subheading
What changed at each approved version and who approved it.
Field 1 label
Version
Field type
Single line text
What this field should contain
The version number this entry describes. One entry per approved revision, newest first.
Example 1
3.0
Example 2
2.0
Required
Field 2 label
Description of change
Field type
Multi line text
What this field should contain
What actually changed in the procedure at this revision, in enough detail that an auditor can see why the version moved.
Example 1
Refund window extended from 14 to 30 days after the returns policy changed.
Example 2
Manager sign-off added for refunds above $500.
Required
Field 3 label
Approved by
Field type
Single line text
What this field should contain
The role that approved this revision. A role rather than a person, so the record survives someone leaving.
Example 1
Head of finance
Example 2
Quality manager
Required

Build the exact structure you need

  • Section

    Fields

    Information filled in once for the whole document.

  • Section

    Timeline

    A series of entries, listed in the order they happened.

  • Field

    Single or multi line text

    A short value on a single line or longer text over several.

  • Field

    Bulleted list

    A list of short items, one per line.

Frequently asked questions

Start recording today

DownloadSpeak to sales