Projects

Projects are the primary working unit under a program. Each project represents a funded project (e.g., a subrecipient’s project) and holds its own budgets, payment requests, status reports, and data.

Project Basics

• Program — Every project belongs to one program and follows that program’s tabs, workflows, and settings.
• Applicant — Projects can be linked to an applicant (organization) for reporting and audit.
• Identifiers and metadata — Project number, name, description, status, category, and optional external IDs (e.g., state or federal IDs).
• Budget totals — Award amount, original budget, amendments, expended, and remaining amounts at the project level.
• Location — Optional coordinates for mapping or location-based reporting.

Project Tabs

Projects use the same tab types defined by their program (Dashboard, Financials, Payment Requests, Status Report, Milestone Summary, line-item fields, etc.). Program administrators can:

• Reorder and show/hide tabs for the program.
• Optionally hide specific tabs per project.

So each project gets a consistent but flexible workspace.

Key Project Areas

Budget

• Project-level budget view under the Financials (or Budget) tab.
• Budget mains, contracts, categories, and column values.
• Change orders and contract-level tracking.
• Links from payment request invoices to contracts and categories.

Payment Requests

• List of payment requests for the project.
• Create and submit new payment requests.
• Track status and workflow (e.g., pending, approved, paid).
• Attach invoices, line items, and miscellaneous files.

Status Report

• Status reports tied to program templates and metrics.
• KPI and target entry at the project level.
• Optional file attachments and submittal workflow.

Milestones and Gantt

• Program-level milestones can be used on projects.
• Project-level milestone dates and status.
• Gantt-style view for timeline and dependency visualization.

Notes and Details

• Project notes.
• Project details/settings (e.g., contacts, custom fields).
• User access and project-level role assignments (e.g., who is the Project Manager for this project).

Access

• Program access — Users need access to the program to see its projects.
• Project access — Additional project-level access and roles control who can view or edit a specific project and its payment requests, budget, and reports.

Projects are where day-to-day grant work happens: budgets are tracked, payment requests are submitted and approved, and status and milestones are reported—all within the structure defined by the program.