Internal reference · Checkout procurement system

Checkout Role Guide

A walkthrough of every role in the Checkout procurement app — what each person sees, what they can do, and how a request moves from a blank draft to a box on a lab bench.

→

Sign in at checkout.umd.edu with your own UMD account. Every role below — Requester, Approver, Purchaser, Receiver, Unit Manager — is a permission level on one login system, not a separate account; what you can do is determined by the role(s) attached to your UMD identity.

The role sections below describe what each screen looks like in use; any names or amounts shown are illustrative example data, not real accounts.

Getting access

What a brand-new login sees before any role is attached to it.

Logging in with no unit assigned skips the Dashboard entirely and drops the user into a four-step Request Access wizard: Unit (search by lab, group, center, or school) → Justify (a sentence on why) → Approver (pre-suggested, editable) → Review (per-field Edit links, a "Routes to [name] for approval" note, then Submit). Submitting leaves them on a plain "Request Submitted" holding screen — there's nothing else to do until it's decided.

On the approver's side, a separate Pending Access Requests section sits above the regular Pending Approvals queue, with the same one-tap thumbs — no comment required, unlike approving a purchase. Once approved, the requester's next login goes straight to the standard role dashboard; no separate signup step.

Core concepts

The vocabulary every role shares. Worth reading once before the role-by-role sections below.

Unit
The org node a request is charged against, e.g. Aerospace Engineering. Units nest under a school — Clark School → Alfred Gessow Rotorcraft Center / Advanced Propulsion Research Laboratory / Aerospace Engineering — and drive which projects, worktags, and approvers show up downstream.
Project
A named initiative within a unit that requests roll up to for reporting. e.g. "Terrapin Rocket Team", "REEACH Pressurized Test Rig", "Autonomous Ground Vehicle Lab".
Worktag
The financial account string charged for a line item. e.g. CC10453 — set per line, defaults to "Default Account."
Spend Category
The budget classification for a line item. e.g. SC00261, "Supplies – Laboratory" — set per line, defaults to "Default Spend Category."
Supplier
A connected vendor catalog searchable while adding items. McMaster-Carr, Amazon.com Inc., Grainger, Digikey, Office Depot, Fisher Scientific, United Refrigeration, The Widget Co., Custom Lux PCs, and Send Cut Send all appeared during testing.
REQ-YYYY-####
A Request — the requester-authored ask. One request can carry many line items across different worktags and spend categories.
PO-YYYY-#####
A Purchase Order — what a Purchaser issues once lines are approved. A single PO can bundle lines from more than one request going to the same supplier.
REQ-####-##
A single line item, tracked end-to-end — it carries its own approval state, its own PO, and its own receiving record. e.g. REQ-2027-0013-04.
RQ

Requester

Starts a request and tracks it to delivery
DashboardRequestCatalog

Dashboard

Four live tiles — Pending Approvals, Awaiting Purchase, Awaiting Receipt, Needs Attention — followed by a Drafts shelf of unsubmitted requests and an Active Requests feed. Each active request is a card: status pill, project, unit, submitted date, cost, and its full line-item table right there in the feed.

Submitting a request

  1. Pick a Unit under "New procurement request for" — this scopes every Project offered later in the form.
  2. Write the Purpose of request (a justification is required) and, optionally, a Needed By date and a Documentation attachment.
  3. Choose a Project, or open New Project to create one inline without leaving the form.
  4. Add Item: search the connected supplier catalogs by name or SKU — results came back instantly against McMaster-Carr in testing — or add a one-off via New Product. Set Quantity, Est. Price, Worktag, Spend Category, and an optional comment; the running Total Estimated Cost updates as items are added.
  5. Choose the Next Approver and Submit Request — or Save Draft to keep working later. The form autosaves in the background regardless ("Saved less than a minute ago").

Requests list & detail

The Request nav item opens a searchable, sortable table filtered by All / Active / Completed / Denied. Opening a request shows a four-stage status tracker (Pending Approval → Approved → Purchased → Received), the business justification, per-line approval state, and an Approval Routing timeline naming who signed off and when.

Catalog

Read access to shared reference tables — Suppliers, Products, Projects, Accounts, Spend Categories — each searchable with a View drill-in.

AP

Approver

Signs off on requests before they can be purchased
DashboardApproveCatalog

Dashboard

A Pending Approvals queue with a live count badge. Every card shows the requester, project, total cost, and the full line-item table inline — no click-through needed to see what's being asked for — plus one-tap Approve and Deny actions that decide the whole request at once.

Approve / deny

