Understanding the service proposal elements

The service proposal elements make the application process in PICMI that is designed to be simple and structured, guiding people through details from the organisation and the engagement through the workflow to the contract. Engagement overrides provide flexibility to accommodate unique circumstances, ensuring that the application process is legal, fair and inclusive for everyone.

PICMI uses a consistent structure for service engagements.

Organisation / Provider
         ↓
    Proposal + engagement overrides
         ↓
    Workflow
         ↓
Contract (with field substitutions)

Organisation / Provider

The organisation participating in the service engagement. Depending on the scenario, this may be the organisation requesting services, supplying services, or both.

Proposal

The service engagement being offered or requested. It defines the service context, such as the type of work, location, timing, capacity, and operational requirements.

note

Engagement overrides allow specific adjustments for an individual service engagement. Examples include service scope details, site-specific conditions, timing changes, or participant-specific agreement values.

Workflow

The workflow is the structured intake path for the organisation. It can include:

• Questions: collect required details, declarations, and confirmations
• Information: present service expectations, responsibilities, and supporting guidance
• Documents: collect certifications, policies, evidence, and records

Contract services agreement

After requirements are met, PICMI presents the relevant services agreement or participation agreement. The agreement can use field substitutions from organisation data, opportunity data, workflow responses, and engagement overrides.

note

Field substitutions replace placeholders with known values. If materially different terms are needed for different service scenarios, use a separate service opportunity or agreement template rather than relying on one generic agreement.

Practical examples

Grower and contractor services

A grower is invited to complete a service workflow before a contractor provides seasonal orchard work. The grower enters orchard profile details, services required, worksite information, and contact details. The contractor provides certifications, pay rate information, subcontractor details, and compliance documents. Once complete, both parties review and sign the service agreement. An example of this is the Kiwifruit Services Agreement Workflow

Provider participation

A provider is invited into a programme or service network. The workflow collects provider details, capability information, declarations, supporting documents, and agreement terms before the provider becomes active.