On this page

People & Budget

In short

Two views answer two questions that come up in every project, every week: who is involved, and how much money is left. In People you keep everyone who matters, with role, organization, contact details and influence. In Budget you set what the project may cost, give each position its share, and see what the project will probably cost.

Both views are part of the project context. The project agent reads them. Who owns a task, which position is over its budget, who needs to be consulted before a decision: the AI can only take that into account if it is recorded here.

When you need this

  • You want to know who to inform when a date moves.
  • An invoice arrives and you want to see whether the matching position still has room.
  • The client asks about the cost position and you do not want to open three spreadsheets first.
  • A variation order is on the table and you want to see its effect before you commit.
  • You are preparing a status meeting and need a list of participants with roles.
  • You want the project agent to address drafts to the right people.

The People view

Open it through the People tab in the left sidebar. The view shows one card per person. At the top you find the search field, the Filter & Sort button, the Export button, and the Person button for adding someone.

The People view shows one card per participant with organization, roles and influence.
The People view shows one card per participant with organization, roles and influence.

What TensorPM stores about a person

The form has two blocks. Under Basic Information:

  • Name * and Organization *. Both are required. The organization matters more than it looks: it separates your own company from the design office, the client, and the subcontractors.
  • Email. Without an address TensorPM can neither address a message nor link the person to a TensorPM account.
  • Phone. The placeholder reads +49 123 456789. The number unlocks the phone and messenger entries in the context menu.
  • Profile Picture.

Under Roles and Influence:

  • Role Groups *. A fixed list, so that filtering works.
  • Custom Roles. Free text, one entry per line, confirmed with Enter. This is where project-specific titles belong, for example "Site manager structural works" or "Health and safety coordinator".
  • Influence Level *. High, Medium or Low.
  • Labels. Free keywords, also confirmed with Enter. Labels are the most flexible field and the most useful one, because you can filter by them.

Every person also carries two entries TensorPM maintains itself: when the record was last changed and by whom. Both appear in the CSV export.

Role groups, custom roles and influence

The list under Role Groups * is deliberately short: Executive, Manager, Team Member, External, Supplier, Customer, Sponsor, Client, Other. A person can belong to several groups.

The role group is the coarse drawer, the custom role is the precise title. An electrical designer gets the role group External and the custom role "Electrical designer". That way you can filter all externals at once and still read the exact function.

Influence Level * does not describe hierarchy, it describes effect on the project. The clerk in the building authority who signs a permit has high influence, even though no org chart puts him above you. The project agent uses this rating when it suggests who to involve in a change.

Profile picture

Under Profile Picture you upload an image and crop it. The Remove Avatar button clears it. Pictures of external people are stored as a file next to the project database on your device. If the person is linked to a TensorPM account, the picture is additionally stored with that account so it shows up on your other devices too.

Without a picture the card shows initials. That is not a defect, it is perfectly sufficient for most projects.

Responsibility: action items and work packages

People is a directory, not an assignment. Who does what is decided in three other places:

  1. In Action Items through the Assigned to column. One item can have several assignees, mixing people and local coding agents.
  2. In a work package through the Responsible (internal) field. That is the person in your own organization who answers for the package.
  3. In a work package through the Executing company field. Here too you pick an entry from People, usually the contact at the executing firm.

All three pickers read from the same list of people. Whoever is missing there appears in no picker. That is the most common reason an assignment "does not work".

Communication tools in the context menu

Right-clicking a person card opens a menu with Edit, Send Email, Invite to Workspace and Delete. You can unlock four messengers under Settings -> General -> Communication Tools:

Toggle New menu entry Requirement on the person
Microsoft Teams Teams Chat and Teams Call email address
Slack Slack DM email address
WhatsApp WhatsApp phone number
Signal Signal phone number

If a phone number is stored, Phone Call appears as well. These entries open the respective service outside TensorPM. TensorPM does not sign in to Teams or Slack and reads nothing there.

Spotting and inviting TensorPM users

If a person's email address belongs to a TensorPM account, the card shows a badge. For accounts already linked it reads TensorPM User, together with the plan (Trial, Pro, Business or Seat) and the workspace role. If the person is registered but not yet in your workspace, it reads Already has a TensorPM account.

