Skip to main content
teamspace

Project execution: from order to sign-off in one run.

The plan is set, now the doing counts. teamspace carries the project from accepting the order through work packages, hours and milestones to billable work, all in one place, with a margin that stays current to the day. Part of project management in teamspace.

teamspace project execution: an order card AUF-2287 leads through an orange arrow into the project card Relaunch PRJ-014 at 62 percent progress, with six work packages, 188 of 240 hours and milestone 12 May, on to a billable card with three items; below runs a planned vs. actual bar with plan 240 hours, actual 188 hours, margin 21 percent and a green traffic light.

What it is about

Spreadsheets, email and phone calls break the project thread.

Execution across scattered tools

  • Plan in a sheet, hours in a second tool, invoice in a word processor
  • The current status is pieced together from several sources
  • An invoice only starts once someone writes an email
  • What a project earns is only clear at quarter-end
Recommended

Execution in teamspace

  • Order, work packages, hours and invoice hang on the same project
  • The status is readable at any time, down to the single entry
  • Once a sub-project is done, the item becomes billable on its own
  • The margin runs along to the day, not only at the close

The start

The order becomes the project.

Execution does not begin with an empty project, but with the accepted order. A single click turns it into the project: the order items become sub-projects and work packages, with budget and owners set from the outset.

So the link between order and work stands from the very first hour. Every entry that follows knows which item it belongs to.

  • Order items become work packages, without creating them a second time.
  • Budget, dates and owners hang on the node, not in a side list.
  • Templates from earlier projects bring phases and milestones along.

The principle

A project runs straight through, with no relay handovers.

Rather than being passed from tool to tool by hand, the project runs as a single pass from accepting the order to billable work. Plan and actual sit side by side the whole way.

Order AUF-2287 accepted
Project 6 packages created
Delivery hours logged 62 %
Milestone 12.05. sign-off
Billable 3 items ready
Plan vs. actual · live updates with every entry

Plan

240 h

Actual

188 h

Margin

21 %

Status

green

From order to sign-off, one run: the margin runs along the whole way.

Margin

The margin runs along, not just at quarter-end.

The key difference between steering and chasing is the moment the figures arrive. teamspace calculates the contribution margin continuously, from the internal hourly rates, the logged hours and the costs incurred. The result sits in the Analysis tab, not in a table someone fills in at quarter-end.

The view can be switched, depending on the question:

  • by project, right down to the single phase and entry
  • by client, to see which one carries
  • by period, from the current month back to the project start
More on project controlling

What holds it together

Three things hold the run together.

Execution only runs smoothly when status, data and billing hang on the same structure. That is what decides whether a project stays steerable.

Everything hangs on the same project

  • Order, work packages, hours and documents on the same node.
  • No carrying over between plan sheet, time tool and invoice.
  • One entry feeds status, margin and billing at once.

The status is readable at any time

  • Progress in per cent, from the task up to the main project.
  • Status with its own sequence per project type.
  • Milestones with an early-warning date, before a deadline slips.

Deviation shows up early

  • Alert levels on the traffic-light method: notice, warning, critical.
  • Thresholds as a fixed value or as a percentage.
  • Response possible before the client complains.

15 minutes

Show us a typical project run.

In 15 to 30 minutes we walk through your flow from order to sign-off, and you see where teamspace holds it together in one place. You get clear first feedback on whether that fits your setup.

Traceability

A log records every status change.

While a project runs, status and dates change. teamspace records these changes automatically in the project log, without anyone keeping a logbook. Whoever needs the history sees when which status was set and which milestone moved.

That keeps the project lead ready to speak to the client at any time: the current status and the path to it are on record, not reconstructed from memory.

Documentation

Documents sit on the work package, not in an inbox.

Sign-off records, concepts and images belong where the work happens. In teamspace the file storage sits on the project structure, so a document hangs on the right work package. Instead of asking a colleague, the people involved reach for it directly.

Office files can be edited online, and the versions stay traceable. So the project documentation builds up along the way, rather than as a double duty at the project's end.

More on project documentation

“I save a lot of time writing invoices.”

con|energy handles projects from order to invoice in teamspace, instead of pulling the status together from several tools.
con|energy consult

The close

