CRONK
A worked example · synthetic information
Follow the work.
See what a better
system needs.
A customer asks for work. Someone plans it. A team completes it. The office sends an invoice. Four familiar steps, with people and information moving between them.
An illustrative design exercise. Scope, permissions and connections would be checked for a real business.
01 / Understand the current work
Where does the information change hands?
The coordinator receives a request by email. A supervisor adds it to a schedule. A team member records hours and materials on paper. An administrator types the same details into accounting.
The point of mapping is to ask what really happens: who agrees the scope, what the team needs before it starts, how completion is confirmed, and who checks the invoice.
Edit this example in the mapper02 / Explore the handoffs
Open a step.
Look behind it.
A usable system needs clear records, responsibilities and exceptions. These are the questions behind a form, an integration or a dashboard.
01 · A request becomes agreed work
What the people need
The coordinator needs enough information to understand the request. The supervisor needs an agreed scope and a reference that follows the job.
What a system could support
A shared job record with a stable reference, a named owner and an agreed status. A form can help capture consistent information; a person still confirms the scope.
What to check
Who can accept the work? What happens when the request changes? Which record is authoritative?
02 · An agreed job becomes an assignment
What the people need
A clear assignment, timing, materials and access to the information required on site.
What a system could support
An assignment view linked to the job, with responsibility and status visible. Select the application around the team's devices, connectivity and existing tools.
What to check
Does the team have a reliable connection? What happens when the schedule changes? How does the supervisor know the assignment was received?
03 · Completed work becomes a reliable record
What the people need
A simple way to record what happened and pass on the information the office actually needs.
What a system could support
Capture completion, time and materials against the same job reference. Show missing information and route the record to the responsible reviewer.
What to check
Who verifies the record? Can an error be corrected with a traceable history? How are late or duplicate submissions handled?
04 · An approved record becomes an invoice
What the people need
Agreed pricing, the reviewed completion record, and a way to reconcile the invoice with the work.
What a system could support
Where the accounting provider supports it, prepare a draft using an approved record rather than retyping it. Keep the review and release decision with the person responsible.
What to check
Are the required API operations available? How will retries avoid duplicates? Which system owns the invoice number and final financial record?
03 / Decide what to build
Start with the smallest
change that resolves the problem.
The first improvement might be a clearer intake form, a shared status view or a simpler completion record. A supported integration may come later, once the information and responsibilities are understood.
The implementation could use existing business software, Microsoft tools, an API connection or a custom application. The choice follows the requirements, including access, licensing, connectivity and maintenance.
AI could help prepare a summary or identify missing information. It doesn't replace deciding who owns the record or who approves the result.
04 / Know whether it helped
Choose evidence
before the build.
Count repeated entries in one completed job. Record how often the office has to chase missing information. Check whether the invoice can be traced back to the reviewed work record.
Agree on a baseline and an outcome with the people involved. Test ordinary work, exceptions and recovery. A working screen is one part of acceptance.
Try it on your operation
What is one workflow
you would like to understand?
The free mapper lets you make a first sketch and take it back to your team. If you want help with the wider operation, recommendations or the build, we can work from that picture together.
Map a workflow Where I can help