Project portal

On a project the question is never what the company is doing. It is what is happening on this job, this week.

Who opens it

The client who is paying for the project, and often the people around them: an adviser, a tenant, an authority, a subcontractor. Each gets access to the one project that concerns them rather than to everything you have running.

What they see

Where the project has reached and what the next milestone is. Drawings and documentation in the current revision. Documentation of what has been delivered and to whom. Handover material collected in one place instead of scattered through a year of email.

Where it comes from

From the project tools your team already works in, including the industry-specific ones. The portal shows what those systems say, so a drawing that was revised this morning is the drawing the client opens this afternoon.

What it saves you

Sending the same file twice, and the discussion about which version someone was working from. On handover it saves the week of collecting documentation, because it was collected as the project ran.

What it is not

  • Not a project management tool. Your team keeps planning where it plans today.
  • Not a drawing archive. The current drawing is the one your system says is current.
  • Not a second place to maintain. Kilango stores neither the plan nor the drawings.

See which systems can feed it