Hi @noorbasha534 ,

To be honest I don't think numOutputRows is is a good candidate. Imaging complex aggregation with multiple jobs and some filtrations on huge dataset. That could return relatively small amount of rows, but the price would be much higher than a job that simply materializes some tables. 

You can apply tags to job, so you have means to pretty accurately attribute cost to specific team/project.

For some inspiration you can check following blogs: 

https://community.databricks.com/t5/technical-blog/queries-for-cost-attribution-using-system-tables/...

https://www.databricks.com/blog/attribute-serverless-costs-departments-and-users-budget-policies

https://medium.com/dbsql-sme-engineering/introducing-granular-cost-monitoring-for-databricks-sql-e7e...