DUTYGRAPH SERVICES

Process mapping services: map the workflow your team actually runs

Process mapping services that connect the real steps, owners, software, decisions and handoffs in a workflow. One department in about 7 days.

DutyGraph Work flows showing supplier onboarding tasks and recorded handoffs with fictional Cobalt sample data
Actual DutyGraph components · Fictional Cobalt sample · AI roles are proposals.

Process mapping services record the workflow your team actually runs: what arrives, who acts, which decisions change the path, which software is used and what the next team needs. DutyGraph maps it from your people's own answers, so you get a current-state map, the handoffs where work waits, and the questions still unresolved.

Book a demo

How it starts: one department, or one process that matters, in about 7 days. Scope, participants, fees, timing and data-handling terms are agreed on a short call before work begins.

What do process mapping services include?

A scoped engagement covers discovery, the map and the review. Discovery gathers the evidence from leadership context and employee accounts. Mapping organizes it into a usable representation. The review puts the map back in front of the people who do the work so they can correct it.

A diagram may include actions, inputs, outputs, decisions, people and measures; ASQ describes these as common elements of a process flowchart. ASQ: Flowchart For DutyGraph, a useful task record also connects the work to its duty, purpose, systems and human checkpoints.

What should you ask process mapping consultants?

The important question is not who draws the cleanest flowchart. It is who can establish what the team actually does, where accounts disagree and which handoffs need evidence. Ask how the map is checked, who checked it and what the consultant does when two departments describe the same step differently.

The aim is a reviewable description of work, not an attractive diagram nobody can verify. A workflow can also cross departments: the organizational chart and the workflow map answer different questions.

How long does process mapping take?

One department takes about 7 days: a 2-hour session with your leaders on day 1, each person checking their role and talking about their own work on days 2 to 4, then the map, the team check and the readout on days 5 to 7. Each person spends about 20 minutes. A workflow that crosses several departments takes longer, because more accounts have to be reconciled.

What do you need from our team?

Begin with a sponsor, a workflow owner and the people who send, perform, review or receive the work. Agree the boundaries and the information that may be collected. Existing SOPs, sample forms and approved system records help, but incomplete documentation is not a reason to invent the missing steps.

Leadership establishes the context. Each participant then answers a private request by voice or text. We review the accounts together and follow up where they do not agree. The process discovery interview guide shows the kinds of questions that make those answers useful.

What does the business process map make visible?

A scoped engagement should establish which of these outputs matter:

  • The normal path from trigger to accepted result.
  • Task owners and performers, including uncertain or disputed ownership.
  • Required inputs, systems and handoff conditions.
  • Exceptions, decisions and human review points.
  • Sources supporting the map and questions that remain unresolved.

A current-state map describes what the team reports doing now. A future-state proposal describes a change they may choose to make. Keep them separate so a proposed improvement is not mistaken for an existing process.

Example: supplier onboarding

Illustrative workflow: A purchasing employee collects supplier information. Finance checks billing details. A manager decides whether the supplier can be used. Someone creates the record in the business system.

A useful map asks what happens when the legal name differs from the bank information, who may resolve the difference and whether an employee is describing a current rule or a workaround. It records that explanation without automatically granting permission to approve a supplier.

The cross-functional handoff guide explains how to test whether the next person can actually start work with what they receive.

Does every finding need a new platform?

No. A mapping exercise may point to clearer intake, a responsibility decision, a better system connection or additional measurement. It may also identify a bounded task worth testing with AI. The mapping work should not assume automation is the answer before the workflow is understood.

If the main decision is what to improve, start with the business operations audit. If a workflow is already understood and you need to check whether one task is ready for AI, use the AI readiness assessment.

How much does process mapping cost?

The scope and the price are agreed on a short call before anything starts. The factors are the workflow boundaries, the number of participants, the departments involved and how much reconciliation the accounts need. See how pricing works.

Common questions

Do you interview everyone live?

No. Private voice and text requests let participants answer on their own schedule, in about 20 minutes each. That changes how evidence is collected; it does not remove follow-up or direct observation where the work needs it.

Is this process mining?

No. Process mining reads system activity logs. DutyGraph starts with the people and the documents. The methods can complement each other; read process discovery, process mining and task mining compared before choosing one.

What software do we get the map in?

You keep the readout and the files from your engagement. The map lives in your DutyGraph workspace, and AI tools such as Claude, ChatGPT, Cursor or any MCP client can read it. Business-system connectors are built during a project, not sold as a finished catalogue.

Can you map a process that crosses departments?

Yes, and that is usually where the useful findings are. Agree the first and last step of the workflow with the sponsor, then include everyone who sends, performs, reviews or receives the work in between.

What if two teams describe the same step differently?

The map records both accounts and marks the difference as unresolved until the right people decide. A disagreement about who owns a step is a finding, not an error to tidy away.

Book a demo