Atlas Integrated Technology
← Discovery StarterILLUSTRATIVE SAMPLE · NOT A CLIENT ENGAGEMENT

A plan you can
build from.

A fictional equipment-request tool shows the shape of a Discovery Starter handoff. This is an abbreviated example, not a working application or a development quote.

01 / PROJECT BRIEF

From email requests
to a clear queue.

The problem
A small team receives equipment requests by email, making ownership and status difficult to follow.
The users
A requester submits a need; a coordinator reviews and updates it.
The primary workflow
Submit a request → review the queue → record a decision → check status.
Success to evaluate
Can a requester submit without assistance? Can the coordinator find pending requests and record a decision? These are proposed evaluation questions, not measured results.
02 / PRIORITIZED SCOPE
  • First releaseRequest form, review queue, decision notes, and status history.
  • LaterEmail notifications, reporting, and configurable approval steps.
  • Outside this scopePurchasing, inventory integration, payments, and mobile store distribution.
03 / ANNOTATED SCREEN CONCEPT
Equipment requestsCoordinator view
1Pending · Approved · Declined
Monitor requestSample request · Pending
2
Keyboard requestSample request · Pending
Review →
3Decision note
Reason for this decision…
ApproveDecline
Static wireframe illustration. Controls are intentionally non-interactive.
  1. Filter by status. Start with work that needs attention.
  2. Review the request. See the item, reason, and request history together.
  3. Record the decision. Require a reason for a decline; preserve the decision in the history.
04 / DELIVERY OUTLINE

Assumptions made visible.

01

Confirm the rules

Validate the two roles, request fields, status transitions, and who can view each record.

02

Build the core flow

Implement the agreed screens, access rules, validation, and decision history.

03

Review and hand off

Check the acceptance criteria with the client and provide operating instructions.

What a build estimate would address

Authentication, hosting, expected usage, accessibility, data retention, and integration needs affect the estimate. A real Discovery Starter handoff includes a build estimate with its assumptions; no price or delivery range is quoted for this fictional example.

Example acceptance criterion: A requester can see the current status of their request, while only the coordinator can record an approval or decline.

Discuss your project ↗