Approve opens a small modal that requires a Comment before it confirms. Deny requires a comment too, plus a categorized Reason — grouped headings like Demand Change (No Longer Needed, Project Cancelled) and Process Error (Duplicate Order, Wrong Vendor Selected) — so denials come back to the requester with a structured reason, not just free text.

Line-item vetoes

Clicking the request itself (its REQ number, not the thumbs) opens a dedicated approval screen for it, with an on/off toggle next to every line. Switching a line off recalculates a running Approved Cost against the original Requested Cost in real time. Clicking Approve then approves the request for whatever's still switched on — as long as at least one line remains on, the request moves forward rather than being denied; the switched-off line just drops out of that cost and shows a distinct status marker on the requester's side. Two more actions live alongside Approve/Deny here: Push and Hold.

Approve page

The same queue as a full table, with Pending / Approved / Denied / All tabs and search — useful for finding something already decided.

Catalog

Identical read-only reference tables to the Requester view.

PU

Purchaser

Turns an approved request into an issued PO
DashboardProcureCatalog

Dashboard

A Pending Purchases queue of approved requests awaiting a purchase order, flagging any that are past their need-by date.

PO detail

Each PO carries the business need, requestor, and the request it came from, an editable per-line Price, and a purchasing block: Payment Method (University P-Card, Purchase Order, or Direct Payment), a Purchasing Card picker, Internal and External Reference Codes, Shipping Method (grouped by real carrier — DHL Express, FedEx, and others), Shipping Cost, and an ETA, all rolling up to a Final Amount. Actions are Purchased, Place On Hold, and Cancel PO, alongside a receipt/document upload and Internal / External print views for the PO itself.

Note: the Purchasing Card field stays disabled until cards are configured for a unit — until then, University P-Card works as the payment method with no specific card attached.

Procure page

The full PO lifecycle as tabs: Pending / Open / Partial / Closed / Cancelled / All.

Catalog

Same reference tables as the other roles.

RC

Receiver

Logs what actually arrived, line by line
DashboardReceiveCatalog

Dashboard

A Receive Items grid with one card per line item still in transit — product, supplier, requestor, unit, and an overdue flag — filterable with a live search box.

Receiving an item

Opening a line shows its product, SKU/ASIN, quantity, item cost, and total cost, then a small form: Qty, Pass, Fail, and a Received timestamp. Splitting pass/fail counts means a partially-damaged shipment is recorded as a partial receipt rather than an all-or-nothing checkbox. Below the form sits a full chain of custody for the line — linked Request, PO, Supplier, Shipping Method, Requestor, Approver, and, once logged, Receiver.

Receive page

Tabs for Open / Partial / Closed / All, listing every line item across every open PO.

Catalog

Same reference tables as the other roles.

UM

Unit Manager

Oversight across every stage, plus admin
DashboardRequestApproveProcureReceiveCatalogManage

This is the one account that carries every other role's nav item at once, scoped to a Unit picker rather than to a single queue.

Dashboard — Table view

Four KPI tiles set the scale of what's in flight: Pending Approvals ($ awaiting sign-off), Open Purchase Orders ($ committed), Awaiting Receipt (shipments in transit), and Needs Attention (on hold or past need-by). Below them, one sortable, filterable table spans every request and PO regardless of stage.

Dashboard — Board view

The same data as a "Procure-to-Receive Board": Kanban columns for Draft, Pending Approval, PO Issued, Awaiting Receipt, and Received · Closed, each column headed with a running count and dollar total — the clearest single view of where money is stuck in the pipeline.

Manage

Four admin panels:

  • Users — directory of every account (name, email, unit) with a New User action.
  • Units — the org hierarchy (Clark School, Alfred Gessow Rotorcraft Center, Advanced Propulsion Research Laboratory, Aerospace Engineering) with a New Unit action.
  • Access — a Grant Admin Access button per unit.
  • Announcements — title, status, priority, publish date, and org-unit scoping, with a New Announcement action; two announcements ("Fall Semester", "Pool Party") existed in the seed data.

Note: Users and Units render read-only for the Unit Manager role by design — their rows are visible but the panels won't expand for editing — while Access and Announcements are fully interactive. Full user/unit administration is reserved for a higher admin tier.

End-to-end lifecycle

The same line item, moving through every role that touched it during this walkthrough.

Draft DRAFT-087 Pending Approval REQ-2027-0035 Approved REQ-2027-0034 PO Issued PO-2027-00010 Awaiting Receipt PO-2027-00021 Received · Closed REQ-2027-0013-04 Requester Requester Approver Purchaser Purchaser Receiver

Two exits branch off this main line: a Pending Approval can be Denied back to the requester instead of approved, and an issued PO can be Placed On Hold or Cancelled before it ships.