Product purpose and connected work
Toolora connects customer work, commercial agreements, project execution and financial follow-up for Swedish painting and service companies. Office staff coordinate that work; workers, customer contacts and subcontractors use separate surfaces with narrower purposes. The application is in pre-launch development under the environment contract.
The project provides shared context for a customer outcome. It can exist before a quote is accepted. Related records retain their own owners, versions and states: creating a project does not establish an agreement, completed work or an amount paid.
Work from enquiry to follow-up
Section titled “Work from enquiry to follow-up”flowchart LR Need[Customer need] --> Opportunity[Opportunity and sources] Opportunity --> Quote[Editable quote] Quote --> Agreement[Customer acceptance] Agreement --> Basis[Accepted billing basis] Project[Project context] --> Execution[Planning and work orders] Basis --> Invoice[Invoice preparation] Execution --> Review[Reported work and review] Review --> Invoice Invoice --> Followup[Accounting, delivery and payment evidence]
Enquiry and quote acceptance explains preparation, sending, customer responses and project handoff. Execution and review follows planning, assigned work and the separate review decision. Invoicing and settlement connects consumed basis to accounting and payment evidence. These are related workflows rather than one status field.
| Business question | Owning information | A nearby fact that does not answer it |
|---|---|---|
| What did the customer agree to? | Accepted quote version and acceptance evidence | A source-offer link or an editable draft |
| Who should perform this work? | Work order, assignment and published scope | A project budget or calendar slot alone |
| What was performed and reviewed? | Execution records, time and explicit review | Planned hours or a scheduled end date |
| What remains to invoice? | Accepted basis, reservations and consumption | A quote total copied into a report |
| Has the invoice reached its destination? | The named accounting or delivery receipt | A successful editor save |
| What is outstanding? | Invoice, credit and payment reconciliation | A transfer acknowledgement alone |
Relationships that must remain distinct
Section titled “Relationships that must remain distinct”A customer is normally an organization or household with a company relationship. Contacts, invoice recipients and household-work deduction recipients have different roles. A work site is a separate location from the customer’s postal address. See customer relationships and the definitions owned by CONTEXT.md.
Planning allocations describe capacity. Reported time describes performed work; approval is another decision and may enable a payroll handoff. Subcontractor procurement additionally has versioned requests, responses and commitments. A worker assignment and a subcontractor award are not interchangeable.
Documents and conversations provide supporting evidence and collaboration. Publication and audience policies determine which participants can see them. A stored file, a linked conversation or a company membership alone does not establish customer visibility. Publication remains independent of commercial validity and project admission.
Example: repainting a shared stairwell
Section titled “Example: repainting a shared stairwell”In a synthetic example, a housing organization requests repainting. Staff record the organization, its contact and the stairwell as the work site. They prepare a quote, then the customer accepts its specific sent version. The project can connect that agreement with two work orders and several calendar allocations without changing what was accepted.
A worker’s reported hours do not silently increase the accepted price. A later agreed addition needs its own commercial authority. Allocating a supplier cost to the project supports management follow-up; it does not prove that a customer invoice was issued or paid. The example shows the relationships, not an executed business acceptance scenario.
Product limits and evidence
Section titled “Product limits and evidence”The navigation and route definitions establish the inspected workspaces. Domain contracts and active migrations establish record behaviour. Reports retain their dataset-specific permissions, date coverage and amount definitions; a missing historical date is not evidence of zero activity. Shared source archives and providers retain the coverage limits described in system ownership.
This article maps current responsibilities from the named sources. It does not declare every independent working-day or financial scenario accepted. Those outcomes need their own scoped evidence.