Features · Penciled.software
The important feature is what a pencil mark means.
The feature list separates a known booking floor from the provisional lifecycle being designed above it. Read each label with its scope: an existing capacity primitive is not a working hold, and planned packaging is not a live setup screen. This site offers no usable reservation or checkout.
The status ledger stays attached to each idea
- The booking floor
- Built · shared engine
- The one edge no incumbent ships
- Planned · designed on the built fixed-slot floor, not built yet
- What happens if nobody acts
- Planned · part of the unbuilt hold lifecycle
- The other way out
- Planned · part of the unbuilt hold lifecycle
- When a hold lapses anyway
- Planned · reuses an engine built for a different surface
- The thing every incumbent paywalls
- Planned · free on every tier, display-only pricing
- The one step up from your own domain
- Planned · Pro tier, display-only pricing
The single built label belongs to the shared fixed-slot floor. Every hold-lifecycle capability, its proposed reschedule application and the Penciled domain/branding surface remain planned. No label changes because this feature page now has its own address.
A provisional state must count for something
The proposed hold is meant to count against capacity while it is valid. That is the difference between a reservation and a personal note. It would be visible as provisional rather than presented as an ordinary confirmed booking with a different color. The input would be a selected slot and the agreed decision window; the output would be a temporary claim with a clear status. That state is planned, not built.
The shared fixed-slot floor is relevant because a hold would need to coexist with the booking decision. It does not establish that the new state already participates in capacity, conflicts or release. Keep those as explicit requirements for a later demonstration. A marketing illustration cannot verify two simultaneous requests, and this page does not simulate one to imply a guarantee. Ask for a working hold lifecycle before relying on its provisional reservation behavior.
Confirmation and expiry are separate features of the same promise
The planned confirm action settles a still-valid provisional choice. The planned expiry releases one that nobody confirms. Neither is an optional visual extra. If confirmation exists without a clear expiry, stale reservations can linger. If a timer is shown without a meaningful state transition, the screen can imply that a slot has become free when nothing has actually changed. The product thesis needs both endings, and both remain unbuilt here.
Use the late-return case when evaluating that thesis. A person who returns after the deadline should not see the same invitation to confirm a claim that has already lapsed. What they see instead is an important design question. This site does not implement the answer, but it makes the question visible before a pilot. A clean description of the refusal is as useful as an attractive successful path, because it tells people what they can safely rely on.
A nearby alternative still needs agreement
Smart reschedule is the planned application of a ranked proposal pattern to a lapsed or declined hold. The desired output is a short list of nearby open slots rather than a dead end. Nearby does not mean interchangeable. The holder may have chosen the original time for a reason the calendar does not know. A proposed option should invite a new decision, not silently move a commitment or describe itself as accepted.
This page makes no generative or autonomous-assist claim. It also does not claim that the proposer has already been connected to a Penciled hold. During a conversation, describe the constraints that would make an alternative useful: another day, a similar time or the same practitioner, for example. Treat those as requirements to discuss. The existing copy's design direction does not establish that every possible constraint has a working control or implementation.
A domain and a brand do not change the lifecycle's status
The packaging plan includes a custom domain from Personal, deeper branding at Pro and team-wide brand inheritance at Team. Those plans concern the name and appearance of a future surface. They do not make a hold, expiry or confirmation available today. No domain connection, branding dashboard or purchase action runs on Penciled.software. Choose a tier only after the required product behavior can be shown and the actual terms have been discussed.
If your first question is whether the proposed third state fits your appointments, start there. A logo decision can wait. Bring a fictional appointment to the evaluation brief and walk both endings. The surface guide then asks who needs to read the provisional state. That order keeps the discussion about a useful decision, rather than decorating an unbuilt workflow and treating the decoration as completion.
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.