Source: https://guthlabs.ai/docs/project-templates/outreach-campaign/forms/ project template / candidate # Outreach campaign โ€” forms The distinct forms record for Outreach campaign. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: project:outreach-campaign **Parent lifecycle**: candidate **Page lane**: forms **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. ## Proposed form sections Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth. ### Intake Define the campaign request, intended outcome, boundaries, and record ownership before research begins. - campaign name - requestor - project owner - date opened - business purpose - target audience or account class - desired outcome - outreach channel as a draft-only label - estimated account count - sensitivity or privacy notes - source locations - visibility - initial lifecycle - explicit no-send acknowledgement ### Scope and qualification Set inclusion, exclusion, qualification, and evidence rules for account dossiers. - in-scope accounts - out-of-scope accounts - geography or segment - qualification criteria - disqualification criteria - required dossier fields - permitted source types - minimum evidence threshold - personal-data handling instruction - claims requiring approval - stop conditions - scope approver - scope approval status ### Milestones Create ordered project checkpoints with owners, dates, acceptance criteria, and dependencies. - milestone ID - milestone name - description - owner - planned start - due date - priority - status - preceding milestone IDs - required records - acceptance criteria - reviewer - completion note - revision reason ### Deadlines and workback Translate a target date into reviewable workback tasks using Notebook deadline fields. - target outcome date - hard or soft deadline - timezone - date source - buffer days - review lead time - draft completion date - evidence completion date - approval deadline - message staging deadline - closure deadline - workback calculation note - conflict or exception note - reschedule decision owner ### Dependencies and handoffs Record prerequisites and ownership transfers without implying external integrations. - dependency ID - dependency description - blocking or non-blocking - dependent milestone or task - dependency owner - needed-by date - current state - source or linked record ID - fallback plan - escalation owner - handoff recipient - handoff receipt ### Owners and authority Make responsibility and authority explicit for each project activity. - project owner - research owner - dossier owner - copy owner - evidence reviewer - approval owner - closure owner - backup owner - allowed actions - prohibited actions - handoff rules - last responsibility review ### Account dossier Capture a bounded, source-labelled account record suitable for internal review. - account name - account identifier - account owner - segment - location if relevant - known public context - stated need or relevance - source URL or locator - source label - source SHA-256 when available - observed date - evidence excerpt or note - confidence label - unsupported-claim flag - contact field only if explicitly supplied by an allowed source - dossier status - reviewer - revision history ### Outreach staging Prepare one or more messages for review while preserving human control over final send. - message ID - linked account dossier ID - draft channel - recipient as manually entered value - subject or opening - message body - personalization claims - supporting evidence IDs - call to action - attachments or linked file references - sender identity - draft owner - draft status - recipient verification status - send authority acknowledgement - final-send state held ### Tools and guides Declare the local surfaces and procedural guidance used for each work item. - tool or route name - tool kind - purpose - linked milestone - record owner - expected local capability - held capability - accessibility notes - fallback if unavailable - usage receipt ### Evidence and receipts Preserve provenance for research, drafting, review, and decisions. - evidence ID - linked record ID - source locator - source label - source SHA-256 if available - captured or observed date - claim supported - claim not supported - reviewer - review status - receipt note - revision relationship - visibility ### Approvals Route scope, dossier, claims, and message proposals through explicit local review states. - approval ID - approval subject - linked record IDs - proposer - reviewer - decision - decision date - decision rationale - conditions - receipt reference - revision required - next action - external effect remains held ### Risks and failure states Identify evidence, deadline, privacy, accessibility, and execution risks with mitigations. - risk ID - risk statement - category - likelihood - impact - severity - trigger - affected records or milestones - mitigation - contingency - risk owner - review date - status - stop-work condition ### Closure Close the project with a factual record of completed, held, rejected, and unresolved work. - closure date - closure owner - objective result - completed milestones - incomplete milestones - approved drafts - held drafts - rejected claims - unresolved risks - evidence completeness check - records linked - final approval receipt - retention or visibility decision - lessons noted - explicit no-send confirmation - follow-up project or task IDs ### Accessible state contract - Every field requires a visible and programmatic label. - Required and optional fields must be stated in text. - Invalid entries require an actionable message linked to the field. - Blocked and Held states remain visible without relying on color alone. ## Supporting documentation fields These fields come from the app_features lane and remain separate from the primary operating form. ### Campaign basics Define the campaign-owned project record and its current planning state. - campaign name - objective - owner - description - lifecycle - visibility - tags - start date - target completion date - success criteria - notes ### Account dossiers Capture account-level planning information without asserting unsupported customer or provider data. - account name - account identifier or internal label - account status - segment - relationship owner - research summary - known needs - open questions - priority - linked source notes - linked file references - next review date ### Outreach stages Define ordered, human-reviewed stages for each account. - stage name - stage order - stage purpose - entry condition - required evidence - draft message reference - review status - planned due date - completion state - blocker - owner ### Deadline and workback plan Turn the target date into explicit local milestones and to-dos. - target date - milestone name - milestone type - due date - duration estimate - dependency milestone - priority - owner - recurrence candidate - completion state - risk note ### Message preparation Prepare communication drafts while keeping final send human-held. - recipient label - recipient address or identifier if locally known - subject - body - stage - personalization notes - linked account dossier - source context - attachments or file references - review status - send state ### Review and receipts Record decisions, unresolved risks, and local evidence for each proposed action. - decision status - reviewer - decision note - risk acknowledgement - receipt reference - revision note - held external effect reason ## Required or proposed record references No record existence is asserted by this documentation page. - project record - account dossier records - source-labelled notes - local file references where needed - to-dos with dueAt and owner tags - draft messages - approval records - evidence receipts - risk records - closure record - local file references - to-do records - draft message records - workback milestone records - revision and provenance records ## Sources and evidence These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment. - `source_record:project:outreach-campaign` - `NotebookCollectionKind.project` - `NotebookTodoPayload.dueAt` - `Notebook Agenda deadlines/workbacks` - `PointGuard` - `Notebook records provenance and revisions` - `/app/notebook/projects/` - `/app/notebook/to-dos/` - `/app/notebook/agenda/` - `/app/notebook/messages/` - `/app/notebook/approvals/` - `/app/notebook/files/` - `/app/notebook/agent-logs/` - `Notebook records provenance and revision contract` - `PointGuard persistent cross-app context surface` - `Web boundary: provider, credential, database, customer, publication, and production effects held`