Modeling a approval process in a graph database? -

i have approval process need model graph , wondering how best it. itself, approval process not make sense model graph, connected bunch of other data does, goal put data in same place.

here in megacorp have bunch of reports need out door in 5 weeks , each need approved boss a, boss b, boss c , big boss. each boss should have report 1 week.

i need able answer questions like:

• which reports in approval process now?
• which reports late now?
• which boss caused delay last year?
• how many reports got out door in allotted time last quarter?

if helps, never particularly large dataset.

how should model such approval process in graph database?

graph database should used if have highly connected data particularly large datasets.

for problem graph databases can used overkill if not hoping use recommendation engine or other highly active graph traversing.

i think problem can modelled in traditional rdbms database , easy maintain.