Article summary
Quality Team Guide
Overview
Who this is for: you keep each program's quality record: customer scores (CPARS and
QASP), the proof that deliverables went out on time to the right people, the approved
changes behind every excused date, subcontractor reviews, and the evidence the monthly
audit is scored against. You usually hold Quality Assurance (internal) (role key
quality_audit). An outside auditor invited for an engagement holds External Auditor
(quality_viewer): read-only, no export, usually with an end date. Adding someone to the
program team as Quality still grants External Auditor today, so an internal QA
person staffed that way gets the same read-only third-party access.
| Page | What it covers |
|---|---|
| Scores | CPARS and QASP entry, extraction proposals, concurrence, get-well issues |
| Deliverable evidence | Checking that every deliverable was filed with proof, on time, to the right people |
| Quality records | Approved changes, subcontractor reviews, potential issues, and issues |
| Audits | Running or supporting the monthly audit and the final audit |
| Checklists | Monthly, quarterly, period-end, audit, and closeout checklists |
Your whole job, in one list
- Record every customer score: each CPARS evaluation when it arrives, and each QASP score every quarter, with the source PDF attached.
- Check deliverable evidence: every filed date has its file and delivery email, the right Sent to, and an honest Submitted on.
- Check every excused date is backed in writing: waivers, extensions, and approved changes carry the CO's or COR's answer.
- Keep the quality records: approved changes and subcontractor reviews are complete. Potential issues and issues are read-and-comment for you.
- Run or support the monthly audit: the program lead or Quality Assurance creates and completes it. You check the evidence it is scored against, resolve corrections assigned to you, and can verify or send back corrections.
- At closeout: confirm every score is on file and every CPARS is complete.
Your first 10 minutes
- Open Delivery > Programs and click your program. You land on Home.
- Read the CPARS / QASP score tile (target 4.0 or higher) and the SDS audit checks passed tile.
- Open Program Health > Quality. It has two tabs: CPARS (opens first) and QASP.
- Open Delivery > Proof & Evidence Board to see, across programs, which dates are on time and which have proof on file.
- Open Program Health > Audits and check this month's audit exists.
Common Tasks
How a deliverable gets resolved
You check that each date ended the right way. Use this table to judge whether the action taken matches what happened.
Every deliverable date in Sprezz ends in one of the ways below. Find the row that matches what actually happened, then use that action and nothing else. Sprezz never emails the customer. You send the deliverable and your delivery email yourself, outside Sprezz, and record here what happened.
| What happened | What you do in Sprezz | Who approves | Customer's part | What the date reads afterwards |
|---|---|---|---|---|
| The deliverable went out | Open the date, click + Submit, attach the file or link, set Submitted on to the day it went out | Nobody | They receive your delivery email, sent outside Sprezz | Awaiting ... review |
| The customer answered | Open the date and click Record review: Approve, Reject, or Comments | Nobody; this needs the verdict permission | Their written answer is the source. Type the reviewer and date | Approved on time, Approved, N days late, or Rejected – resubmit |
| The customer rejected it | Fix it, then click + Submit again. The panel reads Resubmit (attempt N) | Nobody | They review the new version | Awaiting ... review again; the rejected filing stays listed |
| You filed the wrong file, date, or link | Under the submission, click Edit (Propose edit) or Add evidence (Propose evidence) | A second person, not the proposer. No COR | Nothing | Unchanged until approved |
| The COR excused this date in writing | More actions > Propose waiver. If you already have their answer, tick The COR already agreed and attach it | The COR's answer, then a second person | The COR's written agreement (get it outside Sprezz) | Waived by the COR. It no longer counts against on-time |
| The COR agreed to a later date in writing | More actions > Propose extension, with the New due date | The COR's answer, then a second person | The COR's written agreement | Re-dated. Dates that follow it move too |
| The due date in Sprezz is simply wrong | More actions > Move due date, with Why it moved. Not offered on a date that counts from an event; use Propose extension. | Nobody: it takes effect at once | Nothing | Re-dated. Use with care: it changes what counts as on time |
| The date should never have existed (a duplicate, or the contract never required it) | More actions > Mark not owed (date should not exist) | A second person. No COR | Nothing | Not owed (never required). This is not a waiver |
| Someone added the date by hand by mistake | More actions > Remove date | Nobody | Nothing | The date is gone |
| Another team owes this deliverable under its SOW | Delivery Management > Teams, open the team, Handle an award deliverable, set Handling here to Routed and pick Routed to | Nobody | Nothing | No dates for this team. The other team files it, and you see it under Routed by your SOW |
| This team's SOW says it doesn't owe it | Same panel, set Handling here to Not owed and pick a reason | Nobody | Nothing | No dates for this team |
| The CO or COR approved a change to how you deliver (a waiver or tailoring, once called a deviation) | Delivery Management > Approved Changes > New Waiver or Tailoring. Then, from the record's details, click Move the date to ..., Propose waiving this date, or Apply as a team rule... | Saving it as Approved needs an Approval contact | Their written approval, attached to the record | Nothing changes until you take one of those three steps. The record alone never moves a date |
| A meeting or milestone was held | Open the date and click Mark held | Nobody; there is no review | They attended | Held on (date). A milestone never counts as late |
| An event that starts a clock happened, or the government asked for an on-request deliverable | Log event, or Log government request on the deliverable | Nobody | The request itself | Dates that count from it are set |
What counts toward on-time. On-time delivery (this period) counts dates that were approved on time, against those approved late plus those late with nothing filed. Waived, not-owed, awaiting-review, rejected, and milestone dates are left out.
Sprezz can show Approved (review window lapsed), but nothing records that outcome today: Record review offers only Approve, Reject, and Comments, and there is no review-window setting. If a customer's review window lapses, record what the contract says happened with Record review and explain it in Notes.
Example Workflow
This guide has no screenshots yet. The Quality page now uses a fiscal-quarter picker and
a proposal review panel that the published journey frames predate. Screenshots will be added
when the quality journeys are re-run with --publish-docs.
The quarter has closed and the COR's surveillance report has arrived. You record it under QASP from the PDF. Then you open the Proof & Evidence Board for the program and find two dates approved with no proof on file. You ask the program assistant to add the files with Add evidence, and a second person approves the additions.
Workflow Expectations
See Checklists for the full rhythm.
What you can't see or do
| You can't | Who does it |
|---|---|
| Log potential issues or issues | Program Lead or Delivery Ops Coordinator |
| Record the customer's verdict on a deliverable (Record review) | Program Lead, Delivery Ops Coordinator, or anyone holding the verdict permission |
| Submit deliverables or propose waivers, extensions, or not-owed marks | The delivery roles |
| Staff a team or create a program | Program Lead / Delivery Unit Manager |
| Change the standard audit checklist (Audit Templates) | An administrator with company settings access |
| Write anything, if you hold External Auditor | Ask for Quality Assurance (internal) |
If your view is masked, scores, narratives, and the attached PDF read Restricted, and the score tile shows a neutral state.
Done outside Sprezz today
- Responding to a CPARS on the government's CPARS site. Record the concurrence status here.
- Internal peer reviews of deliverables before they go out.
- The final audit itself, after closeout.
Who to ask
- Audit runs, verdicts, the team: the program's Program Lead.
- Access: your Sprezz admin.
Go deeper: QASP, CPARS, Audits and Self-Assessments, Role Responsibilities Matrix.