Deal and Project Tracking: Fields, Status Rules, and Spreadsheet Review

Deal and project tracking means keeping a reliable record of where an item stands and what needs to happen next. A sales opportunity awaiting a customer decision is different from a commissioned article awaiting review. They need different status rules and different financial measures, even when both are called “projects” inside your business.

You can start with Excel or another spreadsheet. Review the specific problem before changing systems: an unclear update rule requires a different remedy from a missing access control. The tables below are copyable starting points. All dates, amounts, and time estimates are fictional examples, not prices, benchmarks, or promises of savings.

Separate sales deals, delivery projects, and internal initiatives

Begin by naming the unit of work. A sales deal tracks the path toward a buying decision. A delivery project tracks an agreed output through acceptance. An internal initiative tracks work toward a business purpose. Combining these units without a type field makes pipeline value look like contracted revenue and makes a sales stage look like a production completion rate.

Keep the project-level record separate from its detailed task list. One delivery project might contain twenty pieces of drafting, design, and review work without needing twenty project records. Link to the detailed creative production tracker so people can move between the overview and the actual work.

Define tracker fields and status entry criteria

Useful common fields are an immutable ID, type, name, accountable owner, current status, next action, next action owner, due date, last meaningful update, and reference link. The accountable owner follows the whole item; the next action owner holds the current action. Replacing the overall owner whenever work changes hands makes later handovers harder.

Define entry and exit conditions for each status. “Proposal in progress” could mean drafting, internal approval, or waiting for the customer. Choose distinctions that support decisions instead of creating a separate status for every tiny activity.

Incomplete intake records can remain in an intake queue. Give someone responsibility for confirming the missing information by a stated date. A blank next action is a prompt to clarify whether the item is still needed, awaiting a decision, or ready to close.

Fill out sales and delivery examples without mixing metrics

The following example uses S and P to distinguish sales from production. Your ID convention can differ, but do not reuse an ID when the project name changes. The ID connects conversations, deliverables, purchase orders, and later financial records.

Do not sum these amounts and call the result revenue. Expected quotes, contract values, and spending allowances are different series. Keep the currency, tax treatment, period, and confirmation status explicit. If you use probability-weighted pipeline value, define the probability and its basis rather than treating an unexplained percentage as a reliable forecast.

When delivery requires an outside purchase, carry the project ID into purchase order tracking. Contract value, committed supplier cost, and cash paid should remain distinguishable. Replacing them in one amount cell destroys the meaning of the record.

Review spreadsheet problems by capability and operating rule

A spreadsheet is not automatically incapable of collaboration or history. Microsoft documents co-authoring for supported versions and storage arrangements. Emailing separate copies creates a different problem from sharing one maintained workbook. Confirm your version and storage conditions before describing a feature as missing.

Two person-hours of consolidation each week across four weeks equal eight person-hours for that activity. This is an illustrative workload calculation, not an estimate of guaranteed savings. A new system adds setup, input, maintenance, and checking work. Compare the same activities before and during the trial. Row count or team size alone is a weak reason to move.

Pilot one work type and reconcile records before switching

Pilot one work type with representative records. Agree on acceptance conditions before the trial: essential fields remain intact, permissions work, ownership transfers correctly, and necessary data can be exported. A pleasant interface is useful, but it does not establish operational fit.

1. Clean duplicate or missing IDs and align statuses and amount definitions.
2. Move representative records and reconcile counts, owners, dates, amounts, and references.
3. Test viewing, editing, handover, export, and recovery with appropriate sample accounts.
4. Name the authoritative update location during the trial and explain any temporary double entry.
5. Agree the switch date, archive access, and conditions for returning to the previous tracker.

Matching record counts is insufficient. Dates can turn into text, currency can disappear, and closed items can lose their history. Include empty fields, completed work, shared ownership, and externally visible records in the checks. Retain the previous tracker under your retention rules instead of deleting the evidence needed for reconciliation.

Maintain update, handover, and access rules

Update the next action and owner when a meaningful event occurs. Use a weekly review to inspect overdue actions, missing ownership, and records that need confirmation. Editing a note is not the same as moving the work forward. Preserve customer responses, decisions, submitted versions, and changes to commitments.

A handover should include current status, open decisions, the next deadline, stakeholders, and deliverable references. For decisions that cross departments, use the marketing roles and RACI examples to distinguish execution from approval.

A frequent mistake is adding columns without deciding how anyone will use them. Remove unused fields after checking their purpose; give decision-critical fields an example and an update owner. Start with one work type and make three things consistently clear: the current position, who acts next, and where the supporting detail lives.