Home / Features / Award records

Award records

One record that holds
the whole purchase

Open an award and everything about it is in one place. The checklist arranged into phases, the documents behind each rule, the modifications with their own amounts, and a timeline showing what happened and when.

Phases you arrange yourselfProgress per modification
The shape of the problem

Why purchasing records break at the joins

Nothing here is difficult individually. What breaks a record is that the pieces live in different places and the connection between them exists only in somebody's head.

How an award is usually recorded
The award itself in a finance or contract system
Supporting documents in a shared drive
Approvals in an email thread
Modifications tracked in a separate spreadsheet
Reasoning for the decision in nobody's system at all
The connection between them held by the buyer
How an award is recorded here
The award, its phases and its rules on one record
Documents attached to the phase they belong to
Approvals recorded against the version reviewed
Modifications carried on the same record, individually
Reasoning written at the decision and stored with it
The connection is the record, not a person
What it gives you

Three things that follow from one record

The benefit of a single record is not tidiness. It is that several expensive activities stop being necessary.

Book a demo
Award records • Walkthrough

Three things that follow from one purchasing record.

Phases, rules, documents and approvals sit on the same award. The expensive work of joining things up afterwards stops being necessary.

  • One record for the whole purchase
  • Phases and rules arranged on that record
  • Uploads and approvals land on the same timeline
ProcureAudit Nothing has to be joined up later
Benefit 01

Nothing has to be joined up later

When the award, its documents and its approvals already sit together, producing the file is a filter rather than an exercise in reconnecting things that were never connected.

Procurement outcomeRetrieval measured in minutes rather than in days of collection.
ProcureAudit Progress means something
Benefit 02

Progress means something

A completion figure calculated per modification tells you where the outstanding work actually is. One blended percentage across a whole award tells you almost nothing.

Procurement outcomeAttention goes to the modification that is behind rather than to the award as a whole.
ProcureAudit The reasoning survives
Benefit 03

The reasoning survives

Prices and dates live in documents. Why one supplier was chosen exists only if somebody wrote it at the time, which is the single hardest thing to recover afterwards.

Procurement outcomeAward decisions remain explainable after the buyer moves on.
Inside an award

Four things the record carries

Open one and this is what is there. Click through each to see it.

Phases4 configured
ModificationsMOD 01 and MOD 02
Documentsby phase
Activitynamed and timed

Rules come from your library and are dragged into whichever phase matches how your team sequences the work. Nothing about the order is fixed by us, because it genuinely differs between organisations.

  • Rules dragged from your library into a phase
  • Reorder or remove without rebuilding the record
  • Progress calculated from what is actually complete
  • Reviewers assigned per phase rather than per award

MOD 01 and MOD 02 carry their own award and funded amounts and their own progress. Folding them into the parent is how teams lose track of which document supports which change.

  • Award and funded amounts held per modification
  • Documents attached to the change they support
  • Progress readable per MOD rather than blended
  • Legible however many accumulate over a program

Evidence is filed against the phase that produced it, so a reviewer opening Phase 2 sees what Phase 2 requires and nothing else.

  • Structured by award, modification and phase
  • Version history retained on every file
  • Approval recorded against the version reviewed
  • Retrieved by filter rather than by folder trawl

Every upload, approval and completed rule lands on the timeline with the person and the moment attached. It is the part that answers questions years later.

  • Each entry carrying a name and a timestamp
  • Scoped to the award, modification and phase
  • Not editable after the fact
  • Written during the work rather than reconstructed
Where it earns its place

Four situations teams describe to us

Award records • Walkthrough

Four situations where a single record earns its place.

Handoffs, reviews and later questions all get easier when the purchasing file was complete while the work was being done — not rebuilt under pressure.

  • When work moves between buyers and reviewers
  • When somebody asks for the file at short notice
  • When progress has to be explained per phase
What lands on the timeline

Six entries that answer later questions

ProcureAudit Uploads
01

Uploads

Which file, by whom, against which rule and phase.

ProcureAudit Approvals
02

Approvals

Who signed off, when, and on which version of the document.

ProcureAudit Rule completion
03

Rule completion

What was marked done and by whom, so progress is traceable rather than asserted.

ProcureAudit Modifications
04

Modifications

When a change was added and what it altered.

ProcureAudit Assignment
05

Assignment

Who the record moved to and when, with both names retained.

ProcureAudit Nothing retrofitted
06

Nothing retrofitted

Entries written as work happens, which is what makes the sequence provable.

FAQ

Questions about award records

Can we decide our own phases?
Yes. Phases are yours and rules are dragged into whichever one matches how your team works. We do not impose an order, because it varies genuinely between organisations and between award types.
How is progress calculated?
From the rules actually completed within each phase, and separately for each modification. A single blended percentage across a whole award hides where the outstanding work sits.
Why track modifications separately?
Because a modification has its own award and funded amounts and its own paperwork. Merging it into the parent makes it unclear which document supports which change, which is where most retrieval problems begin.
What lands on the activity timeline?
Uploads, approvals, rule completions, modification changes and reassignments, each with the person and the timestamp. Entries are written as work happens rather than assembled afterwards.
Can two people work on the same award?
Yes. Assignment shows who is carrying it and the timeline records everybody's actions, so parallel work does not create ambiguity about who did what.
Can activity entries be edited later?
No. A record that can be adjusted afterwards is not evidence of anything, which is why entries are written once and left alone.
What happens if we change the checklist template?
Awards already running keep the template as it applied to them. Changes flow to new awards, so history stays intact and nothing is quietly rewritten.
Related

Other parts of the same workspace

ProcureAudit Compliance checklist builder
FEATURE

Compliance checklist builder

Build the template once and every future award inherits it.

Learn more
ProcureAudit Modification tracking
FEATURE

Modification tracking

Why each change carries its own award, documents and progress.

Learn more
ProcureAudit Document drive
FEATURE

Document drive

Where evidence is filed and how versions are retained.

Learn more

Open one of your own awards

Bring a subcontract with a couple of modifications and we will configure the phases live, using your records rather than a sample.

Book a demo