Use case
1,000 deliverables. One customer who remembers every promise.
Timill keeps the agreed deliverable list, scope of supply, shipments, deviations, and site planning in one live system. What you promised, what you shipped, and what's standing on site never drift apart.
The project lives in five files and three inboxes
- The deliverable list agreed with the customer is a master Excel, versioned by email, argued over at every progress meeting.
- Scope of supply sits in the contract annex; what actually shipped sits in packing lists; nobody has the live delta.
- Deviations are raised in meeting minutes and email threads, then resurface at handover as claims.
- Construction planning runs on a separate schedule that doesn't see procurement reality, so site crews wait on shipments nobody flagged.
- Full EPC/ERP suites exist for the majors. A 20–200-person EPC contractor or equipment supplier gets the same problems with none of the budget.
In an EPC project, the paper trail is the money. It shouldn't live in version seven of a spreadsheet.
The configuration
The contract, as a live data model
Item types
Deliverable
Document/deliverable number, discipline, description, revision, responsible, customer due date, status (Agreed → In progress → Submitted → Customer review → Approved), linked documents and correspondence.
Scope of Supply item
Tag/position number, description, quantity, supplier, linked shipment(s), status (Ordered → Manufactured → Shipped → On site → Installed).
Shipment
Packing list, contents (linked scope items), incoterms, ETD/ETA, actual arrival, customs docs, photos, status.
Deviation / Change
Origin (customer / supplier / site), description, cost & schedule impact, agreed resolution, customer sign-off, linked deliverables or scope items.
Construction Activity
Work package, predecessor links, planned window, crew, prerequisites (linked scope items that must be on site), progress, site photos.
Milestone
Contractual milestones with everything that hangs on them.
Links that create the trail
Construction activity → the scope items it needs → their shipments → their ETAs. When a shipment slips, you see which site activities slip before the crew is standing idle. A deviation links to the deliverable or shipment it came from — with the whole discussion attached, sign-off included. At handover, the claim conversation is a filtered list, not archaeology.
Automations
Deliverable due to customer in 14 days and not Submitted → flag. Shipment ETA changed → dependent construction activities reschedule on the Gantt and their owners are notified. Deviation created → PM notified; customer sign-off recorded → status moves.
From site and workshop
Progress updates and photos from the phone — installation status, arrival inspections, punch items.
What each role sees
Project manager (dashboard)
Deliverable status vs. customer dates, open deviations with cost impact, shipment ETAs against the construction schedule, milestone health.
Document / deliverable controller
Submission queue, customer review returns, revision status.
Site manager (mobile + board)
This week's activities, what's blocked on missing scope items, punch list.
Management
Portfolio view across projects — margin risks (open deviations), late deliverables, handover readiness.
A day with it
- 08:10
Supplier emails: transformer shipment slips 9 days. ETA updated on the shipment; on the Gantt, the two dependent construction activities reschedule automatically and their owners are notified — the site manager confirms the new sequence before the crew mobilises.
- 10:30
Customer progress meeting. Instead of defending an Excel version, you share the live deliverable status: 214 approved, 31 in customer review, 6 late with reasons attached.
- 14:00
Site finds a foundation mismatch. Deviation raised from a phone with photos, linked to the drawing deliverable, cost impact estimated. It's in the claim file from minute one.
- Handover
Scope of supply: every position from Ordered to Installed, traceable. Deviations: every one signed off. The final account discussion takes days, not months.
Who this fits
Common in: EPC contractors and equipment suppliers delivering projects (energy, marine, industrial plants), machine builders with installation scope, electrical/automation contractors on large sites — 20–200 people running projects on Excel deliverable lists and email. Strong fit for the energy-technology supply chain, with its contractual documentation demands.
Why Timill and not…
Excel + email
The current system — and the reason handover claims take months to argue.
Enterprise EPC suites
Built and priced for the majors; a year to implement.
Generic project tools
A deliverable with revisions and customer review cycles, a shipment with a packing list, a deviation with cost impact. These aren't "tasks." Timill lets you model the real contractual objects and link them.
Pairs with non-conformance for workshop quality and work orders for after-sales service. One platform from project to service business.
This configuration comes from real EPC project delivery experience in the Finnish energy sector: the deliverable lists, shipment tracking, and deviation handling are the ones our founder actually ran.
From site and workshop
Live on every dashboard
Questions
Our deliverable list is 800 rows in Excel.
Import it — it becomes the live register, with statuses and owners.
Can the customer see progress?
Role-based access supports limited views; the right setup depends on the project — ask on the call.
Does it do CPM scheduling like Primavera?
More than you'd expect. Timill has a Gantt view where activities are linked by dependencies, and scheduling rules cascade a change: move one activity and its children and dependents reschedule automatically. It's not a full resource-levelling CPM engine like Primavera, but for most EPC delivery it covers the planning you actually need. For heavy CPM, keep your scheduler alongside — the REST API connects them.
Multiple projects at once?
Yes — per-project views plus a portfolio dashboard across projects.
On-premises?
Yes, Docker-automated — often relevant for energy-sector data policies.
See your project, live
Bring one running project's deliverable list — we'll show it as a live register with shipments and deviations connected, in 30 minutes.