Projects keep the commercial and delivery story on one record.
Use projects as the parent record from early enquiry through quoting and into delivery, so quotes, jobs, work packages, rates, permits, files, and site history all hang off the same piece of work.
One home for the work
A project holds the title, customer, main contact, stage, and dates for the whole piece of work.
Commercial and delivery stay linked
Quotes, jobs, work packages, and pricing structures all stay attached to the same parent record.
Context is not rebuilt later
Permits, notes, files, and map captures live around the same project so handovers do not break the story.
The parent record
Projects are the umbrella around the whole piece of work.
Instead of letting the enquiry, quote, delivery work, and supporting files split apart, Oplerra gives the job one home so commercial, operational, and field context stay attached to the same record.
A project is not just a folder name. It is the central container for the work: title, customer, company link, main contact, stage, and key dates.
Quotes, jobs, work packages, rate structures, permits, notes, attachments, and map captures all sit around that same record so the next handover still makes sense.
Oplerra keeps the commercial side and the delivery side tied to the same piece of work from start to finish.
Project record
Coastal reserve maintenance program
Parent record holding customer context, pricing structure, delivery jobs, contract dates, files, and site history.
Quotes
3 attached
LiveJobs
7 linked
LiveWork packages
4 active
LiveLinked records
Customer
City of Stirling
Main contact
A. Williams
Permits
2 linked at project level
Map captures
6 records across 2 sites
Key dates and notes
Created
12 Feb 2026
Quoted
04 Mar 2026
Contract period
01 Apr 2026 to 30 Jun 2026
Last note
Scope split for coastal work package
What the record should answer
Open a project and understand the whole picture immediately.
The project record should help the next person act, not force them to reconstruct commercial and delivery context from several disconnected places.
What is the work, who is it for, and which stage is it in right now?
Which quotes, jobs, and work packages belong to this same piece of work?
Which rate structures, contract periods, permits, notes, and files matter to it?
What changed recently that sales, operations, or field teams need to understand next?
What connects to a project
Everything important to the work should stay attached.
Projects matter because they hold the relationship, the commercial history, the delivery links, and the supporting records in one place.
Contact & company
Keep the customer organisation and the main people tied to the project so the relationship does not drift away from the work.
Stage & dates
Track whether the project is new, scoping, quoted, awaiting response, active, or closed, with key dates visible on the same record.
Quotes
Attach commercial proposals to the project so pricing stays connected to the same job from the start.
Jobs
Link delivery work back to the original project so execution never becomes a disconnected operational record.
Work packages
Split larger projects into defined scopes or sections without losing the parent commercial and delivery view.
Rates & contract periods
Keep project-specific schedules of rates and time-based pricing changes under the same umbrella.
Permits & compliance
Attach permits and related compliance requirements at project level so the team can see obligations in context.
Notes, files & map captures
Shared commentary, supporting documents, and site records remain on the project instead of being scattered elsewhere.
Without a parent project, the story breaks apart quickly.
Work usually does not fail because one field is missing. It fails because the commercial record, the delivery record, and the supporting evidence drift into separate places.
quotes detached from the original enquiry or opportunity
jobs created with no clear commercial parent record
work packages tracked separately with weak handover context
rate changes and contract periods held in side spreadsheets
permits, notes, files, and map captures split across tools
Projects let you split complex work without losing the main record.
You can break work into packages, attach rates and contract periods, and still keep the parent project as the controlling record that everyone recognises.
Split delivery
Work packages create smaller scopes while the parent project still owns the customer, stage, and commercial history.
Control pricing
Schedules of rates and contract periods stay attached at project level where the pricing rules actually belong.
How it hangs together
The project follows the work from enquiry through delivery.
This is what keeps quoting, execution, and supporting records connected instead of becoming separate disconnected systems.
Start the opportunity
A project begins as the parent record for the enquiry or opportunity, with the customer, contact, stage, and dates already anchored.
Price against the same record
Quotes are created against that project so scope, pricing, and commercial history stay tied to the same piece of work.
Run the delivery from it
Jobs and work packages link back to the same project so operations can execute without losing the original commercial context.
Retain the full picture
Rates, contract periods, permits, notes, attachments, and map captures stay around the project for a complete reconstructable record.
What this gives your team
Stronger handovers, clearer control, and less context loss.
Projects help the office, commercial teams, and field operations keep working from the same source of truth.
Commercial
Quoting stays tied to the actual job
Estimators and account teams can keep proposals, stage movement, and pricing structures attached to the same record that delivery will later rely on.
Operations
Delivery inherits the right context
Schedulers and supervisors can see the parent project, linked jobs, work packages, files, and obligations instead of rebuilding context from separate systems.
Governance
The record is easier to defend later
When someone asks what changed, the answer sits on the same project record instead of being reconstructed from inboxes, folders, and spreadsheets.
Connected modules
Projects are strongest when they sit in the middle of the platform.
The parent record becomes far more useful when customer context, pricing, delivery, and map records all connect back to it.
CRM
Keep companies, contacts, and relationship history tied directly to the project that the work belongs to.
Learn moreQuotes
Attach proposals, schedules of rates, and contract pricing to the same project before the work moves forward.
Learn moreJobs & scheduling
Flow approved work into delivery while keeping the operational record tied back to the original parent project.
Learn moreGIS & mapping
Keep site records and map captures linked to the same project, with optional detail down at work-package level.
Learn moreGive each piece of work one record that survives the whole lifecycle.
Replace disconnected enquiries, quotes, jobs, files, and site notes with one project record that keeps the full commercial and delivery story intact.