What to write in the Process field

The Process field is where the mapping starts. Describe how the service actually runs, start to finish, in order, in your own words: inquiry, booking, onboarding, the work itself, delivery, offboarding. Whatever your real sequence is, write it in the order it happens.

Include the touchpoints

The strongest intakes name the moments a client actually touches: when you email, what you send, what the client fills out, when calls happen, when money is due. Those touchpoints become the actions and triggers in your Workflow Map.

The mapping works from what you write. Thin intake produces a thin map. A real start-to-finish description produces a build-ready one.

What happens when something is unclear

Missing details are not silently invented. Where something is unclear, the Workflow Map states the assumption it made rather than guessing quietly. You can correct the assumption and revise, but the cleanest path is a complete description the first time.

A strong example

Willow Lane Design, brand design service: "Client inquires through my site form. I send a pricing guide, then book a discovery call. If we are a fit, I send the proposal, contract, and deposit invoice together. Once paid, they get a welcome email and a brand questionnaire, and we book a kickoff call. Design takes three weeks with a check-in email at the end of each week. I present concepts on a call, collect revisions through a feedback form, then send final files, the closing invoice, and an offboarding email with a testimonial request."

A too-thin example

Same business, same service: "Client books, I design their brand, then I deliver the files."

Both describe the same service. Only one gives the mapping enough to build from.