Glossary
This glossary defines key construction and software terms used throughout Baulit and its documentation. Terms are listed alphabetically.
| Term | Definition |
|---|---|
| BYOK | Bring Your Own Key. Baulit's AI model where users provide their own Anthropic API key rather than using a shared key. This gives you control over costs and usage. See BYOK Setup. |
| Change Order (CO) | A written agreement that modifies the original scope, cost, or timeline of a construction project. In Baulit, COs follow a 4-status workflow: Draft, Submitted, Approved, Rejected. See Change Orders. |
| COI | Certificate of Insurance. A document from an insurance carrier confirming that a subcontractor carries general liability and/or workers' compensation coverage. Baulit tracks COI expiration dates in the Contact Directory. |
| CPM | Critical Path Method. A scheduling algorithm that calculates the earliest and latest possible start and finish dates for every task based on durations and predecessor relationships. See Gantt Chart & CPM and CPM for Builders. |
| Critical Path | The longest chain of dependent tasks through a project schedule. Tasks on the critical path have zero float — any delay to a critical task delays the entire project by the same amount. |
| EAC | Estimate at Completion. The projected total cost of a project based on the original budget plus approved change orders and actual spending to date. Displayed on the Budget tab. |
| Edge Function | A server-side function hosted on Supabase's edge network. Baulit uses Edge Functions for AI processing, Stripe billing, and other operations that require server-side execution. |
| Float (Slack) | The amount of time a task can be delayed without delaying the overall project completion date. Tasks on the critical path have zero float. Tasks with positive float have scheduling flexibility. See Scheduling Fundamentals. |
| FS (Finish-to-Start) | A dependency type where the successor task cannot start until the predecessor task finishes. This is the only dependency type used in Baulit. Example: "Pour Foundation" must finish before "Frame First Floor" can start. |
| Gantt Chart | A horizontal bar chart that visualizes a project schedule over time. Each task is a bar whose length represents its duration, and bars are positioned according to their calculated start and finish dates. See Gantt Chart & CPM. |
| Predecessor | A task that must be completed before another task can begin. In Baulit, predecessors are linked using Finish-to-Start (FS) dependencies through the Dependency Wizard. |
| Punch List | A list of deficiencies and incomplete items identified during the final walkthrough of a construction project. These must be resolved before the project is considered complete. See Punch List. |
| RFI | Request for Information. A formal question submitted during construction to clarify design intent, material specifications, or other project details. Typically directed to the architect or engineer. |
| RLS | Row-Level Security. A database feature used by Supabase (PostgreSQL) that restricts which rows a user can read or modify based on their identity. Baulit uses RLS to ensure users can only access their own projects and data. |
| Successor | A task that depends on another task (its predecessor) being completed first. In a Finish-to-Start relationship, the successor cannot start until the predecessor finishes. |
| WBS | Work Breakdown Structure. A hierarchical decomposition of a project into phases and tasks. In Baulit, this is represented by the Phases & Sub-Tasks hierarchy. |
| Working Days | Monday through Friday, excluding weekends. All task durations in Baulit are measured in working days. A task with a duration of 5 working days that starts on Monday finishes on Friday of the same week. |