TELOMETRIS / HOW IT WORKS
One operational record. Many legitimate business uses.
Every business records work. The harder problem is preserving the meaning of that work as it moves through review, compensation, client billing, reporting, and profitability.
The operational workflow
Telometris is designed around a connected operational workflow. Work is organized through clients, projects, assignments, and tasks. It is recorded through time entries, expenses, and travel compensation. Those records may then be reviewed, approved, invoiced, reported, and evaluated without recreating or disconnecting the original information.
The purpose is not to force every record through the same path. The purpose is to preserve the relationship between what happened and the business decisions that follow.
Company → Client → Project → Assignment → Operational record → Review and approval → Contractor cost / Client billing → Reporting → Profitability
This sequence describes the relationships among the records. It does not mean every record must pass through every stage.
A time entry may contribute to a contractor invoice, a client invoice, both, or neither. An expense may contribute to project cost, worker reimbursement, client billing, or more than one of those relationships. A fixed-fee project may retain detailed time records even when hours do not determine the amount charged to the client.
The operational record remains the point of origin.
Begin with the company
A Telometris company account establishes the organizational boundary for its users, clients, projects, assignments, policies, and records.
The company is not merely a label attached to a user. It is the operating context that determines which records belong together and which people may access or act on them.
Roles and permissions exist inside that company context. Multi-company tenant separation keeps one company's operational records separate from another company's records.
Connect the company to its clients
A client identifies the organization receiving the work.
Projects are organized beneath a client so that recorded work, expenses, billing settings, and invoices retain the correct commercial context.
A company may have several projects for the same client. Those projects remain distinct even when compatible charges are later consolidated into one client invoice.
The client relationship answers: for whom is this work being performed?
Define the project
A project gives the work a specific operational and financial identity.
The project may define or inherit information such as:
- the client relationship;
- available tasks;
- participating users;
- approval requirements;
- billing method;
- billable and cost rates;
- travel treatment;
- invoice grouping;
- fixed-fee obligations.
A project is not merely a reporting category. It is the context that connects people, work, policy, cost, billing, and outcome.
Assign people to the work
A project assignment connects a user to a project.
That assignment may carry the project-specific information needed to interpret the user's work, including role, permissions, cost rate, billable rate, travel classification, and access to project tasks.
The assignment answers: who may participate in this project, and under what project-specific terms?
A user may belong to the company without being assigned to every project. Company membership and project participation are related, but they are not the same thing.
Record what happened
Work becomes operationally useful when it is recorded in context.
Telometris operational records include:
- time entries;
- expenses;
- travel-compensation records where supported by the configured workflow.
Each record describes a real business event connected to the people and work involved.
A time entry identifies work performed by a user against a project and task for a date and duration.
An expense identifies a cost connected to work and may include supporting information such as a receipt attachment.
Travel compensation identifies an amount or measure owed under company policy for qualifying travel.
These records are not invoices. They are the underlying history from which later financial records may be derived.
Preserve the original operational record
The original record should not be casually rewritten simply because it later supports another business purpose.
When a time entry contributes to a contractor invoice, the contractor invoice does not replace the time entry.
When the same time entry contributes to a client invoice, the client invoice does not become the time entry.
When an expense appears on a client invoice, the invoice line is a financial presentation of that expense—not a new unrelated expense.
This separation preserves traceability:
What happened → How it was accepted → How it was valued → Where it was used
Review and approval
A record can exist before the organization accepts it for downstream use.
Approval distinguishes between information entered by a user and information accepted by the organization according to company and project policy.
The general progression is:
Recorded → Reviewed → Approved → Eligible for downstream use
Not every company or project must use identical approval requirements. The important distinction is conceptual: recording describes the event; approval expresses organizational acceptance.
Approval does not erase, replace, or become the operational record.
Use the work for contractor cost
Contractor invoicing represents the inward financial direction:
Contractor → Company
Eligible approved time and configured travel compensation may support a contractor invoice. The invoice answers: what does the company owe the worker?
The contractor invoice is a financial obligation of the company. It may move through submission, review, revision, approval, and paid status.
The invoice remains connected to the work that produced the obligation.
Use the work for client billing
Client invoicing represents the outward financial direction:
Company → Client
Eligible approved time, project-assignment billable rates, billable expenses, and fixed-fee obligations may support a client invoice. The invoice answers: what does the client owe the company?
The client invoice is a receivable or revenue record of the company. It may move through preview, draft, approval, delivery, and payment recording.
The client invoice remains connected to the work and billing obligations that produced the charge.
One work record can support two financial directions
The same time entry may contribute to both contractor cost and client revenue.
That does not make the contractor invoice and client invoice the same record.
The contractor side may use a cost rate or contractor rate. The client side may use a different billable rate or a fixed-fee obligation. The two amounts may differ because they answer different financial questions.
Contractor invoice: what does the company owe? Client invoice: what is the company owed?
Telometris connects both directions to the same operational history without collapsing them into one financial meaning.
Time-and-materials work
For time-and-materials projects, approved time may be valued using the applicable client billable rate.
The amount charged to the client is derived from the billing agreement and project-assignment configuration. The cost of the same work may be derived from a different rate.
The recorded hours are shared operational evidence. Cost and client value remain distinct.
Fixed-fee work
For fixed-fee projects, recorded hours do not determine the client charge.
Configured obligations—such as an upfront amount, milestone, installment, start payment, or completion payment—determine what becomes eligible for client billing.
Time should still be recorded because the company needs to understand the effort and cost required to deliver the fixed-fee agreement.
The fixed fee describes revenue. The time record helps explain cost and profitability.
Expenses can carry several relationships
An expense may have more than one legitimate business meaning.
It may represent:
- project cost;
- an amount reimbursable to a worker;
- an amount billable to a client;
- both project cost and client billing;
- another supported combination determined by company policy.
Billable and reimbursable are not synonyms.
The expense remains one operational record while its permitted downstream uses remain distinct.
Travel compensation has its own meaning
Travel compensation describes what the company owes a worker under company policy.
Client-billable travel describes what the client owes the company under the client agreement.
Those amounts may be related, but Telometris does not assume they are identical.
A contractor travel line and a client travel charge belong to different financial directions, even when both arise from the same trip.
Reporting explains the records
Reports organize and summarize operational and financial information already present in Telometris.
A report does not create the work, approve the work, or invoice the work. It provides a view of those records for a defined purpose.
Different reports may answer different questions:
- How much time was recorded?
- Which work has been approved?
- What does the company owe contractors?
- What has been invoiced to clients?
- Which payments have been recorded?
- What cost and revenue are associated with a project?
The answer depends on which records and statuses the report is designed to measure.
Profitability interprets cost and revenue
Project profitability is derived from connected records rather than entered as a standalone opinion.
Recorded time can contribute to labor cost through the applicable cost rate. Expenses and travel compensation can contribute to project cost according to their implemented treatment. Billable time, fixed-fee obligations, billable expenses, and client invoices can contribute to the revenue side according to the implemented reporting logic.
These measures must remain distinguishable:
- recorded cost;
- billable value;
- invoiced revenue;
- paid revenue;
- project margin.
They are related, but they are not interchangeable.
Why the distinctions matter
A disconnected system often requires the same work to be recreated for timekeeping, contractor payment, client billing, and reporting.
Re-entry creates opportunities for inconsistency. Collapsing all records into one status creates a different problem: the system loses the ability to say whether work was merely recorded, accepted, invoiced, paid, or profitable.
Telometris keeps the records connected while preserving their different meanings.
That allows one operational history to support several legitimate business purposes without pretending those purposes are identical.
What Telometris does not assume
Telometris does not assume that:
- every recorded item requires approval;
- every approved item must be invoiced;
- every contractor cost is billable to a client;
- every billable item is reimbursable to a worker;
- contractor and client rates are the same;
- fixed-fee revenue is calculated from hours;
- invoiced revenue has already been paid;
- every report measures the same status;
- one project policy fits every project.
The workflow connects records. Company policy and project configuration determine how those records are used.
The complete relationship
Organize the work. Record what happened. Accept what is valid. Use the accepted record for the appropriate financial purpose. Report what the records show. Understand the outcome.
That is the operational model behind Telometris.
Common inquiries
What is an operational record?
An operational record is the persistent representation of a business event inside its organizational context. In Telometris, time entries, expenses, and supported travel-compensation records are operational records. They describe what happened before later processes determine whether the record is approved, invoiced, reported, paid, or included in profitability analysis.
Why does Telometris preserve the original record?
The original record provides the traceable history of the work. Later records—such as approvals, contractor invoices, client invoices, and reports—express different decisions or uses. Preserving the original record allows the company to understand what happened and how that event was subsequently accepted, valued, and used.
Does every operational record follow the entire workflow?
No. The workflow describes possible relationships, not a mandatory identical path. A record may support approval, contractor invoicing, client invoicing, reporting, profitability, several of those purposes, or none of them, depending on company policy and project configuration.
Why is approval separate from recording work?
Recording states that a user entered the event. Approval states that the organization accepted the record according to its policy. Keeping those actions separate preserves the difference between submitted information and authoritative information.
Can one time entry support both contractor and client invoicing?
Yes. The same eligible work may contribute independently to a contractor invoice and a client invoice. The contractor invoice describes what the company owes the worker. The client invoice describes what the client owes the company. The two financial records may use different rates and statuses.
Does an invoice replace the underlying time entry or expense?
No. The invoice is a financial record derived from eligible source records or billing obligations. It does not replace the original time entry, expense, or travel record.
How does fixed-fee work fit into the workflow?
Time may still be recorded on a fixed-fee project so the company can understand effort and cost. The client charge is determined by configured fixed-fee obligations rather than by multiplying the recorded hours by a billable rate.
Are billable and reimbursable expenses the same?
No. Billable describes whether an expense may be charged to a client. Reimbursable describes whether the company owes the amount to a worker. One expense may carry either relationship, both relationships, or neither, according to company policy and the implemented workflow.
Is travel compensation automatically billed to the client?
No. Worker travel compensation and client-billable travel are separate financial relationships. A company may owe the worker an amount that differs from what the client is charged.
What is the difference between reporting and profitability?
Reporting organizes and presents selected operational or financial records. Profitability compares relevant cost and revenue measures to explain project performance. A report may contribute to understanding profitability, but not every report is a profitability calculation.
Does invoiced revenue mean the client has paid?
No. An issued invoice represents an amount charged or owed. Payment status is a separate financial state. Telometris records partial and full client payments manually in the current implementation.
Does Telometris require the same workflow for every project?
No. Company policy may establish general rules while project settings and assignments provide project-specific context. Approval, rates, billing method, travel treatment, and invoice grouping may differ among projects where the implementation supports those distinctions.
Begin recording.
14 days free, then from $5–$8 per user per month. Every feature included.
Start Free Trial