A written agreement before work starts
The proposed agreement would describe the tasks, deliverables, fees, payment schedule, client responsibilities, and any approval points. Extra work would be discussed and agreed separately.
Practical support. Clear expectations.
A discussion guide for setting up an administrative support relationship, from the first conversation to the final handover.
The proposed agreement would describe the tasks, deliverables, fees, payment schedule, client responsibilities, and any approval points. Extra work would be discussed and agreed separately.
Discuss what information is confidential, how it may be used for the agreed work, and who may access it. A confidentiality clause or separate NDA can record the agreed obligations.
Use individual user invitations and the minimum access needed wherever the client’s tools support them. Discuss multi-factor authentication and secure credential sharing where invitations are unavailable. Please do not send passwords through the website enquiry form.
Agree on working hours, time zone, preferred channels, check-in frequency, and expected response times. Identify tasks that need explicit approval, such as sending client messages, making purchases, or changing important records.
The written agreement should explain what each package covers, how time is tracked, how additional work is priced, and how either party can end the engagement.
Agree who owns completed work, how reusable templates or third-party materials are licensed, and how client files are returned. Include access removal and a practical retention or deletion schedule at the end of the engagement.
Before client information is shared with a new tool, AI service, or subcontractor, discuss the purpose, permissions, and any processing outside the client’s country. Record the tools and arrangements the client approves.
Tell us what support you need and which systems or information the work involves. Avoid including sensitive client records in your initial enquiry.
Enquire about support