Source: https://guthlabs.ai/docs/project-templates/social-campaign/deadlines/ project template / candidate # Social campaign โ€” deadlines The distinct deadlines record for Social campaign. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: project:social-campaign **Parent lifecycle**: candidate **Page lane**: app_features **Lane lifecycle**: proposed **Owner**: Not separately recorded **Owner role**: Not separately recorded **Owner status**: Not separately recorded **Qualification result**: NOT RUN ยท held for evidence and human review **Working browser surface:** [Project templates & workflows โ€” overview]() โ€” Create a local project from this template and validate its forms. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held. ## Deadline and workback rules - Every hard deadline must include a timezone or an explicit timezone-unknown state. - Every milestone must have an owner, dueAt, completion state, and linked deliverable. - The workback must place final approval before any intended external send or publication activity and include a visible buffer. - A missed or at-risk deadline must create a revision note, risk record, new owner action, and reforecasted dueAt; it must not silently move. - A dependency needed by a milestone must have a needed-by date and fallback plan. - Recurring work may use recurrenceCandidate only as a review signal; no hidden automation is authorized. - No provider calendar write, external send, publication, customer indexing, or production effect is implied by an agenda, message, or approval record. - Closure is blocked while required approvals, evidence, unresolved critical risks, or held external actions remain unrecorded. - Campaign end date is required before workback generation. - Every milestone requires an owner, due date, completion state, and dependency check. - Review due dates must precede any planned publication window by a configurable human-entered buffer. - Missing timezone, ambiguous date, or end date before start date blocks workback generation. - Overdue incomplete milestones appear in Today and PointGuard as blockers. - Conflicting agenda blocks are warnings until a human resolves them; no external calendar change is made. - A draft cannot enter Approved while required accessibility, privacy, or claims checks are unresolved. - Approval expires or returns to Needs review when the draft content, audience, channel, or publication window changes. - Publication and final send remain held regardless of approval state. ## Workback sequence - Create the project and assign an owner. - Complete the brief and record assumptions, audience, dates, and success measures. - Add proposed channels and create one message draft per channel or variant. - Add source-labelled asset references; keep upload and protected storage held. - Generate milestones from the campaign end date using explicit offsets and review buffers. - Review the agenda for deadline conflicts and draft schedule changes without external calendar writes. - Run copy, link, privacy, and accessibility checks; show failures inline and preserve revisions. - Submit drafts to local Approvals as Needs review. - Record an Approved or Held decision with a receipt; approval never publishes or sends. - Capture measurement snapshots manually or from verified local records and compare periods. - Use PointGuard to inspect current work, blockers, approvals, and projection scenarios. - Close the campaign only when required records, decisions, and receipts are present. ## Scheduling records - milestone and deadline records with dueAt, priority, completion state, tags, and revisions - dependency and risk records - owner and reviewer assignments - workback schedule - campaign milestone to-do ## Sources and evidence These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment. - `source_record:project:social-campaign` - `project:social-campaign` - `NotebookCollectionKind.project` - `NotebookTodoPayload.dueAt` - `Notebook records provenance and revision contract` - `Notebook Agenda deadlines/workbacks` - `/app/notebook/projects/` - `/app/notebook/to-dos/` - `/app/notebook/agenda/` - `/app/notebook/messages/` - `/app/notebook/approvals/` - `/app/notebook/paper/` - `/app/notebook/field-guides/` - `/app/pointguard/` - `Notebook records provenance, source locators, SHA-256, revisions, lifecycle, tags, links, and attachments` - `Observed web boundary: provider, credential, database, customer, publication, and production effects are held`