One operational record. Many legitimate business uses.

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 → Project Financial Performance

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 — the payment source identifies how it was funded, which governs reimbursement; billability is a separate relationship. 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.

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.

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?

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.

Companies can define configurable Project Types to represent recurring kinds of work — for example, a service engagement, a development project, or a field installation. A Project Type provides starting structure for a new project, including pre-defined tasks, applicable project roles, and workflow defaults, so the project begins from a consistent foundation rather than an empty state.

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.

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. It carries information about how the expenditure was funded — the payment source — which may be a worker's out-of-pocket purchase, a personal card, a company account, or another organization-defined method. Funding determines the reimbursement relationship; whether the expense is billable to the client is a separate relationship. An expense may include a receipt attachment or other supporting detail where the implementation permits.

Travel compensation identifies an amount or measure owed under company policy for qualifying travel.

Scheduled activity from a connected calendar account — such as a Microsoft Outlook event — can provide context for identifying upcoming work and moving into time recording. That context supports the act of recording; the time entry remains the operational record.

An authorized administrator may enter or correct operational records on behalf of a user according to company permissions. The record continues to represent the user's work, cost, or activity regardless of who entered it.

These records are not invoices. They are the underlying history from which later financial records may be derived.

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

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.

Contractor invoicing represents the inward financial direction:

Contractor → Company

Eligible approved time, reimbursable expenses, 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.

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.

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.

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.

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.

An expense may have more than one legitimate business meaning.

A payment source identifies how the expense was funded — a worker's out-of-pocket purchase, a company account, or another organization-defined method. Funding and reimbursement are related: a worker-funded expense may be reimbursable to the worker; a company-funded expense is not owed back.

It may represent:

• a project cost (every recorded project expense, regardless of billability or payment source);
• an amount reimbursable to the worker (when worker-funded);
• an amount billable to a client (when marked billable, independent of how it was funded);
• both project cost and client billing simultaneously.

Payment source, worker reimbursement, and client billability are distinct aspects of the same record — not interchangeable.

The expense remains one connected operational record while its permitted downstream uses remain distinct.

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.

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.

Project financial performance in Telometris is derived from connected operational records — not entered as a standalone opinion.

Billable Value is the sum of recorded hours at applicable billing rates and the amounts of expenses marked billable to the client. Project Cost is the sum of recorded hours at cost rates, all recorded project expense amounts regardless of billability, and recorded travel compensation. Project Margin is Billable Value minus Project Cost.

These are operational performance measures grounded in the records already present in Telometris. They do not include company-wide overhead, fixed-fee revenue, client invoice totals, or client payment records. They are not a substitute for accounting-level profitability analysis.

Billable Value, Project Cost, and Project Margin must remain distinguishable from invoiced revenue, paid revenue, and company profitability. They are related concepts, not interchangeable ones.

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.

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;
• payment source determines client billability;
• contractor and client rates are the same;
• fixed-fee revenue is calculated from hours;
• scheduled calendar activity constitutes a time entry;
• 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 same connected operational system serves different participants differently.

The organization and its decision-makers use connected records to understand projects, project cost, billable value, client billing obligations, and project financial performance — with the supporting detail necessary to make decisions about pricing, staffing, and operations.

People performing the work — contractors, hourly employees, and salaried employees — interact primarily with their assignments, time recording, expense capture, scheduled-work context where available, applicable reimbursement, and required submissions.

People administering the work manage operational structure, review and approve records, assist users, enter or correct records where authorized, and keep workflows moving.

These perspectives are not rigid classes. One person may occupy more than one perspective at different moments.

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.