Intermediate Requires 1.0.5-beta Updated March 2026

Document Templates and Client Signatures

Create reusable templates, send rendered documents to a project or session, and collect typed signatures from clients.

Mankai stores document templates separately from rendered project documents. That means you can maintain reusable source templates and still keep project-specific signed copies later.

Template Categories

  • General
  • Contract
  • Proposal
  • Agreement
  • Scope of Work
  • Handoff / Credentials
  • Invoice

Macro Support

Templates can resolve values such as client name, business details, totals, remaining balance, project code, session date, session location, and more. Use macros so you do not rewrite the same document over and over.

Sending a Document

When you send a template to a project or session, Mankai renders a project-specific instance and stores it in that record’s document list.

What Happens After Sending

  • The document appears in the client portal
  • A project update can be created automatically
  • Email events can notify the client that a new document is available

Client Signing

Clients can sign documents with a typed full name. Mankai stores signature name, signer ID, signer email, timestamp, IP address, and user agent information on the document instance.

After Signature

  • The document instance is marked signed
  • A project update can be added
  • Email events can notify you that the document was signed

Best Practice

Use document templates for any contract or approval process that should be tied directly to the client portal. If the client needs to revisit it later, keeping it inside Mankai is much cleaner than losing it in email attachments.