We need help analyzing a procurement process to identify inefficiencies and recommend practical improvements. The work includes reviewing current workflows, clarifying decision points, and creating a new scoring model in Excel to support better vendor evaluation. You need to understand normalization, weighted averages, XLOOKUP, etc and you will also develop forms, templates, and workflow documentation to standardize the process and improve overall efficiency. The ideal person can assess existing procedures, identify bottlenecks, and deliver clear recommendations for a more effective procurement process.

This is a part-time, project-based employee role. Anticipate 1 week initially, 15-30 hours; with additional hours 5-20 approximately to refine and finalize the documents and models.

Engagement details

Role type

Part-time, project-based contract

Duration

This is short-term, 1 week immediately needed with an estimate of 15-30 hours and then refinement hours needed appx 2-3 weeks later.

Location

Hybrid - with a potential 1 meeting in person

Reports to

Schenae Rourk, President and CEO

Rate

Depending on years of exemplary experience in this area of expertise

Schedule

Start work at 8:30am pst -

Part-time, project-based engagement. You will work with the team to understand the defined business problem, clarify what is needed, and turn that need into clear requirements, process improvements, and deliverables that can be implemented as part of an efficient and clear procurement process.

This is not a full-time staff role.

• Discovery: Meet with stakeholders to understand the problem, goals, constraints, and what success looks like.

• Analysis: Review current processes, data, and systems to find where work breaks down, slows down, or costs more than it should.

• Requirements: Document clear, prioritised requirements — business requirements, user stories, acceptance criteria, or a vendor brief, as the project needs.

• Process mapping: Map current-state and future-state workflows and identify practical improvements.

• Bridge business and delivery: Translate business goals for technical or vendor teams, and translate technical constraints and trade-offs back for business stakeholders.

• Options and recommendation: Compare options where relevant, with costs, risks, and effort, and make a clear recommendation.

• Validation: Support testing/user acceptance testing (UAT), confirm the solution meets the requirements, and help measure the result.

• Communication: Provide brief written updates on progress, decisions, open questions, and risks for the agreed check-in cadence.

Deliverables

• Deliverables will be confirmed at the start of the project.

• Written document on current state and future state process mapping

• Report review and edits

• Forms - new and concise

• Templates

• Review of proposal language and contract language

• Scoring model

• Dashboard or reporting specification if needed

• Training presentation so the work can be maintained after the project ends

Required qualifications

• Experience as a Business Analyst or in a closely related role (operations, product, project, or data analysis).

• Proven ability to elicit and document requirements from non-technical stakeholders and convey technical application to laymen.

• Strong analytical skills — comfortable working with data, spreadsheets, and process flows.

• Clear written communication: concise documents that others can act on without a follow-up meeting.

• Ability to work independently on a part-time schedule, manage your own time, and meet agreed deadlines.

Preferred qualifications

• Experience with procurement processes; public agency experience preferred

• Experience supporting a system implementation, selection, or migration.

Skills and tools

• You do not need every tool listed. Edit this list to the tools this project actually uses:

• Documentation: Microsoft Word / Google Docs, SharePoint, PowerPoint and/or Canva

• Data and reporting: Excel / Google Sheets

• Process mapping:

• • Communication: [Slack / Teams / Zoom] and regular written status updates

What success looks like

• Stakeholders agree on a clear, written definition of the problem and the requirements.

• Deliverables are completed on the agreed schedule and are usable without rework.

• Recommendations are practical, costed where relevant, and tied to the original business goal.

• Any risks, gaps, or decisions needed are raised early — not at the deadline.

A company that works with public agencies, nonprofits, and large firms. We design, manage, and implement business and community programs. Our mission is to create livelihoods for those who are underrepresented and marginalized, yet just as qualified, and we do this through the programs that we design, manage, and implement.

RedwoodResources.net