Create As-Is BRD, 3 use Cases
Budget: $10 – $30 USD
I have three distinct use-case narratives that all revolve around system integration work within our HRCM landscape. They need to be captured in a clear, professional Business Requirements Document that describes the current (as-is) state only—no to-be or gap analysis at this stage.
Industry & context
Although the use cases span multiple functions, they are all situated in a Business-Analyst–centric environment and focus squarely on system integration. The systems in play sit inside our HRCM stack, so an understanding of HR tech terminology will help you move quickly.
Source material I will supply
• Written use-case notes and swim-lane diagrams
• Access to SMEs for clarification calls
• Existing data-flow screenshots where available
Your task
1. Read each narrative, interview me or the SMEs as needed, and distil what is happening today.
2. Document actors, data inputs/outputs, triggers, and current pain points in a formal BRD template (you may bring your own or use mine).
3. Package each of the three use cases as a separate section, then combine them into a single, well-structured BRD (Word).
Acceptance criteria
• One consolidated BRD containing three clearly labeled as-is use-case sections
• Consistent formatting, version control header, and table of contents
• Clear traceability between business need, current process steps, and any referenced artefacts
• Language that a mixed audience of developers, QA, and stakeholders can understand without extra explanation
If you have delivered as-is BRDs for integration work—especially around HRCM or similar platforms—let me know. Looking forward to seeing how you would approach this.
Industry & context
Although the use cases span multiple functions, they are all situated in a Business-Analyst–centric environment and focus squarely on system integration. The systems in play sit inside our HRCM stack, so an understanding of HR tech terminology will help you move quickly.
Source material I will supply
• Written use-case notes and swim-lane diagrams
• Access to SMEs for clarification calls
• Existing data-flow screenshots where available
Your task
1. Read each narrative, interview me or the SMEs as needed, and distil what is happening today.
2. Document actors, data inputs/outputs, triggers, and current pain points in a formal BRD template (you may bring your own or use mine).
3. Package each of the three use cases as a separate section, then combine them into a single, well-structured BRD (Word).
Acceptance criteria
• One consolidated BRD containing three clearly labeled as-is use-case sections
• Consistent formatting, version control header, and table of contents
• Clear traceability between business need, current process steps, and any referenced artefacts
• Language that a mixed audience of developers, QA, and stakeholders can understand without extra explanation
If you have delivered as-is BRDs for integration work—especially around HRCM or similar platforms—let me know. Looking forward to seeing how you would approach this.