PROCESS MAP + EDITABLE REQUEST TRACKER

Plan a service-request workflow from intake to closure.

Give every nonemergency request a clear next step, an accountable owner and a checked outcome. Use one workbook to map the process, maintain a current record and practice the handoffs with your team.

Nonemergency planning only

This guide and workbook cannot receive, route or manage actual service requests. Submit real requests through the responsible agency’s official channels. For immediate danger or urgent hazards, follow local emergency instructions and use the appropriate official emergency channel.

Four sheets. No sign-in, email gate, macros or upload. Keep personal information in your approved system, using reference IDs in the workbook.

START WITH ONE SERVICE

Understand the work
before you design the handoff.

A request tracker helps only when the people using it agree on the process behind each row. This resource works for a small service desk, a department or a larger organization coordinating several teams. Begin with one ordinary request category and walk through it with the staff who receive, work on and answer questions about it. On Workflow map, primary and alternate next-step fields let one decision branch to two destinations; link additional decision steps when more branches are needed.

Map what happens today, including phone calls, queues and informal workarounds. Where does the request enter? Who checks jurisdiction and location? Where does it wait? Who explains the result? Keep the resident’s experience alongside the staff process. Digital.gov’s journey-mapping and service-blueprint guidance provides useful ways to examine those complementary perspectives.

Workflow map

Define entry conditions, responsible roles, required information, actions, evidence, next steps and escalation.

Requests

Maintain one current-state row per stable Request ID, with its owner, status, next action, target and outcome.

Activity log

Record offers, acceptance, updates, decisions, closure and reopening. The fourth sheet contains instructions and a separate fictional example.

Screen detail of the actual Cedar Bay staff request queue and assignment fields for a fictional streetlight report.
Related owned request demo with fictional records. The staff queue illustrates assignment and next actions; the workbook records your team’s decisions.

When the process needs a working system.

The workbook helps your team plan and record the handoffs. If you need supported routing, staff queues or a custom implementation, explore government workflow automation and staff tools.

SCOPE & MINIMUM INTAKE

Collect enough to act,
and know when to refer.

  1. Define service boundaries. List the request types, public assets, geography and operating channels the team covers. Name the role that resolves uncertain cases. Write down the official route for urgent reports under agency policy.
  2. Give the request a stable identity. Record a unique Request ID, received date/time and intake channel. Keep this identity when sorting, transferring or reopening a record. A spreadsheet row number is not an ID. A simple convention such as letters, numbers and hyphens works well. Use stable text IDs without the reserved characters ~ * ? = < >; the workbook flags these characters and ignores invalid IDs in lookups.
  3. Describe and locate the issue. Use a short, non-sensitive summary, category and sufficient operational location detail. “Riverside Park” may be too broad; “Riverside Park, table P12” identifies an asset. If location is genuinely irrelevant, record “Not applicable” with a reason.
  4. Check scope and completeness separately. A clear report can still be outside the service boundary. Use Pending, In scope or Out of scope for scope, and Needs information or Ready for completeness. Missing details need a specific question, an owner and a next review.
  5. Keep contact details in an approved system. Use a reference ID in the workbook. Do not add resident names, personal addresses, phone numbers, email addresses, sensitive descriptions, photographs or private correspondence.

Plan an acknowledgement with the request reference, submitted summary and next step. The USWDS “Keep a record” pattern explains why a usable record and relevant reference information matter after a submission.

For an out-of-scope report, record the reason and a verified official referral destination. Explain whether the requester must contact that destination. A referral record does not establish that another organization received, accepted or resolved the issue.

ROUTING & ACCOUNTABILITY

An offered handoff
is not an accepted handoff.

Use category and location to identify a proposed receiving team. Record Handoff offered, Handoff accepted and Handoff declined as different events. The current accountable owner remains responsible until the receiving role explicitly accepts. Sending an email or filling in a proposed department does not transfer accountability.

Define a fallback decision-maker for unclear boundaries, absent staff and declined transfers. If a department rejects the route, preserve the offer, rejection and reason in the log. The current owner follows up, offers the request to the correct team or escalates under the agreed rule.

If you later use routing software, test missing locations, overlapping areas, category changes and reopening. CivicPlus’s SeeClickFix assignment documentation describes product-specific rule ordering and location behavior. This workbook is an original planning aid and performs no automated assignment.

Make status meanings explicit

