Penciled.software · pencil it in, not book-or-bust · early access
A pencil mark on a calendar has always meant something specific: held, not yet final, easy to erase, one stroke of ink away from settled. Appointment tools flattened that into a binary a long time ago — a slot is either open or it is booked, full stop. There is no room in that model for "I want this time, but I am not ready to commit yet," so people either hard-book too early or lose the slot waiting.
Penciled.software is being built to put the pencil back. A held slot becomes a real, visible, provisional third state on the same fixed-slot booking engine the schedule.software family is built on — counted against capacity so nobody double-books it, carrying its own expiry, resolving one of two honest ways: you confirm it with one tap, or it releases itself back automatically. Nothing sits in limbo.
Said plainly, because it matters more than the pitch: the fixed-slot floor underneath — database-level no-double-book and a real capacity count — is built. The pencil hold itself is not. There is no penciled.software surface serving holds today, no expiry clock running anywhere, and nothing on this page is a demo of working software. This is early access for the mechanism described below, labelled honestly throughout.
How a pencil hold actually resolves
The board above walks the sequence a pencil hold is designed to go through — drawn, not running. First, a slot is pencilled in — provisional, but already counted, so nobody else can also take it out from under the holder. Second, it is holding, visibly, with an expiry both the holder and staff can see — no hidden clock, no surprise. Third, it resolves one of two honest ways: one tap confirms it, turning the pencil mark into ink, or nobody acts and it auto-expires, releasing the slot back to open capacity on its own, without a support ticket or a staff member noticing a stale hold and clearing it by hand.
A lapsed hold is still not a dead end. Smart reschedule — the design intent to point the fleet's existing self-healing reschedule engine at a lapsed pencil hold instead of an open-ended disruption — is meant to turn "this time is gone" into a short, ranked list of nearby slots instead. That specific application is planned, labelled honestly below as planned, not claimed as live.
How we compare — category by category, no names
This reflects the structural category each product type occupies, not any single vendor — no competitor brand is named on this site. The “Penciled.software” row is honest about status: the fixed-slot floor is built, the pencilled-hold columns are marked partial because they are designed and not yet live, and pricing shown elsewhere on this page is the plan, not a live checkout.
| Product type | Free tier's event-type cap | A held slot before it's booked or lost | What happens if nobody confirms in time | Guaranteed no double-book, at the database |
|---|---|---|---|---|
| Appointment-link tools | Often capped at one | Booked or nothing | Manual cleanup by an admin | One calendar |
| Sign-up-sheet tools | Ads / per-plan | Open sheet, no hold state | No expiry model | Capacity races |
| Group-poll tools | Free / ads | Poll, not a hold | No hold to expire | Poll, not booking |
| Penciled.software | Unlimited by design; not live yet | Designed; not live yet | Designed; not live yet | Database-level |
The mechanism — what is built, what is only designed, labelled honestly
Every capability below is labelled honestly: Built means the mechanism already exists in the shared fixed-slot booking engine this family is built on — never that a penciled.software surface is serving holds today. Planned means designed and not yet built or wired. Exactly one capability below is Built — the fixed-slot floor. Everything that makes a slot pencilled rather than booked is Planned. We do not blur the two, and we do not describe a drawing as a running feature.
The booking floor
Every pencilled or confirmed slot rides the same fixed-slot / identity-keyed capacity decision the schedule.software family is built on: no-double-book and per-slot capacity are both enforced at the database, not in application code that can race. This is the floor every state below -- pencilled, held, confirmed -- sits on top of.
Built · shared engine
The one edge no incumbent ships
Booked-or-nothing is a modeling choice, not a law of scheduling. The design: a pencilled slot is a third state distinct from both "open" and "booked" -- it counts against capacity (so it cannot double-book), it is visibly provisional to everyone who can see it, and it carries its own expiry. It belongs where the booking decision is made, not as a countdown drawn on top of an ordinary booking. To be plain about status: this state is not built today. The fixed-slot floor it is designed to sit on is; the hold state itself is the thesis of this product and the thing being built next. Nothing on penciled.software serves a real hold yet.
Planned · designed on the built fixed-slot floor, not built yet
What happens if nobody acts
A pencilled hold is designed to carry an expiry the holder sees up front. If nobody confirms before it lapses, the slot releases back to open capacity automatically -- no admin has to notice a stale hold and manually clear it, and no client is left wondering whether an unconfirmed hold is still theirs. Auto-release is the design; it is part of the same unbuilt hold lifecycle above, and no expiry is running anywhere today.
Planned · part of the unbuilt hold lifecycle
The other way out
The other resolution to a pencilled hold: the holder confirms before it lapses, in one action, and the slot moves from provisional to booked without re-entering anything they already told the system when they pencilled it in. Designed, not built -- the same unbuilt lifecycle as the two above.
Planned · part of the unbuilt hold lifecycle
When a hold lapses anyway
The scheduling platform this family shares an engine with describes a self-healing reschedule proposer of its own: a ranked list of minimal-cascade changes when a disruption hits a schedule, with a human ratifying before anything commits, built for that platform's dispatch booking law. That is its account of its own engine, not a measurement taken here. "Smart reschedule" is the design intent to point that same proposer at a lapsed or declined pencil hold: instead of a dead end, the holder sees a short ranked list of nearby open slots. That specific application is planned, not yet wired -- this page does not claim it runs today.
Planned · reuses an engine built for a different surface
The thing every incumbent paywalls
A booking page at your own hostname, not a shared subdomain, is planned on every tier including the free one -- the same inversion the rest of this platform's family plans: the appointment-link tools you already know make you climb to a paid, often enterprise, tier just to put your own name on the page. This is a packaging and pricing plan, not a claim that the connect-your-domain flow is live: pricing on this page is display-only.
Planned · free on every tier, display-only pricing
The one step up from your own domain
Your logo, your colors, and the small badge gone -- planned for the Pro tier, the tier a solo practitioner or small studio actually buys, instead of gated behind an Enterprise sales call the way several tools in this category structure it. Team adds org-wide brand inheritance across every seat on top of that, not a separate branding tier. None of this is built on penciled.software yet -- it is a packaging plan, not a claim that a branding surface is live; pricing shown is display-only.
Planned · Pro tier, display-only pricing
One note on the category, since this page makes a claim about it: the appointment-link, sign-up-sheet, and group-poll tools this product is measured against are referred to here by category only, never by name. The “booked or nothing” framing above is our reading of how these tools model a slot as of this writing, not a tested claim about any one of them, and any of them may ship a hold state tomorrow. No competitor brand is named on this site.
Your name on it, your domain under it — not the enterprise upsell
A custom domain is the first thing most personal-booking tools lock behind a paid tier, and full white-label branding is the thing they reserve for an enterprise contract. The plan here inverts that: the custom domain is on every plan, including the free one, and the deeper branding is one step up — not a sales call.
The plan: claim a hostname you control, drop in the DNS-TXT record you're handed, and once it verifies your booking page and its subscribable calendar feed serve from book.yourpractice.com instead of a shared address. Not built yet on penciled.software specifically — this domain-claim mechanism is the same one the wider scheduling family runs in production for its K-12 and studio arms, and it is what this planned tier is designed to bind to. One host belongs to one holder; releasing it unroutes immediately.
Your logo, your colors, and the small “Penciled.software” badge gone — planned for the Pro tier, not held back for an Enterprise call. One brand applies across every seat on Team by inheritance, so a growing practice sets it once rather than per-holder.
This section describes the planned launch tiers, display-only. There is no live domain connection, no branding dashboard, and no checkout on penciled.software today — join the waitlist and we'll walk you through what's real.
Pricing — the plan, grounded and honest. Planned launch pricing, not a live checkout.
The Personal tier is a real tool, not a crippled trial: unlimited holders on one calendar isn't the wedge, a custom domain is — most appointment-link tools cap the free tier at one event type and paywall a custom domain behind an enterprise contract. We plan to give both away free and gate only the deeper branding one step up.
Free
$0
Planned · not a live checkout
Pro
~$10/mo
~$8/mo on the annual plan (~$96/yr, planned)
Planned · not a live checkout
Team
~$15/seat/mo
~$12/seat/mo on the annual plan (~$144/yr, planned)
Planned · not a live checkout
These figures are the planned launch tiers; they are not a live purchase option today. No money changes hands through this site. Payments are honest-off: the payment infrastructure is in place as a reserved line; it is not enabled for live transactions today. Join the waitlist and we discuss what access looks like for you specifically — there is no pricing commitment, and no signup on this page.
What is built and what is not — plainly stated
Built today, in the shared fixed-slot booking engine this family is built on: the database-level no-double-book invariant and the transactional per-slot capacity count. That is an engine, not a penciled.software product anyone can use today.
Not built today — designed, and the reason this page exists: the pencil hold itself. The provisional third state, its visible expiry, the one-tap confirm, the automatic release, the self-serve surface a buyer would sign into, and the smart-reschedule follow-up. None of it is running. Anything on this page that shows a hold is a drawing of the design, and it says so where it is drawn.
Honest-off, stated once: pricing is display-only, there is no live checkout on this site and no card is charged. No AI-assist or AI-generated claim is made anywhere here. No FERPA, COPPA, SOC2, or VPAT certification is claimed or held. We make no claim about whether any sibling product in this family is live, shipped, or running in production — this page does not enforce another product's status, so it does not vouch for one.
Different lanes for different needs
These are separate products for separate jobs, each its own brand — not tiers of one app. They share a booking engine (no-double-book at the database, capacity under a lock, an honest waitlist), and nothing else. Naming them here is not a claim that any is live in production — each is its own brand with its own status, stated on its own page.
One link, one slot
The plainest single-link booking front door for a solo practitioner or a very small team.
Call dibs on a time
A first-come, claim-a-slot sign-up sheet with a consumer voice -- the first to grab a time gets it.
Pencil it in
Fixed-slot booking with a real soft-hold state: hold it provisionally, confirm with one tap.
You are here
More than one calendar
Appointment booking for a business with multiple staff, locations, or shared resources.
Classes & studios
Recurring class, pack, and waitlist scheduling for studios.
Cohort courses
Session-based scheduling for cohort-run online courses.
Staff shift roster
Post an open shift and match it to eligible, credentialed staff -- scheduling only.
Shifts + hours record
Shift scheduling with time-clock and hours-record capture for classified staff and shift-work teams.
Find a time
A native, ad-free poll for finding the time that works for a whole group.
The master timetable
Building the institution's whole schedule -- courses, sections, rooms, terms.
Here is the honest answer first: nothing happens yet, because the hold state is not built. What is designed is a distinct third state -- not open, not booked. It counts against capacity (so nobody else can also book it), it is visibly provisional to the holder and to staff, and it carries an expiry set up front. A real third state where the booking decision is made, not a countdown drawn on top of an ordinary confirmed booking. That is what is being built next, and this page labels it planned rather than pretending it is running.
By design it auto-releases back to open capacity on its own: nobody has to notice a stale hold and clear it by hand, and the slot is available to someone else again without a support ticket. Same status as the hold itself -- planned, not running today.
The intent is to reuse a proposer pattern the sibling scheduling platform describes for its own dispatch surface: a ranked list of minimal-cascade proposals, ratified by a human before anything commits -- never an autonomous change. Pointing that at a lapsed pencil hold, so the holder sees nearby open slots instead of a dead end, is the design intent and nothing more. It is planned, not wired, and this page has not verified that engine itself.
No. The reschedule proposer is a ranked rules/constraint computation a human ratifies -- not a generative or autonomous system, and there is no AI-assist claim anywhere on this page.
This page is early access: it describes the mechanism honestly, labels what is built versus in development versus planned, and asks you to join the waitlist rather than claiming a live, self-serve signup that does not exist yet.
No -- a custom domain is planned on every tier, including the free Personal one, not held back for an Enterprise (or even a Team) sales call. Pricing shown on this page is display-only; there is no live checkout here.
Not for the domain -- a custom domain is planned on every tier, the free one included. Most personal-booking tools charge for that and reserve full white-label branding for an enterprise contract; here, removing the small badge and applying your logo and colors is one paid tier up (Pro), not a sales call. None of this is live yet; pricing shown is display-only.
The fixed-slot floor this product sits on counts capacity inside the transaction, at the database -- a conflict comes back as a clean, retryable response, never a silent double-book. That is the sibling scheduling platform's own account of its shared engine, not something independently verified from penciled.software, and this page does not claim its own deployment.
The help page collects getting-started steps, the pricing and domain/branding plan, and the mechanism status in one place. If it's not answered there, [email protected] reaches a person.
No. None is claimed anywhere on this page.
There is no live checkout on this page and no card is charged here. If a real, visible soft-hold state on a fixed-slot booking engine fits what you run today, the honest next step is to ask about early access.