You can invite anyone with a valid email address, with or without a TensorPM account. There are two ways: the Invite to Workspace entry in the card's context menu, or the person-with-plus icon at the top of the card. The invitation goes to the stored address. Someone without an account is walked through sign-up by the email and then lands straight in your workspace.

If the person is already invited or a member, if you lack the permission, or if the invitation does not get through, TensorPM says so instead of reporting "sent". Owner and Admin of a cloud workspace can invite. See Workspaces and Cloud sync.

Search, filter, sort, export

The search field at the top filters the cards immediately. Filter & Sort opens a panel with:

  • Sort By: Name, Organization, Role, Influence
  • Role: multiple selection across the role groups
  • Influence Level: High, Medium, Low
  • Labels: multiple selection across all labels used in the project
  • Clear All

Export produces a CSV file with the columns Name, Organization, Email, Phone, Role Groups, Custom Roles, Influence, Labels, Last Modified and Last Modified By. It exports exactly what is currently visible. Filter to External first and you get a subcontractor list rather than the whole directory.

How people arise from incoming signals

You do not have to type every participant by hand. People appear in four ways:

  1. At project start, from documents. If you create a project from existing paperwork, TensorPM reads names, organizations, roles and addresses out of the contract, the minutes or the distribution list and proposes people from them. If a role group is missing it uses Team Member, if influence is missing it uses Medium. You can correct both afterwards.
  2. From incoming signals through the Distiller. When an email arrives from an unknown sender, the Distiller can offer a new person as a proposal card. The card carries the name as its headline and details such as organization or role as small chips below. You decide with Approve or Skip. Nothing is stored without you.
  3. In chat. You can ask the project agent to add or update a person.
  4. By hand, through the Person button.

Because route two runs through the Distiller, the same rules apply as for any other context change. The details are in Connectors & approvals.

Why this is worth maintaining even if nobody else uses the app

This is the most common objection: why maintain people if I am the only one working in TensorPM? Four reasons:

  • The project agent addresses correctly. An email draft needs an address and a salutation. Both come from People.
  • Incoming mail gets placed. If TensorPM knows the sender, it can read the message in the light of their role and organization instead of treating it as anonymous text.
  • Analysis and Guidance become concrete. "Clarify the approval" is a weak recommendation. "Clarify the approval with the building authority, the contact is on file" is a usable one.
  • It is your handover. If you drop out or the project lead changes, a maintained list of people with roles and influence is the first thing anyone needs. It exports as CSV and can be passed on.

The effort is modest. For a mid-sized construction project, client, project control, architect, the three or four key designers and one contact per trade are enough to start. Everything else grows in by itself through incoming signals.

What the People view cannot do

TensorPM does not run availability or capacity planning per person. There is no field for weekly hours, no holiday calendar, no utilization curve. Who has how much time when is not a property of the person in TensorPM.

You plan capacity on the work side instead: every action item has Planned Effort and Actual Effort in hours, and every work package rolls those up into Effort (plan) and Effort (actual). Through the assignment you can see how many hours sit with one person. Rough availability, for example "on site Tuesdays and Thursdays only", belongs on the person as a label or in the project context under Context -> Resources.

The Budget view

You open it through the Budget tab in the left sidebar. The view is titled Budget & Material, because it has two tabs: Budget and Material. This article covers Budget. Suppliers and procurement status are described in Materials & procurement.

The Budget & Material view with the overview of budget, forecast, variance and actual, and the table of positions below it.
The Budget & Material view with the overview of budget, forecast, variance and actual, and the table of positions below it.

One calculation for all costs

Costs arise in three places in a project, and TensorPM counts all three:

  • Cost entries: contracts, invoices, fees, rentals. You record them directly in Budget.
  • Action items: Estimated Cost and Actual Cost in the action item list.
  • Material: the estimated cost of a material item, or else quantity times unit price, plus its actual cost.

The Budget view, the Pulse card, the cost columns of the work packages, the chart in Project Insights and the project agent all use the same calculation. A figure shown in one place is the same everywhere else.

