/
Request for Information Template

Request for Information Template

The purpose of this Request for Information template is for customers to provide the essential organisational information/data required to setup a first iteration of a TeamForm Directory.

Minimum data set

Minimum data needed:

  • supervisory structure aka line management structure [source system: HRIS / HRMS such as Workday, SAP Success Factors, Oracle Fusion HCM]

  • cross functional teaming structure [source system: often a spreadsheet]

Information / Data Category

Source and approach

Data needed

Information / Data Category

Source and approach

Data needed

People and supervisory structure

HRIS → integrate with TeamForm (goal)

Minimum:

  • Employee Name (First, Last, Preferred)

  • Employee account name / ID

  • Job title

  • Supervisory Org Name / ID

  • Supervisor / Manager Name / ID

  • FTE (Full Time Equivalent e.g. full time / part time for available 0-1)

  • Email address

Additional useful fields:

  • Employee Band (e.g. rank / level)

  • Employee Avatar / Profile pic

  • Employee Cost Centre

  • Employee Legal Entity / Employer

  • Employee work location (e.g. building, city, country of place of work)

  • Employee type (e.g. employee, contractor, vendor / supplier)

  • Role family or job architecture

  • Employment details (e.g. start / end date)

  • Absence data (e.g. long term leave such as sabbatical / parental leave / military leave)

  • Blended Rate card (e.g. average cost of a person by reporting line by day) [often a Finance provided data set]

Cross-functional Teaming structure

Usually spreadsheets → replace with TeamForm (goal)

Minimum:

  • Teams and team types
    (e.g. squads/crews, missions/domains/tribes)

  • People memberships for each team (employee ID, % FTE allocation to team)

  • Team of Teams / Value Stream Hierarchy (i.e. parent team of each team)

Also useful:

  • Team role aka “Hatted roles” e.g. Product Owner, Scrum Master

  • Team Descriptions / Key Links (backlog / wiki pages)

  • Team cost centre / cost object

  • Additional attributes e.g. IT Asset or product responsibility

  • Team relationships / associations

  • Team design rules / guardrails (e.g. min / max size of team, role composition etc.)

  •  

Work

Delivery system e.g. Jira, ADO, Rally.

  • Work currently open or completed in last 6 months

  • Typically Epics, Programs (not bugs, tasks).

  • Key fields: Key, summary, priority, status, parent, team, assignee, any relevant custom fields (e.g. link to strategic theme / OKR / program)

Capability / Skills

HRIS or Skills Management → integrate with TeamForm

Useful if available:

  • List of skills

  • Skills mapped to individuals

  • Skills with other attributes (E.g. capability or job family)

Additional source systems / data types

  • Contractor information (if not in HRIS). Source System: e.g. Microsoft Entra or spreadsheets

  • Job requisitions / vacancy (e.g. for role approval and hiring status in a team) [Source System: Application Tracking System]

  • Outcomes / Objectives e.g. Goals, OKRs for the organisation and the teams [Source System: Strategy / OKR tooling such as MS Viva Goals, Tability, Workboard, PlanView, Clarity, Jira Align etc.]