Skip to content
Lesson 3 of 4Written guide available

Align the proposal with delivery

Carry the approved promise into the project plan.

Video in production

Our team is recording this lesson. Start with the written guide and exercise below.

Read the lesson

The idea to put into practice.

The proposal should describe deliverables, assumptions, commercial terms and approval. Delivery needs those details before planning. A client name alone is not a useful handover.

Review the agreed version and exceptions. Keep scope, dates and price together. An unusual term can affect how work should start or be scheduled.

Documents, Deals and Projects show the connected direction. Live signing and automation remain in development; a preview status is not legal evidence of agreement.

A useful way to approach it

  1. Identify the approved version.
  2. Review scope, dates and terms.
  3. Hand over inputs and assumptions.
  4. Assign change responsibility.

Try it with fictional work.

Write a sales-to-delivery handover with scope, dates, terms and a risk to resolve before planning.

Before you move on

  • Version identified
  • Scope and price align
  • Inputs transferred
  • Exceptions clear

Check your understanding.

What should travel into delivery?

Keep something useful.

Download the action sheet to reuse the exercise and checklist with your team.

Ready to move forward?

Try the exercise, check your understanding, then mark this lesson complete.

Progress is stored only in this browser. It does not sync between devices.

Written lessons are available now. Videos are coming soon. Connection-dependent exercises use demonstrations until live integrations become available.

Course material is prepared with AI assistance and reviewed for consistency with Tamaam’s product direction. Suggest a correction.