Procurement & Estimate Management is a web application for recording procurement requests and preparing the cost estimates that support purchase decisions. The product exists so that a procurement officer, an estimator, and a procurement manager can work from one ordered system of record instead of scattered spreadsheets and messages: requests are recorded, costs are estimated against those requests, and a manager reviews both together before spending is committed and a procurement case is closed.
The audience is a small in-house procurement function. Three distinct roles share the same durable data but do different work on it: the Procurement Officer keeps procurement records current and drives each purchase cycle; the Estimator prepares and submits cost estimates for procurement items; the Procurement Manager reviews records and estimates in one place, approves estimates, controls spending, and closes procurement cases. Each role reaches only the working surface its responsibility requires.
This document is the System Requirements Document for the product named Procurement & Estimate Management. It specifies the current delivery, the three role-scoped working surfaces, the identity entry points, the visual system, and the technical stack.
The product is a first-party, application-owned web application. All working surfaces are custom UI owned by the application, served by a React frontend against a shared FastAPI backend with MariaDB persistence. There is no provider-owned or external-only surface, and no headless delivery.
Access is split into two boundaries:
The three protected surfaces are separated because their working context, authoritative state, lifecycle, and completion outcome differ: the officer authors and advances procurement records; the estimator authors cost estimates bound to procurement items and submits them for decision; the manager reads records and estimates together, approves, and closes cases. Each is an independently resumed responsibility, so each owns its own destination.
Current scope is limited to recording and maintaining procurement records, preparing and submitting cost estimates, and reviewing records with their estimates to approve and close. Nothing beyond that is current.
Removed from scope
Not applicable. No reference directive in this request declares content_source; the reusable design-system skill is a visual/style reference only and supplies no product facts, and its micro-grid content is explicitly removed above.
FR-1 — Public product explanation. As a prospective user I should see a public Landing page that explains what the product does and offers a way to begin, so that I understand the product before any identity check. (explicit; owner: Landing)
FR-2 — Self-service enrollment. As a new user I should complete self-service enrollment so that I can begin protected procurement work. (required_inference; owner: Sign Up)
FR-3 — Returning verification. As a returning user I should verify my identity on Login so that I can resume my protected work. (required_inference; owner: Login)
FR-4 — Role-appropriate access. As a verified user I should reach only the protected surface my role requires, so that each role works in its own context. (required_inference; owner: Login, Sign Up, and the three protected pages)
FR-5 — Record procurement requests. As a Procurement Officer I should create procurement records so that each purchase request is captured in the system. (explicit; owner: Procurement Records)
FR-6 — Keep procurement records current. As a Procurement Officer I should update procurement records and advance their status through the purchase cycle so that each purchase cycle is tracked to completion. (explicit; owner: Procurement Records)
FR-7 — Track procurement progress. As a Procurement Officer I should see the status of every procurement record and whether an estimate is linked, so that I know where each purchase stands. (explicit; owner: Procurement Records)
FR-8 — Prepare cost estimates. As an Estimator I should create cost estimates for procurement items so that purchase decisions are supported by costed figures. (explicit; owner: Estimates)
FR-9 — Submit estimates. As an Estimator I should submit an estimate so that the Procurement Manager can decide on it. (explicit; owner: Estimates)
FR-10 — Revise returned estimates. As an Estimator I should revise an estimate the manager returned and resubmit it so that the estimate can still support the purchase decision. (required_inference; owner: Estimates)
FR-11 — Review records with their estimates. As a Procurement Manager I should view procurement records and their estimates in one place so that I can judge each purchase against its cost. (explicit; owner: Review)
FR-12 — Approve estimates. As a Procurement Manager I should approve a submitted estimate so that spending is authorized. (explicit; owner: Review)
FR-13 — Return estimates with a note. As a Procurement Manager I should return a submitted estimate to the estimator with a note so that the estimator can correct it. (required_inference; owner: Review)
FR-14 — Close procurement cases. As a Procurement Manager I should close a procurement case once its estimate is approved so that spending is controlled and the case is finished. (explicit; owner: Review)
The visual system follows the supplied creative direction: functional clarity after Dieter Rams — exact, calm, trustworthy, with a strict grid and one signal colour.
Mode: Light mode only.
Colour tokens (exact hex, by role):
| Role | Token | Hex |
|---|---|---|
| Page background (warm grey ground) | --bg | #F2EFE9 |
| Surface (ruled panels, table ground) | --surface | #FBFAF7 |
| Primary text / ink | --text | #1C1C1A |
| Primary (rules, wordmark, dark controls) | --primary | #23231F |
| Accent (one action or one status only) | --accent | #E4611B |
| Muted (secondary text, labels) | --muted | #7A756B |
| Hairline rule | --rule | #D8D3C8 |
| Success / approved | --ok | #2F6B3A |
| Warning / returned | --warn | #B07A12 |
| Critical / rejected | --critical | #A32B22 |
The accent #E4611B is reserved: it marks exactly one action per view (the primary submit or confirm) and the active step in the procurement-flow strip. It is never used for decoration.
Typography:
font-variant-numeric: tabular-nums.clamp(40px, 6vw, 88px).Shape language: Rounded rectangles at 6px radius; hairline 1px rules; no shadows. Controls look like honest switches and dials.
Layout: A 12-column modular grid with visible rules. Label and value pairs align in ruled rows. Sections sit on the grid, not in floating cards. At 375px the grid collapses to one column; at 768px to two; at 1280px the full twelve columns apply. All headlines, labels, numbers, and controls wrap or scale with clamp() to stay entirely inside the viewport and their container at 375px, 768px, and 1280px.
Imagery: Diagrammatic line art of parts, crates, and ruled tables. No stock photography and no decorative illustration.
Avoid: gradient blobs and glass panels; blue or indigo primary colours; hover-lift cards in an identical grid; bouncy or decorative animation.
The public entry is a left-aligned hero on the warm-grey ground (#F2EFE9). An oversized ink headline — "Every purchase, costed and checked." — set in Archivo Medium at clamp(40px, 6vw, 88px) fills eight of twelve columns, flush left, with the subline "Record procurement requests and cost estimates in one ordered system." beneath it in IBM Plex Sans at 20px and the single orange "Start now" control below that.
At the right, a ruled diagram panel shows a sample purchase record: aligned label/value rows (reference, item, quantity, requesting officer, status) separated by hairline rules on the #FBFAF7 surface, with numbers in IBM Plex Mono tabular figures and small orange status marks on the active row. The panel is drawn as diagrammatic line art — no photograph, no shadow, no glass.
Below the hero, a three-step procurement-flow strip (Record → Estimate → Review) carries the signal orange bar on the active step, and each section heading is preceded by a small-cap orange label. The whole composition is a single strict grid with visible rules; the only colour event on the page is orange.
Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: flat
Landing Hero Motion Brief
durable_state_required.)prefers-reduced-motion, the hero reveal is suppressed and a usable static arrangement is provided. (explicit design constraint.)docker-compose.yml with three services — frontend, backend, database — with the frontend depending on the backend and the backend depending on the database.page_contract_version=1)#E4611B, reserved for one action or one status per view.
Procurement & Estimate Management
Record procurement requests and cost estimates in one ordered system.
Each purchase passes through the same sequence, and each step is owned by the role responsible for it.
A purchase request is entered once — reference, item, quantity, officer and date raised.
Costs are prepared against that record: line items, unit cost and a tabular total.
Record and estimate are read together, then approved, returned, or closed.
One signal colour marks one active step

Procurement & Estimate Management
Record procurement requests and cost estimates in one ordered system.
Each purchase passes through the same sequence, and each step is owned by the role responsible for it.
A purchase request is entered once — reference, item, quantity, officer and date raised.
Costs are prepared against that record: line items, unit cost and a tabular total.
Record and estimate are read together, then approved, returned, or closed.
One signal colour marks one active step
No comments yet. Be the first!