Every project reports differently. Some want the day by subcontractor, some by area, some in the order it happened, and some in the company's own format. But the diary summary came back with the same headings on every project, so compilers ended up reworking it by hand. Now, with Diary Recipes, the summary comes back in the format your project needs.

Write it once, in plain words

A recipe tells the diary summary how to lay out your day: the headings, the order, how it's grouped, and which content to include. Write it once, set it as the default in your Diary Settings, and every summary follows it. Happy with your summaries as they are? Nothing changes unless you choose a recipe.

Make it work for your project

Write a recipe the way you'd brief a colleague. A few ideas to get you started:

• Reviewing subcontractors? "Group the summary by subcontractor. List progress first, then delays with the reason, then labour and plant."

• Running night shifts? "List everything in the order it happened, with the time it was captured."

• Building a commercial record? "Start with delays and disruptions, with the cause and the work affected."

Set it up once, and the summary comes back in a format your team will read, whether that's at tomorrow's coordination meeting or when a claim lands.

Find Recipes in the Diary left panel. For more on writing a recipe that works the same way every day, head to the Diary Recipes help docs.

What else has shipped