Skip to main content

Project administration

Sub-areas of the project administration: General, Project settings, Billing settings, Invoicing, Resource Planning, and Reports on the project.

Written by Gideon Weller

Project administration bundles all sub-areas and actions that are stored directly on an individual project. You reach it via the detail view of a project by clicking the abbreviation or the description in the project overview. Which sub-areas appear depends on your role, the product line, and the licensed add-on modules.

Note: The sub-areas are organised into six groups: General, Project settings, Billing Settings, Billing, Resource Planning, and Reports. ZEP shows each group and item automatically by licence, module, and permission. A complete description of all fields of the project dialog is provided in the article Project data, the process from creation to deletion in the article Creating, editing and deleting projects.

General

The General group bundles the sub-areas you need most in day-to-day project operation: the master data, the structure of tasks and team members, and the module-dependent areas such as tickets, work items, offers, and documents.

Data & Plan

Via Data, you open the master data maintenance of the project with the tabs General, Plan, Customer & Invoice, and Address. With the add-on module Project Planning, the item appears under the title Data & Plan, because the plan values are then maintained as well. Via Edit, you open the fields for changes.

A complete description of all fields with their availability hints is provided in the article Project data. On this page, ZEP additionally shows messages as long as the project is not yet fully set up or not yet bookable:

  • If no project team members are assigned to the project yet, No project team members defined appears. Without assigned persons, nobody can book onto the project.

  • If the project is not yet structured into tasks, No tasks defined appears. If both are missing, ZEP adds the hint Employees can’t book project time on this project.

  • If, for billing by daily rate, the daily rate portions are not defined gaplessly, ZEP lists the open hour ranges and notes that 0 daily rates are counted for bookings in those gaps.

  • If work packages lie outside the project run time, a corresponding hint appears so that you correct the run time or the work packages.

Additionally, ZEP checks the consistency of the project data and reports contradictions directly here. This way, you see right on the data page what is still missing for the project to be used productively.

Project Plan

The Project Plan is the graphical view (Gantt chart) of the project, its tasks including tickets, and the scheduled team members. It visualises the project structure and the timeline and at the same time serves the quick entry of plan figures such as tasks, team members, and planned values for the whole project.

Note: The project plan is included in ZEP Professional and is added in ZEP Compact via the add-on module Project Planning.

Filters and view

Via the filter bar, you adjust what the project plan shows:

  • Filter by single, several, or all team members; clicking Execute shows the tasks the selection is assigned to as project or task team members.

  • Via the checkbox show finished tasks, you also display tasks whose end date lies before the display period.

  • Switch between day, week, and month view and navigate via the arrows or the calendar selection.

  • Columns can be shown individually; all settings are saved per user and per project (position on the timeline, expanded summary tasks, and more).

Display and editing

In the project plan, you edit the structure directly in the graphic. The following elements are available:

  • The project hierarchy starts with the project, below it the tasks; summary tasks are shown in grey and can be expanded and collapsed.

  • Project and tasks appear as green bars; a click opens the editing dialog.

  • In drag-and-drop mode, you move tasks to a new position; a possible target is highlighted in yellow on hover.

  • If a person is not employed in a period, this is indicated by a dark grey bar.

  • Via the column selection, you edit plan figures directly in the plan and show or hide the employee assignments.

Display with the add-on module Ticketing system

With the add-on module Ticketing system, the project plan also includes tickets and subtasks:

  • Tickets and subtasks can be shown and hidden and additionally filtered by ticket status.

  • Per row, the employee assignment, the ticket with its processor, and the subtask with processor and status are displayed.

  • On hover, a pop-over shows the details of the respective entry.

Project Team Member

In the Project Team Member sub-area, you manage which persons are assigned to the project. Only assigned team members may book project times and receipts onto the project. Via the period selection and Execute, you see who may book in the chosen period; the list can be exported as CSV or Excel.

Function in the project

