The Timberline system#

Timberline Harvest Co. is Reportworq's own worked example: a complete, working deployment built on one fictitious company, used for demos, enablement, testing and marketing. If you want to see what Reportworq actually does rather than read about it, this is where you look.

Start here: the order that makes sense#

If you are opening Timberline for the first time, go in this order. Each step builds on the last.

1. What Timberline is: the company, the four layers, and what is actually in the workspace. Ten minutes.
2. Signing in, and who to be: the ten accounts, what each one sees, and how to read what a recipient received without signing in at all.
3. Where the files live: the workbooks behind every report, and the one rule that keeps you from breaking a job.
4. Open the Financial Statements job first, ahead of the more eye-catching board decks. It is the most straightforward example of how a source file and a job fit together, and everything else in the catalog is a variation on that shape. See it in the report catalog.
5. Then read the rest of the report catalog and follow whichever task guide matches what you are trying to do.

Run reports#

Collect data back#

AI and integrations#

What people always miss#

Worth reading before anything else. Two mistakes come up again and again:

1. Setting up parameters the wrong way, or on the wrong sheet. A parameter maps to one cell per worksheet, and getting the mapping right per tab is where people go wrong. See How parameters work.
2. Hand-maintaining recipients instead of automating them. In her words: pull the contact information into your source file and use cell values or named ranges to get the Email To and CC right, dynamically sourced from your source system where possible, rather than controlling it manually in Reportworq via the bursting screen. Every Timberline job does it this way. See What bursting looks like.

And three more that catch people out:

3. The email is the deliverable. Timberline's jobs do not send "please find attached", they build a readable dashboard in the message body. Open the demo inbox before you open an attachment.
4. Nothing escapes the box. Email runs in demo-inbox mode, so a demo run cannot mail a real person. Check that before you run anything on a shared environment.
5. Jobs bind to named ranges, not cells. Rename a range in a workbook and the job breaks at run time, silently. See Where the files live.
6. The three board-deck jobs are deliberately similar. They differ in replication, and reading them side by side is the fastest way to understand parameters.

A note on what you are reading#

Timberline is a worked example, not a product feature. Everything in it was built with the same screens you have. Where this guide says "the demo does X", you can do X the same way in your own workspace, and the point of each page is the transferable pattern rather than the demo itself.