31 Compact logo31 COMPACTUser manual
Open application ↗Complete manual

Web portal

Project Management

Projects group a piece of work, its team and tasks. This module is in the web portal; it is not a native POS screen.

In this moduleUnderstand the workflowField referenceCreate a project and assign workCreate and plan a projectSet project tabs and member permissionsCreate a task and assign its deliverableWork through tasks, comments and statusRecord and correct time logsKeep project notes, files and activityCreate a project invoiceReview reports and close a projectPractical exampleCommon questions

Understand the workflow

A project is a container for work, people, dates and related records. Tasks describe individual deliverables. Time logs record time spent, not task completion. Project invoices bill the customer, not the employee’s payroll. Project Lead is the responsible staff user, distinct from a CRM sales lead. Use the project’s settings to enable the optional time, documents and invoice tabs and to control what members can change.

Project Management — module overview
SCREEN GUIDE Project Management — module overview. Select the screenshot to enlarge; optional fields may differ in your business.

Field reference

Use this while completing the form. A required field is marked with *; conditional fields appear only when enabled.

Field / controlWhat to enter or understand
Name * / DescriptionGive the project a recognisable title and clear scope, acceptance criteria and exclusions. Avoid putting every small action only in the description.
CustomerContact for customer work. Internal work may not require a customer until an invoice is needed.
Status *The current overall project stage from configured choices. A project stage is separate from the status of each task.
Lead *Responsible project user. This field does not select a CRM prospect.
Start date / End datePlanned dates for the project. Tasks have their own due dates; review both when a plan changes.
Members * / CategoriesStaff who participate and one or more categories for organisation. Membership and edit permissions are separate checks.
Task Subject * / DescriptionSpecific work item and what counts as done. Include the output needed, not merely a vague topic.
Task Start date / Due date / Priority *Scheduling and urgency for that task. Priority does not automatically change its due date.
Task Status * / Members *Actual progress and responsible project members. A task assigned to nobody useful will still remain on the project.
Task custom fieldsAdditional business-specific values. Follow the administrator’s meaning; these are not mandatory for every project.
Time log Task / User / Start / End / NoteThe person, work item and actual period worked. End must be later than start; avoid overlapping or duplicated logs.
Project SettingsTime logs, notes/documents, invoices, list/Kanban view, task prefix and member add/edit controls where offered.
Invoice Title / Customer / Location / Date / SchemeBilling identity and numbering. Required customer/location must match the intended business transaction.
Invoice Task / Rate / Quantity / Tax / DiscountBillable work lines and amounts. Recorded time is not automatically proof of an approved rate or billable quantity.

PROCEDURE 01

Create a project and assign work

Where to go Project → Projects

Before you start
Identify the customer/project owner, team and target dates.

Steps

  1. Choose Add project and enter its name, description, dates/status and customer/team details where offered.
  2. Open the project and add tasks with clear titles, assignees, due dates and priorities/statuses.
  3. Use the project’s task/list or board view to update progress. Add comments, documents or other project details in the available tabs.
  4. Review remaining tasks and milestones before marking the project complete.

Check the result
The team can find its assigned work and progress in one project.

PROCEDURE 02

Create and plan a project

Where to go Project → Projects → Add / Create Project

Before you start
Identify the lead, members and intended customer before entering the form.

Steps

  1. Enter Name and Description. Describe the outcome, such as installing a shop’s shelving and training its staff, so the team understands the scope.
  2. Select Customer when the project belongs to a client. Choose the overall Status and the staff user responsible as Lead.
  3. Set Start date and End date realistically. Add the Members who will work on it and the intended project Categories.
  4. Complete any configured custom fields using your business definitions. Save and reopen the project.
  5. Check Overview for lead, dates and members. If a colleague cannot see it, review membership and role access before creating a duplicate project.
Create and plan a project — look for the controls described in the steps
SCREEN GUIDE Create and plan a project — look for the controls described in the steps. Select the screenshot to enlarge; optional fields may differ in your business.

Check the result
A project exists with a clear owner, scope and participating team.

PROCEDURE 03

Set project tabs and member permissions

Where to go Project → open project → Settings

Before you start
The project lead or administrator normally controls these settings.

Steps

  1. Open Settings for this project. Enable time logs, notes/documents and invoices only when the team will use those features.
  2. Choose task List view or Kanban board where offered. Set a readable task ID prefix for references.
  3. Review whether members can add/manage tasks, time logs and notes/documents. Give the access needed for the work without sharing the lead’s login.
  4. Save settings, reopen the project and check which tabs actually appear. Tabs depend on both feature settings and user access.
  5. Have a member review their own view. If an enabled feature still does not appear, ask the administrator to inspect access/configuration rather than promising an unavailable tab.
Set project tabs and member permissions — look for the controls described in the steps
SCREEN GUIDE Set project tabs and member permissions — look for the controls described in the steps. Select the screenshot to enlarge; optional fields may differ in your business.

Check the result
The project has the intended tools and staff access.

PROCEDURE 04

Create a task and assign its deliverable

Where to go Project → open project → Task → Add

Before you start
Break the project into work items that someone can finish and verify.

Steps

  1. Choose Add Task and enter a specific Subject, such as Fit shelf in aisle 2. Explain the required output and checks in Description.
  2. Set Start date and Due date. Select Priority and the actual starting Status.
  3. Select Members from the project’s team. Assign the people accountable for this task; project membership alone is not a task assignment.
  4. Complete applicable custom fields and Save. Open the task to confirm assignee, deadline and scope.
  5. Create separate tasks for distinct deliverables rather than one unmanageable task called Complete project. Review the list with the team.
