01
Company
Client, contractor, developer, agency, vendor, or subcontractor
Connected records
The data layer represents business context as related records instead of isolated files or one enormous table. Each record has identity, source, ownership, status, permissions, and history appropriate to its role.
Entity relationships
The company is an organisation; contacts are people; an opportunity or RFQ connects a commercial relationship to a potential project; documents, estimates, communications, costs, and decisions remain related but independently governed.
Client, contractor, developer, agency, vendor, or subcontractor
Senders, decision makers, estimators, reviewers, and project contacts
Commercial relationship, invitation, source, dates, and current status
Name, location, type, stage, value range, and delivery context
Versions, scope, cost, adjustments, review, submission, and outcome
Drawings, specifications, addenda, forms, attachments, and current issue
Messages, notes, calls, decisions, assignments, reminders, and approvals
Committed costs, commercial changes, supporting evidence, and authority
Invited parties, quotes, validity, exclusions, attachments, and response state
When work is awarded, the commercial opportunity can become or connect to the delivery project without re-entering the company, contacts, scope, documents, assumptions, and approved submission context.
RFQ record model
Every RFQ should have a unique identifier and retain a link to its original source. The exact fields follow the client’s workflow, but these record groups establish the operating context.
Estimating data model
The model connects scope, cost build-up, commercial adjustments, supporting evidence, review, submission, and outcome while preserving each approved and superseded version.
A new issue records what changed, who prepared and approved it, which documents and quotes supported it, and which version was submitted.
The operating layer preserves access to the original source while turning important identities, relationships, decisions, approvals, and status changes into usable records.
See how sources become verified recordsEvery document receives a durable document ID
Every revision connects to the original document and carries current or superseded state
Documents connect to the relevant project, RFQ, estimate, company, or change order
Emails connect to sender and recipient contact records
Attachments become document records rather than remaining hidden inside messages
Important email decisions become activities, approvals, or status changes
Source links preserve access to the original message, portal record, or file
Which company, project, document, or estimate is this?
Which source or person controls the current value or state?
What changed, which version applied, and who approved it?
Workflow assessment
Identify the entities, identifiers, relationships, source authority, permissions, revisions, and outcomes required before building integrations, reporting, or automation.