Monument

Glossary

Definitions of key terms and concepts used throughout the platform.

A

Allocation The assignment of a team member (or pool) to a project task for a specific time period. Allocations define who works on what, when, and for how many hours. They drive financial projections on the schedule.

B

Baseline A saved snapshot of a project plan at a point in time. Used to compare the original plan against the current state and measure scope creep or schedule drift.

Billable Hours Time entries that can be charged to a client. Contrasted with non-billable hours, which are internal (admin, professional development, etc.).

Billable Root The top-level task in a project hierarchy that is marked as billable. Revenue items below this point flow through to invoicing.

Blended Progress A metric combining actual time logged against allocated (planned) hours to forecast project completion. Gives a more realistic progress picture than either metric alone.

Budget The total estimated cost or hours for a project. Can be tracked as fixed-fee, time-and-materials, or a combination.

Burn Rate The rate at which a project is consuming its budget, typically expressed as cost per week. Used to forecast when a project will exhaust its budget.

C

Capacity The total hours a team member is available to work, typically per week (e.g. 40 hours). Used for utilisation calculations and overallocation detection.

Change Store Monument's internal mechanism for batching optimistic UI changes and syncing them to the server. Enables undo/redo and crash recovery on the schedule.

Company The top-level entity in Monument. All projects, team members, invoices, and data belong to a company.

Contact A person or organisation that interacts with your company — typically a client, consultant, or supplier. Contacts can be linked to projects for billing.

Custom Field A user-defined field that can be added to projects, tasks, resources, contacts, or expenses. Supports text, number, date, and select types.

D

Dependency A relationship between two tasks where one must start or finish before the other. Types: Finish-to-Start (FS), Start-to-Start (SS), Finish-to-Finish (FF), Start-to-Finish (SF).

E

EAC (Estimate at Completion) A forecast of the total cost to complete a project, based on current burn rate and remaining work. Calculated as actual cost + estimated cost to complete.

Effective Date The date from which a rate, setting, or change takes effect. Used in rate versioning to track when rates change over time.

Entitlement The number of leave days or hours a team member is allocated per year. Can vary by leave type and may include carryover from previous periods.

F

Financial Modifier A percentage or fixed-amount adjustment applied to an allocation's financial calculation. Multiple modifiers apply sequentially.

Financial Rollup The aggregation of financial values (revenue, costs, profit) from child tasks up to their parent. Enables project-level totals from task-level detail.

Formula An expression that calculates a financial value by referencing other items. Example: total.hours * 120 calculates revenue from total hours at $120/hour.

Frequency How often an allocation's hours are distributed — daily, weekly, or for the entire period. Affects how hours are spread across the allocation's date range.

G

Gantt The horizontal bar chart view on the schedule that shows task durations on a timeline. Part of the three-section schedule layout.

H

Holiday A company-defined day off that reduces team capacity. Holidays can be set globally (public holidays) or per region.

I

Invoice A billing document sent to a client for payment. Can include progress claims, time entries, expenses, or fixed amounts.

Item Panel The slide-out detail panel on the right side of the schedule and other views. Shows information about the selected task, allocation, or resource in tabbed sections.

L

Leave Approved time away from work — annual leave, sick leave, personal days, etc. Leave reduces a resource's available capacity for the affected period.

M

Materialized Path The internal representation of a task's position in the hierarchy (e.g. 1.2.3 means 3rd child of 2nd child of 1st root task). Enables fast lookups and reordering.

Milestone A significant checkpoint in a project, often tied to a deliverable or payment. Milestones can have completion criteria and trigger invoice creation.

Milestone Criteria The conditions that determine a milestone's progress — typically based on task completion, hours logged, or revenue earned. Can include sub-criteria.

O

Overallocation When a resource is scheduled for more hours than their capacity allows in a given period. Shown as a visual indicator in the schedule swim lanes.

P

Payment Terms The number of days a client has to pay an invoice after the invoice date (e.g. Net 30, Net 60). Configured per contact or organisation.

Phase A top-level task in a project hierarchy. Phases are a naming convention — technically they are tasks nested at the first level below the project.

Pool A group of resources that share a common characteristic (role, department, skill). Used for scheduling (allocate to the group) and permissions (control access).

Purchase Order A document sent to a supplier authorising a purchase. Tracks ordered vs. received quantities and amounts.

Q

Quote A pricing proposal sent to a client before work begins. Can be converted to an invoice when accepted.

R

Rate The hourly cost or billing amount for a resource. Resolved through a hierarchy: project override → resource → pool → organisation default.

Resource Lane A horizontal row in the schedule swim lanes section representing a single team member or pool. Shows that entity's allocations across the timeline.

Role A named set of permissions assigned to a user. Monument has three role domains: organisation, project, and pool.

S

Sequential Deduction The invoicing pattern where each milestone claim deducts all previously billed amounts. Prevents double-billing across progressive claims.

Shell & Version Monument's data model for projects and tasks. The "shell" has a stable ID that never changes; the "version" contains the actual data and is replaced when changes are saved.

Soft Delete When an item is marked as deleted but not physically removed from the database. Allows restoration and preserves referential integrity.

Split-by-Track A schedule view option that shows separate swim lane rows for each track within a resource pool, enabling more granular allocation visibility.

Sub-Criteria Nested conditions within a milestone criteria. Allow more detailed progress tracking — e.g. a milestone with criteria per project phase.

Swim Lane A horizontal row in the schedule's resource section. Each resource or pool gets its own swim lane showing allocations.

T

Task Status The current state of a task: Pending, In Progress, Completed, Blocked, or Cancelled. Organisations can define custom statuses mapped to these standard states.

Template A pre-built project structure that can be used to create new projects. Includes tasks, hierarchy, and optionally financial items and allocations.

Time Entry A record of work performed — includes date, duration, project, task, and description. The atomic unit of time tracking.

Timesheet A collection of time entries for a specific period (usually a week), submitted for manager approval.

Track A named sub-group within a resource pool (e.g. "Interior", "Structural"). Allocations can target a specific track for finer-grained scheduling.

U

Utilisation The percentage of a team member's capacity allocated to work. Calculated as allocated hours ÷ total capacity. Billable utilisation considers only billable allocations.

V

Variance The difference between planned (budget) and actual values. Positive variance means under budget; negative means over budget.

Version A snapshot of a project's or task's data at a point in time. See Shell & Version.

View Scale The timeline zoom level on the schedule — weekly (shows days), monthly (shows weeks), or quarterly (shows months).

W

Work Pattern A resource's weekly schedule defining which days they work and hours per day. Affects capacity calculations and how allocation hours are distributed across days.