Name the people and artifacts

Map three lanes:

  • service team: prepares, revises, schedules, and delivers;
  • client: reviews, asks questions, approves, rejects, or delegates; and
  • record: stores the version, request, response, date, and next owner.

Give every approval object a stable name, version, and destination. “Latest draft” is not a durable identifier when an attachment, shared document, and exported PDF can all diverge.

Follow one ordinary journey

Start when the work becomes reviewable:

  1. staff freezes or labels a version;
  2. staff sends an approval request to named approvers;
  3. the record captures sent time and requested response date;
  4. the client opens or acknowledges the request;
  5. the client approves, rejects, or asks for changes;
  6. staff confirms the decision and assigns the next action; and
  7. the final artifact and decision remain linked.

Beside every step, record channel, artifact, owner, expected time, and proof of completion.

Add the exceptions before selecting a tool

Walk through:

  • two client contacts disagree;
  • the approver delegates while away;
  • feedback arrives on an older version;
  • the client replies “looks good” without naming the artifact;
  • approval is late but the delivery date is fixed;
  • silence is mistakenly treated as approval;
  • the client withdraws approval after downstream work begins; and
  • urgent approval happens by phone.

For each exception, decide who resolves it, which work pauses, what evidence is recorded, and how the normal journey resumes.

Find the smallest coherent improvement

The first improvement may be process, not software:

  • one stable version identifier;
  • one approval owner on each side;
  • four explicit states: preparing, awaiting client, changes requested, approved;
  • a visible sent date and response date;
  • a reminder rhythm; and
  • a rule that phone decisions receive a written confirmation.

This can live in a shared tracker while the team learns. A portal becomes more plausible when volume, external access, file sensitivity, or client confusion makes the simple record inadequate.

Use the workflow-map artifact

Create one row per handoff:

Step Staff action Client action Record changed Version Owner now Clock Exception path
Review ready
Request sent
Response received
Decision confirmed
Work resumed

The map is done when a new staff member can locate the authoritative version, name the next owner, distinguish waiting from approved, and recover a phone or wrong-version exception without relying on one person's memory.