New
Received and awaiting review. An intake owner remains responsible.
Needs information
Essential details are missing. Record the question, owner and next review.
Assigned
The receiving role has accepted responsibility. Record the acceptance evidence and next action.
In progress
Work has begun. Record meaningful progress and supporting references.
Waiting
A dependency blocks progress. Keep an owner, dependency-specific action and next update due.
Resolved
A proposed result is recorded and awaits verification or closure checks.
Closed
Closure checks are complete. The separate outcome explains how the request ended.
Reopened
New information needs further work. Preserve prior closure history and assign the next action.

Agree allowed transitions locally. A straightforward case may skip Waiting; a declined proposed handoff should not appear as accepted assignment.

WAITING, UPDATES & ESCALATION

Make the next check
a real plan.

Record a concrete next action and a full next-update date/time in the agency’s named timezone. Identify the waiting dependency and the role that will follow up. Apply the agency’s escalation rules rather than inventing a universal service deadline.

Unknown deadlines stay blank and show Target not set. The workbook compares a due value only after you enter an explicit Review date / time and Agency timezone on Guide and example. It then shows “Overdue at review time” or “Not due at review time.” It does not read the current clock, convert timezones, calculate business hours or send reminders.

Refresh the review controls before each review. All dates are local wall-clock values in that named timezone. These checks describe the entered information at that review time; they are not live service-level monitoring. If a target changes, record the old target, new target, reason and responsible role in an activity event.

OUTCOMES & EVIDENCE

Closed tells you the stage.
The outcome tells you the result.

Before closure, check that the outcome matches the evidence and that required resident follow-up is recorded in the approved system. Record the outcome, evidence reference, closure verifier, actual closure date/time and follow-up reference.

  • Completed: the defined work is finished and verified
  • Duplicate: another request covers the same issue; link a different, existing original Request ID
  • Referred out of scope: the boundary decision and verified referral destination are documented
  • Withdrawn: an authorized withdrawal is documented
  • Unable to complete: the reason, decision authority and any next steps are documented

A duplicate cannot reference itself, an unknown ID or another duplicate. Check that both requests concern the same issue. Closing a duplicate does not mean that the original work is complete, and the duplicate’s outcome must remain Duplicate.

If new information reopens the issue, append a Reopened event with its reason, timestamp and evidence reference. Keep the earlier closure event and outcome in history. Set the current status, owner and next action, and clear old closure fields from the current record until the new result is verified. Decide under local policy whether a new occurrence should instead receive a linked, new Request ID.

KEEP THE TWO RECORDS ALIGNED

The workbook records decisions.
Your team carries them out.

  1. Append the event. Give each Activity log row a unique Event ID and matching Request ID. Record timestamp, event type, actor role, previous/retained owner, receiving owner where relevant, old/new status, evidence and a brief note.
  2. Update the current snapshot. Manually update the Requests row and its Last Event ID. The workbook does not apply events automatically or determine which event is latest. Check chronology yourself.
  3. Review the words, not just the colors. Text flags identify missing or ambiguous IDs, missing location or ownership, waiting without a date, incomplete closure, duplicate/referral problems and owner/status differences from the selected event.

The editable log is not a secure audit trail. It does not authenticate actors, enforce permissions, prove actions happened or certify compliance. Use your approved operational system for actual requests, evidence, access controls and retention.

Each working sheet has 200 prepared blank rows, filters, frozen headers, date formatting and dropdowns. The fictional example stays on its own guide sheet. Sort the entire table, including calculated columns; never sort one ID column alone. Extending the prepared range requires updating every linked range, formula, validation and filter. AutoFit or expand row heights to read long notes and every warning. Confirm calculation and date behavior after importing into another spreadsheet app.

FICTIONAL WORKED EXAMPLE

One park table,
from phone call to checked closure.

Cedar Bay, its roles, places and records are invented. This is not a client project, real service request or turnaround promise. All dates below are local wall-clock times in America/New_York. Urgent hazards are outside this routine maintenance example.

Request
CB-R001: worn paint on table P12, Riverside Park
Intake
Telephone, January 11, 2027 at 9:15 a.m.; Service Desk owns the New request
Offer and acceptance
Service Desk offers to Parks Maintenance at 9:30 a.m. and retains ownership. Parks Maintenance accepts at 10 a.m.; status becomes Assigned.
Work and update
In progress on January 12 at 8:30 a.m.; resident update CB-UPDATE-001 recorded at 10 a.m.
Evidence and verification
Refinishing work note CB-WO-014 supports the January 14 Resolved event. Parks supervisor checks the work and final follow-up CB-FOLLOWUP-001.
Final current record
Closed January 15 at 9 a.m.; outcome Completed; owner Parks Maintenance; verifier Parks supervisor; Last Event ID CB-E007

