Project contract Project contract steering, fixed-price or time and materials

A project contract commits to milestones, deliverables, payment terms, and client obligations. Once signed, it is filed away; the execution carries on without it. In pylotik, the contract lives with the project: its billing mode, its schedule, its milestones in the grid, and the margin at completion read every week.

The object

What a project contract commits to.

Four families of commitments, which usually live in four different places. Details on contractual commitment tracking.

Milestones

Dates that commit, sometimes with penalties.

Deliverables

What is owed, and on what conditions it is deemed accepted.

Payment terms

What triggers an invoice: a milestone reached, a deliverable accepted, a due date.

Client obligations

Providing access, approving within a deadline, appointing a contact. They commit just as much.

Billing mode

Two schedules, one reading of the margin.

The mode is chosen in the project's contract. It changes neither the governance nor what the client reads.

Fixed-price

A schedule tied to the milestones. The gap between consumed and sold is computed when time is entered: drift shows from the first month, not at billing. See fixed-price project tracking.

Time and materials

A monthly schedule computed on the days produced and the rate of each profile. Days produced are reconciled with what was announced, month by month. See project time tracking.

In both cases: ordered, invoiced, paid, outstanding and margin at completion, read continuously. See financial tracking and profitability and margin.

In practice

The contract inside the project, not next to it.

Milestones in the grid

Contractual milestones live with the work packages and tasks. An approaching milestone shows, and a milestone reached triggers what it should trigger.

Change orders backed by a gap

Each request becomes a dated record when it is made. The change order starts from an observation, not from an end-of-project argument.

Client delays, dated

An approval expected from the client is a line with a due date, and its overrun is recorded instead of being told.

Governance

Committees that decide, and a record each side can produce.

The project committee follows progress, the steering committee decides. Each meeting produces minutes submitted to the client, approved or rejected with a reason, then frozen: the dated proof of what was decided, on both sides. Roles are set in a RACI matrix, with a single approver per decision.

See project governance, the project committee and the steering committee. Public procurement milestone models are supported natively.

FAQ

What we are asked about project contracts.

Does an internal project have a contract?

There is nothing to sign, but the same commitments run: due dates, mutual obligations. The project is steered the same way. See internal projects.

What happens to the project after go-live?

A maintenance contract can take over, with its period, volume, catalog and committee. See maintenance contracts.

Does pylotik issue the project's invoices?

No. It sends billing orders to your ERP's financial management, which issues the invoice.

Next

Going further.

See a project contract steered

The demo runs on a data set that is already filled in: a fixed-price project, its milestones, its schedule and its committees.