Delivery module
PROJECTS / MODULEProjects
Live gross margin, computed from approved labor, expense, and procurement actuals against contracted revenue, while the project is still open.
Plan to Delivery and Profitability
- 01
Staff and budget
The project is staffed, and a versioned budget is set across labor, expense, procurement, and contingency.
- 02
Break down work
Tasks and milestones define the deliverables.
- 03
Track time and expense
Consultants log time and expenses; self-approval is blocked.
- 04
Feed real actuals
Approved labor, expense, and linked procurement actuals compute live gross margin against contracted revenue.
What it is
The Vercentlabs Projects module plans, staffs, executes, and financially tracks billable and internal projects, connecting tasks and timesheets to real project cost and margin as the work happens, not after close.
Module atlas / operating conditions
Why Projects becomes difficult in fragments
Profitability is a surprise at close
You don't know whether a project actually made money until the books are closed and it's too late to change course.
Billing gets double-entered
Billable work is tracked in a project tool and re-entered into Sales or Accounting to actually invoice it.
Budget overruns surface too late
Labor and expense run over budget quietly, and nobody notices until the project is already behind.
Unclear timesheet accountability
Time entries get approved without a clear record of who signed off, or whether the person logging the time approved their own entry.
Operating outcomes
What changes when Projects shares one system of record
Real-time margin, not a post-mortem
Gross margin is computed live from approved labor, expense, and procurement actuals against contracted revenue — while the project is still open.
One billing handoff, not two
Billing milestones use idempotency keys to hand off to Sales/Accounting without a duplicate entry.
Budget visibility before it's a problem
Versioned budgets split labor, expense, procurement, contingency, and revenue, so overruns are visible against a specific line, early.
Accountable time entry
The person who logs a time entry cannot approve their own entry.
Capability architecture
The module, decomposed by operating capability.
5 capability groups organised by the way the product works, not as a flat marketing feature wall.
Project setup & staffing
How a project is defined and connected to the commercial record that funds it.
- 01Fixed, T&M, milestone, or non-billable billing method
- 02Customer and Sales-order linkage
Work breakdown
Breaking the project into trackable pieces.
- 01Tasks and milestones
- 02Subtasking
Time & expense tracking
The raw actuals that feed cost and billing.
- 01Time entries carrying both cost rate and bill rate
- 02Self-approval blocked on time entries
Budgeting
A versioned plan to measure actuals against.
- 01Budgets split into labor, expense, procurement, contingency, and revenue
Profitability & billing
The live financial picture of the project.
- 01Live gross-margin calc from approved actuals vs. billed revenue
- 02Idempotency-keyed billing milestones
- 03Completion blocked while tasks remain open
Primary operating sequence
A transaction-level view of how work progresses through Projects.
See it work
Plan to Delivery and Profitability
The ordered process a real Projects workflow follows inside Vercentlabs.
Trigger
A project is set up, linked to a customer and (optionally) a Sales order.
- Staff and budget
The project is staffed, and a versioned budget is set across labor, expense, procurement, and contingency.
- Break down work
Tasks and milestones define the deliverables.
- Track time and expense
Consultants log time and expenses; self-approval is blocked.
- Feed real actuals
Approved labor, expense, and linked procurement actuals compute live gross margin against contracted revenue.
- Bill
Idempotency-keyed billing milestones hand off to Sales/Accounting without duplicate entry.
- Close
A project cannot be marked complete while tasks remain open.
Approvals
- 01The person who logs a time entry cannot approve it themselves.
Automated actions
- 01Live gross-margin recalculation as actuals post
- 02Completion blocked with open tasks
Connected modules in this workflow
Outcome
A closed, profitable (or honestly unprofitable) project with a billing history that never required re-keying into Sales or Accounting.
Operational proof
Projects, documented as an operating system.
Capability architecture
5 groups
Grouped by how the module is actually structured.
Primary operating sequence
Plan to Delivery and Profitability
Rendered above as an ordered process rather than a feature collage.
Connected system
3 modules
Adjacent modules are linked through the operating model on this page.
Business outcome
Real-time margin, not a post-mortem
Gross margin is computed live from approved labor, expense, and procurement actuals against contracted revenue — while the project is still open.
Ready to see Projects running on your own data?
Book a DemoSystem map
Projects does not operate alone.
The handoffs below are part of the operating model, not decorative cross-sells.
Linked procurement records feed real actuals into project profitability — a confirmed, wired connection, not an estimate.
Projects can link to a Sales order, and billing milestones hand off through the same idempotent request pattern Sales uses.
Support tickets can reference the related project, giving service context on delivery issues.
Output register
What Projects tells operators and managers
Status, budget consumption, and open tasks across active projects
Audience / PMO, delivery managers
Live gross margin against contracted revenue
Audience / Finance, delivery managers
Rule register
What the module can run on its own
Gross margin recalculates as approved actuals post, not just at project close.
A hard rule blocks marking a project complete while it still has open tasks.
Enforced at the data layer, not just a UI convention.
Control register
How Projects stays governed
Module-specific controls shown separately from the platform-wide security architecture.
Access is controlled per project function — staffing, budgeting, billing — not one blanket role.
Applies to time-entry approval specifically, preventing a conflict of interest in cost reporting.
Row-level security backs the audit log, so history can't be edited around the access controls.
What to plan before going live.
- 01
Billing methods (fixed/T&M/milestone/non-billable) are configured per project type before go-live.
- 02
Cost and bill rates are set up per role or per employee, depending on how you actually price work.
- 03
Existing in-flight projects are migrated with their actuals-to-date, not restarted from zero.
- 04
Projects has no mobile presence today — a real gap for field-based time entry; plan for browser access.
Buyer questions
Questions teams ask about Projects
Can I see project profitability before the project closes?
Yes — gross margin is computed live from approved labor, expense, and procurement actuals against contracted revenue while the project is still open, not just as a post-close report.
Does project billing require re-entering data into Sales or Accounting?
No — billing milestones use idempotency keys to hand off, so the same billing event can't be entered (or double-billed) twice across systems.
Is there a mobile app for logging project time in the field?
Not today — Projects has no native mobile presence, which is a real gap for field-based time entry. Time tracking is a browser workflow.