You set the function of a person via the Project lead column in the team-member row. Three functions are possible:

  • Project team member (empty checkbox): may record times and receipts and report on the data they have entered themselves.

  • Project lead without budget responsibility (green check): leads the team professionally but sees no menu items with monetary amounts.

  • Project lead with budget responsibility (yellow check): additionally controls budget, planning, and billing of the project.

Note: What the two project-lead functions may do in detail is described in the roles-and-rights overview in the article Employee data in the Employee roles section.

Assigning team members

You assign further persons via Assign additional team members; only currently employed, not yet assigned persons are offered, filterable by employee category and search term. Via Copy team assignment from another project, you take over a complete team, and via the e-mail icon, you write to individual or all project team members directly from the project. Via the marker Only currently employed in the list, you hide assigned but currently not employed persons.

Tip: You filter the selection of persons to assign by employee category and search term. If you maintain categories by skill level, qualification, or topic area, you assign exactly the matching team members instead of searching the entire workforce.

If a person does not appear in the selection, they are usually already assigned in the past or future, or their employment only begins later. In this case, extend the assignment period from the project start or assign the person via employee management. With the add-on module Locations & departments, an assigned person does not have to belong to the department of the project; in the department reports, the costs are then distinguished by department-internal and department-external team members.

Tip: If a person with the role User with additional rights creates a project, they are automatically assigned as the project lead of that project and can set it up further right away.

Assignment periods

Per person, you store one or several assignment periods via the blue bar. A click on the bar opens the assignment window with the following entries:

  • Assignment period: from and to date in which the person may book onto the project. Via the plus icon, you create a further period when something changes from a date; if periods overlap, ZEP shortens the older one automatically after confirmation.

  • Price group: determines the billing rate of the person in this project. Set project-specifically, it deliberately deviates from the person’s standard price group, for example when a customer receives a special price.

  • Default planning (availability): percentage of working time at which the person is scheduled onto the project by default in resource planning, for example at 50 percent, without maintaining each day individually.

  • Internal hourly rate: project-specific internal rate of the person if it deviates from their standard rate in the project, so that revenue and cost reports calculate correctly.

  • Remark: free text on the assignment, for example a note on the role or a restricted availability of the person. Only visible internally in the assignment.

Note: The price group and the internal hourly rate appear from ZEP Compact with the add-on module Revenue and costs as well as in ZEP Professional. The default planning appears only with the add-on module Resource Planning.

Mass editing

For several persons at once, you use mass editing: mark the desired rows via the checkboxes, choose the operation in the action selection field that appears, and confirm. Available are:

  • Change function: set selected persons as project team member, as project lead without budget responsibility, or as project lead with budget responsibility.

  • Change default planning (only with the add-on module Resource Planning).

  • Set end date for the assignments of the selected persons.

  • Delete employee assignments.

Scheduling and collisions

Via Edit planning, you open the day-by-day scheduling of the person directly from this sub-area; this function appears with the add-on module Resource Planning.

Note: If schedules collide with the project assignment or with absences, ZEP points this out specifically. If schedules lie outside the assignment period, you collect and remove them via a dedicated hint; likewise, schedules that fall on absence days of the person can be deleted via a hint. This way, you keep planning and actual availability consistent.

Tasks

Tasks structure a project into professional work packages, often also called project phases or milestones. Through them, you map the complete structure and complexity of a project, from a simple to-do list to a deeply nested undertaking. Tasks are at the same time the basis of any Time Reporting: without at least one bookable task, nobody can book times onto the project.

Task list and filters

In the task list, you see all tasks of the project. Several filter criteria are combined with AND, so that only tasks appear that meet all criteria:

  • Period (preset to project start until end), task status, and team members (explicitly or implicitly assigned).

  • The checkbox show remark in full and the checkbox do not expand structuring tasks control the display.

  • Via the arrow icon, you set a single task directly to the next status.

  • Frequent filter combinations are saved as a favourite. Plan and actual figures always refer to the overall project, not to the set period.

Creating and structuring tasks

