Project field reference

The fields on a project and what each one controls.

This page describes the fields on the New Project form, including their validation rules and where each one is used across Consult.

Project details

Name: The name of the project. It appears across the app in lists, dashboards, reports, plan pages, and the organogram, and is used when searching for and sorting projects.
Description: A short, internal description of the project that provides context in reports and overviews.
Project Code: An internal short code that identifies the project. It appears in project lists and exports and can be used for cross-system mapping.
Priority: The importance of the project, set to High, Medium, or Low. It is used in filters, sorting, and dashboards to indicate urgency.
Win Probability: The confidence level in winning the engagement, set to Low, High, or Certain. It supports pipeline forecasting and prioritisation in the early stages.
Project Type: The billing nature of the project, set to Billable, Non-Billable, or Firm Contribution. Only billable projects can have rates assigned to resources; non-billable projects automatically set project resource rates to 0.
Currency: The billing and expenses currency for the project. It applies to invoices and expense claims and determines the symbol and tax acronym shown in financial views.
Estimated Value: A best-guess total value for the project. It is used in pipeline and financial projections and high-level project metrics, and can appear on dashboards and reports subject to role permissions.

Start Date: The planned start date for the project, which drives schedule creation and planning windows.
End Date: The planned end date for the project, which defines the end of the scheduling window and planning horizon.
Country: The primary country where the project operates, which sets the regional context and reporting.
Offerings: One or more offerings that describe the nature of the work. They control which designations, or rate cards, are selectable during organogram setup.

Select Client: The client organisation for the project. Leave it blank for internal projects. When a client is selected, the invoicing fields Invoice Day of Month, Invoice Frequency, and Payment Terms become required and enabled. It is also used in client-centric views and reports.
Proposal Submission Deadline: The date by which the proposal must be submitted, which supports proposal management and timeline visibility.
Proposal Expiry Date: The date after which it is reasonable to assume the proposal was not won, which supports pipeline tracking and expected decision timelines.
Invoice Day of Month: The day of the month an invoice is expected to be sent. It drives the invoicing cadence and reminders and is disabled when no client is selected.
Invoice Frequency: The invoicing cadence, set to Every month, Once in 2 months, or Once in 3 months. It is used by the invoicing scheduling logic and is disabled when no client is selected.
Payment Terms: When payment is due after an invoice, set to Same as Client, 14 Days, 30 Days, 60 Days, or On Invoice. It is used to compute due dates and ageing for invoices and is disabled when no client is selected.

These default rates prefill and standardise expense claims on the project:

Mileage Rate: The default rate per kilometre, excluding tax, for mileage expense claims.
Accommodation Rate: The default rate per night, excluding tax, for accommodation expense claims.
Subsistence Rate: The default rate per day, excluding tax, for subsistence expense claims.