Practice exceptions too: offer to the wrong department and retain the declined route; leave a waiting deadline unknown; close a duplicate against a valid original; then reopen while preserving the earlier closure event. None of those cases should silently become completed work.

WHAT EACH COLUMN MEANS

Field dictionary

Expand a sheet to review its inputs. The workbook’s Guide and example sheet includes the same definitions and dropdown choices. Keep calculated columns intact. ID fields must not contain ~ * ? = < >.

Workflow map inputs (13)
Step ID
Unique stable step ID; keep IDs when sorting.
Stage
Recorded request state for this step.
Entry condition
What must be true before this step begins.
Responsible role
Accountable role, including while a handoff is pending.
Required information
Minimum information needed to perform this step.
Action
Specific work or decision to make.
Completion evidence
Record or observation that demonstrates this step is finished.
Next Step ID
One matching Step ID, or END for a terminal step. Primary destination for the condition in the next column; use the alternate fields for a second branch.
Next-step condition
Decision rule for this transition; a date alone is not acceptance.
Alternate Next Step ID
Optional second destination: one matching Step ID or END. For more branches, link additional decision steps.
Alternate condition
Required when an alternate destination is set; make the two conditions distinct.
Escalation rule
Who reviews an exception and when; use the agency rules.
Resident update
What is communicated, through which approved channel and when.
Requests inputs (21)
Request ID
Unique stable ID for one request; never use the row number as identity.
Received date / time
Local wall-clock receipt time in the agency timezone on Guide and example.
Intake channel
Where the request was received through an approved agency channel.
Category
Agency-defined service category; confirm before routing.
Summary
Brief non-sensitive description of the issue.
Location / asset
Enough location or asset detail to identify the work. Record Not applicable with a reason if appropriate.
Scope
Record jurisdiction/service-scope decision, not a guess.
Completeness
Ready only after the required intake information is present.
Approved-system contact reference
Reference only to contact details in an approved system; no names, phone numbers, email addresses or other PII.
Status
Current record, updated manually with the Activity log. Closed is not necessarily Completed.
Accountable owner
Current accountable role. An offered handoff does not change this owner.
Next action
Concrete next action, including the waiting dependency or reopening work.
Next update due
Agreed local date/time for the next update; blank means Target not set, never on time.
Outcome code
Result of the request, separate from status. Duplicate and referral are not completed work.
Evidence reference
Approved-system work/decision evidence; no private details.
Closure verifier
Responsible role that checked outcome, evidence and follow-up before closure.
Closed date / time
Actual closure time; clear from current record on reopening and preserve prior closure in Activity log.
Original Request ID
For Duplicate only: one existing different Request ID; cannot point to itself or another duplicate.
Referral record
For Referred out of scope: destination, referral reference and instructions in the approved system; referral is not proof of receipt.
Resident follow-up reference
Reference to the final update or documented inability to contact, before closure.
Last Event ID
Manually select the latest relevant Event ID for this request after updating the log; formulas do not choose the latest event.
Activity log inputs (11)
Event ID
Unique stable ID for each event; do not overwrite history.
Request ID
One exact existing Request ID on Requests.
Timestamp
Local wall-clock event time in the agency timezone on Guide and example.
Event type
Offer and acceptance are separate events. The record does not send a handoff.
Actor role
Role recording or authorizing the event; not authenticated by this workbook.
Previous / retained owner
Accountable role before the event; retained unless this event records an accepted handoff.
Receiving owner
Proposed role for an offer; accepted role only for Handoff accepted.
Old status
State before this event. Leave blank only for initial intake.
New status
State after this event; an offer alone should preserve the existing status.
Decision / evidence reference
Approved-system record for acceptance, rejection, escalation, outcome, closure or reopening.
Note
Brief reason and result; preserve wrong-department offers and declines, closure outcome and reopening reason. No PII.

Calculated columns

Review flags appear on all three working sheets. Requests also shows Target check, evaluated against the explicit review controls. Activity log shows Recorded owner after event: Receiving owner only for Handoff accepted; otherwise Previous / retained owner. These are consistency aids based on editable records, not authenticated proof or permission to act.

COMMON QUESTIONS

Before you use the template.

Can one person hold several roles?

Yes. Keep the responsibilities distinct even when one person performs them. Follow local requirements for independent verification or approval.

What if no receiving team accepts?

The current owner remains accountable. Log the unsuccessful handoff, identify the fallback decision-maker and set the next review. The workbook cannot compel acceptance or notify the team.

Does Closed mean the issue was fixed?