Via Create new task, you create a task. In the dialog, you assign an abbreviation that is unique within the project, a description, optionally a superordinated task, and a sort order that determines the order in the selection lists.

This creates a hierarchy: a task with subordinate tasks becomes a summary or structuring task and is not bookable itself; bookings only go to the lowest level. The superordinated task temporally encloses the run times of its subtasks.

Example: In a multi-level engineering project, the task hierarchy maps the project phases and work packages:

  • 1 Planning (structuring task)

    • 1.1 Basic assessment (structuring task)

      • 1.1.1 Site analysis (bookable task)

    • 1.2 Preliminary design (bookable task)

  • 2 Execution (structuring task)

    • 2.1 Detailed design (structuring task)

      • 2.1.1 Structural calculation (bookable task)

    • 2.2 Assembly (structuring task)

      • 2.2.1 Commissioning (bookable task)

No bookings go to the structuring tasks; they only bundle the hours and costs of their subtasks for the analysis. This way, even a very complex project can be mapped cleanly and analysed in a differentiated way at every level.

Warning: A task that has already been booked can no longer be turned into a structuring task, and a task with its own employee or activity assignment is not offered as a superordinated task. With the add-on module Invoicing, the superordinated task can also no longer be changed once invoice items exist for the task.

Copying tasks from another project

Via Copy tasks from another project, you take over the structure of a template project instead of creating each task anew. You select the template project and then all or single tasks.

  • Optionally, you take over the periods and the task team members of the template.

  • Copied task team members are, if needed, automatically created as project team members too (with the standard price group, the task assignment with the task price group).

  • The task status is not copied along; the copy always starts with the first status of the sequence.

Table configuration and quick actions

The task overview works analogously to the project overview. Which columns appear depends on the product line and modules; the hierarchy is shown as an expandable tree. Configurable are, among others:

  • Plan, actual, and plan-minus-actual hours for the target-actual comparison per task (with the add-on module Project Planning).

  • Type of accounting and Daily rates offered for the commercial view (with Invoicing or Revenue and costs).

  • Cost centre, remark, task team members, and start and end date as additional columns.

Directly in the row, quick actions are available:

  • Edit task via the edit icon.

  • New task as a copy via the copy icon.

  • Delete task.

  • Change status via the status field (next status by click in the popup).

  • Toggle billability via the billability icon.

  • Add work package via the work-package icon (with the add-on module Resource Planning).

Mass editing

For several tasks at once, you use mass editing: mark the tasks via the checkboxes, choose the operation in the action selection field, and confirm. Available are:

  • Change task status for several tasks at once.

  • Add or remove task team members.

  • Delete the selected tasks.

Task data as a sub-project

On the detail page, a task behaves like a small sub-project. It is organised, like the project dialog, into three tabs in which you set many values task-specifically and deviating from the project.

The three tabs at a glance:

  • General: abbreviation, description, superordinated task, sort order, run time, status, and a remark. Only tasks with a bookable status appear in the selection lists during project-time and receipt recording.

  • Plan: planned hours (fixed or dynamically aggregated from the subtasks, with the suffix (dyn)), planned total rates as well as planned receipts and mileage. A negative planned amount acts as a discount, and with flat-rate billing these planned values form the fixed price. The booked actual and billable actual hours are shown for control. Via prevent overbooking, you block bookings once the planned hours are exceeded; the project lead is informed by e-mail in this case.

  • Billing: type of accounting (like project or deviating, in which case the task is shown separately on the invoice), Daily rates offered (only with daily-rate billing, determined from the billable actual hours according to the daily rate portions), default billability, receipt recording possible (only if the project allows receipt recording), order number, job number, cost centre, and cost unit.

The price group and the internal hourly rate can also be set deviating at task level, so that you can calculate and analyse internal rates in a differentiated way per task.

Additionally, a task can be assigned its own deviating task team members and an own activity list via dedicated functions, so that a sub-project can be calculated and analysed fully independently. The meaning of the individual fields, such as the types of accounting or the overbooking options, is identical to the project level and described in detail in the article Project data.

