A useful back-office support arrangement identifies what needs handling, who reviews the result and where decisions remain with your business.
Begin with the departments, locations and systems involved. Explain which work your current team handles and where you need support.
You can start with a recurring workflow, a department or a broader requirement across the chain. The aim is to connect the support discussion to the way your business operates.
Describe the information needed to begin, the work to be performed and the output to be reviewed. Include dependencies on store staff, head office and software vendors.
For an invoice workflow, for example, preparation, clarification and payment approval are separate steps. A scope should name the responsibility for each.
The provider takes responsibility for the agreed recurring workflow and its review process. The engagement needs to state the output, unresolved-item ownership and retained operator approvals.
The buyer directs the assigned people and retains day-to-day process supervision unless the agreement states a different division.
With co-managed support, work is divided between the operator’s existing team and the provider. Each task needs an owner and a route for questions that cross the team boundary.
Identify the people who supply information, review the work and approve a decision. Confirm the systems and permitted tasks involved.
Working hours, workload assumptions and transition requirements are part of the engagement discussion. They should match the actual requirement and responsibilities agreed.
A useful open-item record explains the location or process, the question awaiting a decision and the person responsible for the next action.
The review should distinguish work completed from work awaiting information or approval. That helps each party understand the status being reported.
Include the team in the scope discussion. Identify the work it will retain and the tasks for which you want additional support.
Describe the systems already in use and the workflow requirement. Any system change, vendor task or implementation work needs its own scope.
Share the departments involved, broad workflow and current team setup. Detailed private records and credentials are not needed to explain the initial requirement.
Tell us the work you want handled and the responsibilities you want to retain.