Getting started
What pencilit.in is and when to use it
Understand the five-state project lifecycle (Proposed → Penciled → Validating → Inked, with Expired) and the core building blocks - workspaces, projects, slots, stakeholders, invitations, and prerequisites - so you can decide whether pencilit.in fits your work.
Step by step
- 1
Identify the coordination problem
Confirm you have a real multi-party coordination problem: several slot options, several responders, optional prerequisites, and a need to lock the outcome with a clear handoff artifact.
- 2
Set up the workspace
Create a workspace (or accept an invite to an existing one). Everything else - members, projects, stakeholders, templates, reminders, reporting - lives inside that scope.
- 3
Run one project all the way to Inked
Build one real project end-to-end: add slots, invite stakeholders, collect votes, manage prerequisites, ink the result, and download the summary PDF. One full pass makes the lifecycle concrete for the rest of the team.
- 4
Add reusable structure
Once the workflow is familiar, layer in tags, groups, templates, reminder defaults, and communication templates under Configuration so future projects start from a cleaner baseline.
Guide details
The five-state lifecycle
Projects flow through five lifecycle states. Each state corresponds to a real action the coordinator or team has taken, and slots inside the project share the same vocabulary.
- Proposed - candidate slots have been added but no commitment has been made.
- Penciled - a working slot has emerged from votes and is the current best candidate.
- Validating - required prerequisites are being collected, reviewed, and resolved.
- Inked - the project is finalized; the selected slot and outcome are durable.
- Expired - the workflow is closed without a final commitment (workspace admins can reopen).
The core building blocks
These are the everyday pieces you will work with. Each one has its own surface in the app and its own guides in this docs center.
- Workspace - the operating context that holds members, projects, stakeholders, templates, and reports.
- Project - the coordination unit, with identifier, name, timezone, slots, stakeholders, and prerequisites.
- Slot - a candidate time window with start, end, timezone, and optional label.
- Stakeholder - a reusable contact (name, email, organization, title, notes) who can be invited to projects.
- Invitation - a per-stakeholder link used to vote and respond, with PENDING/SENT/OPENED/RESPONDED/REVOKED/EXPIRED status.
- Prerequisite - a readiness check on a project (required or optional) with PENDING/SUBMITTED/SATISFIED/BLOCKED/WAIVED states.
What it is not
pencilit.in is not designed for instant personal booking, public availability widgets, or open RSVP collection. If your workflow does not need votes, prerequisites, or a durable inked record, a simpler tool will be faster to operate.
FAQ
What kind of scheduling work fits best?
pencilit.in fits work where you need to propose multiple times, collect input from several people, gate the result on real prerequisites, and keep a durable record of the final commitment. Common examples include client onboarding sessions, interview panels, program reviews, and cross-team checkpoints.
Is this meant for one-click booking?
No. It is built for multi-party coordination, not personal booking. If you only need a single attendee to grab a slot from your calendar, a one-tap booking link will be lighter weight.
What can I do in pencilit.in?
Coordinate projects through five lifecycle states (Proposed, Penciled, Validating, Inked, Expired), collect availability votes, manage required and optional prerequisites, ink final outcomes, generate a summary PDF, and export CSV reports for pipeline, outreach, prerequisites, and finalized work.
Do external stakeholders need an account?
Stakeholders respond through a per-invitation link without creating an account. They can vote Available, Maybe, or Unavailable on each slot and-if you allow it-propose alternative times.