Surfaces · Penciled.software
One provisional time, with two people reading it.
The holder needs room to decide. The practitioner needs to know whether the slot is still available. A team needs the same meaning to survive a handoff. These are proposed views of the unbuilt soft-hold lifecycle, not separate live products or a set of booking forms.
For the person deciding whether the time works
The holder's question is small and familiar: can I keep this time while I check one thing? The planned surface would show the selected slot, the provisional status and the expiry together. Its useful output is a clear decision window. It should not make someone infer a commitment from a timer graphic or mistake interest for a confirmed appointment. In a product discussion, describe the missing decision before asking for a particular interface.
A consultant's client might need to check travel; two collaborators might need to agree on a shared session. Those examples do not require detailed personal circumstances. A fictional appointment and a rough decision interval are enough to discuss the design. Today the website records no hold for that person. The illustration is only an explanation, and the contact link starts an email rather than a reservation that another person can rely on.
For the person offering the appointment
The practitioner needs to know what can still be offered. A private pencil note in one person's calendar can disappear during a handoff or remain after the original conversation has gone quiet. The proposed staff view makes the provisional meaning explicit. A hold would count against capacity while it remains valid, then either become a confirmed booking or release. The outcome to evaluate is a readable distinction between open, provisionally held and committed.
That distinction also has a cost: a provisional hold temporarily limits what can be offered to someone else. Decide whether that trade fits the appointment type. An urgent same-day service may need a different decision window from a planning consultation. This page does not offer policy automation for those cases. It asks the operator to describe the real trade so the planned workflow can be evaluated against a concrete need rather than a universal claim.
For a team that inherits the conversation
A second member of the team should not have to reconstruct what pencilled in meant to the first. In the proposed workflow, the time, provisional state and expiry are the shared facts that make the handoff useful. The team should be able to tell whether someone still has a decision to make. It should also be able to tell when that decision window has ended, rather than assuming a note remains valid indefinitely.
Bring a handoff example to a walkthrough: one person receives the initial request, another handles a later reply. Ask which facts each would need and what a late confirmation should mean. Do not assume that a Team tier label proves those permissions or screens exist. Team packaging and inherited branding remain plans. A new marketing page makes the design easier to inspect; it does not promote an unbuilt collaboration surface to a shipped capability.
For the person who returns after the pencil mark has gone
An expired hold should not leave the returning person guessing whether they can still confirm. The planned ending is to state that the provisional claim has lapsed. If another suitable time is open, a proposed alternative could help the person continue. This is the smart-reschedule design on the feature list: a ranked set of nearby choices, reviewed by a person. It is not an automatic reassignment and has not been wired to a Penciled hold.
A useful evaluation asks what nearby means for your work. The next hour may be useful for one appointment and the following week for another. Tell us which constraints matter, without treating the examples as options currently offered by the site. If you only need ordinary confirmed bookings, the extra provisional state may add no value. The about page explains why this product concentrates on the pause before commitment.
The pencil has not become a working reservation yet
The distinction runs through the whole site. The fixed-slot capacity floor has existing sibling-source grounding. The hold state is a separate design: it would count provisionally, carry an expiry and resolve into confirmation or release. None of those hold actions is running on Penciled.software. A route that displays this explanation does not supply the missing state transition. The small board on the home page is a static illustration, and no timer runs inside it.
That is why the next action is a conversation rather than a booking button. No date shown in an example is being offered to you, and no click can confirm a slot. Smart reschedule is also planned: applying a ranked proposal pattern to a lapsed hold has not been wired here. The useful question is whether the proposed behavior fits your work, followed by what evidence you would need to see before relying on it.