1. What this release delivers

The Evaluation and Moderation (E&M) Hub is a single home page for evaluators and moderators. It replaces the previous journey of separate emailed links per stage with one place that shows every project a person is involved in, the state of their work on each, and what they need to do next.

The redesign covers four linked areas, each described in its own section below: the Hub landing page and project tracking, a two step Conflict of Interest declaration, a rebuilt Project Evaluation scoring interface, and a matching Project Moderation experience.

The full journey has been rebuilt on Lightning Web Components.

Who this affects

2. What is different for existing evaluators and moderators

Three behaviours have changed for organisations already running evaluations. We recommend briefing evaluation panels before the first tender that uses the Hub.

Moderation now follows evaluation rather than running alongside it

Previously, moderation could be carried out at the same time as evaluation and was controlled section by section, with no explicit start. In the Hub, moderation becomes available only once the evaluation deadline has passed. Until then a moderator sees Assigned to Moderator and cannot begin.

For a moderator who is used to reviewing sections as they are completed, this is the most noticeable change in the release.

Progress is now measured on manually scored requirements only

The percentage shown against an evaluator on the Hub counts only the requirements that person has to score by hand. Auto scored and optional requirements are excluded, so work the system does on their behalf does not read as progress.

The legacy evaluation screens continue to show a different figure that includes auto scored requirements. The two numbers are not expected to match. An evaluator whose sections contain only auto scored requirements will read 100 per cent and Ready to Submit, because they have no manual work to do.

Advancing a procurement stage resets both columns

The Hub always describes the project’s current procurement stage. When a project advances, both deadline fields are cleared, the new stage’s sections have not started evaluation, and both columns return to their waiting states until the new stage is set up. Work on an earlier stage never affects the status shown for the current one.

3. Before you begin

Four setup points determine whether the Hub behaves as described. We suggest working through these with your Atamis contact before the first project goes live on the Hub.

1. Set an Evaluation Deadline on every project, for every stage

The Evaluation Deadline drives three things: the deadline warnings on each row, the point at which evaluation closes, and the point at which moderation opens. It is not yet populated automatically. Until that is delivered, tracked separately as ATA-1355, it must be set by hand.

• A project with no Evaluation Deadline shows no chip and no banner for anyone.
• Evaluation never closes on that project, so moderation never opens and every moderator continues to see Assigned to Moderator.
• Both the Evaluation Deadline and the Moderation Deadline are cleared when a project advances to its next procurement stage, so each stage needs its own dates.

2. Check permission sets before go live

The Hub reads four fields on Procurement Team Member and runs its queries in user mode. A user who cannot read one of those fields receives an error rather than an empty list. The fields are granted in the Atamis Fields (No CRUD) and ProSpend 2.7 Fields permission sets. Organisations using other or customised permission sets should have access reviewed before release.

3. Review team members created outside the user interface

Access to Evaluation Scoring has a default value that is applied by the user interface only. Procurement Team Member records created by data load, integration or migration have no value in that field and are therefore not treated as evaluators, so their projects will not appear on the Hub. If your team memberships were bulk loaded, these should be reviewed.

4. Confirm the install backfill has run

A one off backfill populates the new fields for existing records so that people already part way through an evaluation see their projects. Without it the Hub is empty for anyone mid evaluation. Your Atamis contact will confirm this has completed as part of the upgrade.

4. Hub landing page and project tracking

Overview

The Hub is a single home page where evaluators and moderators find every project they are involved in and see what needs their attention, replacing the previous journey of separate emailed links per stage.

What it does

Projects sit under four tabs, All Projects, To Action, Upcoming and Closed, each with its own live search. Rows are ordered by the project’s evaluation deadline, soonest first, with projects that have no deadline set at the bottom.

Each row carries two independent status buttons, one for evaluation and one for moderation. Both always describe the project’s current procurement stage, so work on an earlier stage never confuses the status of the current one. The full set of states is listed in section 7.

A colour coded chip above the project name flags the deadline that applies to that person: Overdue, Urgent, or Due in a stated number of days. A New Project chip appears for evaluators on a project whose evaluation opened recently and who have not yet scored anything. Projects in the Urgent and Overdue bands also carry a full width banner above the row, which can be dismissed for the current view.

