Start with eight working rules and a named owner for each. A team working agreement should tell your technicians how work moves when someone is unavailable or a client asks for something outside the plan. Put the usable instructions on a page the desk can find. Keep the detailed procedures one step away.
My test is: what does this do to the board on Monday morning? It should leave the next technician able to identify the current owner and next action without searching a colleague's private messages. I'd write the page around those handoffs, then check it with the people who must follow it.
Write the Action Instead of the Virtue
Cut be proactive from the draft. Say what the technician should notice and who they should tell. A rule about raising a blocked client decision gives the desk something to do; a general instruction to show ownership doesn't assign the next action.
Use the hours and service commitments you've actually agreed. The team needs to know where the current roster lives and how to report an availability change. The roster doesn't read minds.
Keep a named lead responsible for arranging coverage. A technician can report a problem, but that shouldn't leave them guessing which colleague must take their queue. The lead checks the work that needs reassignment and confirms who has accepted it.
Don't use the working agreement to conceal a capacity problem. The model links healthy margins to paying good people well. If the work doesn't fit the available team, the manager needs a staffing or service decision alongside any change to the written rules.
Use a Page the Team Can Act On
Treat the table below as a proposed starting page. Replace its role names with actual people and its general references with the routes your desk uses. The owner checks that each rule can be followed before you ask staff to use it.
| Working Rule | What the Team Does | Who Owns the Arrangement |
|---|---|---|
| Hours and Coverage | Use the published roster and report an availability change through the agreed route. | The desk lead confirms coverage and reassignment. |
| Client Updates | Record the next promised update and arrange coverage if you can’t provide it. | The assigned technician owns the update; the desk lead confirms a replacement. |
| Ticket Notes | Record the action, result, and next step where the covering technician can find them. | The assigned technician maintains the work record. |
| Handoffs | Give the receiving person the relevant context and confirm they accept the next action. | The outgoing technician hands over; the receiving technician accepts. |
| Approved Tools | Use the approved stack and request an exception before adding another work route. | The technical lead approves tools and maintains the instructions. |
| Client Contact | Put actionable client requests into the agreed service route rather than leaving them in private messages. | The receiving technician records the request; the desk lead assigns it. |
| Changes and Extra Work | Use the agreed approval path before promising a change or extra service. | The technical lead handles change authority; the account owner handles commercial decisions. |
| Help and Unresolved Work | Raise a blocker through the named escalation route and state what decision is needed. | The desk lead accepts the escalation and assigns its next owner. |
The page should identify its owner and current version. Link it to the detailed procedures rather than copying the entire knowledge base onto it. A short rule still needs to lead to instructions the technician can use.
Keep the client's service arrangement visible where it changes the action. A general desk rule can't decide whether an unfamiliar request is included in a particular agreement. Give the technician the person who can settle that question.
Keep Client Requests Out of Private Dead Ends
Picture a client asking a technician directly for an extra application while another ticket is in progress. Have the technician put the new request into the agreed route and explain who will respond. Don't let a friendly conversation become an unassigned promise.
The account owner handles a commercial question when the request needs a separate price. The technical lead checks any unfamiliar delivery commitment. The technician should be able to continue the original work without negotiating the new offer alone.
Apply the same rule to a client update promised in a direct conversation. Record the commitment against the work and make the handoff explicit if the technician becomes unavailable. A colleague shouldn't discover the promise only when the client asks why it was missed.
Teach the Rules to Experienced Staff Too
The model calls for a standard technology stack and training every technician on it. Show how the approved tools support the working rules. If the handoff depends on a PSA field, demonstrate the actual field and what the receiving person should see.
Mark Sowden recommends teaching company-specific service-desk standards and their reasons, including to experienced technical staff. He distinguishes those ways of working from vendor-product training. Keep that as his practitioner advice, and explain why your rule exists alongside how to follow it.
Walk a real request through the draft with the team. Ask the next technician to find the required information without coaching from its author. Fix the unclear instruction or missing tool access before assuming staff simply need another reminder.
Check the Handoff Before Adding Another Rule
Have the desk lead inspect a recent reassignment. Check whether the receiving technician could identify the current state and next action from the record. If they couldn't, find the specific gap before rewriting the whole agreement.
Keep the reason for the change beside the page's version record. Tell the team what action changes and who can answer questions. A silent edit leaves people following different versions of the same instruction.
Use the same check when the work moves between your team and the client. Confirm who accepted the next action rather than treating a sent message as a completed handoff. The work stays assigned while the lead resolves an unanswered transfer.
Start with a handoff that required someone to chase a colleague for context. Draft the relevant rule with the technician who sent it and the one who received it. Then use the next comparable request to check whether the written instruction gives them what they need.
mspoutpost.com/articles/team-working-agreement-write-the-desk-rules-clearly
Written by Megan Friesen
MSP Outpost publishes information, not legal, financial, insurance, tax or compliance advice, and reading it creates no professional relationship. For decisions about your business, talk to a qualified professional.