pencilit.in

Create workspace
Docs/Validation and finalization

Validation and finalization

Manage prerequisites before finalization

Walk every required prerequisite through PENDING → SUBMITTED → SATISFIED (or WAIVED with a note) so the Ink action unlocks with a clean readiness record.

6 min readcoordinatoradmin

Step by step

  1. 1

    Open the Prerequisites panel

    Once a working slot is selected and the project is Penciled, open the Prerequisites panel on project detail. The 'Required to ink' badge counts blockers still outstanding.

  2. 2

    Make sure the list is complete

    Add any missing prerequisites. For each one set a clear name, choose Required or Optional, and assign the right responder. Templates can pre-fill common items.

  3. 3

    Review submissions item by item

    As assignees submit responses the status moves to SUBMITTED. Open each item, read the response, and click SATISFIED, BLOCKED, or WAIVED with a review note when relevant.

  4. 4

    Confirm readiness

    Use the readiness summary at the top of the panel to confirm zero outstanding required items. If anything is BLOCKED, decide whether to unblock, waive with note, or pause inking.

  5. 5

    Hand off to the inking step

    Once all required items are SATISFIED or WAIVED, the project is ready for the Ink action. Proceed to the inking guide for the final step.

Guide details

What prerequisites do

Prerequisites are the readiness gate between a Penciled slot and an Inked project. They make sure the team isn't confusing 'we found a time' with 'we are actually ready to commit'.

  • Required prerequisites block inking until SATISFIED or WAIVED.
  • Optional prerequisites are tracked but never block inking.
  • Each prerequisite is assigned to a workspace member or a stakeholder.
  • Assignees see PENDING items in the dashboard prerequisite queue.
  • Reviewers can add notes that persist on the inked record.

Status lifecycle

Each prerequisite walks through one of five states. The transitions are explicit so the workflow record matches what actually happened.

  • PENDING - created but no response yet.
  • SUBMITTED - assignee uploaded/recorded a response; awaits coordinator review.
  • SATISFIED - coordinator confirmed it is complete.
  • BLOCKED - cannot be completed; pauses finalization until resolved or waived.
  • WAIVED - coordinator decided to skip with a recorded reason.

Use WAIVED with intent

Treat WAIVED as a deliberate action, not a shortcut. Always add a review note so the inked project's audit trail explains why a required item was skipped.

FAQ

Where do prerequisites come from?

Three sources: add them inline on a project, inherit them from a Project template applied at create time, or copy them from a similar project. All of them produce the same prerequisite record shape on the project.

What do the prerequisite statuses mean?

Each prerequisite has a status: PENDING (nothing submitted yet), SUBMITTED (the assignee uploaded or recorded a response awaiting review), SATISFIED (you confirmed it is complete), BLOCKED (it cannot be completed and is holding up finalization), or WAIVED (you decided to skip it with a note).

Which prerequisites actually block inking?

Inking is blocked while any REQUIRED prerequisite is in PENDING, SUBMITTED, or BLOCKED status. Optional prerequisites do not block inking but still show on the project record.

Can I waive a required prerequisite?

Yes. Mark it WAIVED and add a review note explaining why. The waived state is preserved on the inked project so the audit trail stays readable.

How are prerequisite reminders sent?

The workspace 'Prerequisite review cadence' (default 24 hours) drives automatic reminders to assignees with PENDING or SUBMITTED items. Adjust the cadence in Configuration if your team needs a different pace.