IT managed service providers
The agreement signed once,the schedule reissued when it moves.
Send the master agreement and the per-seat schedule as one pack, get both signed, and keep the version the client actually agreed.
Recipients
Everyone is asked at the same time.
- R. HartleySignerr.hartley@hartleyandco.exampleSignedSigned 04/06/2026 11:02
- J. OkaforSignerj.okafor@okafordesign.exampleViewedViewed 04/06/2026
- Accounts, Okafor Design LtdCCaccounts@okafordesign.exampleSent
The three documents
Agreed once, reissued when the seat count moves.
The master services agreement
Liability, term and termination, data protection, intellectual property, what happens at the end. Agreed once with a client and reused for everything after it.
The service schedule
What is being provided and at what price: help desk, monitoring, backup, security, per user per month. It names the seat count and the term, which is the pair of facts a renewal conversation twelve months later turns on.
The data processing terms
The terms that govern the personal data you handle on a client’s behalf. They travel with the agreement as part of the same pack rather than as an attachment nobody can later find.
Project statements of work and hardware orders go through the same mechanics if you want them to. They are not what this page is about.
Where this sits in onboarding a client
Before the first device is touched.
The agreement is the document most likely to be handled loosely, because when it should be signed the client is keen to start and so are you. A year on there is a disagreement about what the monthly fee covered, and the answer is in an attachment that has been through two mailbox migrations.
This sits in front of your ticketing, monitoring and billing, at the point where what was bought is settled. It carries the agreement, the schedule, the signature and the evidence around all three.
Keep the agreement and the schedule as one pack
The master agreement, the service schedule and the data processing terms travel together as a template, so a client signing at a new seat count gets a fresh schedule rather than an amended copy of the old one.
Send the agreement and the schedule as one pack
Master agreement, service schedule and data processing terms complete as a single signed record with one certificate. On the next client the agreement is already drafted and only the schedule changes.
Reissue when the seat count moves
A client that grows from forty seats to sixty gets a revised schedule, agreed, with the original left intact and dated. A billing dispute becomes a two-minute conversation instead of a search through a shared mailbox.
Put your next onboarding agreement through it.
What you can produce when the invoice is queried
Managed services are sold per seat, per month, on terms that change as a client grows. So the question is rarely whether an agreement exists. It is which version applies now, whether the client agreed to the tier they are being billed for, and whether the work started before the new figure was agreed. A dated, agreed document that neither side can alter answers that in a link. A folder of PDFs called MSA_final_v3 does not.
The certificate
Produced automatically when the last signature lands. Each signature with its time, actor and IP address, a fingerprint of every document in the pack, and a QR code linking to an independent check.
Checkable without you
A client or their adviser can verify a completed agreement themselves, with no account and no login. It confirms the document, the signers and that the chain is intact, without disclosing what the document said.
Verify a document →CecurSign
Certificate of Completion
- Subject
- Letter of engagement 2026/27
- Created
- 04/06/2026 09:12 UTC
- Sent
- 04/06/2026 09:14 UTC
- Completed
- 05/06/2026 16:41 UTC
Documents
Engagement letter and schedules.pdf (7 pages)
SHA-256: a4f1c9e0b7d3
Signers and recipients
- R. Hartley (Signer)Signed 04/06/2026 11:02 UTC
- J. Okafor (Signer)Signed 05/06/2026 16:41 UTC
Scan to verify
Envelope ID
9c1f2a34-5b6d-4e71-8f90-2ad4c6e13b58
What you would actually be using
The parts of CecurSign that matter to it managed service providers, and what each one does here.
Templates
The master agreement and the per-seat schedule as two documents that travel together, so a client signing at a new seat count gets a fresh schedule rather than an amended copy of the old one.
Build a document once with its fields, its signers and its reminders, then send it as often as you need without rebuilding it.
Sending for signature
The schedule names the seat count and the term, which is the pair of facts a renewal conversation twelve months later turns on, and the client signatory and the data protection contact are both asked for it.
One person or several, in a set order or all at once, with a deadline and a copy to whoever else needs one.
Client records
Which clients are inside a term, which have one ending and which are running on nothing, taken from the schedules they signed.
Your clients, and every document you have sent each of them, with its date, its status and its certificate.
Certificate of completion
What was agreed, at what seat count and on what date, for the month the invoice is queried.
Produced when the last signature lands: every signature with its time, the person who made it and their IP address, and a fingerprint of each file.
API and webhooks
Raise the agreement from the system you already run the service desk in, and be told the moment it is signed rather than going to check.
Drive it from the system you already work in, and be told the moment something is signed rather than going to look.
What providers ask before they buy
Short answers to the ones that come up first.
Does this replace our PSA or ticketing system?
Our contracts are twelve-month rolling. Do they renew automatically?
Can we show a per-seat price that scales?
Can a client sign this on a phone?
More detail on how a document is sent, signed and proved on the e-signature page, or see how other companies use it on the industries index.
See the document itself
The whole thing, section by section, with the priced schedule attached. Free to read, and nothing to sign up for.
These show structure rather than wording, and where your professional body publishes model wording you should use theirs. Every one we publish is in the specimen gallery.
How it fits your documents
Send a document for signature, or sign one yourself. This is what each looks like in your line of work.
E-signature
A new client reads your service description and the data processing terms beside the master agreement, with a record of what they opened.
Sending for signatureSelf sign
A vendor partner form, a security questionnaire sign-off, or an internal approval: signed by you alone, in one sitting, with a certificate.
Signing something yourselfWhat to read next
The parts of the help centre this page assumes, in the order you would meet them.
- Creating a templateSet up a document you send often, with the fields already in place.
- Sending, and what happens nextWhat we do the moment you press send, and how to follow progress.
- Adding the people who need to signSigners, approvers and people who only need a copy, and how they differ.
- The audit trailEverything we record about an envelope, and why it cannot be edited.
Everything else is in the help centre.
Put your next service agreement through it
Build a schedule from your own per-seat pricing, send it to a real client, and look at what comes back.
No credit card required.