A sound contract does not predict every dispute; it makes ordinary decisions less ambiguous. The Code of Obligations and Contracts gives force to a validly formed agreement and requires good-faith performance. Document quality therefore rests on what both parties understood, accepted and can prove, not the page count of a template.
Negotiation page
- Parties and signing authority verified.
- Outcome, deliverables and exclusions written.
- Customer inputs and their due date stated.
- Stages, schedule and dependencies visible.
- Acceptance procedure and revision count.
- Price, deposit, expenses, tax and due date.
- Intellectual property and portfolio handled.
- Data, confidentiality, exit and dispute organised.
1. Identify before promising
The contract should name provider and buyer, then confirm who can commit each.
| Party | What to verify |
|---|---|
| Freelancer | name, address, identifiers and activity |
| Individual client | identity and contact |
| Company client | legal name, identifiers and office |
| Signer | role and authority |
| Contact | who gives daily instructions |
| Approver | who accepts deliverables |
An employee’s email does not always replace agreement by an authorised representative.
2. Write testable scope
Replace adjectives with objects and criteria.
- Name every deliverable and format.
- State what is expressly excluded.
- List customer content, access and approvals.
- Set a date for every dependency.
- Define a revision and its number.
- Explain how change is priced.
- Set the acceptance test or criteria.
- Address silence after legal advice.
A new request becomes an amendment or change order, not an endless WhatsApp thread.
3. Connect price, time and evidence
Price must say what it includes and when it becomes due.
- Deposit: capacity reservation and refund conditions
- Milestone: delivery or event triggering invoice
- Expense: included, capped or approved
- Tax: confirmed treatment, never improvised
- Delay: reminder, suspension and proportionate consequence
- Evidence: invoice, acknowledgement, transfer and possible withholding
For a professional customer, also check current payment-delay rules and their scope.
A template is a start, not legal advice
Adapt the agreement to activity, customer, data, IP and risk. Have it reviewed when value, duration or dependency is material.
4. Protect output and exit
Distinguish pre-existing tools and know-how from created deliverables. Set licence or assignment, territory, duration, media, source code, fonts, third-party images and portfolio display.
For data: purpose, access, security, processors, incident, return and deletion. For exit: grounds, notice, paid work, files handed over, access revoked and transition assistance.
BelloPOS neither drafts nor signs the contract. Once agreed, a sales tool can only issue and track payment documents corresponding to the validated framework.
Mistakes to avoid
- Starting from a simple “OK”.
- Writing “complete website” with no list.
- Forgetting customer inputs.
- Allowing unlimited revisions.
- Assigning every right without naming it.
- Cutting access with no exit protocol.
Frequently asked questions
Can electronic exchange prove agreement?
Moroccan law addresses electronic exchange; strength depends on process, identity and evidence. Create clear acceptance.
How much deposit should be requested?
There is no universal percentage here. Set it from reserved capacity, purchases, risk and negotiation, then state its treatment.
What if the customer adds a request?
Return to scope and issue a change describing price, schedule and impact before performance.
When should rights transfer?
The contract should state what and when, often linked to payment, after checking third-party works and licences.
Is this a ready-to-sign template?
No. It is a negotiation checklist to adapt and validate for the actual assignment.
What to take away
A useful contract turns assumptions into mechanisms: who delivers what, who accepts, when payment is due, who owns, how change works and how to exit.
Sources
The figures and rules quoted above come from these pages, read on the date given in the article.
- AMDIE, Code of Obligations and Contracts, read 31 August 2026
- Ministry of Justice, Electronic Legal Data Exchange Law, read 31 August 2026
- Ministry of Justice, Consumer Protection Law 31-08, read 31 August 2026
- Ministry of Economy and Finance, payment-term texts, read 31 August 2026
Invoice what the contract provides
After validation, keep quotation, invoice, settlement and any credit connected with the assignment and its milestones.
Read next
Other practical guides on the same subject:
- Auto-entrepreneur invoices in Morocco: fields, sequence and payment evidence
- Declaring auto-entrepreneur turnover in Morocco: from collection to payment
- Student auto-entrepreneurs in Morocco: validate activity, time and real cost before registering
- Morocco auto-entrepreneur quotation template: services and goods