---
title: "Projects and Documents"
url: "https://hurukan.com/modules/projects-and-documents"
description: "Programmes, stages, milestones and budgets per project, portfolio views, and every document attached to its record with revisions and reviews."
---

# Projects and Documents

Projects run across every other module: they sell, buy, schedule work and spend money. This module holds the programme, its stages, milestones and budget, shows the whole portfolio at once, and keeps every document attached to the record it belongs to, with its revisions and reviews.

[Talk to us](https://hurukan.com/contact)

Engineers in hard hats reviewing a printed plan and a tablet in a construction site office

Module

-   Programmes, stages and milestones
-   Budgets per project against real costs
-   Portfolio views across all projects
-   Every document on its record, with revisions and reviews

## Projects that touch everything

A project is rarely only a plan. It sells something in **Commerce**, buys materials in procurement, schedules work in operations and spends money tracked by **Finance**. When the project tool is separate, its status is whatever the project manager last typed in. In Hurukan the project is a record that the orders, purchases, hours and invoices already point to, so its status is what has actually happened.

## Budgets that are current

Each project budget shows plan, committed and actual. A purchase order approved this morning is already committed; hours recorded yesterday are already actual. The portfolio view puts every project side by side — stage, next milestone, budget position, open risks — without anybody assembling it for a meeting.

## Documents where they belong

A drawing belongs to the item and the project; a contract to the customer and the order; a certificate to the delivery. Documents in Hurukan are attached to the records they describe, with every revision kept. Reviews are routed to named people, recorded with their outcome, and a revision is released only when the required reviews are complete. An agent reading a project reads its documents too, and can answer which revision a customer approved and when.

## How it fits with what you run

An existing project or document tool can stay connected through the data layer while the module is adopted. Agents draft project reports, flag milestones at risk and propose changes to a plan; a person approves moving a milestone a customer was promised and releasing a document revision.

## What the module covers

01

### Programmes and stages

Projects grouped into programmes and broken into stages, each with an owner, dates and the records that belong to it.

02

### Milestones

Milestones linked to customer orders and billing schedules, so a delivered milestone can trigger the invoice it was agreed to trigger.

03

### Project budgets

Budgets per project shown as plan, committed and actual, drawn from purchase orders, invoices and recorded hours in the other modules.

04

### Portfolio views

All projects at once by stage, risk, budget position and next milestone, built from the record rather than assembled for a meeting.

05

### Documents on records

Contracts, drawings, specifications and reports stored against the project, order, item or supplier they belong to.

06

### Revisions and reviews

Every revision kept, every review recorded with the reviewer and the outcome, so the current version and its approval are always clear.

## Works with

[A hand placing a block on a white architectural model of a campus, with threads linking the buildings

### Ontology

The company's digital model: objects, relations and rules, versioned and growing with the business.

→

](https://hurukan.com/system/ontology)[A technician's hand plugging a cable into a neatly routed fibre-optic patch panel

### Data

Connectors and one data model: imports, sync, documents, e-invoicing and office suites in one record.

→

](https://hurukan.com/system/data)[Three people around a large touch table in a glass meeting room, one pointing at a flow of cards

### Agentic Logic

Domain agents that act within written limits, with people deciding on critical steps.

→

](https://hurukan.com/system/agentic-logic)[A person reviewing cash-flow charts on a large monitor at a tidy desk with a calculator and documents

### Finance

Finance and controlling: budgets from plan to forecast, inbound invoices, invoicing, payments and cash flow, linked to accounting.

→

](https://hurukan.com/modules/finance)[A manager approving items on a tablet at a desk in a minimal office

### Decisions and Tasks

One approval inbox for agent proposals with sources and risk, and tasks that always have an owner.

→

](https://hurukan.com/modules/decisions-and-tasks)

## Questions

How does it work with our document management system?

Documents are designed to live with the records they belong to. An existing document system stays connected through the data layer for as long as you keep it.

How do reviews work?

A document revision is sent for review to named people. Each review is recorded with its outcome and comments, and the revision is released only when the required reviews are complete.

Can a project budget show real costs?

Yes. Purchase orders, inbound invoices and recorded hours are already on the same record, so the project budget reflects what was committed and spent, not what was reported.

[← PreviousPeople](https://hurukan.com/modules/people)[Next →Decisions and Tasks](https://hurukan.com/modules/decisions-and-tasks)

## Build the company's operating system with us

Hurukan is pre-launch. If you run a company and want a sovereign, agentic system rather than another suite, we would like to hear what you need.

[Talk to us](https://hurukan.com/contact)