BoardSnap is an iOS app that reads a workflow diagram whiteboard — sequential steps, decision branches, actor labels, and handoffs — and produces a structured written workflow description in one snap.
Workflow diagrams are essential for understanding how work actually moves through a team or system. They reveal handoffs that nobody talks about, decisions that have no explicit owner, and steps that are supposed to be one minute but are actually taking two days. Drawing the diagram forces the team to describe the process precisely — vague processes become precise when you have to put every step in a box and every handoff on an arrow.
The whiteboard is the right tool for this because workflow diagrams evolve during the session. You start with what you think the process is, and someone in the room says 'actually, there's a step before that' or 'that handoff doesn't go to Design, it goes to Legal first.' The board gets revised in real time. The final board is the accurate version.
But workflows on whiteboards are process documentation, and process documentation needs to live somewhere accessible. A whiteboard workflow that gets photographed and filed in a folder is not a living document. It won't be updated when the process changes. A clean written workflow description, stored in the team's wiki, gets updated.
At the top of the board, write the workflow name and its scope: 'Customer Onboarding — from signup to first value.' Draw horizontal swim lanes for each actor: Customer, Sales, Product, Engineering. Label each lane on the left side. Steps in a lane belong to that actor.
Mark the starting point with an oval on the left side: 'Customer submits signup form' or 'Bug is filed in Jira.' The starting trigger defines what kicks off the workflow.
Each step in the workflow is a labeled rectangle. Write the action inside: 'Send welcome email,' 'Schedule kickoff call,' 'Configure account settings.' Place rectangles in the actor's lane. Connect sequential steps with arrows.
Decision points are diamonds with a question inside: 'Is the account enterprise?' with Yes/No branches leading to different steps. Each branch gets a label. Decision points are where the workflow splits.
When an arrow crosses from one actor's lane to another, it's a handoff. Handoffs are where delays and errors concentrate. Mark each cross-lane arrow with the handoff mechanism: 'Email notification,' 'Jira ticket,' 'Slack message.' These are the integration points.
Every workflow path needs an end state — an oval at the right side: 'Customer is active,' 'Bug is resolved,' 'Order is shipped.' If a branch doesn't reach an end state, you've found an incomplete process path.
Open BoardSnap. The swim-lane diagram with actor labels, rectangles, diamonds, arrows, and end states. VisionKit corrects the angle. BoardSnap AI reads the diagram structure — steps, decisions, branches, and cross-lane handoffs.
A written workflow description organized by actor lane. Each actor's steps are listed in sequence with decision branches described as conditional logic: 'If X, then Y; else Z.' Handoffs are described with the mechanism noted. The end states are listed. The output is a readable process description — paste it into a team wiki, an SOP document, or an onboarding guide.
The support team drew the escalation workflow to understand why tier-2 tickets were taking five days to resolve. The diagram revealed a handoff from tier-1 to tier-2 that went through email (slow) instead of a Jira ticket transition (instant). BoardSnap captured the workflow. The fix was implemented the same week. Resolution time dropped to two days.
The editorial team mapped the article lifecycle from assignment to publication. Six steps, two decision points, four actors. The diagram showed that legal review was happening after design, causing redesigns when legal requested changes. BoardSnap produced the process doc. The workflow was resequenced — legal review moved to step three.
The team diagrammed the deployment process to identify manual steps that could be automated. Eleven steps, two decision branches, three actor lanes. BoardSnap produced the process description. The engineering lead used the output as the basis for automating four of the eleven steps.
Yes. Standard flowchart shapes are recognized: rectangles as process steps, diamonds as decisions, ovals as start/end states. The shapes are used along with the labels inside them to determine each element's role in the workflow.
Loop-back arrows are read as conditional returns. Label the loop-back arrow with the condition: 'If not approved, return to Review.' BoardSnap will describe the loop in the output as a conditional repeat of the relevant steps.
Yes. Many teams draw the 'as-is' workflow on one board and the 'to-be' workflow on another. Snap both boards in the same project. The AI chat can compare the two and help identify the specific steps that changed between the current and proposed workflow.
Snap the board, ship the action items in ten seconds.