Costs are organized by positions. Positions are your categories, or the work packages in a WBS project. There is no separate budget structure next to the project structure: whatever sits in the category Structural works counts in the position Structural works.

Setting the project budget

The project budget is the figure everything is measured against. You set it directly in the overview. While none is set, Budget shows Not set with Set project budget next to it. Later you change it with the pencil icon Edit project budget. The same field is available under Context -> Resources, and the wizard asks for it when you create a project.

Without a project budget TensorPM still calculates. The overview then says No project budget set yet. Forecast: …. Whether you are within budget only shows once the figure exists. Set it early, even if it is still rough.

Budgets per position

Below the overview sits the table of positions with the columns Budget, Forecast, Actual and Variance, plus a bar with the costs recorded so far.

Click the amount in the Budget column to edit it. Enter saves, Esc cancels, and an empty field removes the position's budget.

  • A parent position without a budget of its own shows the sum of its sub-positions. Its tooltip then reads Sum of the sub-positions.
  • In a WBS project only work packages carry a budget. Structure nodes show the sum of their packages, and the tooltip says In the WBS, work packages carry the budget.
  • The variance reads on budget, … left or, in red, … over. Because of the forecast rule (see below), on budget is the usual state while a position is not fully recorded.

The table only shows positions with a budget or costs. The Show all positions checkbox shows the rest, for example to give a new category a budget. You create a new position like any category, or as a work package in a WBS project.

The arrow in front of a position expands it. Below it are the costs recorded directly in that position. Each line names the kind (action item, cost entry or material), its stage with the amount, and forecast and actual on the right. You open a cost entry there with Edit. The Cost entry button below the lines creates a new cost entry right in that position.

Recording cost entries

A cost entry is a contract, an invoice, a fee or a rental. The Cost entry button at the top right opens New cost entry with these fields:

  • Name, placeholder e.g. Window contract, scaffolding invoice
  • Amount: the estimate, and once committed the contract value
  • Status: Estimated, Committed or Settled
  • Invoiced so far: how much of it has been invoiced
  • Date
  • Position, or No position
  • Pays for: Nothing specific, an action item or a material item
  • Note
  • Attached Files

Save stores it. An existing cost entry also offers Delete, which you have to confirm.

The status says how certain an amount is. A typical path: you enter a quote as Estimated. With the contract you switch to Committed and set the contract value as Amount. Progress invoices raise Invoiced so far. With the final invoice you switch to Settled.

Status What goes into the forecast
Estimated the larger of Amount and Invoiced so far
Committed the larger of Amount and Invoiced so far
Settled Invoiced so far. If it is missing, Amount stands in, with a hint

Estimated and Committed calculate the same way. The difference shows under Actual in the overview: what is committed but not yet invoiced appears there as of which committed, not yet invoiced: ….

Counting nothing twice

In practice a window order often shows up three times: as an action item "Order windows" with an estimated cost, as a material item "Windows" with a price, and as the window maker's invoice. If TensorPM added all three, the forecast would be three times too high.

That is why a cost entry can pay for something. Choose an action item or a material item under Pays for, and its own amounts no longer count. The cost entry carries the money. If it pays for a material group, that applies to everything below it.

You see the link in three places:

  • In the table the cost entry shows pays for “…”.
  • In the action item's details, Costs shows for example Paid through 1 cost entry: forecast … · actual … and below it The task's own figures no longer count.
  • In the material list the item shows paid through “…”.

The quickest way to create the cost entry for an action item is from the item itself. Its details show the button Record contract or invoice next to the cost fields. It opens New cost entry with the item's name, position and estimate, and the item already selected under Pays for.

If a cost entry has about the same amount as an action item or material item in the same position that it does not pay for yet, TensorPM points it out. The line shows Looks like “…” with a Link button, and the overview gives the count. One click links the two. If they really are two different costs, leave the hint as it is.

Attaching receipts to a cost entry

Every cost entry can carry files. In the Attached Files area you have two routes:

  • Upload takes a file from your disk into the project folder.
  • Search existing files searches the files already in the project, for example an invoice that arrived by email.

