A wedding day rarely happens at one address, and every move between locations takes time out of the schedule. Daymarked watches for these gaps and offers to fill them in for you.
What a travel block represents
Travel time isn't its own block type on the timeline. It's a travel subtask attached to the block you're leaving. Give two adjacent timed blocks each a location, and Daymarked offers to insert a subtask on the earlier one reading something like "Travel Time 18 min to Rosewood Barn." That subtask always sorts to the bottom of the block's subtask list, so it reads as connective tissue between two stops rather than a task in its own right. The timeline editor covers subtasks more generally.
The suggestion only fires between directly adjacent blocks. If a location-less block sits between two located ones, Daymarked treats that as a gap and doesn't prompt. Accept the suggestion or dismiss it; if you dismiss it, that specific pairing won't be offered again on this timeline.
How the estimate is calculated
When you accept a suggestion, Daymarked sends the two locations to Google's routing service and asks for a drive time between them. It uses whichever address is more precise: a block's full street address if one is on file, otherwise the location name you typed when you added the block. Both addresses are typed text. There's no map-pin dragging involved, so an estimate is only as accurate as the address behind it.
The lookup runs on Daymarked's server, not in your browser, and it's rate-limited per photographer to keep it from being abused. If a lookup is temporarily unavailable (you've hit the rate limit, or your session needs a refresh), Daymarked tells you so directly rather than quietly adding a travel subtask with no time on it. In that case the subtask still gets added, without a duration filled in, so you can enter one yourself.
The subtask's time field holds a departure time, not a raw duration: Daymarked subtracts the drive time from the next block's start time to land on when you'd need to leave. If the destination block doesn't have a start time yet, the subtask is added without one.
Adjusting an estimate
A travel subtask isn't locked once it's on the timeline. Open the block it belongs to and you'll find it like any other subtask: a time field and a label, both editable. If Google's estimate runs long or short for a route you know well, or the address on file wasn't specific enough to get a good result, type over the time directly.
You can also skip the automatic suggestion entirely and add your own. Open the block and use the Travel time button near the subtask list. It adds a blank travel subtask with a "Destination" placeholder for the label and an empty time, ready for you to fill in by hand. This is useful when you'd rather estimate a drive yourself than wait on an address lookup, or when the leg you're planning for doesn't map cleanly to two blocks on the timeline. Each block allows one travel subtask, whether it came from a suggestion or you added it manually, so two conflicting estimates can't stack up on the same stop.