When working on SOC 1 and SOC 2 engagements for the same client, you’ll find that multiple controls and tests are shared between both frameworks. In this tutorial, you’ll set up a combined engagement with multiple control testing sheets linked together to streamline testing and reporting.
By the end of this tutorial, you’ll learn to do the following:
Set up a combined SOC 1 and SOC 2 engagement for a client
Link data across sheets using shared columns
The steps in this tutorial can also be applied to other multi-framework engagements.
Before you begin
You should have an account with an admin role, or another role that grants you permission to create engagements and sheets.
Your firm should have sheet templates available for the SOC 1 and SOC 2 frameworks.
Your client's company should exist under the Clients menu.
The controls should be in the client’s Controls menu and include the following:
Relevant mappings to the SOC 1 and SOC 2 frameworks.
Tags to help identify them, like
SOC
Step 1: Create an engagement
Create a new engagement for the client and select this options:
Create from scratch.
Type: Advisory
Sheet Template: No Template
Check Automatically add this client’s controls to the sheet.
Control Tag:
SOC
Step 2: Create a control testing sheet
After creating your engagement, rename your default sheet to Control Testing. Your control testing sheet contains a flat list of all the controls used in this engagement.
Add columns to store tests, results, and any other fields that are part of your firm's control testing methodology.
The magic columns Tasks, Requests, Documents, and Sign Offs are added by default.
Step 3: Create SOC 1 and SOC 2 sheets
Create two new sheets to your engagement named SOC 1 and SOC 2 and select these options for each:
Sheet Template: Select the appropriate template for the framework.
Select Automatically add this company’s controls.
Framework: Select the framework.
Step 4: Link the framework sheets to the control testing sheet
Next, link the columns from the Control Testing sheet to the SOC 1 and SOC 2 sheets. Perform these steps on the SOC 1 and SOC 2 sheets:
Open the Add Column menu and enter values for these fields:
Column Type: select Shared Columns. This column type is used to link sheets and displays columns from another sheet in a 2-way sync.
Sheets: select the
Control Testingsheet from this engagement. This field is where you choose what sheet to link.Shared Columns: keep the default setting (all columns). This field is where you choose which columns from the
Control Testingsheet to share into the current sheet.How do you want to link rows?: select Automatically link rows based on Control Activity. This setting controls how Fieldguide decides which rows from
Control Testingmap to each row on the current sheet.
Select Add column.
Add the shared columns to your SOC 1 and SOC 2 sheets, not to your Control Testing sheet. Be careful not to do it the other way around.
Columns in your SOC sheet that are shared display Control Testing in the column header.
Any data you add to a shared column syncs to any other sheet where that column exists.
Link documents and requests
Link the Documents and Requests from Control Testing to the other sheets. Perform these steps on the SOC 1 and SOC 2 sheets:
To link requests: Open the vertical ellipses menu on the Requests column and select Link Row Requests.
To link documents: Open the vertical ellipses menu on the Documents column and select Link Row Documents.
Remove unneeded columns
If extra versions of the columns on your Control Testing sheet also exist on your SOC 1 or SOC 2 sheets, we recommend keeping the version from Control Testing and deleting the version on your other sheet.
For example, you should remove the Sign Offs column from the SOC 2 sheet that isn’t linked from the Control Testing sheet. That way, you only need to sign off once per control, and it will sync across all sheets in the engagement.
Next steps
Consider following these guides to learn about working your engagement and using additional time-saving features in Fieldguide:
Add requests for evidence to the engagement
Create tasks to delegate work to the engagement team