Create a task and assign its deliverable — look for the controls described in the steps
SCREEN GUIDE Create a task and assign its deliverable — look for the controls described in the steps. Select the screenshot to enlarge; optional fields may differ in your business.

Check the result
The task has an accountable person and a clear completion condition.

PROCEDURE 05

Work through tasks, comments and status

Where to go Project → My Tasks; project → Task → View

Before you start
Use your own staff account so updates are attributable.

Steps

  1. Open My Tasks or the project task list. Set project/assignee/status/due-date filters to locate your current work.
  2. Open the task and read its description and existing discussion. Add a comment with the actual progress, question or blocker.
  3. Change status through the offered status action when the stage changes. If a Kanban move is available, check the saved status after moving the card.
  4. Update the due date/assignment through the authorised edit action when the lead agrees to a plan change. Explain significant changes in the discussion.
  5. Mark the task completed only after the required output is checked. Check project Overview separately; completing one task does not necessarily close the entire project.
Work through tasks, comments and status — look for the controls described in the steps
SCREEN GUIDE Work through tasks, comments and status — look for the controls described in the steps. Select the screenshot to enlarge; optional fields may differ in your business.

Check the result
The task reflects actual work and the next person can understand its history.

PROCEDURE 06

Record and correct time logs

Where to go Project → project → Time logs / task → time-log action

Before you start
The project must expose the time-log feature and your role must permit it.

Steps

  1. Choose Add time log and select the correct task and User if the form offers them.
  2. Enter actual Start date/time and End date/time. Add a short Note describing the work performed, then Save.
  3. Review the duration and task/project association in the list. A log of 10:00 to 11:30 represents 1 hour 30 minutes, not a quantity of 1.30 decimal hours.
  4. Use Edit on the mistaken log when authorised. Check for overlapping entries before adding another log for the same period.
  5. Open Project Reports → Project/Employee time-log report with the intended date range to review time recorded across staff.
Before recording time, review Enable Time Log and member permissions in Project Settings; the detailed time-log fields are explained above
SCREEN GUIDE Before recording time, review Enable Time Log and member permissions in Project Settings; the detailed time-log fields are explained above. Select the screenshot to enlarge; optional fields may differ in your business.

Check the result
Work time is attributed to the correct task/person and can be reviewed.

PROCEDURE 07

Keep project notes, files and activity

Where to go Project → project → Documents & Notes / Activities

Before you start
Enable the notes/documents feature and ensure the file is appropriate to share with project members.

Steps

  1. Open Documents & Notes and use the offered add/upload action for a plan, checklist or relevant document.
  2. Give it a recognisable name and note explaining its purpose/version. Attach the file in the permitted format and save.
  3. Reopen the record to confirm the attachment is accessible to the intended members. Do not rely on a filename alone as evidence of successful upload.
  4. Use task comments for discussion specific to one task; use project notes for information affecting the whole project.
  5. Review Activities to understand changes by staff. Keep the approved final document distinguishable from working drafts.

Check the result
The team can locate the correct instructions and change history.

PROCEDURE 08

Create a project invoice

Where to go Project → project → Invoices → Add

Before you start
Enable invoicing and use lead/admin access; confirm the customer-approved scope and rates.

Steps

  1. Enter invoice Title, Invoice Scheme, Customer, Business Location and Invoice date. Set payment terms and the intended draft/final status offered by the form.
  2. Add billable Task lines with Rate and Quantity. Check units/time interpretation; a time log is not automatically a customer-approved bill.
  3. Select applicable tax and any authorised discount. Review each line and the total, then enter Terms and Notes appropriately.
  4. Save the intended invoice and open its detail. Check customer, number, dates, lines and payment status.
  5. Use the offered payment/view/print actions for that invoice. Do not also create a retail POS invoice for the same work unless the manager has a deliberate accounting reason.
Create a project invoice — look for the controls described in the steps
SCREEN GUIDE Create a project invoice — look for the controls described in the steps. Select the screenshot to enlarge; optional fields may differ in your business.

Check the result
The customer is billed once for the agreed project work.

PROCEDURE 09

Review reports and close a project

Where to go Project → Reports; project → Overview / Edit

Before you start
Review work, time and invoices separately before final closure.

Steps

  1. Filter reports by project/person and date. Compare task completion and actual time with the plan.
  2. Review open tasks, blocked items and notes. Reassign or correct due dates through the lead rather than hiding incomplete work.
  3. Check the project invoices and outstanding payments. Completion of work and collection of money are distinct events.
  4. Record a completion note and update the overall project status through its authorised edit action when the deliverables are accepted.
  5. Keep the project and its history for reference. Do not delete completed projects simply to clean up the active list; filter by status.

Check the result
The project is closed based on checked deliverables and traceable billing.

IN PRACTICE

A practical example

Shop setup project: create a project for Sample Customer, assign a manager as Lead and two staff as Members. Add Survey, Fit shelving and Train cashier as separate tasks. Log actual fitting time against its task, store the accepted layout in Documents & Notes, and create one agreed installation invoice. Review all tasks and invoice balance before closing the project.

Common questions

Why can I not assign a staff member to a task?

Check that the person is a project member and that you can edit task assignments.

Where are Time logs or Invoices?

Their visibility depends on project settings and role/lead access. Enable and verify the actual tab before planning its use.

Is Project Lead a CRM lead?

No. It is the staff user responsible for the project.

Why does a completed task not make the project completed?

The project contains several tasks and separate overall status. Review all deliverables and close the project through its own flow.