# Build a maintained handbook and request desk

Serve two distinct jobs: help employees find instructions and help operators
maintain guidance and fulfill requests. Connect those jobs through shared records
without forcing every visitor through an operational dashboard.

## Compose the handbook home

Give the home a recognizable identity, a concise purpose, and an index organized
around what employees need to do. Use a relevant cover and a restrained accent
palette to establish that identity; use meaningful colored page icons throughout links and mentions.
Group routes such as joining, buying, and delivering with short section headings.
Use color and spacing to distinguish sections without repeating the same callout
for every item. Each route opens an existing, complete procedure.

Place a browsable guidance library prominently. Use gallery cards to surface a
procedure's purpose or area and review state, with readable titles and enough
context to choose a route. Keep cards compact enough that useful guidance is
visible on arrival. Use text previews or relevant original assets, never invented
asset previews. Provide clear navigation to the request desk and maintenance view.

Separate surfaces with native page tabs or durable child destinations:

- **Procedures:** reader-facing routes and guidance cards.
- **Owners & reviews:** a table showing procedure, area, steward, review
  state, and review date supported by evidence. Make ownership and stale
  guidance easy to scan.
- **Requests:** actionable requests with title, status, coordinator, and due
  date. Offer open and completed views; preserve undated and unassigned work.

Choose a request table or list for the actual workflow. Keep important dates and
responsibility visible, and put detailed next steps inside the request. Use full
width and deliberate column widths, wrapped text, and property visibility to
make the work readable. Keep all three surfaces on the same underlying records.
For a brief chiefly about tracking requests, lead with the request desk rather
than constructing an unnecessary directory.

## Write complete procedure and request records

Give procedures visible stewardship and review state. Explain when to use them,
inputs, ordered steps, exceptions, escalation, and the result that counts as done.
Keep proposed guidance visibly distinct from approved policy. Do not invent a
policy threshold, approver, review date, or real person assignment.

Describe each request's actual need, next action or blocker, and related procedure.
Use native relations to connect requests to reusable guidance. Add return routes
to the library and request desk. Make onboarding a route through real procedures;
track individual onboarding work separately only when that execution needs it.

## Configure the visual details

Set page width and column balance for the content. Configure record layouts so
operational metadata stays near the title and secondary details remain accessible.
Choose meaningful icons for handbook, procedure, request, and contact pages. Use
section backgrounds and status colors consistently, and keep duplicate database
titles out of the reading flow. Keep long reference material in detail pages.

Build actual inline views in working tabs; reserve links to full-page sources for
navigation. Preserve existing records and relationships when rearranging the
home. Read the saved hierarchy after composition changes and confirm that
sections, tabs, and views retained the intended order.

## Inspect the finished system

Enter as a first-time employee: find a relevant procedure, read useful steps,
and return home. Then enter as an operator: find an open request, identify who
acts next and when, and follow its relation to the procedure. Switch to completed
work and verify that records remain accessible.

Inspect the home, library, maintenance table, request desk, and representative
records at desktop and narrow widths. Check legible card titles, complete dates,
visible ownership and review state, and usable first-screen navigation. Compare
hierarchy and density with the intended design. Record incomplete features and
unverified checks separately; a functioning queue alone is not a design pass.