Tickets

The ticket list per project shows all tickets assigned to this project with status, priority, processors, and deadlines. With the active ticket board, you additionally open a kanban board of the project-related tickets. Tickets are geared towards externally incoming matters, such as change requests or support enquiries from the customer side.

Note: The ticket view only appears with the add-on module Ticketing system. Structure and operation are described in detail in the corresponding collection.

Work Items

In the Work Items sub-area, you manage the internal to-dos of a project. Work items represent internal project-management topics, in contrast to tickets, which are geared towards externally incoming matters such as change requests or support enquiries. Both can be used in parallel and thus cleanly separate external matters from internal to-dos.

Note: Work Items are included as a standard function in ZEP Compact and ZEP Professional; they are not available in ZEP Clock.

Views and use

Work items are available in two views between which you can switch at any time: a list in tabular form and a project board (kanban) on which work items are moved between status columns via drag & drop. This way, you use the work-item management flexibly as a personal to-do list, for distributing work in the project team, or as a project-management board for the project lead.

Creating a work item

When creating a work item, the following fields are available:

  • Title (mandatory): short name; without a title, the work item cannot be saved.

  • Project and task (optional): assignment to project and task; without a project, the work item is a purely personal to-do, invisible to others.

  • Assignee: only persons assigned to the project as project team members or project lead.

  • Status and priority from the values defined in administration, each preset with the default for new work items.

  • Due Date (optional): highlighted by colour in the list and board (orange from tomorrow, red when today or exceeded).

  • Description, file attachment (PDF, JPG, or PNG, maximum 52.5 MB), and a checklist with up to 15 items.

Project work items

In the project, you find the work items under General > Work Items; all work items assigned to this project are shown. If you create a work item here, the project is already preselected and no longer changeable in the dialog. As assignee, only persons assigned to the project are available. If an administrator creates a work item in a project in which they are not a project team member themselves, they cannot set themselves as assignee but can assign the work item to another person or create it without an assignee.

The project work items are available in two views. Via the icon at the top right, you switch between them; depending on the current view, the tooltip reads Switch to board or Switch to table:

  • List view: shows the work items in a table. You sort via the column headers, filter and search the list, and show or hide columns via the gear icon. Clicking the title opens the work item for editing.

  • Board view: shows the work items as a kanban board with one column per status, with the assignee additionally appearing on each card. Via drag & drop, you move a card into another column and thereby change its status. The column structure (move, show, and hide columns) is adjusted only by administrators and the project lead; project team members move work items but do not change the structure. Adjustments to the project board do not affect the personal boards of the users.

Permissions

  • Administrator: sees and edits all work items of all projects and adjusts every project board.

  • Project lead (with or without budget responsibility): sees, creates, and edits all work items of their own project and adjusts its project board.

  • Project team members: see and edit the work items of the project but do not change the column structure of the board.

Note: The status and priority master data as well as the setting whether employees may see project work items are maintained by administrators under Administration > Work Items; details are described in the article Work Items – Administration, the daily operation and the personal work item list in the article Work Items in the Personal Area.

Offers

The offer list per project shows all offers created in the context of the project, including status, volume, and transfer to invoices. This way, you track an order continuously from the offer to the billing in one place.

Note: The offer view only appears with the add-on module Quoting. Creation and workflow of the offers are described in the corresponding collection.

Documents

The document list per project maintains documents with status, category, tags, and versions. It is suitable for the structured filing of all project-related contracts, concepts, protocols, and delivery documents in a central location accessible to all project participants.

Note: The document view only appears with the add-on module Document management. Filing structure and versioning are described in the corresponding collection.

Change History

The Change History logs every documented change to the project data: who changed which field to which value and when. This makes subsequent adjustments fully traceable. Typical use cases are the proof for a data protection request, the audit proof towards an inspection, and the later reconstruction of a project configuration.

The sub-area appears as soon as the recording of project-data changes is activated in the administration. How you switch on the recording is described in the article Other – Administration.