The second route is the important one. When an invoice arrives as an email attachment and lands in the project through a connector, you do not have to upload it again: you search for it and attach it to the cost entry. Remove file releases a link again.

That puts the receipt where the number is. It is not bookkeeping, but it answers the question "where does this amount come from?" without a hunt through the mailbox.

Reading the overview

The overview at the top shows these values:

  • Budget: the project budget.
  • Forecast: the expected total cost. The info icon next to it explains the rule.
  • Variance: budget minus forecast, as … under budget, on budget or, in red, … over budget.
  • Actual: what has been incurred so far, with of which committed, not yet invoiced: … below it where it applies.
  • Unallocated: the part of the project budget no position has received yet. If more is allocated than exists, the field reads Allocated beyond budget in red. It appears once a project budget is set and at least one position has a budget.

Below that, a bar shows actual and forecast against the budget. If the forecast runs past it, a mark shows where the budget ends. One sentence sums up the state, for example The forecast is 8,500.00 EUR under budget. 1 position is over its budget. TensorPM never shows lower costs than planned as a problem.

Then come hints on what makes the forecast uncertain. Each one gives a count:

Hint starts with What you do
… cost entry looks like a task or material item … Check it and Link if it is the same cost
… entry is completed but has no actual cost Add the actual cost. Until then the estimate counts
… material item without a price Enter a price on the Material tab. Until then it is missing
… material group has a price of its own Nothing, if intended. The sub-items are counted
… position is not fully recorded yet Nothing. The rest of its budget is in the forecast, see below
… cost entry from a deleted bucket is not counted Choose a position under Not assigned

While cost entries and material are still loading, it says Cost entries and material are still loading – the figures are incomplete.

How the forecast is calculated

Per source:

  • Action item: once completed, its actual cost counts, or its estimate if no actual cost is recorded. Otherwise the larger of estimated and actual cost counts.
  • Cost entry: as in the status table above.
  • Material: Received or Completed with an actual cost counts the actual. Cancelled counts only what has already been spent. Otherwise the larger of estimate and actual counts.

One rule is added per position: as long as a position's recorded costs are below its budget, the rest of the budget stays in the forecast. What is recorded is rarely everything yet. If structural works have a budget of EUR 1,200,000 and EUR 1,149,300 is recorded so far, TensorPM still forecasts EUR 1,200,000. The tooltip on the figure then says Recorded 1,149,300.00 EUR – the rest of the budget (50,700.00 EUR) stands in the forecast until the costs are known.

Two consequences:

  • A work package with the status Done or Accepted counts only its recorded costs. The rest of its budget is then free.
  • For every other position you release savings by lowering its budget. Only then does the forecast go down.

This is deliberately cautious. A forecast that reads every invoice not yet recorded as a saving looks too good until shortly before the end.

Not assigned

Costs without a position count in the total, but in no position. They are listed in the Not assigned area above the table, in groups:

  • From bucket “…”: cost entries from a budget bucket of earlier versions, see below
  • No position: cost entries without a position
  • Material without category
  • Tasks without category: these get their position through the category in the action item list.
  • From deleted buckets: these cost entries do not count until they have a position.

Choose position … on a group moves all of its entries at once. You change a single cost entry through Edit and its Position field.

What became of the budget buckets

Up to version 1.42 there were budget buckets. They had no amount of their own and stood next to the project structure. In 1.43 they were folded into the positions:

  • The expenses in the buckets are kept as cost entries. Planned: became Amount, Actual: became Invoiced so far, and the status is Estimated.
  • They are listed under Not assigned, grouped by their former bucket. One choice under Choose position … moves the whole bucket into a position.
  • Action items count through their category. Their former bucket assignment no longer matters.
  • When a bucket was deleted, older versions left its expenses behind without a bucket and counted them nowhere. They are listed under From deleted buckets and count once you give them a position.

Cost over time

The budget view shows a position, not a trend. For the trend go to Context -> Info, to the Project Insights card, and open the Budget tab there. The chart shows:

  • Daily Actual as bars
  • Total Actual as a rising line
  • Project Budget as a horizontal reference line

