SUPPORT / GETTING STARTED
Prepare for a technology project.
Before project work begins, make the current situation inspectable. This checklist helps you organize the inputs a scoped engagement may need. It is not a request to send every file or grant access before requirements are agreed.
1. Identify the decision owners
Name the person who can approve scope, the people who perform the work and the administrator responsible for each relevant system. Note who will review deliverables and who can resolve conflicting requirements. A single contact may coordinate the work without owning every decision.
2. Gather representative source material
List the current forms, process instructions, data sources and examples that explain the workflow. Note their owners and whether they are current. Use redacted or synthetic sample records for initial review; identify sensitive material without placing it in general email.
3. Record dependencies and unknowns
List the platforms involved, available export options, external approvals and deadlines that may affect delivery. Mark unavailable documentation or uncertain ownership as unresolved. Do not treat a missing answer as an assumed requirement.
4. Plan access rather than sharing passwords
Identify the accounts and permissions that might be required. Agree who authorizes access, the minimum role needed and how access will be removed when the work ends. Use the platform’s supported invitation or access-management process after the requirement is confirmed.
5. Prepare observable review cases
Describe a normal task, an incomplete input and a restricted action. State the expected result for each. For example, a reviewer can approve a complete record, a missing required field blocks progress and an unauthorized user cannot approve. These are illustrative review cases; the project needs its own agreed criteria.
Technology Solutions & Business Services