Project settings

The Project settings group bundles the professional defaults that control the booking and billing behaviour of the project. It is visible for administrators and project leads.

Default Billability

The default billability defines how new project times are preset during recording.

Four presets are available:

  • Billable, user can change the flag: times are preset as billable, team members can switch the flag per booking. The standard for customer projects.

  • Billable, user can not change the flag: times are billable, the flag is locked; useful when all services are billed.

  • Default Not Billable, user can change the flag: times are not billable by default but can be marked as billable when needed.

  • Not Billable, user can not change the flag: times are not billable and locked; useful for internal projects without a customer assignment.

How the setting works:

  • It works hierarchically: project, then task, then project activity, with the respectively lower level overriding the higher one.

  • A change affects only future bookings; already recorded times remain unchanged and are adjusted when needed via the action Rebook project times in the project time report.

  • For flat-rate projects, billability does not affect the invoice amount but is relevant for the Time Report and the Project Status Plan report.

Project Activities

Under Project Activities, you define which activities are available for this project during time recording. If the list remains empty, all activities defined in administration are allowed; as soon as you maintain an own table via Add activity, only these are available.

  • Standard activity: presets the activity selection during time recording, separately at project and at task level. If none is set, - Without - appears; via Assign other standard activity, you change it. This avoids mis-bookings, for example by a task Travel suggesting the travel activity.

  • Per project activity, an own default billability can be stored that deviates from the project and task level.

  • If you want to prevent the booking of travel for a project, add all activities except the travel activity to the list.

Daily Rate Portions

Daily rate portions stagger which share of a daily rate is billed per booked number of hours; they apply exclusively to the type of accounting expenditure at daily rates. Per line, you define an hour range via from hrs and To hrs and the chargeable daily rate portion within it, for example 0.5 daily rates from 4 to 6 hours and 1 daily rate from 6 hours. Without an own definition, the staggering from administration applies.

Warning: As soon as you define an own daily rate portion for the project, the administration graduation becomes completely invalid for this project. The project-specific graduation must then be defined gaplessly from 0.00 to 24.00 hours, otherwise no daily rates are calculated for the gaps. Gaps are not filled from the administration.

Project Work Locations

Under Project Work Locations, you assign certain work locations to the project. Via Change project location assignment, you select the locations and confirm with Apply. If project locations are defined, only these locations are available during time recording, and also when rebooking in the project time report, only a location from this list can be chosen; a target location that is not assigned stays unchanged. This keeps the location assignment consistent across the whole project, and with active travel expense management, the subsistence costs are calculated correctly per location.

Billing Settings

The Billing Settings group bundles the commercial defaults of the project, from the layout specification for the record to prices, receipts, and travel.

Note: The group and its items appear depending on the add-on modules Invoicing and Revenue and costs as well as the permission to edit the invoicing of the project.

Format

Under Format, you define how the services billed by effort are displayed; the same format applies to the Time Report, which can also be used for flat-rate projects. You control separately for the Invoice attachment, the Project Accounting, and the Time Report the level of detail with which the content appears.

In the detailed report, you select per area how the individual entries are output:

  • Team members: do not display, as grouping, or as table columns.

  • Working times, travel costs, and receipts: do not display, summary only, table only, or table and summary.

  • Times of day: without times, with times, or without times with daily totals.

For billing by hour, you additionally control the subtotals (none, by task, by task and ticket, by activity, or by price group) and show tasks, activities, remarks, locations, and tickets; the billable travel times can be shown separately in the summary.

For billing by daily rate portions, you additionally output the number of hours per line, show remarks, locations, and activities per day, and optionally take into account the price factors for hourly rates.

Further switches show a billable or price group column, insert a page break at groupings, or hide unbooked tasks. Via the output language, you determine in which language the record is created.

Example: For a detailed customer invoice, you output the working times as a table with subtotals by task and shown activities, while for a compact internal control you choose only the summary without times. The underlying invoice and revenue values themselves arise in interplay with the areas Invoicing and Revenue and costs.