Once the sub-project is done, the item becomes billable.

At the end of a run stands the invoice, and it too does not start with an email to accounts. Through billing rules the items are tied to the project status: as soon as a sub-project reaches the agreed status, the related items appear in the order as billable.

From the approved hours, flat rates and costs, the invoice is created in the stored layout, with the contact details from the client record. Fixed price, time and materials sit side by side in the same order.

More on project billing

More from project management

Use cases that dock straight on.

Project execution shares its data with these areas, without anyone keeping anything twice.

Work Breakdown Structure

Main project, sub-project and work package: the structure the execution runs on.

Learn more

Project Time Tracking

Log time on a phase or task, the source for status, margin and invoice.

Learn more

Project Controlling

Plan, actual and forecast current to the day, with alert levels on budget and margin.

Learn more

Project Billing

Approved hours become the invoice, fixed price and time and materials side by side.

Learn more

Project Documentation

Files, activities and a log that records the course on its own.

Learn more

Capacity Planning

Who is scheduled, who is free: utilisation per person and week.

Learn more
teamspace project management: control cockpit with planned vs. actual, forecast and traffic light per project

Part of project management

Execution sits inside project management.

Order, work packages, hours and billing are not a separate tool, but the delivery view of the projects you run in teamspace anyway. From the work breakdown structure through controlling to billing, in one overview.

See project management

Execution day to day

What project execution means day to day.

Project execution covers carrying out all project-related tasks from the start to the close of a project. The planning is taken as given; execution is about getting the work packages done and the administrative and steering tasks that keep a project on plan. Three of them decide its success: the project documentation, which evidences the status, the project controlling, which shows deviations early, and the project billing, which turns the work delivered into invoices.

teamspace brings these three together on one data basis. Because status, margin and billing all come from the same logged hours, every figure is traceable down to the single entry. Whoever wants to steer does not have to gather data, they see it. Where capacity planning is needed, the scheduling assistant in the enterprise edition takes account of holiday, sickness and contracted working time and reports conflicts to the planner.

We have been developing teamspace in Darmstadt since 1999. It runs in an ISO 27001 certified data centre in Frankfurt am Main, with data processing exclusively within the EU. The contracting party is 5 POINT AG, a German public limited company under German law.

Frequently asked questions about project execution

What is project execution?
Project execution covers carrying out all project-related tasks from the start to the close of a project, that is, getting the work packages done together with the administrative and steering tasks that keep the project on plan. The project planning is generally not counted as part of it.
What belongs to project execution?
Alongside the delivery itself, documentation, controlling and billing belong to it. Documentation evidences the status, controlling shows deviations in time, cost and performance early, and billing turns the work delivered into invoices. In teamspace all three work on the same logged hours and costs.
How does project execution differ from project planning?
Planning sets out what is to be done, when and by whom: structure, phases, budget and milestones. Execution is carrying that plan out: getting work packages done, logging hours, keeping the status and finally billing. teamspace connects both views on the same project structure.
How does an order become a project?
The accepted order is turned into the project with a single click. The order items become sub-projects and work packages, with budget and owners set. So the link between order and work is kept across the whole execution.
Do we see the margin during delivery already?
Yes. teamspace calculates the contribution margin continuously from the internal hourly rates, the logged hours and the costs incurred. The margin sits in the Analysis tab, current to the day and switchable by project, client or period, not only at quarter-end.
When does work become billable?
Through billing rules the items are tied to the project status. As soon as a sub-project reaches the agreed status, the related items appear in the order as billable. From these the invoice is created in the stored layout, with fixed price, time and materials side by side.
Does the project lead keep the overview when something drifts from plan?
Yes. teamspace works with three alert levels on the traffic-light method, whose thresholds you set as a fixed value or a percentage. When a project crosses a threshold, the system reports the level notice, warning or critical; each milestone also has an early-warning date.
Where is the project data stored?
All data is processed in an ISO 27001 certified data centre in Frankfurt am Main, exclusively within the EU. teamspace is Made in Germany and GDPR compliant. The contracting party is 5 POINT AG, based in Darmstadt.

First call

Let us walk through a live project once.

From the accepted order to billable work. In a short call you see how teamspace holds the run in one place, instead of passing it across several tools.