30 days, 90 days and All time switch the range. All time reaches back five years at most. The interesting moment is when the Total Actual line approaches the Project Budget line while months of the schedule are still open.

The chart is calculated on opening from the actual costs of all three sources. Each actual amount sits on a day: for an action item the day it was completed, otherwise its due date; for a cost entry its Date; for material the delivery date or Needed By. Costs without a date or with a date in the future sit on today. Without actual costs you see the No Budget Data notice.

Currency and exchange rates

TensorPM distinguishes two currencies.

The display currency decides which currency amounts appear in on screen. It applies per project and lives under Settings -> General -> Currency -> Display Currency. Available are EUR, USD, GBP, JPY, CHF, CAD and AUD. The Show Currency Symbols toggle switches between the code and the symbol.

The storage currency is the currency TensorPM calculates and stores in internally. It applies to the whole application, knows only EUR and USD, and sits behind the Advanced Currency Settings button.

Important: Changing the Storage Currency converts all existing data, including the budgets of the positions. The app warns that this converts everything already recorded. Create a backup first under Settings -> General -> Database Backup -> Create Backup.

The Update Exchange Rates Automatically toggle is off by default. Turn it on and TensorPM fetches daily central-bank reference rates when needed, through the free Frankfurter service. No account and no key are required, only currency codes are sent, and the rates are then cached locally for 24 hours. The Refresh Exchange Rates button forces a fetch, but it only works while the toggle is on.

Without rate fetching TensorPM keeps working with built-in conversion factors. Amounts stay visible, just not converted at today's rate. For invoices and settlement the rate used by your accounting applies anyway, not the one in TensorPM.

A worked example from a construction project

The starting position

A four-storey office building, refurbishment of an existing structure. The project budget is EUR 2,400,000. Display currency and storage currency are both EUR. The project's categories are the four positions.

The four positions

Position Budget Forecast Actual Variance
Structural works 1,200,000 1,200,000 1,004,300 on budget
Fit-out 700,000 700,000 210,000 on budget
Building services 350,000 350,000 96,000 on budget
Ancillary costs 90,000 141,500 141,500 51,500 over
Total 2,340,000 2,391,500 1,451,800

Ancillary costs are fully invoiced and EUR 51,500 over their budget. The other three positions are not fully recorded yet: their forecast sits at their budget, even though only part of it exists as a contract or invoice so far.

The Structural works position in detail

Entry Kind Stage Forecast Actual
Pour ground slab Action item completed, estimated 180,000 186,500 186,500
Build basement walls Action item completed, estimated 240,000 240,000 240,000
Contract slabs ground to 3rd Cost entry Committed 560,000, invoiced 415,000 560,000 415,000
Site setup Cost entry Settled 138,000 138,000 138,000
Crane hire May to July Cost entry Settled, estimated at 22,000 24,800 24,800
Total recorded 1,149,300 1,004,300

The contract for the slabs pays for the action item "Slabs ground to 3rd floor". Its own estimate of EUR 620,000 therefore no longer counts, otherwise structural works would be that much too high. The crane hire carries the crane company's invoice, which reached the project through the email connector.

EUR 1,149,300 is recorded against a budget of EUR 1,200,000. The difference of EUR 50,700 stays in the forecast, because not all costs of the structural works are known yet. The position therefore shows on budget, not 50,700 left.

What the overview makes of it

  • Budget: EUR 2,400,000
  • Forecast: EUR 2,391,500
  • Variance: 8,500.00 EUR under budget
  • Actual: EUR 1,451,800, with of which committed, not yet invoiced: 279,000.00 EUR below it. These are the open parts of the committed cost entries in structural works, fit-out and building services.
  • Unallocated: EUR 60,000, the difference between the project budget and the sum of the position budgets
  • Sentence: The forecast is 8,500.00 EUR under budget. 1 position is over its budget.
  • Hint: 3 positions are not fully recorded yet – the rest of their budgets stands in the forecast.

A variation order arrives

