Skip to main content
Article summary
This feature is coming soon

Deliverable Logger Guide

Overview​

Who this is for: your job is to make sure every deliverable that goes to the customer is filed in Sprezz, with its proof, on the right date. You usually hold Delivery Ops Coordinator (role key deliverables_ops). On a program's Roles page that seat is titled Program Assistant or Delivery Ops Coordinator. Project Manager / Division Lead (project_manager) can do the same steps. A Unit Lead (read/update) can also file deliverables and record reviews on programs under their unit, but cannot add deliverables.

PageWhat it covers
DeliverablesFind, file, fix, and resolve every kind of deliverable date, with the decision guide
ChecklistsDaily, weekly, monthly, period-end, and audit checklists

Your whole job, in one list​

  • Know what's due: every date coming up in the next two weeks, and anything late.
  • File each deliverable the day it goes out: the file, the delivery email, who it went to, and the date.
  • Record the customer's answer when it comes in, and resubmit after a rejection.
  • Raise anything that changes a date: waivers, extensions, wrong dates, and dates that should not exist. Attach the COR's written answer.
  • Approve teammates' proposals when you are the second person.
  • Mark meetings held, and log the events and requests deliverables count from.

Your first 10 minutes​

  1. Open Delivery > Delivery Calendar. It lists every deliverable due date across the programs you can see.
  2. Open Delivery > Programs and click your program.
  3. Open Delivery Management > Deliverables.
  4. Read Next 14 Days at the top: what's due soon and anything already late.
  5. Set Show to Needs attention. That is your to-do list.

Common Tasks​

All the steps are on Deliverables:

  • finding what's due;
  • filing a deliverable, and resubmitting after a rejection;
  • recording the customer's answer;
  • fixing a filing;
  • proposing a waiver, extension, or not-owed mark;
  • moving a stored date that is simply wrong (Move due date), not a newly agreed contractual date (Propose extension);
  • marking a meeting held;
  • approving someone else's proposal.

Example Workflow​

note

This guide has no screenshots yet. The published deliverables frames show the old Tasks tab, which has been replaced by Deliverables. Screenshots will be added when the contract-model-manual journey is re-run with --publish-docs.

The monthly status report went out by email this morning. You open Deliverables, see it in Next 14 Days as Due today, open the date, and click + Submit. You attach the report and a PDF of the email, leave Submitted on as today, and click Submit.

Workflow Expectations​

File each deliverable the day it goes out. Submitted on decides whether it counts as on time.

What you can't see or do​

You can'tWho does it
Approve your own proposals or editsA second person on the program
Staff the team, create programs, or apply modificationsProgram Lead / Delivery Unit Manager / contracts team
See funding figures (they read Restricted, and Financial may not appear)Program Lead or Finance / EAC Controller
Record review, if your admin removed the verdict permission from your roleProgram Lead

Your role can also keep contacts, companies, periods, potential issues, issues, and documents up to date. The Program Lead Guide has those steps. Do them only when the program lead asks.

Done outside Sprezz today​

  • Sending the deliverable and delivery email to the customer.
  • File-naming standards and the delivery email template.

Who to ask​

  • A deliverable or date that's missing or wrong: the program's Program Lead (listed on Roles).
  • A program you can't open: your Sprezz admin.
In this article