# Project ## Projects In FieldWorker, a Project is the "connective tissue" of the platform. It is far more than just a folder; it is the structural link that binds a Customer (the person receiving care) to a Payer (the entity funding the care) and a specific Plan of Care. Because the Project houses these core relationships, it creates a ripple effect across every other functional area of the application: #### The Strategic Intersection A project is where the administrative and clinical sides of the house meet. By defining the following three elements, the project dictates how the app behaves for that specific case: * Customer & Sponsor: Defines *who* is being served and their primary contact points. * Payer (Primary/Secondary): Determines *where* the money comes from and which billing rules (like 837P or 837I forms) will apply. * Plan Version: Links the project to a specific set of authorized services and hours, ensuring staff don't work outside the approved scope. #### Downstream Implications Setting up a project correctly has direct impacts on the following modules: * [Scheduler](https://dev.fieldworker.ai/scheduler): You cannot effectively schedule a visit without a project. The project tells the scheduler which employees are authorized to work with that customer and ensures that the total hours scheduled don't exceed the [Plan's](https://dev.fieldworker.ai/projects) authorized limits. * [Locate](https://dev.fieldworker.ai/locate) & [EVV](https://dev.fieldworker.ai/evv): When a staff member checks in via the mobile app, the GPS data is compared against the Locations saved within the Project. This is critical for Electronic Visit Verification (EVV) compliance. * [Timesheets](https://dev.fieldworker.ai/timesheets): Every minute logged by an employee is "tagged" to a Project. This allows the system to calculate the Time Spent on Tasks (e.g., the *11 hours* seen in the Dexter Morgan Project) accurately. * [Billing](https://dev.fieldworker.ai/billing): This is where the project context is most vital. The system pulls the Price, Self Pay status, and Payer info directly from the [Project Page](https://dev.fieldworker.ai/projects) to generate clean, error-free claims. #### Data Centralization (The "One-Stop Shop") The Project page acts as a "Source of Truth" for the entire team: * Managers use it to monitor progress via the Project Overview. * Biller/Admins use it to verify insurance and contract end dates. * Field Staff (via the mobile app) see the project notes and tasks to understand exactly what is required during their visit. #### Summary of Project Metadata
FieldImpact on the App
Start/End DateControls the window of time when Tasks can be created and billed.
ManagerDetermines who receives Notifications regarding task completions or issues.
ArtifactsCentralizes all proof-of-service (photos, signatures) required for audits.
> Context Note: Without a properly configured Project, the app cannot automate billing or ensure EVV compliance, making it the most critical step in the [Workflow](https://dev.fieldworker.ai/workflows) setup. ### Project Navigation & Filtering The top of the [Projects](https://dev.fieldworker.ai/projects) page contains a header bar designed for quick searching and organization: * Project Search: A dedicated search bar to find projects by name. * Status Filter: A dropdown to filter projects by their current stage (e.g., Ongoing Plan). * Sort By: Options to organize the list by Title or other metadata for easier browsing.
#### Project Details Sidebar When a project is selected (e.g., the Dexter Morgan Project), the left-hand pane displays essential administrative data: * Core Info: Includes the Project Status, Start/End Dates, and a brief Description (e.g., "EVV Services"). * Financial & Plan Data: Lists the Plan Version, Price, Self Pay status, and Payer information (Primary/Secondary). * Key Personnel: Identifies the assigned Manager (e.g., Gregory Robinson) and the Customer/Sponsor. * Edit Tool: An Edit Icon () allows administrators to modify these project parameters on the fly. #### Management Tabs The main workspace is divided into several tabs to separate different types of project data: * Overview: The default view, featuring a map of project-related locations and high-level statistics. * Tasks: A list of all scheduled and completed work items associated with the project. * Employees: A directory of staff members assigned to this specific project. * Files / Notes: Centralized repositories for [Documents](https://dev.fieldworker.ai/documents) and internal communications. * Contacts: A list of key stakeholders or family members related to the project. #### Interactive Overview Features The Overview tab specifically provides visual and quantitative insights: * Geographic Map: An interactive map showing the physical Locations (pins) associated with the project. * Project Metrics: Summary cards that display: * Locations: Total count of service sites. * Time Spent on Tasks: Cumulative hours logged (e.g., 11 hours across 13 tasks). * Artifacts: Total number of files or proof-of-service uploads. #### Quick Actions From this page, users can utilize the sidebar to jump to related functions like the [Scheduler](https://dev.fieldworker.ai/scheduler) for future planning or [Billing](https://dev.fieldworker.ai/billing) to process the hours logged within the project. ### Editing a project The Edit Project form is the central interface for configuring the administrative and financial rules of a project. It is divided into two primary sections: Basic Details and Date & Location. #### Basic Details Tab This tab establishes the project’s identity and its billing structure. * Project Title: The formal name of the engagement (e.g., Dexter Morgan Project). * Project Description: A brief summary of the services being provided (e.g., EVV Services). * Project Active Plan Version: A numerical field indicating which iteration of the care plan is currently authorized. * Customer: A dropdown to link the project to a specific client record. * Project Sponsor: Allows for the selection of a third-party or family member overseeing the project. * Project Manager: Assigns an internal staff member to oversee the project’s progress and notifications. * Financial Configuration: * Self Pay?: A toggle (Yes/No) to indicate if the customer is paying out-of-pocket. * Primary/Secondary Payer: Dropdown menus to link the project to specific insurance providers or government agencies. #### Date & Location Tab The Date & Location tab is where you define the physical and temporal boundaries of the project. This data is critical because it directly controls the [EVV (Electronic Visit Verification) logic and ensures that staff check in at the correct times and locations.](https://dev.fieldworker.ai/evv) #### Service Timeline * Start Date: The official beginning of the project or contract. The system will generally prevent [Task](https://dev.fieldworker.ai/new) creation or check-ins before this date. * End Date: The final date of service. This is vital for compliance to ensure no services are rendered (or billed) after a plan expires. #### Geographic Boundaries (Geofencing) This section ensures that fieldworkers are physically present at the authorized site: * Location Dropdown: Allows you to search for and select specific addresses. * Interactive Map: A [Google Maps](https://maps.google.com/maps?ll=40.735657,-74.172363\&z=10\&t=m\&hl=en-US\&gl=US\&mapclient=apiv3) interface provides a visual confirmation of the service area. You can see the exact purple pin representing the client's location. * Selected Locations List: A summary list appearing below the map that displays all authorized addresses (e.g., *140 east centre street Apt 2, Kearny, NJ*). This allows for multiple authorized sites per project. #### Financials & Billing Units At the bottom of this tab, you define the "unit cost" for the project: * Price: A mandatory field (`*`) where you enter the numerical rate for the service. * Currency: Defaults to the local currency (e.g., United States USD). This ensures that when [Timesheets](https://dev.fieldworker.ai/timesheets) are converted to [Billing](https://dev.fieldworker.ai/billing) claims, the math is handled automatically by the system. #### Finalizing Changes * Submit Button: Once all mandatory fields (marked with `*`) are filled, clicking Submit saves the configuration. * Immediate Effect: Updates made here will instantly reflect on the [Locate](https://dev.fieldworker.ai/locate) page, moving pins or updating the project's active status for the entire team. > Pro Tip: Always double-check the End Date. If a project reaches its end date, it may move to an "Expired" or "Completed" status, which could prevent staff from checking into their [Tasks](https://dev.fieldworker.ai/reports). #### Key Functionalities * Validation: Fields marked with an asterisk (\*) are mandatory to ensure data integrity for [Billing](https://dev.fieldworker.ai/billing) and [Timesheets](https://dev.fieldworker.ai/timesheets). * Persistence: Clicking the Continue button saves the changes and updates the project across the entire [FieldWorker platform](https://dev.fieldworker.ai/). * Global Impact: Updating the Payer or Plan Version here will immediately reflect in how future claims are generated in the [Billing module](https://dev.fieldworker.ai/billing). ### --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://fieldworker.gitbook.io/fieldworker-docs/fundamentals/pages/project.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.