The structural contractor reports a variation: the subsoil under the ground slab has to be replaced over 400 square metres, claim EUR 85,000. You create a cost entry in the Structural works position:

  • Name: Variation V-014 soil replacement
  • Amount: 85,000, Status: Estimated
  • Date: the date of the variation letter
  • Attached Files: the variation letter as a PDF

The calculation changes at once:

Value Before After
Structural works, recorded 1,149,300 1,234,300
Structural works, forecast 1,200,000 1,234,300
Structural works, variance on budget 34,300 over
Forecast total 2,391,500 2,425,800
Variance 8,500 EUR under budget 25,800 EUR over budget

The variation does not hit the forecast with EUR 85,000 but with EUR 34,300. The other EUR 50,700 were already in the forecast as the unrecorded rest of the structural budget. The overview still jumps to over budget although not a single euro has been paid. That is the point: you see the overrun before you agree to it, not after the invoice.

Two weeks later the variation is negotiated down to EUR 71,000 and commissioned. You set the cost entry to Committed with Amount 71,000. The forecast drops to EUR 2,411,800, still EUR 11,800 over the project budget.

Then building services turn out cheaper: the heating is committed at EUR 180,000, and the position will not cost more than EUR 300,000. You lower the budget of Building services to EUR 300,000. The forecast drops by EUR 50,000 to EUR 2,361,800, and the overview shows 38,200.00 EUR under budget.

What this example shows

  • Every number in the overview is a sum of lines you can trace one by one.
  • The forecast is cautious. Unrecorded parts of a budget count as still to come until you lower the budget.
  • Whatever a cost entry pays for counts only once.
  • A variation becomes visible the moment you record it as Estimated, not only with the invoice.

What TensorPM is not

TensorPM is not accounting software. There are no accounts, no journal entries, no VAT, no chart of accounts, no year-end close and no audit-proof receipt archive. Cost entries are project control figures, not bookings.

TensorPM also does not replace cost accounting in your ERP. Cost centres, cost objects, order settlement, payment runs, dunning, fixed-asset accounting and accruals stay where they belong. What sits in TensorPM is the project's view of its cost, at the precision that steering requires.

In practice that means:

  • The truth about paid amounts lives in accounting. Where TensorPM differs, accounting is right.
  • Enter net amounts in TensorPM, unless your project has deliberately agreed otherwise. TensorPM does not separate tax.
  • Do not expect an automatic reconciliation with the ERP. Where a link to an upstream system exists, it runs over the usual routes, see Connectors & approvals and Agent integrations.
  • Use the precision that fits the decision. Whether a line costs EUR 24,800 or EUR 24,812.47 changes no project decision.

That is not a limitation, it is a division of labour. Accounting tells you what happened. TensorPM tells you what follows from it for the rest of the project.

Step by step: the first setup

  1. Open People and create the five to ten most important participants. Mind email and organization. You know it worked when a card appears for each person.
  2. Open Settings -> General -> Communication Tools and enable the messengers you actually use. Then right-click a person card and check that the entries appear.
  3. Open Budget and set the project budget in the overview. A rough figure is fine.
  4. Give the most important positions a budget. If a position is missing, create it as a category, or as a work package in a WBS project.
  5. Record running contracts and existing invoices with Cost entry, including status, position and receipt. If a cost entry pays for an action item or material item, choose it under Pays for.
  6. If Not assigned appears at the top, give its groups a position with Choose position ….
  7. Check the overview. If it shows a sentence about the forecast and no hint about costs counted twice, the setup is done.

After that a short weekly round is enough: add new invoices under Invoiced so far, switch new contracts to Committed, record variations as Estimated, work through the hints.

What happens behind the scenes

All amounts are stored in the storage currency and only converted into the display currency when they are shown. That is why changing the display currency changes nothing about the data, while changing the storage currency changes everything.

Only the inputs are stored: the project budget, the position budgets, the cost entries and the amounts on action items and material. TensorPM recalculates forecast, actual and variance on every open. That is why a total is never stale, and why there is no field into which you could type a total directly.

Delete an action item or material item and its amounts go with it. If a cost entry paid for it, the cost entry keeps counting; only the link no longer has an effect.