Benefits

Evaluators and moderators get one place to see what needs action, and by when. Deadline warnings are personal to each person’s own outstanding work, so nobody is chased for a stage or a role that is not theirs, and the warning clears once they have finished their part or a contract is awarded.

5. Conflict of Interest declaration

Overview

The first time someone opens a project’s evaluation page, a Conflict of Interest check runs against the suppliers involved in that project. The declaration has been reduced to two steps.

What it does

Step one lists the project’s suppliers for review, shown as an accordion once there are more than six, followed by two mutually exclusive declarations: a confirmation of no conflict of interest, or a declaration of a potential conflict with a rich text field for the details. Any details entered are saved against the team record. Step two confirms the declaration is complete and offers a button to continue straight to the project.

Declaring a conflict does not stop someone from evaluating or moderating. Where an organisation wants a person’s scores excluded, that is done through the existing Omit From Scoring setting on the project team rather than through this screen. Note that omitting someone from scoring also removes the project from their Hub.

Benefits

Conflict declarations are captured consistently and in context, before anyone starts scoring, rather than through a separate process. The shorter two step flow gets evaluators and moderators into their work faster without losing the audit trail.
 

6. Project Evaluation and Project Moderation

Both pages have been rebuilt with the same layout: a navigation tree on the left for moving between lots, sections and requirements, with the requirement detail and scoring on the right.

Project Evaluation

Each requirement carries Evaluate and Documentation tabs. The rationale field can be configured as mandatory and flagged if a user tries to move on without one. A green tick appears against a requirement once both a score and a rationale are saved, and against a section once every requirement within it is complete.

Where lots are involved they sit above sections in the navigation, and the page subtitle shows the user’s exact position, for example L2, S1, R1a. Section weighting is shown as subtext once a section is expanded. Requirements with more than one supporting file show a file list rather than a single preview, and files can be downloaded or opened in a new window. Once every requirement is complete, Submit Evaluation becomes available and asks for confirmation before submitting.

Once evaluation closes, anyone who did any work on it can still open View Responses to look back over what they scored, whether or not they submitted. Anyone who did no work sees Closed.

Project Moderation

The moderation page mirrors the evaluation layout but orders requirements by section only. Editing a score or rationale through the pencil icon saves immediately. The layout adapts for Pass or Fail requirements, for auto scored requirements, and, where the project is configured to show it, for the evaluator average score. Expanding a requirement’s answers orders each evaluator’s response by score, highest first, then by evaluator name. View Supplier Response opens the supplier’s answer in a new window in the same layout used during evaluation.

Moderation becomes available once the evaluation deadline has passed, and it closes as a single project wide event. Once every weighted section at the current stage has been formally finished, every moderator sees Submitted and everyone else sees Closed. Completion is not tracked moderator by moderator, so the record stays consistent regardless of who moderated which section. Sections with no weighting are not counted towards this.

Benefits

Evaluators always know where they stand, because the percentage shown counts only the requirements they must score by hand and describes the current stage alone. Moderators get a faster, larger, auto saving review experience with evaluators’ answers pre ordered by score, so the strongest and weakest responses are easy to compare.

7. Status reference

Each project row carries two status buttons. Each is worked out by taking the conditions in order from the top and stopping at the first one that applies. This section is written to be lifted directly into end user training.

Evaluation column

The evaluation deadline is shown beneath the button on the three states you can act on: Ready to Submit, Start Evaluation and Continue. Where no deadline has been set, nothing is shown.

Moderation column

The moderation deadline is shown beneath the button on the two states you can act on: Submit, and Start Moderation or Continue.

8. Deadline warnings reference

Warnings are worked out per person, not per project. Two people looking at the same row can see different warnings, or one can see none at all.

Which deadline applies to you

No warnings of any kind appear on a project where a contract has been awarded.

Chips and banners

• Working day counts exclude weekends. Public holidays are not excluded.
• A row carries at most one chip.
• Banners can be dismissed, which hides the banner and leaves the chip in place. The dismissal applies to the current view only; the banner returns on refresh, or on changing tab, page or search.

Updated 24 September 2026 08:04