Learn

Architecture & pattern guides

Read the idea, build it on a Grid, prove it in a challenge. Short, practical guides — illustrated with RodGrid's own nodes — on system design, design patterns, flow modeling, and how to get the most out of the app.

All articles

Connectors, off-page links & delays

Replace an edge that crosses the whole page with a labelled jump, move a long flow onto a second diagram, and draw a deliberate wait so nobody takes it for a missing step.

One line across the whole page

A line leaves a diamond near the bottom of a page and climbs towards a card at the top right. Your eye follows it until it crosses another edge, has to guess which of the two carries on, and goes back to start again. By the time it lands, you have forgotten which question sent you there.

The page is a wedding venue's booking flow: enquiry, date check, tour, contract, deposit, final numbers and the day itself run down the left, with follow-ups in a column at the top right. The diamond is Deposit paid? and the card is Send reminder. Moving the reminder closer breaks up the follow-ups and leaves some other line to cross the page.

So remove the line. A Connector is a labelled jump: the flow leaves at one connector and resumes at the matching one, with nothing drawn between them. Put a small circle titled R beside the diamond and another titled R above the reminder. The one with no outgoing edge is where the flow leaves; the one with an outgoing edge is where it resumes.

Wait a day, then jump to the reminder

Connectors are pure readability: they don't change the logic, just the drawing. Draw the long edge back in, take out the two Rs, and the flow is the same flow.

When the titles don't match

The jump can fail in a way of its own. Mismatched connector labels are the classic case: one circle titled R and another titled Reminder, meant as a pair, don't resume anywhere. The circle the flow reaches is a dead end, and nothing ever reaches the step after the other one, because the title is the only thing joining them. The opposite slip is two Rs that both have outgoing edges, which gives the jump two possible landings. For each title you jump from, keep exactly one Connector that continues.

Jumps also make a tangle easy to hide. A Connector removes a line, not the complexity behind it: if a diagram needs five of them, it may be several flows sharing a page, and Subprocesses & reusable steps shows how to pull one out. When what the reader needs from the crossing lines is who does each step, Swimlanes & responsibility answers that instead.

When the page itself runs out

The venue's cancellation path, with its refund rules and supplier notices, deserves a diagram of its own, and nothing about it needs hiding. An Off-page Connector does the same across diagrams: the flow leaves this one and resumes at the card with the same title on the other. Since the partner is out of sight from here, the title should name the destination, Cancellation rather than C.

A day that cannot end early

Back in the diagram, the card between the request and the question is a Delay: a deliberate wait in the sequence, such as a cool-down or a scheduled pause. Its title is doing real work. A Delay with no indication of how long or what it is waiting for leaves the reader unable to tell a deliberate pause from a missing step. "Wait 24h" answers that, and so would "Until 30 days before the date".

Notice the order, too: the question comes after the wait. Ask first and remind after the wait, and the reminder goes to people who paid during the day. A Delay in a straight line runs in full, so a couple who pays early is confirmed only when it ends; if the payment should end the wait, that is a wait for an outside event, which BPMN events: timer, message & boundary draws. A reminder that repeats needs a way back to the wait, and Loops & retries covers that, along with the Delay on a retry branch that models backoff.

Traffic Light Controller requires its cycle to loop through a Connector and its yellow and red phases to be timed, so close the loop with a single Connector title and write each Delay's duration on its card; Order Lifecycle Flow has both stencils in its palette if you want a second run.

Practice this