Customers

The Customers sub-area appears for projects with the option Allow invoicing to multiple customers. Here you manage the customers assigned to the project and define the primary customer, who serves as the default for invoice address, order reference, and contact person. Useful for consortium projects or shared orders with proportional billing.

Note: The Customers sub-area requires the add-on module Invoicing and only appears for external projects with the multi-customer option active.

Price Tables

In the Price Tables, you store the project-related prices per price group and activity, as hourly or daily rates depending on the type of accounting. The default values are taken from the customer and employee master data and can be adjusted for exactly this project:

  • Per price group and activity, you set an own rate, for example to bill consulting higher than pure implementation.

  • The project-related prices override the globally stored prices exclusively for this project.

Useful for special projects with deviating conditions. The basics of the price logic are described in the area Invoicing.

Project-Price-Group

Under Project-Price-Group, you determine which price groups are available in this project. This controls according to which price logic billing happens:

  • Only the price groups allowed here can be assigned to the project team members in their assignment periods.

  • The invoice items are grouped by price group, which enables a separate analysis by tariff.

A deliberately restricted selection (for example Standard, Premium, or Maintenance) keeps the price structure of a project clear and prevents mis-assignments.

Receipt Settings

The Receipt Settings define which receipt types may be booked onto the project and which amount is invoiced to the customer. Via the selection amount to be invoiced, you determine per receipt type which portion is transferred to the invoice, for example the total amount, only the profit portion, or only the expenses. Team members can only record receipts of the released types; the global receipt-type master data is maintained by administrators in the administration.

Travel Settings

Under Travel Settings, you store the project-specific rules for travel costs that complement the global travel settings from the administration for exactly this project:

  • Mileage allowance: do not bill, flat rate, or per kilometre, optionally with an own project-specific kilometre flat rate.

  • Arrival flat rate: none, per day, or per assignment, optionally only from an adjustable hour threshold.

  • Subsistence costs: project-specific flat rates that override the globally stored rates for this project.

Note: The travel settings appear with the add-on module Travel expense management. The calculation methods and the global configuration are described in detail in the corresponding area.

Billing

The Billing group bundles the invoice functions available directly on the project. They map the path from the service to the finished invoice and are used for the day-to-day invoicing of a customer project.

Note: The Billing group only appears with the add-on module Invoicing and only for external projects with a customer assignment.

The group comprises the following items; their operation in detail is described in the collection Invoicing:

  • Invoice items: creating invoice items, generating invoices, and identifying missing items.

  • Invoices: listing of all invoices already created for the project.

  • Open items: overview of which invoices have been open since when.

  • Sales forecast: projection of the revenue of the coming months based on the invoice items.

  • Project Custom Fields: freely definable fields with name and content that appear on the invoice.

Resource Planning

The Resource Planning group bundles the project-related scheduling of team members onto days and hours and the comparison of the planning with the actually booked times.

Note: The Resource Planning group only appears with the add-on module Resource Planning and is not available in ZEP Clock.

The group comprises the following items; concepts and operation are described in the collection Resource Planning:

  • Planning: day-by-day assignment of team members to tasks with planned hours.

  • Work packages: bundling of efforts into packages for a coarser planning and analysis.

  • Project Times Chart: temporal development of the project times in a target-actual comparison.

  • Planning overview: aggregated view of all schedules and work packages of the project.

Reports on the project

Via the Reports submenu on the project detail view, you reach all reports focused on exactly this project, without having to open the central reports area. Available are, among others, the cover page as a printable summary, the project time and receipt analysis limited to the project, the Time Report, the Project Accounting or project revenue, as well as the plan views Project Status Plan and Overall State Plan and the revenue view Project Status Revenue. Which reports appear depends on the product line, role, and licensed modules.

A complete overview of all project reports, including the global lists from the main menu and their interplay with the central reports area, is provided in the article Project reports.

Did this answer your question?