Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

project template / candidate

Grant application — forms

The distinct forms record for Grant application. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID
project:grant-application
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 opportunity, decision context, and accountable people before work begins.

  • project title
  • granting organization
  • opportunity name and identifier
  • source URL or source locator
  • opportunity source date
  • application deadline with timezone
  • internal submission target date
  • project owner
  • application coordinator
  • reviewers and approvers
  • applicant organization
  • contact details
  • funding amount requested
  • currency
  • application status
  • why this opportunity fits
  • decision to pursue
  • decision rationale
  • visibility and access notes

Scope and requirements

Translate the opportunity into an explicit, bounded application scope.

  • funding priorities
  • eligible applicant requirements
  • required narrative sections
  • required questions and character limits
  • required attachments
  • budget categories
  • matching or cost-share requirements
  • evaluation criteria
  • allowable and unallowable activities
  • out-of-scope activities
  • drafting assumptions
  • open interpretation questions
  • definition of complete application package

Milestones and deliverables

Create owned checkpoints for research, drafting, review, packaging, and closure.

  • milestone ID
  • milestone name
  • milestone purpose
  • deliverable description
  • owner
  • reviewer
  • planned start
  • internal due date
  • external due date if applicable
  • status
  • completion evidence required
  • approval required
  • blocking condition
  • notes

Deadlines and workback

Record source-bound deadlines and derive a human-reviewable schedule without external writes.

  • deadline label
  • deadline timestamp
  • timezone
  • deadline source locator
  • deadline confidence
  • internal buffer
  • workback start date
  • workback calculation or rationale
  • task sequence
  • task duration estimate
  • task owner
  • review window
  • approval window
  • packaging window
  • final readiness check
  • late-state action
  • deadline change history

Dependencies

Expose prerequisites and handoffs that can block the application.

  • dependency ID
  • dependency description
  • dependent milestone or task
  • dependency owner
  • needed-by date
  • dependency type
  • source or evidence reference
  • current state
  • blocking severity
  • fallback plan
  • escalation owner
  • resolution note

Owners and responsibilities

Make record ownership and decision authority explicit.

  • person or role
  • responsibility
  • records owned
  • tasks owned
  • approval authority
  • backup owner
  • availability constraints
  • handoff rule
  • last reviewed date
  • acknowledgement state

Tools and guides

Declare the allowed local surfaces used for execution and review.

  • tool or route name
  • tool kind
  • intended use
  • record owner
  • input records
  • output records
  • authority boundary
  • manual action required
  • failure or unavailable state
  • last checked date

Evidence and attachments

Preserve traceable support for claims, requirements, budget assumptions, and packaging.

  • evidence ID
  • claim or requirement supported
  • evidence type
  • title
  • source locator
  • source date
  • source SHA-256 if available
  • provenance note
  • linked milestone
  • linked application section
  • attachment reference
  • access status
  • review status
  • limitations
  • replacement needed

Reviews and approvals

Separate drafting from human decisions and preserve review receipts.

  • approval ID
  • decision subject
  • version reviewed
  • reviewer or approver
  • review requested date
  • decision due date
  • decision state
  • comments
  • required changes
  • conflict or abstention note
  • decision receipt
  • approval date
  • next action owner

Risks and failure states

Track uncertainty, deadline exposure, missing evidence, and packaging failures.

  • risk ID
  • risk statement
  • category
  • likelihood
  • impact
  • severity
  • trigger
  • owner
  • mitigation
  • contingency
  • due date
  • current state
  • escalation threshold
  • resolution evidence

Closure

Close the project with a truthful record of what was completed, held, or abandoned.

  • closure date
  • final project state
  • application package version
  • completed deliverables
  • incomplete deliverables
  • held actions
  • unresolved risks
  • approval status
  • evidence completeness status
  • file and record references
  • lessons learned
  • follow-up owner
  • retention note
  • explicit non-submission confirmation

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.

Project identity

Define ownership and the local working context.

  • project title
  • applicant or organization name
  • project owner
  • collaborators
  • project status
  • private visibility
  • tags

Opportunity and requirements

Capture source-labelled requirements without treating them as verified qualification.

  • opportunity name
  • source locator
  • source SHA-256 if available
  • funder name as written in source
  • deadline date and time
  • timezone
  • required documents
  • page or word limits
  • eligibility notes
  • open questions

Application case

Structure the proposed work and evidence.

  • problem or need
  • proposed activities
  • goals and outcomes
  • audience or beneficiaries
  • timeline narrative
  • evaluation approach
  • risks and mitigations
  • evidence links

Budget and attachments

Track draft financial and supporting materials locally.

  • budget categories
  • requested amount
  • matching or in-kind notes
  • budget assumptions
  • attachment checklist
  • file references
  • missing evidence

Review and packaging

Prepare a human-reviewed package without submission.

  • reviewers
  • review due dates
  • review criteria
  • decision state
  • final local package label
  • submission owner
  • external action notes

Required or proposed record references

No record existence is asserted by this documentation page.

  • project record
  • grant opportunity note
  • application requirements checklist
  • scope and deliverables record
  • milestone records
  • deadline to-dos
  • dependency records
  • owner assignments
  • workback schedule
  • evidence and attachment references
  • risk records
  • review and approval records
  • closure record
  • project record with canonical ID, lifecycle, provenance, revision, tags, links, and attachments
  • opportunity brief or source-labelled call record
  • eligibility and requirements notes
  • draft narrative sections
  • budget worksheet or budget notes
  • workback to the stated deadline
  • review comments and approval records
  • submission-readiness checklist
  • held external-effect receipt

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

  • source_record:project:grant-application
  • NotebookCollectionKind.project
  • NotebookTodoPayload.dueAt
  • Notebook Agenda deadlines/workbacks
  • Observed native contract: project_and_field_guide_collections
  • Observed native contract: deadlines
  • Observed native contract: records
  • Observed native contract: pointguard
  • Observed app routes: /app/notebook/projects/
  • Observed app routes: /app/notebook/to-dos/
  • Observed app routes: /app/notebook/agenda/
  • Observed app routes: /app/notebook/approvals/
  • Observed app routes: /app/notebook/paper/
  • Observed app routes: /app/notebook/files/
  • Observed app routes: /app/notebook/field-guides/
  • Observed app routes: /app/pointguard/
  • project:grant-application
  • Notebook records provenance, source locators, revisions, lifecycle, tags, links, and attachments
  • PointGuard persistent cross-app context surface
  • APP_ROUTES:/app/notebook/projects/
  • APP_ROUTES:/app/notebook/to-dos/
  • APP_ROUTES:/app/notebook/agenda/
  • APP_ROUTES:/app/notebook/approvals/
  • APP_ROUTES:/app/notebook/paper/
  • APP_ROUTES:/app/notebook/files/
  • APP_ROUTES:/app/pointguard/