Only a verified Completed outcome indicates completion of the defined work. Duplicate, Referred out of scope, Withdrawn and Unable to complete explain other endings. Always read status and outcome together.

Can the file notify staff or residents?

No. It records planning information and manual updates. Use approved operational systems for notifications, correspondence and real requests. This website has no request-submission or file-upload facility.

What happens when a due date is unknown?

Leave it blank. The record shows Target not set. Enter a date only when the responsible team has agreed it, and use the explicit review time and agency timezone before interpreting overdue text.

Is this a CRM, official government template or compliance tool?

No. It is an original Civicfield planning workbook. It does not provide live case management, emergency dispatch, authentication, secure audit history or a compliance guarantee. Review it against your agency’s own process and records requirements.

REFERENCES & RELATED RESOURCES

Use the guide
with your local rules.

The original template draws on general practices described in Digital.gov’s journey and service-blueprint guidance, the USWDS record-keeping pattern and CivicPlus’s product-specific assignment guidance. Those sources do not endorse this workbook or replace agency policy.

Use the website content audit workbook to check the service information residents rely on, and the content calendar workbook to plan reviewed updates. For the website around those services, see our local government website approach and cost and scope guide.

Choose intake fields that support the next action.

Begin with the receiving team’s task, then ask why each field is needed. Separate a resident’s observation from staff classification. A person can describe a damaged sign without knowing its internal asset code. Provide an approved route for incomplete location information rather than forcing an inaccurate answer.

FieldResident-facing purposeStaff or data decision
Issue descriptionExplain what happened in plain languageAvoid requesting sensitive narrative not needed for the task.
Location or asset descriptionHelp staff identify the issueUse address alternatives or a descriptive location where appropriate.
CategorySupport routing when the choice is understandableAllow staff review rather than making the resident settle department boundaries.
PhotoAdd useful context if optional and authorizedSet upload, privacy, access and retention rules before accepting files.
Contact routeEnable approved follow-up when neededExplain purpose; keep personal details in the authorized operational system.
Reference and received timeConfirm receipt and support traceabilityGenerate stable IDs and define the recorded timezone.

Mark required fields with a reason tied to the service. Test labels, errors, confirmation and the assisted route. Follow the service-page pattern for instructions before the form. The workbook’s stable IDs and evidence references support process planning; they do not replace the operational system’s access or privacy controls.

Close duplicates and referrals without claiming completed work.

Fictional examples. CB-R002 reports the same paint damage to park table P12 already recorded under CB-R001. Staff verify that the issue is the same and that CB-R001 exists and is not itself a duplicate. CB-R002 can close with outcome Duplicate and a link to CB-R001, after the required checks. CB-R001 remains open until its own work is verified.

If a report concerns an asset maintained by another organization, record the boundary decision, the verified official referral destination and the requester’s next step. Close with Referred out of scope only when the agency’s closure checks are satisfied. That does not mean the other organization accepted or completed the report.

If the same location develops a new problem after a completed repair, staff decide under local policy whether to reopen the original or create a linked new occurrence. Preserve history either way. Do not send a duplicate into a chain of other duplicates or overwrite Completed with a new event that erases the earlier result.

Use the existing outcome dictionary above. Keep Duplicate, Referred out of scope and Completed separate in reporting, following the metrics guide. Closing administrative records is not the same as completing physical work.

Move social questions into an accountable service route.

A public comment may ask a general question or describe an individual case. The channel monitor first uses the approved agency boundary: give a verified public-information answer when appropriate, direct service work into the approved intake route, and follow the authorized urgent-information process for urgent reports. Do not ask for private details in a public thread.

If policy permits staff-assisted intake, record the request in the authorized system and give the person its reference through an approved channel. Avoid copying sensitive correspondence into the planning workbook. If the resident must submit the request themselves, explain that next action without implying a case has already been accepted.

Name who owns the handoff until the receiving service accepts it. A forwarded message is an offer, not acceptance. The original owner follows up on missing or declined acceptance, and the service owner authorizes the operational response. Keep a public reply concise and suitable for the audience.

The social strategy should state monitoring windows and the approved intake link. Test an ordinary question, a private case detail, an unclear jurisdiction and an absent receiving owner before adopting the process.

A WORKFLOW YOUR TEAM CAN EXPLAIN

Start with one service.
Make every next step clear.

Discuss a process review, clearer intake instructions or a practical digital workflow. Share a public service page and the process you want to improve. Keep actual requests, confidential records and credentials out of your inquiry.

Project inquiries are currently unavailable.

For planning and project discussions. Real public-service requests belong in the responsible agency’s official channels.