# Salesforce implementation acceptance worksheet

Use one copy for each important business problem. Agree the business and technical checks with the people who will accept the work.

## 1. What needs to improve?

**Business problem:**  
Describe today's difficulty and who experiences it.

**Current baseline:**  
What happens now? Record a measure or a concrete example, and its date.

**Intended business outcome:**  
What should someone be able to do differently?

## 2. What must the system do?

**Technical requirements:**  
Name the required records, relationships, rules, access and system handoffs.

**Scope and exclusions:**  
What is included in this release? What stays manual or waits until later?

**Dependencies and assumptions:**  
What data, access, decisions, licences or other teams must be available?

## 3. What will count as acceptance?

<div class="table-scroll">
<table>
<thead>
<tr>
<th>Check</th>
<th>Agreed test and expected result</th>
</tr>
</thead>
<tbody>
<tr>
<td>Technical acceptance</td>
<td>Write the scenarios, population, reconciliation and important exceptions to check.</td>
</tr>
<tr>
<td>Business acceptance</td>
<td>Write the tasks the intended users must complete and the information they must be able to use.</td>
</tr>
<tr>
<td>Evidence</td>
<td>Name the test record, report, receipt or observation that will support the decision.</td>
</tr>
<tr>
<td>Unresolved risk</td>
<td>Record what is not proven, the consequence and who can accept it.</td>
</tr>
</tbody>
</table>
</div>

## 4. Who owns each decision?

**Business owner and backup:**  
Who prioritizes the process and accepts its operational result?

**Technical owner:**  
Who delivers and supports the technical work?

**Representative users:**  
Who will perform the working scenarios and give feedback?

**Release decision owner:**  
Who decides whether open issues prevent launch?

## 5. What happens after launch?

**Measure and target:**  
Agree a useful measure, target and method. Distinguish usage from business outcomes.

**Review date:**  
Choose a period appropriate to the workflow.

**If the result falls short:**  
Who investigates, how are repairs prioritized, and when is the effect checked again?

**Status / decision / date:**  
Record accepted, accepted with named conditions, or not yet accepted.

---

## Fictional worked example

**Problem:** Enquiries remain unowned. Follow-up depends on someone noticing them.

**Technical check:** Run the agreed routing cases, fallback path and a missing routing-value case. Confirm access for the receiving user and visible exceptions.

**Business check:** The receiving team can find each enquiry, understand the next step and handle it within the agreed response window. A supervisor can identify unowned enquiries.

**Ownership:** Name a sales owner and technical owner. Agree a baseline, target and review date together.

This is an illustrative planning example, not a completed Salesforce test or a client result.

[Discuss a scoped next step with Logic Conduit](https://logicconduit.com/#contact)