People and budget data belong to the project and are synchronized in a cloud workspace, end-to-end encrypted along the way. Two details of a cost entry are readable on the server: its status and which action item or material item it pays for. That way they are not lost when a teammate on an older version edits the cost entry. Name and amounts stay encrypted. Profile pictures of external people stay as files on the device. See Encryption.

Frequently asked questions

Can I give a position its own budget? Yes. Click the amount in the Budget column of the table. In a WBS project this works only on work packages; structure nodes add up their packages.

Where are my budget buckets? They were folded into the positions. Their expenses are listed as cost entries under Not assigned, grouped by bucket. See "What became of the budget buckets" above.

Why does the forecast not go down when a position gets cheaper? As long as the recorded costs are below the budget, the rest of the budget stays in the forecast. Lower the position's budget and the forecast goes down with it. A finished work package releases its rest on its own.

Does an action item count twice if there is also an invoice for it? Only while the two are not linked. Choose the action item under Pays for on the cost entry, or use Link on the Looks like “…” hint.

I cannot find the Currency group in the settings. The group only appears while a project is open, because the display currency applies per project.

Can the project agent create budgets and cost entries itself? Yes. It sets budgets per position, creating a new position where needed, and records, changes or deletes cost entries including status and link. What it did is visible afterwards under Trail -> Changes.

Are cost entries created automatically from invoices? Not without you. Incoming invoices, contracts and quotes land as a signal and as a file in the project. The Distiller proposes a cost entry from them, with status, position and what it pays for; from a cost plan also the budgets of the positions. Nothing is booked until you accept the proposal.

What is the difference between Budget and Material? Material manages line items with supplier and procurement status. Their costs count in Budget, in the position you choose on the material item. See Materials & procurement.

Can I import people from a file? There is an export, but no CSV import. The fastest route to many people is project creation from documents, or the chat.

What happens to a person who leaves the project? Do not delete them while they still appear in assignments or in the history. Give them a label such as "left the project" instead, and filter on it.

When something does not work

A participant does not appear in the Assigned to picker. The picker only knows people who exist in People. Create the person and reopen the item.

Teams Chat or WhatsApp are missing from the context menu. Two causes. Either the toggle under Settings -> General -> Communication Tools is off, or the person has no email address respectively no phone number. Teams and Slack need the address, WhatsApp and Signal need the number.

Invite to Workspace is missing. The entry needs a cloud workspace, a valid email address on the person and a sign-in. Owner and Admin can invite, Member cannot. Someone who is already a member is not offered again.

The invitation is refused. TensorPM names the reason. … has already been invited or is already a member means there is nothing to do. You don't have permission to invite people to this workspace means your role does not allow it. With That's too many invitations for now. wait a while.

The list is empty although people exist. A filter is active. Open Filter & Sort and choose Clear All. Check the search field too.

The overview shows Not set. No project budget is stored. Click Set project budget.

A position is missing from the table. The table only shows positions with a budget or costs. Tick Show all positions.

I cannot change a position's budget. In a WBS project only work packages carry a budget. A structure node shows the sum of its packages. Change the budget on the work package.

The forecast is higher than all recorded costs together. That is the rest of the position budgets that are not fully recorded yet. The tooltip on a position's forecast shows recorded costs and the rest separately.

A cost entry does not count. It comes from a deleted bucket and is listed under From deleted buckets. Give it a position and it counts.

An action item no longer counts although it has costs. A cost entry pays for it. Its details then say The task's own figures no longer count. If the link is wrong, set Pays for on the cost entry back to Nothing specific.

The amounts look wrong after a settings change. First check whether only the Display Currency was switched. Then the numbers are correct, just shown in a different currency. If the Storage Currency was switched, all data was converted. Only a backup brings that back, see Settings & backups.

Refresh Exchange Rates is greyed out. The button only works once Update Exchange Rates Automatically is on. The app says so in a hint.

The rate fetch fails. TensorPM reports that exchange rates could not be refreshed and that the existing ones were kept. No data is lost. Check the internet connection and try again later.

The Budget tab under Project Insights shows nothing. No actual costs are recorded yet. The notice reads No Budget Data.

Next steps