1 — Tell us what you want to pencil in
Write to [email protected] with what you're scheduling and what you want a soft hold to do for you. One paragraph is plenty.
Getting started · Penciled.software
There is no sign-up form on this page. That is deliberate.
The hold state is not built yet, so a sign-up form that promised a working pencilled slot would be lying about what it does. A conversation first, and an honest account of what runs today: the fixed-slot floor, live in the shared engine; the pencil itself, still ahead.
What actually happens
Four steps, and you can stop after any of them.
2 — A walkthrough of what's built, not a pitch
We show you the fixed-slot floor that's live in the shared engine today and name, plainly, which parts of the pencil-hold lifecycle are still planned. You should leave able to repeat back what's real.
3 — Try it on one calendar
A scoped look at the same correctness guarantee every booking on this engine gets: no double-booking at the database, capacity counted under a lock.
4 — Move up only when Building feels tight
District is a plan change, not a migration, once the hold lifecycle ships — there's no forced upgrade on this page.
Describe the pause between interest and commitment
Begin with an appointment you cannot sensibly confirm immediately. Perhaps a client needs to check travel, a colleague needs to agree to join, or a practitioner needs an answer before choosing between two possible windows. Describe the decision without naming the client or forwarding their messages. The useful input is the reason a short, explicit pause would help. A hold is not automatically better than an ordinary booking; it should solve a specific hesitation.
Say how long the decision normally takes and what happens when nobody answers. An afternoon and a week create different expectations for the person holding the slot and the person offering it. Do not start by choosing a countdown because it looks tidy on a page. Start with the work someone must finish before they can honestly say yes. The proposed expiry should be understandable to both sides, rather than a surprise hidden behind a button.
Walk through both exits on paper first
Take a fictional slot and write down three states: open, provisionally held and confirmed. Add the expiry you would want a holder to see. Then write two endings. In one, the holder confirms before that point; in the other, they do nothing and the planned hold releases. This small exercise reveals whether your team is using held to mean a genuine reservation, a preference or merely a note. Those meanings should not be mixed.
Try one awkward ending as well: the person returns after the proposed expiry. What would you want the message to say if the time is no longer open? What nearby alternatives would still be useful? Penciled's replacement-suggestion idea is planned, not wired. Treat this as a design conversation about the desired response, not a test of a running system. A drawing of an expired hold cannot prove that capacity was released or another booking was protected.
Leave with a question answered, not an imaginary account
A useful first conversation should establish whether the proposed third state fits your work, which part of the lifecycle matters most and what you would need to see before trying it. Ask specifically about hold creation, expiry, confirmation and the late-return case. The fixed-slot floor described elsewhere on this site does not by itself answer those questions. The hold lifecycle is not built, so there is no Penciled account or live reservation to hand over at the end of this page.
Keep your current booking process authoritative while the product is being developed. Do not tell a client that an illustration on this website has reserved their time. Joining the waitlist is an email conversation; it does not store payment details or commit you to a tier. The planned Building and District packaging helps explain the direction of the product, but a price label is neither a working feature nor a promise that a particular release will arrive by your deadline.
Choose the decision the pencil mark is meant to protect.
Begin with an invented adult bookbinding studio, Oak Fold. Ivo offers a forty-five-minute consultation on Tuesday 20 October 2026 at 11:00, in the studio's local time. A prospective visitor, Case A, needs colleague Tess to agree to join before accepting. These are fictional planning facts. The example is not a customer record, a live offer or a hold created through this page.
The first preparation note says, “They are interested, so keep the time.” That phrase does not say whether other people may still request the appointment. Ivo's revised question is more precise: “Would a provisional claim on this one consultation help while Case A checks with Tess, and what would we expect to happen to other requests during that period?” The wording identifies the capacity question without claiming that Penciled implements the answer.
This is a useful first decision because some hesitations do not justify holding a place at all. A person browsing several possibilities may need information rather than a reservation. Someone waiting for one concrete answer may have a stronger use case for a short provisional state. The preparation should distinguish those situations instead of assuming that every expression of interest needs a countdown.
The output is one statement of purpose: this example concerns time to coordinate with another adult before accepting a particular appointment. Stop if the purpose remains “more flexibility” with no identifiable decision behind it. A narrow question makes the discussion more useful; it does not require the writer to supply a private conversation or explain the visitor's personal circumstances.
Make the proposed decision window intelligible to both sides.
For the paper exercise, Ivo proposes a cutoff of Monday 19 October at 16:00 in the same studio-local time convention. The appointment is the following morning at 11:00. Writing both values prevents “until four” from being mistaken for the appointment time or a limit on the day of the visit. No clock starts by printing those values here.
The proposed limit needs a reason. In this fictional case, Case A expects to hear from Tess by Monday afternoon, while Ivo needs to know which consultation remains under consideration before preparing the next day's materials. These are local arrangements invented for the example, not rules the product has imposed or a recommended deadline for every business.
The first draft says, “Hold until tomorrow.” The revision names the appointment, the proposed cutoff and the outcome expected if nobody confirms. That last part is a question about the planned lifecycle: should the provisional claim end without being treated as a confirmed appointment? The page describes that design intent, but it supplies no operating expiry service that can prove the event occurred.
A reader may object that this makes a casual conversation formal. It need not create a contract or add legal language. The useful work is simply preventing the two adults from relying on different meanings of tomorrow or held. If they cannot state the same intended ending, the preparation has found a real ambiguity to resolve before evaluating any interface.
Prepare a success case and a no-answer case.
Write two separate endings to the invented consultation. In the first, Case A obtains Tess's agreement and asks to confirm at 15:00 on Monday, before the proposed cutoff. In the second, no answer arrives by 16:00. These endings must stay separate on the worksheet; putting both under a single “completed” label hides the difference between a settled appointment and a provisional claim that has ended.
For the first ending, the desired result is a valid confirmation of the same appointment, not a silent change of date, duration or resource. For the second, the desired result is the end of the provisional claim according to the stated design. Both remain expected outcomes for discussion. Neither a written checkmark nor this page's illustration establishes that a booking changed state.
Add the awkward case: Case A returns at 16:15 and refers to the earlier time as theirs. The paper response should acknowledge that the proposed limit has passed and that the old note does not establish a current reservation. Any alternative requires its own current availability. Penciled's planned reschedule idea does not supply a live recommendation in this exercise.
The preparation ends with an evidence question for each branch. What would demonstrate confirmation? What would demonstrate release? What would show the late visitor's actual options? If the required surface is unbuilt, record that answer. A useful evaluation can identify a coherent design without claiming that the design has already become a service.
Notice when the original appointment is no longer the request.
Suppose Tess's reply adds a new requirement: the visit needs sixty minutes rather than forty-five. The original proposal was 11:00–11:45. An 11:00–12:00 conversation is a different interval. Confirming the original choice cannot honestly mean that the extra fifteen minutes have also been accepted. The new requirement needs to stay visible as a change in the human discussion.
A clear revised preparation note says, “Coordination is complete, but the requested duration changed; suitability of the longer window remains unresolved.” That is more useful than marking the whole case ready because one source of uncertainty disappeared. The product conversation can then distinguish settling the original choice from asking for another arrangement, without inventing a Penciled change-control screen.
Keep the existing booking process authoritative throughout this evaluation. The page creates no provisional claim and offers no working confirmation action. The final artifact is a small adult planning brief: the original appointment, the outstanding decision, the proposed limit, the two expected endings and the changed-duration question. It is material for a conversation, not a handoff of an account.
The fair objection is whether this much preparation is necessary before asking about early access. It is optional craft, not a requirement for contacting the team. A writer can send a shorter question. The advantage of this worked brief is that it makes the important uncertainty easy to name and keeps an attractive illustration from answering a question that remains open.
What starting does not involve
No card, no charge, no contract signed on a web page.
There is no live checkout on this site. Joining the waitlist does not create a payment, does not store a card, and does not commit you to anything — the pricing on the home page is the planned launch tier, not a price you can be billed at today. No pricing commitment, no signup.